Ask whether the connection already exists
Hospital discharge, receiving-practice acceptance and follow-up completion may already be connected reliably. Public data cannot establish whether they are connected at a particular organization. Ask the operational owner how confirmation works today, what information crosses organizational boundaries and how an unresolved handoff is picked up. A documented, reliable process is a useful answer; it does not need a new product.
A referral can be transmitted correctly and still remain operationally unresolved when no shared record shows who accepted ownership, what evidence is missing or when a person must intervene.
An EHR can be the authoritative clinical record without being the complete record of a job that crosses scheduling, outreach, external providers, payers and human work queues. That is not a criticism of the EHR. It is a boundary question.
A system can be authoritative for its records and still be one participant in a larger execution job.
A referral sent is not yet a referral accepted
Synthetic scenario—not a patient record or a reported customer outcome. A discharge team sends a follow-up referral. The receiving practice has not accepted it. The sending system correctly records transmission, while the coordinator still needs to establish who owns the open request and what happens if acceptance does not arrive.
The first discovery question is whether existing EHR, referral and scheduling capabilities already provide that shared state. If they do, preserve and use them. Where external participation or local configuration leaves a gap, an adjacent execution record can reference the original receipt and keep the unresolved obligation visible.
| Evidence already available | Remaining operating question |
|---|---|
| Referral transmission receipt | Has a receiving party accepted responsibility? |
| Requested follow-up window | Who sets and reviews the applicable deadline? |
| Message delivered | Is further communication needed, and who owns it? |
| Appointment arranged | Does this close scheduling only, or is attendance a separate obligation? |
The proposed benefit is fewer ambiguous handoffs and less repeated checking. The team must measure that benefit against its existing process. Adding another queue without removing rework would be a poor result. Article 3 follows the same synthetic referral into an explicit execution record.
The 30-day transition has a different shape
A heart-failure transition begins with clinical facts and discharge obligations, but its execution may continue through appointment availability, medication access, outreach attempts, accepted referrals, external-provider responses and exception resolution. Each participant sees a valid portion. The job needs a way to preserve the state between those portions.
| Authority | What it should continue to own | What the cross-system job still needs |
|---|---|---|
| EHR | Patient chart, orders, clinical documentation | Obligation state after ownership moves |
| Scheduling | Appointments and availability | Why the appointment matters and whether an exception is open |
| Communication platform | Messages, calls and delivery events | Whether outreach satisfied the obligation |
| External provider | Its clinical and operational records | Accepted handoff and completion receipt |
| Analytics platform | Measures, trends and models | The authorized action and its disposition |
The execution layer does not copy every underlying record. It holds the minimum governed representation required to answer: What job is active? Who owns the next step? What evidence was available? What decision was authorized? What happened? What remains unresolved?
shared record of coordination work
The shared operating record described here is the intended direction for later workflow work. Today’s facility brief helps frame and check the question; it does not demonstrate an installed execution layer or replace an existing EHR function.
In the intended design, the coordination record would retain how the agreed job moved across systems. That requires a separately scoped and tested workflow; the current public-data brief does not supply live execution state.
This separation creates a useful control boundary:
- A source system reports a fact or performs an authorized action.
- Lime Health records the applicable obligation and evidence lineage.
- Deterministic controls decide whether the next route is eligible.
- A named human retains authority where policy requires judgment.
- A receipt closes—or fails to close—the obligation.
For the people doing the work, the practical question is whether this reduces repeated searching, status checking and manual reconciliation. Lime Health can make those activities and unresolved obligations measurable. Any reduction in workforce burden must be established against a hospital-approved baseline. The architecture alone does not establish that reduction.
The goal is not to make the EHR responsible for more. It is to make cross-system responsibility inspectable.
What this enables—and what it does not
An execution record can make delayed handoffs, unresolved exceptions, duplicate work and missing receipts visible. It can support reconstruction of why a route was taken. It does not prove that the workflow caused a clinical or reimbursement outcome. Those relationships require an approved evaluation design, time and balancing measures.
For a quality owner, this creates evidence below an aggregate result. For an operational owner, it creates accountable job state. For a clinical leader, it preserves the boundary between operational coordination and clinical judgment. For technology and security owners, it limits what the coordination layer may read, retain and disclose.
Questions for a hospital team
- Where does ownership leave the EHR, and how is acceptance confirmed?
- Which obligations can be reconstructed without asking several teams?
- Which exceptions have a named owner, deadline and disposition?
- Which source remains authoritative when Lime Health records a reference to its evidence?
- What minimum receipt demonstrates that the job—not merely a task—closed?
Start with one transition obligation. Map its source authority, owner changes, evidence, exception path and closing receipt before considering broader automation.
Related: The missing execution record between discharge, scheduling, communication and follow-up
Payment-lens continuity
A CMS reduction rate or an Lime Health materiality scenario can make the 30-day job more important to examine. Neither assigns an obligation nor records closure. The governed execution record must still preserve the owner, events, exceptions and receipts beside the EHR.
Sources and boundary
See the CMS HRRP program and Lime Health evidence disclosures. This article is informational and does not provide clinical, legal or reimbursement advice.