No patient should wait between teams.
Patient flow becomes reliable when readiness is explicit, the receiving team acknowledges and accepts usable capacity, and the sending team protects the patient until arrival or completion can be proved.
A queue is not only a number of patients. It is a set of people in different clinical states, waiting for different decisions, services, information, places, or recoveries, with different risk while time passes.
Hospitals and clinics can know the census, average wait, length of stay, boarding count, backlog, and capacity while one patient still becomes anonymous inside the aggregate. A dashboard may show where delay exists without showing who is accountable for the next safe action.
The Transition Contract makes one patient movement accountable. Ready means clinical, information, patient, and caregiver readiness with unresolved risk stated. Receive means explicit acknowledgment and acceptance by a named team with usable capability. Protect means the sender retains accountability, reassesses risk, updates the patient, and escalates until arrival or completion.
The Flow Reliability Ledger records the clinically ready, request, acknowledgment, acceptance, physical arrival or completion times; accountable team; safety review and patient update; blocker and owner; fallback; escalation; defect; and first-pass acceptance. Both labels are editorial models, not CMS, AHRQ, or Joint Commission terms or required forms.
Leaders can connect this patient-level contract to the site’s existing guidance on optimizing patient flow management, streamlining healthcare operations, value-based care for hospital CEOs, and patient engagement through telehealth. Those wider strategies become more reliable when each patient transition still names the request, sender, receiver, protection plan, completion evidence, and next accountable step.
Movement is not flow when accountability disappears. A transition closes only when the patient is ready, the receiving team has accepted usable capacity, the sender has protected the wait, arrival or completion is verified, and the patient knows what happens next.
The approach is narrower than an enterprise flow program. It does not replace demand forecasting, staffing, bed management, huddles, surge plans, or capacity investment. It adds patient-level accountability where aggregate operations can otherwise hide delay, uncertainty, and handoff failure.
The twelve contract exhibits below move from one-patient transition definition through ledger construction, Ready, Receive, Protect, external handoffs, expired-contract learning, time distributions, fairness, safety, and verified close.
Define what the patient is waiting for right now.
Use a patient-level queue object: registration, triage, examination, bed, consult, test, result, procedure, recovery, transport, referral, authorization, medicine, equipment, discharge service, transfer acceptance, follow-up, or another explicit dependency. One encounter may move through several queues.
Record the entry event and the event that closes the wait. An order placed may start a diagnostic queue, but completion may require performance, interpretation, communication, clinical acknowledgment, and a resulting decision. Choose the closure that matters to care rather than the easiest timestamp.
Do not label every elapsed minute as waste. Some waits protect safety, allow physiology to change, support shared decision-making, respect patient choice, or provide necessary monitoring. Make the clinical purpose visible and test whether the interval and setting remain appropriate.
Separate elapsed time from preventable delay. A long wait may be clinically justified; a short delay may be dangerous for one patient. Pair time with condition, priority, reason, due time, reassessment, and harm or burden during the interval.
Version the queue definition. If teams count different entry or closure events, performance comparisons mislead and patients can disappear between systems. Preserve source, field, clock, timezone, exclusions, corrections, and owner.
Record the transition without creating a second chart.
The receipt should point to authoritative clinical documentation and operational systems rather than duplicate them. Its job is to expose the next-step contract: reason, risk, owner, time, reassessment, escalation, receiver, communication, and closure.
Create the receipt automatically where reliable data exist, then require human confirmation for clinical purpose, risk, owner, and exceptions. A prefilled owner based only on department or order type is not accountability if that role cannot see, accept, or act on the queue.
Make the receipt visible in the workflow used by the responsible team. Avoid a separate queue that requires staff to maintain the chart, tracker, whiteboard, email, and dashboard independently. Reconcile changes and identify the authoritative source for each field.
Protect sensitive status. Operational visibility should not expose diagnoses, behavioral health information, domestic safety concerns, immigration information, or other details beyond what the role needs. Use role-appropriate displays that expose no more sensitive detail than the operational purpose requires, plus safe public-facing identifiers.
Retire the receipt when the queue closes, but preserve required evidence and learning. An abandoned, duplicated, or stale receipt can create false work and unsafe assumptions. Define cancellation, merge, correction, and audit rules.
Protect the patient, not only the position in line.
Priority can change after queue entry. Symptoms evolve, vital signs change, pain increases, medication wears off, fall risk rises, delirium emerges, a caregiver leaves, transportation becomes unavailable, or new information changes the clinical need. The reassessment plan must match that risk.
Define what will be reassessed, by which qualified role, at what cadence or event trigger, where the finding is recorded, and what action follows. A fixed interval may help some queues; continuous observation, symptom-triggered review, or a shorter clinically determined cadence may be necessary for others.
Do not let an operational estimate become a clinical promise. If the expected wait changes, reassess risk and communicate. Provide a route for the patient or caregiver to report worsening symptoms, new needs, inability to continue waiting, or misunderstanding.
Capture missed reassessment and unobservable patients as high-risk queue defects. A patient in a waiting room, hallway, remote location, vehicle, home, or virtual channel may require different monitoring and escalation. State the limit of what the organization can observe.
Use event review to improve the receipt. Deterioration, elopement, left-without-being-seen, fall, delayed treatment, complaint, or near miss can reveal a poor interval, unclear owner, inaccessible reporting route, unsafe environment, or broken escalation.
Record the contract timestamps that expose lost accountability.
One elapsed interval can hide several different failures. A patient may be clinically ready but never requested, requested but not acknowledged, acknowledged but not accepted, accepted but waiting for staffed capability, physically moved without a complete handoff, or completed without the patient understanding the plan.
Capture clinically ready, request, acknowledgment, acceptance, physical arrival or completion, and verified close as separate events. Record the accountable sending team at every moment. Use locally defined due times based on clinical risk and operating design; do not present a local commitment as a universal regulatory threshold.
Use four blocker families without stopping at the category. Clinical work may include stabilization or unresolved treatment. Coordination may include missing request, unclear owner, or delayed decision. Capacity means usable staffed capability, not an empty room. External dependency may include transport, payer process, post-acute service, family readiness, or supplier.
Preserve reason changes. A transition may begin with clinical work and later become coordination delay. Reporting only the final blocker hides the sequence and directs improvement to the wrong team. Timestamp the change, new owner, patient effect, and escalation.
Audit a sample against the actual patient journey. Automated events can misclassify readiness, acceptance, arrival, or completion. Compare data with chart, conversation, patient account, observation, and receiver record before governing performance.
Assign an owner to every ledger event and missing field. The sending team may own clinically ready and request; the receiver may own acknowledgment and acceptance; transport or the performing service may own arrival or completion. Technical capture does not change clinical accountability. If an event is inferred from a system action, label the inference, validate it, and prevent a proxy such as an opened message from being reported as human acceptance.
Make readiness a clinical state, not an order.
An order or disposition decision can start a transition without proving readiness. The patient may still need stabilization, symptom control, medication, result review, equipment, consent, education, goals or preference clarification, accessible transportation, caregiver preparation, or a resolved infection-control concern.
Define readiness for the specific receiving capability. A patient ready to leave one unit is not necessarily ready for the next setting. State clinical criteria, information, equipment, medicines, services, patient and caregiver understanding, outstanding risk, and what can safely follow after arrival.
For hospital discharge planning, the binding federal condition of participation requires attention to the patient’s goals and preferences, early and timely evaluation, re-evaluation when factors change, and necessary information. The Transition Contract does not replace those duties or prescribe one discharge time.
Allow conditional readiness. Some pending work can safely follow in the receiving setting if that team agrees, the responsibility is explicit, the patient understands, and risk is controlled. Label the condition rather than hiding it inside a generic ready status.
Reopen readiness when condition, information, destination, patient preference, receiving capability, transport, or time changes. A stale ready flag can create unsafe transfer pressure. Record who revalidated and when.
Require acknowledgment, acceptance, and usable capability.
Sending information is not a handoff. An order, referral, message, page, electronic alert, bed assignment, or transmitted record may reach a system without reaching a person who understands the request, accepts responsibility, and can provide the needed care.
Separate acknowledgment from acceptance. Acknowledgment confirms receipt and understanding of the request. Acceptance confirms that the receiving team agrees to the transition and has or will have the necessary staffed capability, information, equipment, environment, authority, and support at the agreed time.
AHRQ TeamSTEPPS handoff guidance describes transfer of information with authority and responsibility, with the sender accountable until the receiver is aware, understands, acknowledges, and accepts. It is voluntary guidance and does not mandate one universal script or electronic format.
Do not equate an empty bed with usable capacity. The appropriate staff, monitoring, equipment, supplies, isolation conditions, service coverage, physical access, cleaning, and emergency capability must be ready for this patient. Capacity can be unavailable even when the location appears open.
Treat rejection as evidence. Record the specific readiness, information, clinical, capability, policy, capacity, or scope reason. Correct the defect, clarify criteria, escalate disagreement, and protect the patient. A rejected request should not silently disappear into another queue.
Use conditional acceptance carefully. A receiver may accept when a pending result, treatment, bed preparation, equipment delivery, or staffing action will complete before arrival. Name the condition, responsible role, due time, fallback, and who cancels the movement if it fails. Reconfirm immediately before movement. Conditional acceptance should expose coordinated work, not disguise unavailable capability or shift unfinished care without agreement.
Keep the sender accountable until the transition closes.
Acceptance changes the plan but does not remove the patient from the sending team’s care. Until arrival or completion, the sender continues clinically appropriate monitoring, treatment, comfort, communication, documentation, and escalation while the receiver prepares and responds to material change.
Set a locally defined safety review and patient-update cadence based on risk, not one universal clock. A deteriorating patient, high-risk medicine, behavioral health concern, pending result, infection-control need, long transport, or uncertain receiver may require closer observation and earlier escalation.
The patient should not have to coordinate the transition alone. Patient and caregiver participation supports safety, but responsibility for finding the receiver, chasing a result, arranging necessary equipment, or resolving a failed handoff remains with the accountable teams.
Use a clear coverage transfer at shift change. The outgoing owner confirms open contracts, risk, next review, blocker, receiver status, patient update, and escalation. The incoming owner acknowledges and accepts the protection duty just as the downstream team must accept the care transition.
If the receiving capability changes or becomes unavailable, reopen the contract. Do not leave the patient attached to an acceptance that no longer represents reality. Assign a new receiver or alternate plan and communicate immediately.
Carry accountability across the organizational boundary.
External transitions add differences in records, criteria, staffing, hours, coverage, transport, equipment, language, technology, and accountability. Referral, discharge, transfer, post-acute care, home service, pharmacy, diagnostic partner, and community handoffs need an explicit receiver and a closed route.
Confirm the receiving entity, service, named contact or accountable role, eligibility, clinical capability, availability, accepted information, timing, patient cost or coverage issue, equipment, transportation, and what happens if the patient cannot arrive or the service does not start.
For covered hospital emergency departments, EMTALA requires an appropriate medical screening examination, stabilizing treatment within capability, or an appropriate transfer when conditions are met. Insurance questions cannot delay the examination or treatment. The law is not a throughput target or authority to move an unstable patient for convenience.
Hospital discharge and transfer duties remain applicable. Federal discharge-planning requirements address patient goals and preferences, evaluation, re-evaluation, necessary information, and transfer policies and training. The Transition Contract supports, but does not replace, the controlling discharge process.
Admission, discharge, and transfer notification rules are entity and system specific. CMS guidance does not treat internal unit moves as required notification events under that condition. Delivery of an ADT alert does not prove that a clinician acknowledged, understood, accepted, or acted on the handoff.
Treat an overdue transition as a safety signal.
A contract expires when a locally defined safety review, patient update, receiver response, accepted arrival, completion, or escalation event passes without the required action. Expiration does not automatically mean harm occurred. It means the current protection plan is no longer reliable enough to remain passive.
At expiration, reassess the patient, confirm the owner, contact the receiver, validate readiness and capacity, explain the delay, and activate the defined escalation or alternate. Record the specific reason, action, time, patient effect, and whether the contract can continue safely.
Report expired contracts per one hundred transitions with the numerator, denominator, scope, and local definition. Pair the rate with deterioration, rapid response, higher-acuity transfer, omission, patient complaint, left-before-completion, staff burden, and other setting-appropriate balancing outcomes.
Use the hospital quality assessment and performance improvement structure where applicable to investigate material patterns and implement improvement. The underlying federal condition is binding for in-scope hospitals; survey guidance interprets it and does not separately mandate this ledger, cadence, or threshold.
Learn from first-pass acceptance. Repeated rejection for missing information, unresolved clinical work, wrong destination, unclear eligibility, or absent capability reveals an upstream defect. Improvement should reduce preventable rejection without pressuring receivers to accept unsafe transitions.
Review a small set of expired contracts in narrative depth. Reconstruct what the patient experienced, what each team believed, which information was available, when accountability changed, why escalation did or did not occur, and how the receiver’s conditions affected the sender. Combine that narrative with ledger events. Numbers show the pattern; the reconstructed contract shows the mechanism that must change.
See the patients hidden behind the median.
An average or median summarizes the center of a distribution. It can improve while a small group waits much longer, experiences repeated rejection, loses an owner, or deteriorates. Patient-level transition governance needs the center, the tail, and the clinical story of extreme cases.
For ready-to-accept, accept-to-arrival, and total intervals, report the count, median, ninetieth percentile, longest waits, missing events, exclusions, and locally defined due-time performance. Add blocker hours and repeat blockers. Preserve the formal specification if using a public measure.
The CMS Timely and Effective Care dataset released in May 2026 contains formally specified public hospital measures. Preserve each population, exclusion, definition, and period. Public medians are not local targets and do not show the tail, accountability, readiness defect, or cause of delay.
Recent retrospective cohorts add useful concern without proving causation. A 2026 study across three English emergency departments associated boarding time and load with outcomes. A 2025 single-hospital UK study associated inaccurate planning, moves, and handoff conditions with delay. Neither provides a universal effect size, target, or proof that one intervention will work locally.
A current AHRQ funding notice identifies emergency department boarding and crowding as a research priority through December 20, 2027. It is a grant notice and research agenda, not a standard, required strategy, or evidence that the Transition Contract is effective.
Make faster transitions safer and fairer.
Shorter is not automatically safer. A faster transition can reflect better readiness, coordination, and capacity, or premature movement, reduced observation, incomplete information, inaccessible communication, denied choice, unsafe discharge, or a problem shifted to another team or setting.
Balance time with correct patient, correct care, clinical outcome, deterioration, medication and result reliability, transfer to higher acuity, return, complaint, understanding, consent, access, workforce burden, and unresolved work at the receiver. Stop or correct an intervention when these worsen.
Joint Commission National Performance Goal number one organizes existing accreditation requirements around the right patient receiving the right care, and number four addresses high-quality safe care for all, including identifying differences and acting on them. Accreditation scope is not federal law, and these goals do not prescribe this ledger or one flow-disparity measure.
Stratify where privacy, data quality, and sample size permit: language, disability, age, geography, race and ethnicity, payer, time of day, arrival route, service, and locally relevant factors. Investigate missingness and unstable small groups rather than ranking them carelessly.
Use the AHRQ Hospital Survey on Patient Safety Culture as staff-perception context for teamwork, handoffs, communication, and reporting. It is not an outcome measure, compliance audit, or causal proof that a flow change improved safety.
Check for burden transfer across groups and settings. A faster hospital interval can rely on family coordination, unpaid caregiver work, a distant facility, repeated travel, unaffordable medicine, staff overtime, or a receiving team absorbing unresolved tasks. Record where work and risk moved, whether the receiver accepted it, and whether the patient can use the plan. Do not call a local time reduction equitable flow when another party carries an invisible wait.
End the contract only when the receiving work begins.
Physical movement is not always completion. Arrival in a unit, facility, home, clinic, diagnostic department, procedure area, or virtual appointment may still leave the patient without an accountable team, required service, medicine, equipment, result, monitoring, or usable plan.
Define the close event for each transition. It may require receiver verification, first assessment, service start, treatment administration, result acknowledgment, equipment delivery, medicine access, home visit, follow-up appointment, patient teach-back, or another clinically meaningful action.
Close unresolved pending work separately. A result, referral, medicine, equipment, or service that will occur later needs a named owner, due time, acknowledgment, escalation, patient instruction, and confirmation. The main transition should not erase its obligations.
Audit the complete chain from ready through close and back from complaint or harm to the responsible contract. Compare ledger events with patient account and frontline observation. A technically closed record can still conceal a failed experience or unsafe handoff.
Retire duplicate tracking when the model stabilizes. Embed the minimum fields and alerts into existing work, preserve authoritative documentation, and remove shadow spreadsheets or messages that divide accountability. Measure documentation burden and correct work that does not protect the patient or close the transition.
Conclusion: no patient should be left between teams.
Patient flow is often governed through aggregate demand, capacity, throughput, and time. The Transition Contract adds the patient-level assurance those views can miss: who is ready, who has received and accepted accountability, who protects the wait, and what proves the next care step began.
Ready is more than an order. It includes clinical, information, patient, caregiver, and unresolved-risk readiness for the actual receiving capability. Receive is more than an alert or empty location. A named team must acknowledge, understand, accept, and possess usable staffed capability.
Protect keeps accountability from vanishing after the request. The sender reassesses risk, treats the patient, communicates changes, updates the patient and caregiver, and escalates until arrival or completion. The receiver prepares and responds to new information.
The Flow Reliability Ledger shows where the contract broke: readiness, request, acknowledgment, acceptance, usable capacity, arrival, completion, patient understanding, or pending-work ownership. Medians show typical time; tails, expired contracts, harm, burden, and subgroup results show who the average left behind.
Faster movement is valuable only when it preserves the right patient, right care, safe setting, clear responsibility, informed choice, equitable access, and a workforce able to perform the handoff. Reliable flow is not movement at any cost. It is an accountable transition that closes.
Sources and further reading
- AHRQ, Special Emphasis Notice on Research Addressing Emergency Department Boarding and Crowding. An active research-priority and grant notice through December 20, 2027. It is not a care standard, required strategy, or proof that a particular intervention is effective.
- The Joint Commission, National Performance Goal 1: Right Patient, Right Care. A 2026 organization of existing accreditation requirements for covered hospitals and critical access hospitals. Accreditation requirements are not federal law and do not mandate this editorial model.
- AHRQ TeamSTEPPS 3.0, Handoff. Voluntary guidance describing transfer of information with authority and responsibility, with the sender accountable until the receiver is aware, understands, acknowledges, and accepts. It does not require one format.
- AHRQ, Surveys on Patient Safety Culture Hospital Survey 2.0. A staff-perception culture instrument relevant to communication, handoffs, reporting, and teamwork. It is not an outcome measure, compliance audit, or causal evaluation.
- The Joint Commission, National Performance Goal 4: High-Quality, Safe Care for All. Accreditation requirements for identifying differences in care and taking and monitoring action within scope. It does not prescribe one flow-disparity metric.
- CMS, You Have Rights in an Emergency Room Under EMTALA. An official consumer summary of medical screening, stabilizing treatment, appropriate transfer, and the prohibition on delaying examination or treatment for insurance questions at covered hospital emergency departments.
- 42 CFR 482.43, Condition of Participation: Discharge Planning. Binding requirements for in-scope hospitals, including goals and preferences, timely evaluation, re-evaluation, necessary information, and transfer policies and training. It does not mandate this model or one timing target.
- CMS, Admission, Discharge, and Transfer Patient Event Notification CoP FAQs. Entity- and system-specific guidance. Internal unit moves are not required notification events under this provision, and delivered alerts do not prove clinical acknowledgment or acceptance.
- CMS Data, Timely and Effective Care Hospital Dataset. The May 13, 2026 public release contains formally specified hospital measures and populations. Public medians are not internal targets and do not explain tail cases, ownership, or causes.
- CMS QSO-23-09, Hospital Quality Assessment and Performance Improvement Interpretive Guidance. Guidance interpreting the underlying binding condition for in-scope hospitals. The memo does not separately impose a universal transition ledger, review cadence, or escalation threshold.
- Howlett and colleagues, Emergency Medicine Journal, 2026. A retrospective cohort across three English emergency departments examining boarding time, boarding load, and outcomes. Observational, non-U.S. findings do not prove causation or establish a universal effect size.
- Burns and colleagues, BMJ Open, 2025. A retrospective cohort at one NHS hospital examining planning accuracy, patient moves, handoffs, and delays. Single-site observational findings do not create a universal rule or causal claim.
