the knowledge platform

quality improvement & patient safety

patient safety and qi concepts including swiss cheese model, root cause analysis, pdsa cycles, sentinel events, near misses, adverse events, handoffs, and systems thinking

preventive medicine & biostatisticscommonquality-safety

About This Page

This is a clinician-written, evidence-based summary aligned to the USMLE Step 2 CK Content Outline. It is intended for medical students preparing for USMLE Step 2 CK. Management reflects current ACC/AHA, USPSTF, and APA guidelines. Always cross-reference with UpToDate, institutional protocols, and clinical judgment.

The Bottom Line

  • Most medical errors are systems problems, not simply individual negligence; use just culture and systems thinking
  • Swiss cheese model: harm occurs when multiple layers of defense have aligned holes
  • Root cause analysis is retrospective and used after serious adverse events or sentinel events
  • PDSA cycles are prospective small tests of change: Plan, Do, Study, Act
  • Near miss = error that could have caused harm but did not; it should still be reported and analyzed

Overview

Quality improvement and patient safety questions test whether the clinician responds to error with transparency, reporting, systems analysis, and prevention rather than blame or concealment. Patient safety focuses on preventing harm; quality improvement focuses on making care more effective, efficient, equitable, timely, patient-centered, and safe. Step 2 CK commonly asks whether to perform root cause analysis, launch a PDSA cycle, disclose an error, report a near miss, or use a checklist/standardized handoff.

Epidemiology

Medical errors contribute substantially to preventable morbidity, mortality, cost, and loss of trust. High-risk settings include transitions of care, medication prescribing/administration, surgery/procedures, diagnostic handoffs, abnormal test result follow-up, infection control, and communication across teams. Safety science emphasizes that frontline errors often reflect latent system conditions such as poor interface design, understaffing, fatigue, unclear responsibility, interruptions, look-alike/sound-alike medications, and inadequate feedback loops.

Safety Event Recognition

Symptoms
Adverse event: patient harm caused by medical care rather than underlying disease
Preventable adverse event: harm that could have been avoided with appropriate systems/processes
Near miss: error reaches no harm because it is caught or luck intervenes
Sentinel event: unexpected event involving death, serious physical/psychological injury, or risk thereof
Never event: serious, largely preventable event such as wrong-site surgery or retained foreign object
Diagnostic error: missed, delayed, or wrong diagnosis with potential or actual harm
Signs
Latent error: hidden system flaw such as confusing medication labels, poor staffing, or unsafe workflow
Active error: frontline action such as administering wrong medication
Handoff failure, unclear task ownership, or missing closed-loop communication is a common cause of harm
Culture of blame reduces reporting; just culture encourages reporting while maintaining accountability for reckless behavior

Analysis Tools

First-line
Root cause analysisRetrospective structured analysis after serious harm/sentinel event. Asks what happened, why it happened, and how to prevent recurrence
PDSA cyclePlan a change, Do small-scale test, Study results, Act by adopting/adapting/abandoning. Used prospectively for quality improvement
Process mappingMaps each step in a care process to identify bottlenecks, handoffs, duplication, and failure points
Second-line
Failure mode and effects analysisProspective risk assessment that identifies how a process might fail before harm occurs
Run chart / control chartTracks performance over time. Control charts distinguish common-cause from special-cause variation
Fishbone/Ishikawa diagramOrganizes possible causes into categories such as people, process, environment, equipment, materials, and policy
Specialist
Safety event reporting systemCaptures adverse events and near misses for learning; reporting should be easy, nonpunitive, and feedback-producing
Human factors assessmentEvaluates design, usability, workload, interruptions, alarms, cognitive load, and environmental contributors to error
1
Immediate response to an error
  • Stabilize and treat the patient first
  • Disclose the error honestly and promptly to the patient/family with apology and known facts
  • Report through institutional safety system
  • Document clinically relevant facts objectively in the medical record
  • Do not falsify records, hide the event, or blame another team member in front of the patient
2
Root cause analysis after serious event
  • Assemble interprofessional team including frontline staff involved in process
  • Create timeline and identify active failures and latent conditions
  • Ask repeated "why" questions without focusing on individual blame
  • Generate strong corrective actions: forcing functions, standardization, simplification, automation, checklists, and redundancy
  • Assign owners, deadlines, and measurable follow-up
3
PDSA for improvement
  • Define aim statement: specific, measurable, time-bound goal
  • Choose process, outcome, and balancing measures
  • Test change on small scale before wider implementation
  • Study data and adapt intervention iteratively
  • Scale only after evidence of improvement and no unacceptable balancing harm
4
Common safety interventions
  • Standardized handoff tools such as I-PASS or SBAR
  • Surgical time-outs and checklists
  • Medication reconciliation at transitions of care
  • Barcode medication administration and tall-man lettering for look-alike/sound-alike drugs
  • Closed-loop communication for critical results and urgent tasks

Complications

  • Patient harm: Death, disability, prolonged hospitalization, infection, medication toxicity, or missed diagnosis
  • Second victim phenomenon: Clinicians involved in errors may experience guilt, shame, anxiety, depression, and burnout
  • Loss of trust: Concealment or poor communication worsens patient/family distress and medicolegal risk
  • Recurring harm: Failure to analyze near misses and latent conditions allows the same error to happen again
  • QI unintended effects: Narrow metrics can cause gaming, neglect of unmeasured care, or new workflow burdens
USMLE Step 2 CK Exam Tips
  • 1Serious adverse event after it happened = root cause analysis
  • 2Testing a small improvement prospectively = PDSA cycle
  • 3Near miss should still be reported; no harm does not mean no learning
  • 4Swiss cheese model = multiple defense layers fail simultaneously
  • 5Always disclose medical errors honestly to the patient after stabilizing them
  • 6Do not punish a single nurse/doctor as the main intervention for a systems error
  • 7Wrong-site surgery prevention = time-out/checklist before incision
  • 8Medication reconciliation is especially important at admission, transfer, and discharge
practicetest your knowledge on quality improvement & patient safetyApply what you've learnt with USMLE Step 2 CK-style questions from the iatroX Q-Bank — preventive medicine and beyond.
open q-bank

Verified Sources & References

AHRQ Patient Safety Network
AHRQ TeamSTEPPS
Institute for Healthcare Improvement — How to Improve
The Joint Commission Sentinel Event Policy