Context
Organization, workflow, population, period, owner, and baseline.
Proof
A complete case names the prior workflow, eligible population, AI and navigator actions, returned work, comparison, and limitations.
A credible case connects prior state, performed work, result, comparison, and limits.
A customer story does not turn association into causation.
Read the path around the number. A credible case connects prior state, performed work, result, comparison, and limits. The diagram shows Prior workflow, Population and period, Work performed, Measured result, Comparator or baseline, Limits and permission. A customer story does not turn association into causation.
Case template
The outcome means little if the operation and limits are missing.
Organization, workflow, population, period, owner, and baseline.
What AI, navigators, and the customer's licensed team each owned.
Measure, source, method, comparison, limitation, and evidence label.
What changed for the people doing the work, not only the reported rate.
Program context
A result stays attached to its program type and workflow. It is not carried onto an unrelated page as portfolio-wide proof.
| Program type | What it covers |
|---|---|
| Multi-hospital post-discharge program | Follow-up after inpatient discharge across more than one hospital inside the same organization. |
| Hospital after-hours call program | Inbound calls outside staffed hours, with a defined routing path and a defined fallback. |
| Hospital-owned ambulatory clinic | An outpatient clinic operated by a hospital or health system. |
| Regional health-plan care-gap program | Member outreach against a defined quality or care-gap measure. |
Reviewers can inspect the full case record for the workflow they are evaluating under NDA.
The approved AI actions, the nonclinical work a navigator accepted when included, and every item returned to the customer team.
Completed, closed with a defined reason, or handed to a named owner who accepted it. Escalation alone is not closure.
The comparison design, missing fields, and attribution boundary travel with the result instead of disappearing into a footnote.
Under NDA, inspect the population, actions, reconciliation, comparison, and limits for the workflow you are evaluating.