Home / Learn / Sentinel Events & RCA
Guide

Sentinel Events & Root Cause Analysis (RCA) for Indian Hospitals

When something goes seriously wrong, NABH doesn't want blame — it wants understanding. This guide explains what counts as a sentinel event, how to run a proper root cause analysis, and how to close the loop with corrective and preventive actions that actually stick.

Quick answer: A sentinel event is a serious, unexpected patient-safety event causing death or major harm. NABH requires hospitals to report it, run a structured, blame-free root cause analysis (RCA) using tools like the 5 Whys and fishbone diagram, and implement corrective and preventive actions (CAPA) tracked to closure. The goal is fixing the system, not punishing the individual.

What is a sentinel event?

A sentinel event is an unexpected occurrence involving death or serious physical or psychological injury to a patient — one not related to the natural course of their illness. The name captures the idea: these events "sound a signal" that demands immediate investigation. Classic examples include:

  • Surgery on the wrong patient, wrong site, or wrong procedure
  • A retained instrument or sponge after surgery
  • A serious medication error causing harm or death
  • A haemolytic transfusion reaction (ABO incompatibility)
  • Patient suicide in a setting providing round-the-clock care
  • Infant abduction or discharge to the wrong family
  • A serious patient fall resulting in death or major injury

Sentinel, adverse, and near-miss — the difference

TermWhat it meansHarm level
Near missAn error caught before it reached the patientNo harm
Adverse eventAn unintended injury caused by care, not the illnessSome harm
Sentinel eventA severe event causing death or major harmSerious / fatal

NABH expects hospitals to capture all three. Near misses are gold — they reveal weak system defences before a patient is harmed, and a healthy reporting culture surfaces many of them.

What is root cause analysis (RCA)?

Root cause analysis is a structured method for finding why an event happened — the underlying system failures, not the individual at the sharp end. Its founding principle is blame-free (just culture): most serious events result from several latent system weaknesses lining up, not a single careless person. If staff fear punishment, they stop reporting, and the hospital goes blind.

The RCA process, step by step

  • 1. Report & contain. Log the event immediately; make the patient safe; preserve records and evidence.
  • 2. Form a team. Assemble a multidisciplinary group — clinical, nursing, pharmacy, quality — ideally people close to the process but not defensive about it.
  • 3. Reconstruct the timeline. Map exactly what happened, minute by minute, from records and interviews.
  • 4. Ask why. Use the 5 Whys and a fishbone (Ishikawa) diagram to move from the immediate cause to contributing and root causes across people, process, equipment, environment, and policy.
  • 5. Identify root causes. Distinguish the true system causes from symptoms. Good RCA usually surfaces more than one.
  • 6. Design CAPA. Define corrective actions (fix this instance) and preventive actions (stop recurrence), each with an owner and deadline.
  • 7. Implement & verify. Roll out actions, then re-measure to confirm the fix worked — RCA isn't closed until effectiveness is proven.

Common RCA tools

  • 5 Whys — repeatedly asking "why" to drill past symptoms to root cause
  • Fishbone / Ishikawa diagram — grouping causes by category (people, process, equipment, environment, materials, management)
  • Timeline / flow chart — reconstructing the sequence of events
  • FMEA — a proactive cousin used to anticipate failure modes before they occur

Closing the loop with CAPA

The single most common failing NABH assessors see is an RCA that ends with a report and no change. Corrective and preventive action must be specific, owned, time-bound, and — crucially — verified. Prefer stronger, system-level fixes (forcing functions, checklists, protocol changes, equipment standardisation) over weak ones (a memo, "re-training," "be more careful"). Track every action to closure and re-measure the relevant quality indicator to prove the event is less likely to recur.

What NABH assessors look for

  • A defined incident/sentinel-event reporting policy that staff actually use
  • Evidence of a blame-free culture — reports flowing in, including near misses
  • Completed RCAs with timelines, tools used, and identified root causes
  • CAPA with owners, deadlines, and proof of implementation
  • Effectiveness checks — indicators trending in the right direction after action

Frequently asked questions

What is a sentinel event?
A serious, unexpected event causing death or major harm to a patient, unrelated to their illness — e.g. wrong-site surgery, a fatal medication error, or a patient suicide.

What is RCA?
A structured, blame-free method to find the system root causes of an event, using tools like the 5 Whys and fishbone diagram, ending in CAPA.

Does NABH require RCA?
Yes — its patient-safety standards require reporting, analysis, and corrective action for sentinel and adverse events, tracked to closure.

Sources

  • nabh.co — National Accreditation Board for Hospitals & Healthcare Providers
  • qcin.org — Quality Council of India

Make incident reporting effortless

EaseOps lets any staff member report an event in seconds, routes it for RCA, and tracks every corrective action to closure — so nothing slips and your safety culture strengthens.