Coordinate the handoff, not the clinical decision
Fictional example: Harborview Care Network uses this page to illustrate coordination across its inpatient units and diagnostic services. For an internal transfer, the requesting team uses its locally approved channel, the sending team confirms readiness through its approved process, and the receiving team confirms the destination handoff. This page contains no patient information and is not a request queue, system of record, or clinical procedure.
Know which situation you are coordinating
These examples show coordination boundaries; authorized roles retain clinical decision-making.
The sending team has used the approved request channel and confirmed readiness through its local process. Transport coordination can proceed to the agreed destination handoff.
The receiving team has not confirmed it can accept the handoff. Do not treat a planned destination as confirmed; use the established local exception route.
A change in timing, destination, or readiness affects the agreed handoff. Contact the relevant roles through approved local channels and re-establish the handoff before proceeding.
Use the same four coordination checks
The local approved procedure and authorized roles determine readiness and clinical requirements.
-
1
Request through the approved channel
The requesting team uses the organization's locally approved request channel and supplies information only through that approved workflow—not on this Sites page.
-
2
Confirm the sending-side handoff
The sending team confirms readiness using its approved local process and communicates the agreed handoff to transport coordination through the appropriate channel.
-
3
Confirm the destination handoff
The receiving team confirms the destination handoff through the locally established process. A planned destination alone is not confirmation.
-
4
Route exceptions through local escalation
If readiness, timing, destination, or acceptance changes or cannot be confirmed, use the established local exception route and follow approved procedures.
Illustrative responsibility reference
Fictional coordination example only—not a live queue, system of record, or substitute for local approved procedures.
| Handoff stage | Accountable role | Confirmation to establish |
|---|---|---|
| Request | Requesting team | The request was submitted through the locally approved channel. |
| Sending readiness | Sending team | Readiness was confirmed through the approved local process. |
| Transport coordination | Transport coordination role | The agreed movement handoff and relevant local coordination details were communicated through approved channels. |
| Destination acceptance | Receiving team | The destination handoff was confirmed through the locally established process. |
| Exception | Relevant local operational lead | The established exception route was used when a handoff could not be confirmed or the plan changed. |
Roles in the handoff
Responsibilities below describe the fictional coordination model. Use the organization's approved local procedures and reporting lines to identify the actual accountable roles.
Requesting team
Initiates the request through the locally approved channel and provides information through that workflow.
Sending team
Confirms readiness using its approved process and communicates the sending-side handoff.
Transport coordination role
Coordinates the agreed movement handoff through approved local channels; does not make clinical readiness decisions.
Receiving team
Confirms the destination handoff through the locally established process.
Operational lead
Provides the local escalation route when a handoff cannot be confirmed or the plan changes.
When the handoff is uncertain
Keep the exception with the accountable local roles.
If the agreed sending or receiving handoff cannot be confirmed, or a material change affects the plan, pause coordination and use the organization's established local exception route. Do not infer readiness or destination acceptance from an earlier plan.
Clinical, safety-critical, or other sensitive questions belong with the authorized roles and domain-owner-approved local procedures. Keep patient details and operational records in approved systems, not in this page.
Content owner: Clinical Operations and Support Services. The owner should review this reference when approved local handoff procedures, role responsibilities, or escalation routes change.