ASF Standards · Medical Transport · Standard 4
Standard 4 — Handover & Communication
Criteria in this standard
4.1 — Structured Handover at Pickup
4.2 — Structured Handover at Destination
4.3 — Real-Time Status Communication to Dispatch
4.4 — Written Documentation Accompanies Patient
4.5 — Language-Appropriate Communication with Patient
4.2 — Structured Handover at Destination
4.3 — Real-Time Status Communication to Dispatch
4.4 — Written Documentation Accompanies Patient
4.5 — Language-Appropriate Communication with Patient
4.1
Structured Handover at Pickup
Non-Negotiable
A structured, standardized handover is conducted between sending facility staff and transport crew at pickup, covering clinical status, treatment given, allergies, and specific concerns, not an informal verbal summary.
In plain terms: Crew get a real, structured briefing from sending staff covering everything that matters — not a quick, informal rundown that varies depending on who happens to be handing over.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
An unstructured verbal handover depends entirely on what the handing-over staff member happens to think to mention in the moment, which means critical details — a specific allergy, a recent medication change — can be omitted simply because they weren’t top of mind during a brief exchange. A standardized format forces coverage of the specific categories most likely to matter clinically, regardless of who is giving or receiving the handover.
What good looks like
- A standardized format is actually used, not a verbal summary that varies by staff member.
- Allergies and specific concerns are covered explicitly, not folded into general diagnosis.
- The handover is documented with both parties’ acknowledgment.
Common failure modes
- Handover quality depends heavily on which staff member is giving it.
- Allergies get mentioned only if the handing-over staff member happens to recall them.
- No documentation exists confirming the handover actually occurred.
Worked example
In practice
A sending facility with high staff turnover and no standard handover format.
BeforeHandover quality varied significantly by which sending facility staff member happened to be available. A new nurse once omitted a documented medication allergy during a verbal handover, which only came to light when crew separately reviewed the chart.
ActionThe transport organization introduced a standardized handover card with required fields — allergies, current medications, treatment given, specific concerns — that both sending staff and crew complete and sign together before departure.
AfterThe Monitor reviewed recent handover cards and found consistent, complete coverage of all required fields with both parties’ signatures, regardless of which sending facility staff member was involved. Criterion verified.
If you are starting from zero — do this first
- Build a standardized handover card or checklist with required fields.
- Require both parties to complete and sign it together, not just crew alone.
- Pilot it with a sending facility partner and refine based on gaps found.
The most common mistake: Relying on an informal verbal handover whose completeness depends heavily on which individual staff member happens to be giving it, rather than a standardized format that forces coverage regardless of who’s involved.
Self-assessment questions
1. Is a standardized handover format actually used, not a verbal summary that varies by who’s handing over? — An unstructured handover risks omitting critical details depending on who’s speaking.
Evidence: Handover card or checklist
Evidence: Handover card or checklist
2. Does the handover cover allergies and specific concerns explicitly, not just general diagnosis? — These are commonly the details lost in an informal handover.
Evidence: Completed handover record
Evidence: Completed handover record
3. Is the handover documented, with both parties’ acknowledgment? — An undocumented handover leaves no record if information was missed.
Evidence: Signed handover record
Evidence: Signed handover record
Common reasons for a PARTIAL answer
- A format exists but isn’t consistently used by all sending facility partners.
- Handover happens but only one party signs or acknowledges it.
Implementation plan
| When | What |
|---|---|
| Week 1 | Build a standardized handover card with required fields. |
| Week 2 | Pilot with one or two sending facility partners. |
| Week 3 | Refine based on pilot feedback and roll out broadly. |
| Ongoing | Audit handover card completeness periodically. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Handover record review | Checks completed handover cards for consistency and both-party acknowledgment. |
Evidence base
World Health Organization. Communication During Patient Hand-Overs. Patient Safety Solutions, Volume 1, Solution 3. Geneva: WHO; 2007.
Joint Commission International. Accreditation Standards for Medical Transport Organizations, 1st ed. Oak Brook (IL): JCI; 2021.
4.2
Structured Handover at Destination
Non-Negotiable
A structured handover is conducted between transport crew and receiving facility staff at arrival, covering changes in status during transport, interventions performed en route, and current clinical status, with receiving staff acknowledgment.
In plain terms: At arrival, receiving staff get a real briefing specifically on what happened during the trip — not just a repeat of what the sending facility already said.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Receiving staff already have access to the sending facility’s own records in most cases — what they genuinely need from crew is specifically what happened during the transport itself, information that exists nowhere else. A handover that simply repeats the pickup information without adding transport-specific detail misses the one thing only crew can actually report.
What good looks like
- The handover specifically covers what changed during transport.
- Receiving staff provide documented acknowledgment of the handover.
- Handover goes directly to a responsible clinician, not whoever is nearby.
Common failure modes
- The handover repeats pickup information without transport-specific detail.
- No acknowledgment record confirms the handover was actually received.
- Handover is given to whichever staff member happens to be present.
Worked example
In practice
An inter-city transport where the patient required an intervention en route.
BeforeAt arrival, crew gave receiving staff a brief summary that largely repeated what was already in the sending facility’s transfer paperwork, without clearly flagging that an oxygen intervention had been needed partway through the journey.
ActionThe organization built a destination handover format specifically structured around “what changed during transport,” requiring crew to lead with any intervention or status change rather than repeating baseline information.
AfterThe Monitor reviewed a recent destination handover record and found the oxygen intervention clearly flagged as the lead item, with documented acknowledgment from the receiving nurse. Criterion verified.
If you are starting from zero — do this first
- Build a destination handover format specifically structured around transport changes.
- Require documented receiving-staff acknowledgment.
- Confirm handover goes to a named, responsible clinician, not whoever is nearby.
The most common mistake: A destination handover that largely repeats pickup information, missing the opportunity to clearly flag the transport-specific changes that only crew can actually report.
Self-assessment questions
1. Does the destination handover specifically cover what changed during transport, not just a repeat of the pickup information? — Transport-specific changes are exactly what receiving staff most need and often don’t get.
Evidence: Destination handover record
Evidence: Destination handover record
2. Is there documented acknowledgment from receiving staff that handover was received? — Without acknowledgment, there’s no confirmation the information actually transferred.
Evidence: Receiving staff acknowledgment
Evidence: Receiving staff acknowledgment
3. Is the handover given directly to a responsible clinician, not left with whoever happens to be nearby? — A handover to the wrong person functions the same as no handover.
Evidence: Named recipient on handover record
Evidence: Named recipient on handover record
Common reasons for a PARTIAL answer
- Handover repeats baseline information without highlighting transport-specific changes.
- No clear process ensures handover reaches a specifically responsible clinician.
Implementation plan
| When | What |
|---|---|
| Week 1 | Build a destination handover format focused on transport-specific changes. |
| Week 2 | Train crew on leading with changes, not repeating baseline information. |
| Week 3 | Build a documented acknowledgment requirement. |
| Ongoing | Spot-check destination handover records for transport-specific content. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Destination handover record review | Checks for transport-specific content and documented receiving-staff acknowledgment. |
Evidence base
World Health Organization. Communication During Patient Hand-Overs. Patient Safety Solutions, Volume 1, Solution 3. Geneva: WHO; 2007.
4.3
Real-Time Status Communication to Dispatch
Core
Crew communicate transport status to dispatch at defined checkpoints throughout the journey, with a documented escalation procedure if expected communication is missed.
In plain terms: Dispatch actually hears from crew at set points throughout the trip — and if an expected check-in doesn’t come, something real happens about it.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Communication only at departure and arrival leaves a long gap during which a problem — vehicle breakdown, patient deterioration, a crew member in distress — could develop with nobody at dispatch aware anything is wrong. Checkpoint communication closes this gap, but only if a missed checkpoint actually triggers a response; otherwise the checkpoint system provides an illusion of oversight without the substance.
What good looks like
- Checkpoint communications actually happen at defined intervals.
- A documented procedure exists for what dispatch does when a checkpoint is missed.
- A documented instance exists of this escalation procedure actually being used.
Common failure modes
- Communication happens only at departure and arrival, no interim checkpoints.
- A missed checkpoint has no defined dispatch response.
- No example exists of the escalation procedure ever actually triggering.
Worked example
In practice
An inter-city transport losing cellular coverage for an extended period.
BeforeDispatch expected a mid-route check-in that didn’t arrive due to a coverage gap. With no defined escalation procedure, dispatch simply waited, uncertain whether this reflected a coverage issue or something more serious, for over an hour before taking any action.
ActionThe organization built a specific escalation procedure: a missed checkpoint triggers an attempt via backup communication method within ten minutes, and if that also fails, a defined follow-up protocol including last-known-location tracking.
AfterThe Monitor reviewed a subsequent instance where a missed checkpoint triggered the backup communication attempt within the required window, successfully reaching crew and confirming they were simply in a coverage gap. Criterion verified.
If you are starting from zero — do this first
- Set specific checkpoint intervals appropriate to typical route lengths.
- Build a defined, time-bound escalation procedure for missed checkpoints.
- Test the escalation procedure, don’t just document it.
The most common mistake: A missed checkpoint communication is met with uncertain waiting rather than a defined, immediate escalation procedure, leaving dispatch unsure how long to wait before taking action.
Self-assessment questions
1. Are checkpoint communications actually happening at defined intervals, not only at departure and arrival? — Without interim checkpoints, a problem mid-route can go unnoticed for a long period.
Evidence: Checkpoint communication log
Evidence: Checkpoint communication log
2. Is there a documented procedure for what dispatch does when an expected checkpoint communication doesn’t arrive? — A missed checkpoint with no follow-up defeats the purpose of checkpoint communication.
Evidence: Written escalation procedure
Evidence: Written escalation procedure
3. Is there a documented instance of this escalation procedure actually being used? — Evidence the procedure functions, not just exists on paper.
Evidence: Escalation event record
Evidence: Escalation event record
Common reasons for a PARTIAL answer
- Checkpoints exist but a missed one has no defined response.
- The escalation procedure has never actually been tested or used.
Implementation plan
| When | What |
|---|---|
| Week 1 | Set defined checkpoint intervals for typical route types. |
| Week 2 | Build a time-bound escalation procedure for missed checkpoints. |
| Week 3 | Test the escalation procedure with a simulated missed checkpoint. |
| Ongoing | Review checkpoint adherence and escalation triggers periodically. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Checkpoint and escalation log review | Reviews checkpoint communication logs and any escalation event record. |
Evidence base
Joint Commission International. Accreditation Standards for Medical Transport Organizations, 1st ed. Oak Brook (IL): JCI; 2021.
4.4
Written Documentation Accompanies Patient
Core
Complete written documentation — transport record, medications given, vital sign trends, any incidents — physically or digitally accompanies the patient to the receiving facility, not relying on verbal handover alone.
In plain terms: A real written record of the trip actually travels with the patient — not just whatever crew happened to say out loud at handover.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Verbal handover, however thorough, is not retrievable later — a written record is what the receiving team can reference hours or days afterward if a question arises about what happened during transport. A record limited to final values at arrival loses the trajectory information that trend data over the journey actually provides, which can be clinically significant in its own right.
What good looks like
- Written documentation actually arrives with the patient, complete.
- Vital sign trends are included, not just final values.
- Incidents are clearly documented even if they resolved without lasting effect.
Common failure modes
- Documentation is sent separately and doesn’t actually arrive with the patient.
- Only final vital sign values are recorded, losing trend information.
- A resolved incident is omitted since it “didn’t end up mattering.”
Worked example
In practice
A transport where documentation was meant to follow electronically.
BeforeWritten transport records were meant to be uploaded electronically after each transport, but a system delay meant receiving staff sometimes had no written record available for several hours after the patient arrived, relying entirely on the verbal handover in the meantime.
ActionThe organization required a printed or immediately accessible digital copy of the transport record to physically accompany the patient at handover, with the electronic upload as a backup rather than the primary delivery method.
AfterThe Monitor confirmed recent transports all had a physical or immediately accessible record present at the moment of handover, not dependent on a separate system upload. Criterion verified.
If you are starting from zero — do this first
- Confirm documentation physically or immediately accompanies the patient, not sent separately.
- Check whether vital sign trends are captured, not just final values.
- Confirm resolved incidents are still documented, not omitted.
The most common mistake: Relying on a separate electronic upload system for documentation delivery, which can introduce a delay leaving receiving staff without a written record at the actual moment of handover.
Self-assessment questions
1. Does written documentation actually arrive with the patient, not sent separately or left incomplete? — Verbal handover alone is not a substitute for a written record the receiving team can reference later.
Evidence: Transport record present at handover
Evidence: Transport record present at handover
2. Does the documentation include vital sign trends throughout transport, not just final values? — A trend shows trajectory; a single final value does not.
Evidence: Trend documentation
Evidence: Trend documentation
3. Are any incidents or interventions during transport clearly documented, not omitted if they resolved without lasting effect? — Even a resolved incident is relevant clinical history for the receiving team.
Evidence: Incident documentation
Evidence: Incident documentation
Common reasons for a PARTIAL answer
- Documentation delivery relies on a system with occasional delay.
- Resolved incidents are sometimes left out of the written record.
Implementation plan
| When | What |
|---|---|
| Week 1 | Review current documentation delivery timing against actual handover. |
| Week 2 | Build a physical/immediate-access backup to any electronic system. |
| Week 3 | Confirm trend and incident documentation requirements are being met. |
| Ongoing | Spot-check documentation completeness and delivery timing. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| OBSERVE | Handover observation | Confirms written documentation is physically present at the point of handover. |
Evidence base
Joint Commission International. Accreditation Standards for Medical Transport Organizations, 1st ed. Oak Brook (IL): JCI; 2021.
4.5
Language-Appropriate Communication with Patient
Standard
Where crew and patient do not share a language, a practical communication method — phone interpretation, translation cards, or equivalent — is available and used during transport, not simply skipped due to practical difficulty.
In plain terms: When crew and patient don’t share a language, there’s a real way to communicate that actually gets used — not skipped because it felt too hard in the moment.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
A phone interpretation line that exists in the organization’s resources but that crew have never actually used provides no real benefit to a patient during an actual transport — access on paper and genuine use in practice are different things. The gap between the two is usually about familiarity and friction: crew need to know exactly how to access the resource quickly, or it won’t be used under the time pressure of an actual transport.
What good looks like
- A practical interpretation method is actually available on board, genuinely accessible.
- A documented instance exists of the method being used during an actual transport.
- Crew can describe how to access it without hesitation.
Common failure modes
- An interpretation resource exists in policy but is rarely actually used.
- No example exists of the resource ever being used in a real transport.
- Crew aren’t confident or quick in knowing how to access it.
Worked example
In practice
A transport organization reviewing interpretation resource usage.
BeforeA phone interpretation line was available under the organization’s vendor contract, but crew rarely used it in practice, finding the access process cumbersome, and often fell back on gesture-based communication for language-discordant patients.
ActionThe organization simplified access to a single speed-dial button on the vehicle’s communication device, briefed all crew directly, and tracked usage to confirm the resource was genuinely being used.
AfterThe Monitor reviewed usage logs showing a clear increase in actual interpretation line use following the simplified access, and crew described the access process confidently without hesitation. Criterion verified.
If you are starting from zero — do this first
- Check actual usage records for any interpretation resource, not just its existence.
- Simplify access if crew find it cumbersome in practice.
- Brief crew directly and confirm they can describe access confidently.
The most common mistake: Having an interpretation resource technically available through a vendor contract, but with access cumbersome enough that crew default to gesture-based communication instead of actually using it.
Self-assessment questions
1. Is a practical interpretation method actually available on board, not just theoretically accessible? — A phone interpreter line that’s never actually used in practice functions the same as not having one.
Evidence: Usage log
Evidence: Usage log
2. Is there a documented instance of this method being used during an actual transport? — Evidence the resource is genuinely used, not just available.
Evidence: Usage record
Evidence: Usage record
3. Can crew describe how to access the interpretation method without hesitation? — If crew don’t know how to access it quickly, it won’t be used under time pressure.
Evidence: Crew interview
Evidence: Crew interview
Common reasons for a PARTIAL answer
- A resource exists but access is cumbersome enough to discourage real use.
- Crew know the resource exists but hesitate on how to access it quickly.
Implementation plan
| When | What |
|---|---|
| Week 1 | Review current interpretation resource usage records. |
| Week 2 | Simplify access if usage is low due to friction. |
| Week 3 | Brief all crew directly on fast access. |
| Ongoing | Track usage to confirm the resource is genuinely used. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| ASK | Crew access check | Asks crew to describe how to access interpretation during an actual transport without hesitation. |
Evidence base
World Health Organization Regional Office for Europe. Global Competency Standards for Refugee and Migrant Health. Copenhagen: WHO/Europe; 2024.