Root cause analysis and sentinel events
- US frame (USMLE)
After a patient is seriously harmed, the useful question is not ‘who did it?’ but ‘why did the system let it happen?’. Root cause analysis answers it.
What it is
Root cause analysis (RCA) is a structured, multidisciplinary review of an adverse event or a close call that asks what happened, why it happened and how to prevent it, focusing on how and why rather than who. A sentinel event is a patient safety event, not primarily related to the natural course of the illness, that results in death, permanent harm or severe temporary harm; in the US the Joint Commission, the main hospital accreditor, expects an RCA and an action plan for each one. The analysis ends in changes to the system and in measures that check they work.
Compared with Colombia’s SGSSS
- Colombia’s patient safety policy uses the London protocol for the same reactive job: it sorts contributory factors (patient, task, individual, team, environment, organisation) where a US team often uses a fishbone and five whys.
- Trigger: in the US an RCA is expected after a sentinel event and is useful after a close call; in Colombia the SOGCS asks institutions to analyse adverse events and incidents.
- Both are non-punitive by design: the VA method looks at how and why, not who; the Colombian policy asks for a climate of confidentiality and trust.
Worked example
- A made-up hospital: a 52-year-old has arthroscopy on the left knee instead of the right. Wrong-site surgery is a sentinel event.
- The patient is told and supported. Within days a team forms: a surgeon and a nurse not involved, an anaesthetist, the quality lead and a risk manager.
- Timeline: consent says right knee, the theatre list says left, the site was not marked, and the time-out took 20 seconds with the circulating nurse out.
- Five whys: the leg was prepared from the theatre list; the list was typed from a handwritten request; nobody checked it against the consent.
- Fishbone: 3 contributing factors on 3 bones: procedures (no marking step), communication (handwritten request), people (time-out rushed).
- Root causes: the list could be built without matching laterality to the consent, and the time-out could start without the whole team.
- Actions, strongest first: the system blocks a case whose side does not match the consent; a time-out read aloud by all; a reminder memo.
- Measure: audit 200 cases over 3 months. Site marked in 196 (98 %); full-team time-out in 190 (95 %).
- Reading: nobody was fired. The fix sits in the process, and the audit shows whether it is working.
RCA and its look-alikes
| Feature | RCA | FMEA | Blame-focused review |
|---|---|---|---|
| When | After an adverse event or close call | Before harm, on a new or risky process | After an event |
| Question | Why did the system allow it? | How could this process fail, and how badly? | Who made the error? |
| Typical tools | Timeline, fishbone diagram, five whys | Process map, failure modes ranked by risk | Interviews about individual fault |
| Typical result | System changes plus measures | Barriers built before anything goes wrong | Discipline; latent failures remain |
Markers
- RCA
- Sentinel event
- Close call
- Fishbone
- Five whys
- FMEA
Common traps
- An RCA is done only after a patient is harmed: close calls are analysed too, because they show the same holes without the harm
- The root cause is the person who made the error: an RCA looks for system causes (design, process, communication); stopping at a person usually means the analysis ended too early
- Retraining staff and writing a new policy are strong actions: they rely on memory and are weak; forcing functions, standardisation and simplification are stronger
- A sentinel event is any adverse event: it is the most serious kind (death, permanent harm or severe temporary harm) and is not caused mainly by the illness itself
- The RCA decides whether to tell the patient: disclosure is a separate duty owed to every harmed patient; the RCA exists to prevent the next case
Test yourself
Think of the answer, then tap the question to see it.
An RCA after a wrong-patient transfusion concludes ‘the nurse did not follow policy’ and recommends retraining. Why is this a weak result?
It stops at a person and relies on memory. A deeper analysis asks why the policy could be skipped and adds stronger fixes, such as bedside scanning that blocks a mismatched blood bag.
A wrong drug is drawn up but caught before it reaches the patient. Is an RCA worth doing?
Yes, it can be: a close call shows the same system weakness without harm, so it is cheaper to learn from. The VA approach analyses close calls as well as adverse events.
Which is a sentinel event: death from the expected progression of metastatic cancer, or a sponge left in the abdomen that needs a second operation?
The retained sponge: severe harm caused by care. Death from the natural course of the illness is not a sentinel event.
How does FMEA differ from RCA in when it is used?
FMEA is prospective: it maps a process before harm and ranks how it could fail. RCA is retrospective: it starts from an event or close call that has already happened.
Elsewhere in DurgiPedia
Connections
Educational content on epidemiological and statistical methods; the examples use made-up numbers to teach the calculation. Not a clinical or legal guide: current Colombian rules are in the official sources.
Sources: Root Cause Analysis - VHA National Center for Patient Safety (US Department of Veterans Affairs, 2025); Guidance for Performing Root Cause Analysis (RCA) with Performance Improvement Projects (PIPs) (Centers for Medicare & Medicaid Services, 2026); Patient safety (World Health Organization, 2023).
Spotted a mistake?We are always improving for the community. Tell us what is wrong and our team will review it.Report a mistake
Representative model, for educational purposes only.
