1.2 Reactive Analysis: Root Cause Analysis
Key Takeaways
- Root Cause Analysis (RCA) is a retrospective process mandated by the Joint Commission for all sentinel events, requiring completion within 45 days of the event.
- The National Patient Safety Foundation's RCA² guidelines recommend that RCA teams consist of 4 to 6 multidisciplinary members, excluding those directly involved in the event to prevent bias.
- Up to 70% of RCAs fail to implement 'strong' systemic actions, relying instead on 'weak' actions like retraining or policy reminders.
- RCA² introduces a risk-based prioritization matrix to ensure that close calls (near misses) with high recurrence potential receive full analysis.
Reactive Analysis in Patient Safety
In contrast to proactive risk assessment, reactive analysis occurs after an event has taken place. The primary mechanism for reactive analysis in healthcare is Root Cause Analysis (RCA), a structured, retrospective process designed to identify the underlying systems and processes that allowed an adverse event to occur. The goal of an RCA is not to assign individual blame, but to understand why the event happened and how to redesign systems to prevent recurrence. The sentinel events—unexpected occurrences involving death, serious physical or psychological injury, or the risk thereof—typically trigger a formal RCA. The Joint Commission mandates that accredited healthcare organizations conduct a thorough and credible RCA and implement an action plan within 45 days of a sentinel event or its discovery.
The Evolution of RCA²
While traditional RCA has been used in healthcare for decades, it historically suffered from a significant limitation: organizations spent substantial resources identifying causes but failed to implement sustainable changes. To address this, the National Patient Safety Foundation (NPSF), in partnership with the Professional Scientific Groups, published guidelines in 2015 introducing RCA² (Root Cause Analysis and Action). The second "A" in RCA² explicitly emphasizes action, reflecting the belief that the value of any root cause analysis lies entirely in the effectiveness and sustainability of the actions taken to prevent future harm.
RCA² introduces several refinements to the traditional process:
- Risk-Based Prioritization: Organizations use a probability-impact matrix to determine which events (including near misses or "close calls") warrant a full RCA², focusing resources where the potential for learning and prevention is greatest.
- Strict Timelines: RCA² reviews should begin within 21 to 45 days of the event, ensuring that recollections are fresh and evidence is preserved.
- Action-Oriented Feedback: The process requires measurable, system-focused actions with clear leadership accountability and timeline constraints.
Investigating Causes: Five Whys and Fishbone Diagrams
During the investigation phase, the RCA² team uses specific tools to drill down past active failures (the immediate actions of clinicians) to identify latent conditions (underlying system defects).
The two most common tools are:
- Five Whys: An iterative interrogative technique used to explore the cause-and-effect relationships underlying a particular problem. By repeatedly asking the question "Why?" (typically five times), the team can peel away layers of symptoms to reveal the root cause. For example: A patient received the wrong medication. Why? The nurse selected the wrong vial. Why? The vials looked identical. Why? They were stored next to each other. Why? There was no look-alike/sound-alike segregation policy. Why? The pharmacy lacked a standardized storage protocol (the root cause).
- Fishbone diagram: Also known as the Ishikawa or cause-and-effect diagram, this visual tool helps teams categorize the potential causes of an event. Causes are grouped into standard categories: People (staffing, training), Methods (procedures, policies), Equipment (devices, software), Environment (lighting, noise), Materials (supplies, drugs), and Measurements (metrics, monitoring). This structure prevents the team from focusing too narrowly on human performance.
RCA² Team Composition
To ensure a comprehensive and objective review, the RCA² team should consist of 4 to 6 multidisciplinary members. The team must include:
- A patient safety professional or facilitator trained in RCA² methodology.
- Clinical representatives from the relevant disciplines (e.g., a nurse, a physician, a pharmacist).
- A representative with process knowledge (someone who understands how the work is actually performed on the unit).
- A leader with decision-making authority to sponsor and implement the action plan.
Crucially, to prevent defensive bias and ensure objectivity, the team must exclude individuals who were directly involved in the sentinel event. These individuals should be interviewed separately to gather factual details, but they must not participate in the analysis or action-planning meetings.
The Hierarchy of Actions
The defining feature of RCA² is the development of an action plan using the hierarchy of actions. This framework classifies actions based on their reliability and likelihood to succeed in preventing error recurrence.
| Action Strength | Level of Human Reliability | Operational Description | Clinical Examples |
|---|---|---|---|
| Strong Actions | High Reliability | Focuses on system design and physical barriers; does not rely on human memory or vigilance | Introducing a physical forcing function (e.g., unique enteral tubing connectors); standardizing equipment; barcode medication administration |
| Intermediate Actions | Medium Reliability | Reduces reliance on cognitive load but still requires human compliance | Implementing checklists; software integration (e.g., EHR alerts); independent double checks for high-alert medications |
| Weak Actions | Low Reliability | Relies entirely on individual compliance, vigilance, memory, or training | Writing or revising a policy; distributing educational memos or warnings; retraining staff; verbal reminders |
Organizations must aim to implement at least one strong or intermediate action for every identified root cause. Relying solely on weak actions like retraining or policy changes is a common failure point that leaves the organization vulnerable to repeat events.
Action Measurement and Follow-Up
An RCA² is not complete until the effectiveness of the action plan is measured. The team must define:
- Outcome Measures: Metrics that determine if the intervention actually reduced the rate of the adverse event.
- Process Measures: Metrics that track whether the action was implemented as planned (e.g., the percentage of staff trained or the compliance rate with a new checklist).
- Auditing Timelines: A schedule for presenting follow-up data to leadership (typically at 30, 60, and 90 days) to ensure sustainability.
Why did the National Patient Safety Foundation (NPSF) transition from Root Cause Analysis (RCA) to the RCA² framework?
According to the RCA² hierarchy of actions, which of the following is classified as a 'strong' action?