🎭 Interprofessional Team Communication Simulation (SBAR)

Patient Deterioration & the Escalation Trigger

Most in-hospital cardiac arrests are not sudden. Studies show that 70–80% of patients exhibit measurable physiological deterioration in the 6–8 hours before an arrest — abnormal vital signs that were noticed but not effectively communicated up the chain. The moment of recognition is only useful if it triggers a structured, unambiguous escalation.

• 70–80%: Deterioration before arrest (of patients show warning signs 6–8h prior)
• ~70%: Communication-linked sentinel events (Joint Commission root-cause data)
• ≥5: Early Warning Score threshold (triggers mandatory escalation (NEWS2))
• ~30%: Failure-to-rescue contribution (of preventable inpatient deaths)

Why recognition alone is not enough

Nurses are usually the first to detect subtle deterioration — a rising respiratory rate, a falling urine output, a patient who "just doesn't look right." Early Warning Score (EWS/NEWS2) systems assign points to heart rate, blood pressure, respiratory rate, SpO₂, temperature, and consciousness level; a composite score above a threshold mandates escalation within a defined time window.

But recognizing a problem and successfully transferring that concern to a decision-maker are two different skills. Research on "failure to rescue" — death following a treatable complication — consistently identifies the gap not in clinical knowledge but in communication: nurses who correctly identify a problem often struggle to convey the appropriate urgency to a physician who cannot see the patient and is triaging multiple simultaneous demands.

A seminal 2004 review of malpractice claims found that ineffective handoff communication was a contributing factor in over 60% of adverse events — more than any single clinical or technical failure.

The hierarchy gradient problem

One of the most persistent barriers to escalation is the steep authority gradient in medicine. Junior nurses calling senior physicians — especially at night, especially about an "unclear" concern — face real social pressure to soften language, bury the concern in hedges, or avoid the call altogether.

This is not a hypothetical: several high-profile pediatric and obstetric sentinel events have been traced directly to a nurse who noticed deterioration but whose warning was diluted, dismissed, or never escalated at all. Structured communication tools exist specifically to flatten this gradient — a nurse using SBAR is not "bothering" a physician with vague worry, she is delivering a standardized clinical data package that both parties recognize as a legitimate escalation.

From individual vigilance to a systems response

Modern rapid-response systems pair the "afferent limb" (detection and escalation, usually EWS-triggered) with an "efferent limb" (a dedicated responding team — rapid response team, medical emergency team, or the primary physician). SBAR functions as the connective tissue between these two limbs: it is the exact message format the afferent limb uses to activate the efferent limb.

Hospitals that pair EWS triggers with mandatory SBAR-formatted callouts report measurably shorter time-to-intervention and fewer unplanned ICU transfers, because the receiving clinician gets a complete, prioritized picture in the first 30–45 seconds of the call rather than piecing it together through follow-up questions.

Opening the Call — Situation and Background

SBAR structures a clinical conversation into four deliberate movements. The first two — Situation and Background — exist to get the receiving clinician oriented fast: who is this patient, what is wrong right now, and what context makes that problem meaningful. Nothing here is opinion; it is verifiable fact delivered in a fixed order.

• 1990s: SBAR origin (adapted from US Navy nuclear submarines)
• 2002–04: Healthcare adoption (Kaiser Permanente, Dr. Michael Leonard)
• <45 sec: Target call opening time (to state Situation + Background)
• >85%: Hospitals using SBAR (US, 2023) (of acute-care facilities)

Where SBAR came from

SBAR was not invented in a hospital. It originated in the U.S. Navy's nuclear submarine service, where officers needed a terse, standardized way to brief a commanding officer on a developing situation without wasting time or omitting anything mission-critical — an environment where an incomplete report could be catastrophic and there is no room for ambiguity.

In the early 2000s, physician Dr. Michael Leonard and colleagues at Kaiser Permanente, working with former submarine officers through a patient-safety collaboration, adapted the military framework for clinical handoffs. The Institute for Healthcare Improvement (IHI) subsequently popularized SBAR as a core patient-safety tool, and it is now taught in nearly every nursing and medical curriculum in the developed world.

The same structural discipline that keeps a submarine crew synchronized under pressure — situation first, context second, opinion third, ask last — turned out to map almost perfectly onto the bedside-to-physician phone call.

Situation — the 15-second headline

"Situation" answers four questions in a single breath: Who am I, who is the patient, what is the immediate problem, and how urgent is it? For example: "This is Sarah, RN on 4 West. I'm calling about Maria Chen in bed 12. She's acutely short of breath and her oxygen saturation has dropped to 89% — I need you to come see her now."

The discipline here is brevity. A rambling opening buries the urgency signal; the receiving clinician has to actively extract the actual problem from a wall of narrative. SBAR training explicitly drills callers to lead with the headline, not the backstory.

Background — just enough context

"Background" supplies the minimum clinical context needed to interpret the Situation correctly: admitting diagnosis, date of admission, relevant history, current medications, code status, and recent trend in vital signs. It is not a full chart review read aloud — it is curated.

Common Background elements for a deteriorating post-op patient: "She's post-op day 2 from a bowel resection, history of hypertension and type 2 diabetes, currently on IV antibiotics for suspected wound infection. Her heart rate has climbed from 88 to 128 over the last two hours and her blood pressure has trended down from 128/78 to 84/50." This single sentence often tells an experienced physician most of what they need before the Assessment is even given.

Assessment — Sharing Clinical Judgment Across Roles

Assessment is the most psychologically difficult component of SBAR because it requires the reporting clinician to commit to an opinion — "I think this patient is septic" — rather than simply relaying data. It is also the point where other disciplines, especially pharmacy, are pulled into the loop to verify the picture from their own vantage point.

• ~54%: Nurses reporting fear of speaking up (surveyed pre-SBAR training)
• ~30%: Reduction after SBAR/CUS training (drop in reported reluctance)
• 1 in 5: Medication errors caught at reconciliation (admissions have a discrepancy)
• ↓ 25–30%: Pharmacist-involved rapid responses (adverse drug event rate)

From data to judgment

Where Situation and Background are objective, Assessment asks the reporting clinician to synthesize: "Putting this together, I think she's developing septic shock" or "I'm concerned this is a pulmonary embolism." This single sentence carries enormous communicative weight — it tells the receiving physician not just what the numbers are, but what the nurse believes they mean.

Many hospitals pair SBAR with the "CUS" escalation phrase set (I am Concerned / I am Uncomfortable / this is a Safety issue) for situations where the Assessment is being dismissed. CUS words are trained as a verbal "circuit breaker" — when spoken, policy requires the listener to stop and actively re-engage, regardless of hierarchy.

TeamSTEPPS training data shows that clinicians who are explicitly taught to state an Assessment — rather than just relay data and hope the listener draws the same conclusion — are significantly more likely to have their concern acted on within the target window.

Bringing pharmacy into the loop

A deteriorating patient is rarely a purely "medical" problem in isolation — medications are frequently implicated, either as a cause (an unrecognized drug interaction, an accumulating renally-cleared drug in a patient with worsening kidney function) or as part of the fix (correct antibiotic selection and dose for suspected sepsis, appropriate vasopressor titration).

Medication reconciliation at this stage means the pharmacist cross-checks the full medication administration record against the new clinical picture: is there a drug that could be causing or masking these vitals? Is the proposed antibiotic appropriate for renal function and known allergies? Roughly one in five hospital admissions carries at least one unintentional medication discrepancy — surfacing it during the Assessment phase, rather than after an order is written, prevents it from compounding the emergency.

Shared mental models

The goal of the Assessment phase is not just information transfer — it is the creation of a shared mental model across roles. TeamSTEPPS, the evidence-based teamwork system developed jointly by the U.S. Department of Defense and the Agency for Healthcare Research and Quality (AHRQ), formalizes this concept: a high-performing team is one where every member holds the same up-to-date picture of the patient's status, the plan, and their own role in executing it.

When the nurse, physician, and pharmacist each restate their understanding of the working diagnosis before moving to Recommendation, discrepancies surface immediately — while they are still cheap to correct — rather than downstream, after orders are already in motion.

Recommendation and Closed-Loop Confirmation

SBAR closes with a specific, actionable Recommendation — and every order that follows is confirmed using closed-loop communication: the sender states the instruction, the receiver repeats it back verbatim, and the sender confirms the read-back is correct. This three-step loop is one of the single most effective, lowest-cost interventions in patient-safety science.

• ~90%+: Closed-loop error interception rate (of verbal-order errors caught at read-back)
• ~35%: Verbal/telephone orders in EDs (of all orders in high-acuity settings)
• Mandatory: Read-back adoption (Joint Commission NPSG) (since 2006 for verbal/telephone orders)
• 1979: CRM origin (aviation) (NASA workshop after 1978 Portland crash)

The Recommendation — asking for something specific

A well-formed Recommendation is concrete and time-bound: not "can you check on her" but "I need you at the bedside within 10 minutes" or "can we start a 500 mL normal saline bolus and order a lactate now?" Vague recommendations invite vague responses; specific ones invite specific action.

Where the physician cannot come immediately, the Recommendation phase is also where explicit verbal orders are given over the phone — and every one of those orders is exactly where closed-loop communication becomes mandatory rather than optional.

Closed-loop communication, step by step

Closed-loop communication has three explicit steps:

1. Call-out — the sender states the instruction clearly and directs it to a specific person ("Sarah, give 500 mL normal saline bolus now") 2. Check-back — the receiver repeats the instruction back verbatim, in their own voice, before acting ("Giving 500 mL normal saline bolus now") 3. Closure — the original sender confirms the read-back is correct ("That's correct") or corrects it immediately if it is not

The entire loop typically takes under 10 seconds, yet it is one of the highest-yield interventions available: because errors most often occur in the moment of transmission — a misheard dose, a transposed digit, a name confused for another patient — closing the loop catches the error before it reaches the patient rather than after.

The Joint Commission's National Patient Safety Goals have required read-back verification of all verbal and telephone orders since 2006 — closed-loop communication is not a best practice, it is an accreditation requirement in accredited U.S. hospitals.

Crew Resource Management — the aviation parallel

Closed-loop communication and structured escalation both trace back to Crew Resource Management (CRM), developed by NASA and the airline industry after a string of accidents in the 1970s where the technical cause was survivable but the crew failed to communicate effectively under pressure. The best-known case is United Airlines Flight 173 (Portland, 1978): the crew became fixated on a landing-gear indicator light and ran out of fuel while junior crew members, aware of the falling fuel level, did not assertively challenge the captain in time.

The resulting NASA workshop in 1979 produced CRM: standardized phraseology, mandatory read-backs between pilot and air traffic control, and explicit training for junior crew to assertively escalate concerns regardless of rank. Healthcare's adoption of SBAR, closed-loop communication, and CUS phrases in the 2000s is a direct, deliberate import of CRM principles — TeamSTEPPS itself was co-developed with aviation human-factors experts.

Where closed loops break down

Closed-loop communication fails predictably under certain conditions: extreme noise or chaos (a full code, a mass-casualty event), competing simultaneous verbal instructions from multiple people, fatigue, and — critically — hierarchy gradients where a junior team member is reluctant to interrupt a senior clinician to check back an order they didn't fully hear.

High-reliability teams counter this by making closed-loop communication the social norm rather than a special-occasion behavior: every verbal order, every time, gets a read-back, so that doing it never singles anyone out and skipping it feels conspicuously wrong.

SBAR components with example phrases

Outcome — Response Time, Errors, and Team Score

The measurable payoff of structured SBAR communication and closed-loop confirmation is not abstract: hospitals that implement it rigorously see faster escalation-to-intervention times, fewer missed or garbled orders, and measurably higher scores on validated teamwork assessment instruments. This final stage totals the exchange into a team communication score.

• ↓ ~50%: Adverse event reduction (IHI data) (sites with mature SBAR programs)
• 60 min: Golden hour for sepsis bundle (from recognition to antibiotics/fluids)
• ↓ 20–30%: Unplanned ICU transfers (with EWS + SBAR escalation pathways)
• >4,000: TeamSTEPPS rollout (US hospitals) (sites trained since AHRQ/DoD launch (2006))

What "team communication score" actually measures

A team communication score aggregates several observable behaviors rather than a single number: was every SBAR component present (Situation, Background, Assessment, Recommendation)? Was every verbal order closed-loop confirmed? Was the total time from recognition to intervention within the target window? Were any CUS escalation phrases needed, and were they honored?

Validated instruments used in simulation and real-world debriefing — such as the TeamSTEPPS Teamwork Attitudes Questionnaire (T-TAQ) and structured SBAR audit checklists — convert these behaviors into a composite score, typically normalized to 100, used both for individual team feedback and hospital-wide quality tracking.

The measurable clinical payoff

Institutions that have implemented structured handoff and closed-loop training report consistent, replicated benefits: the Institute for Healthcare Improvement's SBAR collaborative sites reported roughly a 50% reduction in adverse events tied to communication failures. Sepsis-bundle compliance — fluids and antibiotics delivered within the "golden hour" of recognition — improves measurably when the initial escalation call uses a structured format instead of an unstructured page, because the receiving physician can act on the first call rather than needing two or three follow-up questions to understand the situation.

Unplanned ICU transfers, a proxy for "the ward team recognized deterioration too late," also fall meaningfully at hospitals running combined EWS-plus-SBAR escalation pathways.

None of these gains come from new equipment or new drugs. They come entirely from disciplining how three or four humans exchange eleven sentences of information under time pressure — arguably the highest return-on-investment intervention in modern patient safety.

Training level and urgency both matter

Simulation and real-world data agree on two modifiers of performance: team training level and scenario urgency. Novice or newly-formed teams take longer to complete a full SBAR exchange and are more likely to skip or truncate closed-loop read-backs, especially under high urgency, when the instinct is to "just move fast" rather than confirm. Expert, high-training teams paradoxically get faster and more accurate simultaneously — the structure becomes automatic rather than effortful, freeing cognitive capacity for the actual clinical problem.

High scenario urgency (a critical, rapidly deteriorating patient) compresses available time and raises stress, which is exactly when structured communication protocols matter most and are hardest to maintain — which is why deliberate practice through simulation, like this exercise, is considered essential rather than optional for high-stakes clinical teams.