Compare two calls a registrar might receive at 2am. The first: "Hi, sorry to bother you, the patient in bed 4 doesn't look right, could you come?" The second: "I'm reviewing a 72-year-old admitted yesterday with pneumonia who is newly hypotensive at 82/48 despite 500 millilitres of crystalloid; she's tachycardic at 118, alert, peripherally cool; I've started my sepsis assessment and repeated cultures; I think she may need escalation beyond the ward and I'd like you to see her now." Both calls come from the same worried FY1 about the same patient. One transmits worry; the other transmits the patient. Learning to make the second call is among the most valuable skills of the first year, and it is entirely learnable.
Problem representation: the one-sentence patient
The skill underneath the skill is problem representation: compressing a patient into one sentence that carries the clinically relevant shape. Who (age, relevant background), what (the presenting problem and its trajectory), and the key finding that makes this a call at all. "A 72-year-old with pneumonia who is newly hypotensive despite fluid" is a problem representation; "the lady in bed 4" is a location. Building the sentence forces the assessment: you cannot represent a problem you have not examined, which is why the discipline of composing it improves your medicine, not just your phone manner. It is also, not coincidentally, exactly the skill clinical reasoning teaching tries to build, and the one the iatroX Tutor drills when it asks what you concluded and what supports it.
SBAR: the container
SBAR exists because 2am brains need containers. Situation: who you are, where you are, the one-sentence patient. Background: the relevant history in two or three lines, admission reason, key comorbidities, current treatment. Assessment: what you found and what you think, including the observations with their trend, not just their values. Recommendation, better read as request: what you are asking for, by when. The order matters less than the completeness; the registrar is assembling a picture, and SBAR is simply the parts list.
Say your uncertainty out loud
The counterintuitive move that marks a safe doctor: state your degree of uncertainty explicitly. "I think this is fluid-responsive hypotension but I'm not confident" or "I can't decide whether this breathlessness is failure or infection" is not weakness; it is calibration, and it tells the senior exactly what kind of help to send. The dangerous FY1 is not the uncertain one; it is the one who converts uncertainty into false confidence to sound competent on the phone. Seniors triage partly on your worry; give them accurate worry.
What you have already done
Before the call, do what is safely yours to do, and then say it: the assessment completed, the observations repeated, the bloods sent, the fluid started per protocol, the ECG done. This is not about proving industriousness; it changes the conversation from "go and assess" to "here is my assessment, what next", which gets your patient senior input one whole cycle faster. The exception is equally important: when the patient is peri-arrest, the first thing you have done is call for help, and everything else follows.
Know what you are actually asking
Every call has a request hiding in it; find yours before dialling. Come and see the patient now. Talk me through the next step. Sanction my plan. Take over. Teach me for two minutes so I can handle the next one. Vague calls happen when the caller has not decided which of these they need; the registrar then has to extract it, at 2am, from someone anxious. Decide, ask directly, and if the answer is "you can manage this", ask the follow-up that turns the call into education: what would change your mind?
The meta-skill
Every call you make is also training your judgement for the next one. Afterwards, thirty seconds of reflection: was my representation accurate, did my worry match the reality, what will I recognise earlier next time? This loop, case, representation, feedback, adjustment, is clinical reasoning practice in its purest form, and it is exactly the loop worth drilling deliberately between shifts; five minutes a day on structured cases builds the pattern library the phone calls draw on, which is precisely what the Tutor's Socratic dialogue is for.
Frequently asked questions
What if the registrar is dismissive or annoyed?
Your job is the patient, not the registrar's mood; a structured call with stated worry is defensible every time, and persistent concern justifies the next rung, your consultant or outreach, without apology. Document the conversation either way.
Is it acceptable to read from notes during the call?
Not just acceptable, recommended. Write the SBAR before dialling for anything complicated; nobody was ever criticised for a call that was too organised.