A discharge plan is a starting point, not proof of completion
A patient is discharged with a clear plan: a specialist needs to see them, home health needs to begin, and a prescription may require follow-up. The hospital has documented the next steps. The referral has been sent. From the sending team's perspective, the handoff may look complete.
But someone still needs to answer a different question: what actually happened next?
An order sent to an outside organization is not necessarily an order accepted. An accepted home-health referral is not a first visit. A specialist appointment scheduled is not a specialist visit completed. Each stage is useful, but each proves something different.
This distinction matters to accountable care organizations (ACOs), health systems, and the people coordinating care across organizational boundaries. Their work does not stop when information leaves one system. It continues until someone can establish whether the intended next step occurred, or why it did not.
Where ownership gets lost
Consider an illustrative home-health workflow. A patient is discharged with an order for home-health services. The discharge team sends a referral to an agency. The agency receives the request but cannot proceed because a required document is missing.
The hospital's system may show the referral as sent. The agency may show it as pending. The care coordinator may believe the request is being handled. Meanwhile, the patient and family may still be waiting for the first visit.
No individual has to make an obvious mistake for this process to stall. Each organization can perform its assigned part and still leave a gap between the handoff and the outcome.
The operating question is not simply which team sent the request. It is who has accepted responsibility for the next action, who can address a blocker, and how the parties will know when the first visit has actually occurred.
A home-health handoff, step by step
A useful way to examine the workflow is to separate the operational states rather than collapse them into one completion label.
These states are an illustrative operating model, not a prescribed universal home-health protocol. Different organizations, payers and workflows have different requirements.
The important distinction is the evidence standard. A transmission receipt can confirm delivery of a referral. An acceptance record can confirm organizational agreement. Neither, by itself, establishes that a clinician visited the patient.
What should happen when something is missing?
Missing documents are not rare edge cases in cross-organization work. They are a normal reason an otherwise reasonable plan can stop moving.
When an agency requests missing information, a reliable workflow should answer four questions. Who is authorized to obtain or provide the document? Who is responsible for acting? When should the issue be escalated? And what record will demonstrate that the blocker was resolved?
Without these answers, a work item may bounce among a hospital unit, an agency intake team, a patient or caregiver, and a care coordinator. Everyone can see pieces of the situation, yet no one has a dependable view of the entire handoff.
The goal is not to automate every clinical judgment or move every task to one centralized team. It is to make the next action, the permission boundary, and the escalation path explicit.
Define the evidence before calling a task complete
Completion should be defined from the beginning of the workflow. What would count as proof that the requested outcome occurred?
For a home-health start of care, that might be an appropriate visit-confirmation record from the responsible provider. For a specialist referral, it might be evidence of an attended encounter, not merely an appointment booking. For a medication-access workflow, an approval or authorization may still fall short of evidence that the medication was obtained.
The precise evidence must fit the clinical, operational, privacy and contractual requirements of the organization. More documentation is not automatically better. Teams need the minimum reliable proof appropriate to the decision.
A useful exception state matters just as much as a completed state. If the visit cannot occur, the record should show what prevented it, who owns the decision, and what alternative or escalation was accepted.
Questions ACO and care-transition leaders can ask today
Before introducing another dashboard or automation tool, choose one common handoff and walk it from the originating order to the final outcome.
These questions create a practical basis for evaluating the workflow without assuming any particular vendor, technology or cost-saving figure.
Where governed AI execution fits
Workflow technology can help organize authorized next actions, route exceptions, request human review and keep matching evidence attached to the correct case. It should not silently invent completion, act outside delegated permissions, or treat an unrelated document as proof that the intended result occurred.
At Marqi Medical, ELLA (Execution Lifecycle & Longitudinal Accountability) is being developed around this distinction: an approved next step is not the same as a verified resolution.
Our public ELLA demonstration illustrates how a stalled specialist-referral workflow can be tracked through ownership, a blocker, escalation and matching proof. The examples use synthetic data; they do not establish a clinical-outcome improvement or imply a live EHR integration.
The next question after every discharge plan
A care plan can be clinically sound and still depend on follow-through that happens outside the originating team's immediate view. Better transitions require more than an instruction to the next organization. They require clear ownership, a way to recover from exceptions, and evidence that the intended next step occurred.
When the plan is handed off, the question worth asking is simple: who owns what happens next, and how will we know?