When relaying patient information via radio communications, you should be clear, concise, and structured. That means using a consistent reporting format, speaking in plain language rather than codes, and delivering the most critical details first so the receiving facility can prepare. Whether you’re calling in a routine transport or a trauma alert, the way you organize and deliver your radio report directly affects patient care on the other end.
Use a Structured Reporting Format
A structured format keeps your report predictable for the person listening, which reduces the chance they’ll miss something important. Two widely used frameworks are SBAR and IMIST-AMBO, and understanding both helps you pick the right tool for the situation.
SBAR stands for Situation, Background, Assessment, and Recommendation. It’s a general communication framework used across healthcare settings. You open with what’s happening right now, provide relevant medical history, give your clinical assessment, and finish with what you think needs to happen next. SBAR works well for hospital-to-hospital transfers or physician consultations where a recommendation is expected.
IMIST-AMBO stands for Identify, Mechanism/Medical Complaint, Injuries/Information related to the complaint, Signs and Symptoms, Treatment and Trends, then Allergies, Medications, Background, and Other information. It’s essentially a more granular version of SBAR, sequenced specifically for the prehospital-to-emergency-department handoff. Emergency department staff prioritize mechanism of injury, consciousness level, vital signs, and how the patient has responded to treatment over details like allergies and past medical history. IMIST-AMBO mirrors that priority order. One key difference: rather than prompting a recommendation, it asks you to state objective trends in the patient’s condition after treatment and flag other relevant details like advance directives or family presence.
Regardless of which framework your agency uses, the core data points in any radio report include the patient’s age and gender, chief complaint with mechanism of injury or nature of illness, current vital signs, and any previously abnormal vitals worth noting. A standard county EMS radio report format calls for exactly these elements, and receiving hospitals expect them every time.
Lead With the Most Critical Information
The receiving team is listening for one thing first: how sick is this patient, and what do we need to have ready? Front-load your report with the urgent concerns. If your patient has a blood pressure below 90, a heart rate above 120, or a consciousness score that’s dropping, say that before you get into the medical history. In multi-casualty incidents, this is even more important because reports need to be shorter and faster. Age, gender, urgent findings, vital signs if available, and transport priority should come through in that order.
For trauma alerts specifically, receiving hospitals activate their trauma teams based on objective criteria you relay over the radio. The findings that trigger a full team response include oxygen saturation below 90%, respiratory rate under 10 or over 29 breaths per minute, systolic blood pressure below 90, heart rate above 120, and a Glasgow Coma Scale score of 12 or lower. Injuries like flail chest, unstable pelvic fractures, penetrating wounds to the torso or neck, and traumatic amputations above the wrist or ankle also qualify. If you’ve had to secure an airway, decompress a chest, apply a tourniquet, or administer any vasopressor medications in the field, relay that clearly because each of those interventions independently justifies trauma team activation.
For older patients, the thresholds are lower. A blood pressure under 100, a consciousness score of 14 or below with suspected head injury, fractures involving long bones after a vehicle crash, or injuries to two or more body regions all warrant alerting the hospital to a higher level of readiness.
Speak in Plain Language
The National Incident Management System has required plain language for any incident involving multiple agencies, jurisdictions, or disciplines since 2006. A follow-up directive in 2009 reinforced that “the use of plain language in emergency response is a matter of public safety, especially the safety of first responders and those affected by the incident.” Federal preparedness grant funding has been tied to this requirement since fiscal year 2006.
In practice, this means avoiding 10-codes, agency-specific shorthand, and jargon that a nurse, physician, or dispatcher from another system might not recognize. Say “difficulty breathing” instead of a numeric code. Say “unconscious” instead of a signal number. While there’s no federal mandate requiring plain language for routine single-agency operations, NIMS strongly encourages it for daily use so that crews are already comfortable with the terminology they’ll need during a large-scale event.
When you need to spell something out, such as a medication name, a street, or an alphanumeric identifier, use the NATO phonetic alphabet. Military and emergency service personnel are routinely trained in it for exactly this purpose. Saying “Ward November Two” is unambiguous in a way that “N-2” might not be over a noisy radio channel.
Technical Delivery: How You Sound Matters
Content is only useful if the receiving party can actually hear it. Hold your microphone two to four inches from your mouth and speak in a normal voice. If you tend to speak quietly, bring the mic closer. If you’re naturally loud, pull it back a bit. This simple adjustment prevents the distortion that comes from speaking directly into the mic and the faintness that comes from holding it too far away.
Speak at a measured pace. The instinct during a high-acuity call is to talk fast, but the person on the other end is often writing down what you say or entering it into a system. Pause briefly between sections of your report, especially between vital signs and the next category of information. If you’re in a loud environment (sirens, helicopter rotor, highway noise), shield the microphone with your hand and enunciate more deliberately rather than simply raising your volume.
Keep It Concise but Complete
Research on what emergency department staff actually want from radio reports identified 21 distinct elements that readers look for in a high-quality narrative. That sounds like a lot, but a well-structured report covers most of them naturally. The goal isn’t to read off every data point you’ve collected. It’s to give the receiving team exactly what they need to prepare the right room, the right equipment, and the right specialists before you arrive.
A practical radio report for a medical patient might sound like this: unit identification, patient’s age and sex, chief complaint with relevant history of the present illness, pertinent medical background, current vitals and mental status, what you’ve done so far, how the patient responded, and your estimated arrival time. For a trauma patient, swap in mechanism of injury, specific injuries found, field interventions performed, and any alert criteria that were met.
Before you key the mic, take a few seconds to organize your thoughts. Knowing what you’re going to say before you say it is the single most effective way to sound professional and deliver a report the receiving team can act on without asking you to repeat yourself.