Handoffs & Communication (SBAR)
Handoffs are high-risk care transitions where communication failures drive sentinel events; SBAR structures urgent clinical messages while I-PASS structures shift sign-out. Closed-loop read-back plus the two-challenge/CUS escalation tools are the board-favored, systems-level fixes over individual blame.
Why handoffs & SBAR are tested
Handoffs—the transfer of patient information and responsibility during transitions of care (shift change, unit transfer, ED-to-floor admission, OR-to-PACU)—are among the highest-risk moments in medicine. Communication failures are a leading root cause of sentinel events reported to the Joint Commission, and errors cluster at these transitions where information is dropped or garbled. The boards frame handoffs as a systems problem: the fix is a standardized, structured, closed-loop process—not blaming the individual who forgot a critical result. SBAR (Situation, Background, Assessment, Recommendation)—adapted from US Navy nuclear-submarine communication and brought into healthcare at Kaiser Permanente—is the classic scripted framework for any urgent clinical message: nurse-to-physician calls, escalation of a deteriorating patient, or a consult request. It gives the message a predictable shape so nothing vital is lost.
- SBAR = Situation, Background, Assessment, Recommendation — the scripted format for an urgent clinical message (e.g., a nurse paging about a deteriorating patient).
- S: patient, location, the acute problem right now ("Mr. X in 402 is hypotensive, BP 80/40").
- B: pertinent context—diagnosis, relevant history, meds, recent vitals/labs trend.
- A: your read of the situation ("I think he's septic").
- R: a specific ask ("Please come evaluate now; can we start fluids and cultures?").
- Closed-loop / read-back: receiver records and repeats verbal orders and critical values back to confirm—required for telephone orders and critical results (Joint Commission NPSG).
- I-PASS is the evidence-based handoff bundle; implementation cut medical errors ~23% and preventable adverse events ~30% (Starmer, NEJM 2014).
- Board reflex: to prevent handoff error → standardize the process, don't counsel/blame the individual.
Communication tools compared
| Tool | Use case | Components / action |
|---|---|---|
| SBAR | Urgent clinical message / escalation | Situation, Background, Assessment, Recommendation |
| I-PASS | Structured shift handoff / sign-out | Illness severity, Patient summary, Action list, Situation awareness & contingency, Synthesis by receiver |
| Read-back (closed-loop) | Verbal/telephone orders, critical labs | Receiver records and repeats the order/value back to the sender to confirm |
| Two-challenge rule | Concern initially ignored | Voice the safety concern at least twice until acknowledged |
| CUS | Graded assertiveness / escalation | "I'm Concerned, I'm Uncomfortable, this is a Safety issue" |
Vignette: At 2 AM a nurse pages the on-call intern about a 68-year-old on post-op day 1 with BP 82/48, HR 122, temp 38.9°C, and new confusion. The call is rushed and disorganized, and the intern can't build a coherent picture.
Best communication approach → SBAR. Situation: "Mrs. R in 512 is hypotensive and confused." Background: "POD1 colectomy, now febrile, HR 122." Assessment: "I'm worried about sepsis." Recommendation: "Please come now; can we draw blood cultures, start IV fluids, and give broad-spectrum antibiotics?"
Teaching point / next best step: When the stem asks how a nurse should communicate a deteriorating patient—or how to reduce miscommunication during escalation—the answer is the structured SBAR report, not vague options like "call the attending" or "increase monitoring."
Vignette 1 — read-back. A physician gives a verbal telephone order for "heparin 5,000 units subcutaneous." Best next step to prevent error → the nurse records it and reads it back verbatim ("heparin 5,000 units subcutaneous—confirm?") before administering. This closed-loop read-back is required for verbal/telephone orders and for critical lab values (Joint Commission NPSG), and it forces the physician to specify any missing drug, dose, route, or frequency.
Vignette 2 — speaking up. A resident notices the attending about to operate on the wrong side, but the first comment is waved off. Best action → invoke the two-challenge rule using CUS language ("I'm Concerned, I'm Uncomfortable—this is a Safety issue"), and if still unresolved, stop the line. Voicing a safety concern at least twice to ensure it is heard overrides hierarchy when patient safety is at stake.
SBAR — Situation · Background · Assessment · Recommendation
I-PASS (handoff bundle):
- I — Illness severity (stable / watcher / unstable)
- P — Patient summary
- A — Action list (to-dos)
- S — Situation awareness & contingency planning ("if X, then do Y")
- S — Synthesis by receiver (read-back of the handoff)
CUS — Concerned · Uncomfortable · Safety issue (graded assertiveness to escalate a concern)
- Deteriorating patient, need to escalate → communicate with SBAR.
- Verbal/telephone order or critical lab value → record and read-back to confirm (closed-loop).
- Recurrent handoff errors on a service → implement a standardized handoff (I-PASS); don't single out one resident.
- Safety concern dismissed by a senior → two-challenge rule / CUS, then stop the line.
- Root cause of a sentinel event → most often a communication failure at a transition of care.
- Good handoffs are interactive/two-way, face-to-face when possible, in a quiet setting with minimal interruptions, and include a read-back/synthesis by the receiver.
- Just culture: pair standardization with non-punitive error reporting—systems fix > individual blame.
Practice Patient Safety now
Board-style questions, spaced-repetition flashcards, and a Socratic AI tutor — free to start.