Root Cause Analysis in Nursing
On this page
Direct answer
Bad outcomes rarely have one villain — they have a chain: a look-alike vial stored beside its twin, a short-staffed night, an unwritten handover habit, a warning nobody owned. Root cause analysis (RCA) is the structured, retrospective method a team uses after a sentinel event or serious adverse event to expose that chain: build a timeline, ask why repeatedly (the five-whys discipline), map contributing factors on a fishbone (Ishikawa) diagram, write causal statements linking causes to the event, and design corrective actions that change the system rather than lecture the person. Its founding assumption is just culture — errors are symptoms of system weaknesses, and blaming individuals merely drives reporting underground. Accreditation bodies, including NABH in India, expect an RCA after sentinel events, commonly completed within weeks.
What you must remember
- Trigger events: sentinel events — death, permanent harm or severe temporary harm (wrong-site surgery, inpatient suicide, a fatal fall, a wrong-blood transfusion) — convene an RCA, commonly within 30-45 days of the event.
- Team: small and multidisciplinary, including staff close to the event but not involved in it, led by someone trained in the method.
- Sequence: fact-gathering from records, interviews and equipment → timeline flowchart → identify the care and service delivery problems → ask why down to root causes → fishbone mapping → causal statements → corrective actions with owners and deadlines.
- Five whys: keep asking why of each answer until the causes become systemic and actionable — stop at the layer where change is possible.
- Fishbone categories (adapted): people, methods and processes, equipment and technology, environment, materials, management and policy.
- Causal statement rules: show a clear cause-and-effect link, be specific, and never name or blame individuals — "the nurse failed" is banned, "the night crossover was unverifiable because..." survives.
- Action strength hierarchy: stronger actions (forcing functions, standardisation, embedded system changes) outlast weaker ones (reminders, retraining alone); pair every weak action with a strong one.
- RCA versus FMEA: RCA looks backward after an event; failure mode and effects analysis looks forward, predicting failures before they harm — the examiner's favourite pairing.
RCA after a night fall
An 84-year-old man falls at 3 a.m., strikes his head and dies; the hospital convenes an RCA. The timeline: a sedative at 10 p.m.; one bed rail raised, the other lowered; the call bell on the far side of the bed; found on the floor at 3:05; the fall itself unobserved. The whys: why did he get up unaided? To urinate. Why unaided? He was drowsy and the bell was out of reach. Why out of reach? It was not repositioned after the evening linen change. Why not repositioned? Bedside checks were not on the rounding checklist. Why was a fall-risk patient sedated without a toileting plan? Because the admission risk score was recorded but never acted upon — the form ends at scoring. Each why moves one layer outward from the bedside to system design. The fishbone sorts the findings — people: no scheduled night toileting; process: scoring without action; equipment: bell placement; environment: dim corridor; management: a falls policy with no monitoring loop. Actions follow with owners and dates — hourly rounding with fixed toileting, bell checks on the round, low beds for high-risk patients, sedation review, and a re-audit — and the final report never once writes "she should have been more careful".
The blame reflex
The reflex the method exists to defeat is ending the analysis at "nurse error" — which is where untrained teams stop, and exactly where the exam distractor sits. Given a list of findings, the wrong options name individuals while the right ones name system conditions. Remember the pairing: RCA is retrospective (after the event), FMEA prospective (before harm); both are systems tools, not personnel tools. And the viva line worth memorising: human error is the beginning of an RCA, never its conclusion.
Frequently asked questions
What is a sentinel event?
An unexpected occurrence involving death or serious physical or psychological harm — wrong-site surgery, inpatient suicide, a fatal fall — which triggers root cause analysis.
What are the five whys?
The discipline of asking "why" of each answer until system-level causes surface — the questioning core of root cause analysis.
What does a fishbone diagram do in RCA?
It sorts contributing causes into categories such as people, process, equipment, environment and management, exposing the system weaknesses behind an event.
How does RCA differ from failure mode and effects analysis?
RCA works backwards after an actual event; FMEA works forwards, mapping how a process could fail and prioritising fixes before harm occurs.
Why is blame avoided in root cause analysis?
A just culture treats error as a symptom of system weakness — blame suppresses reporting and leaves the real causes intact to recur.