7.2 Safety Event Analysis: Root Cause Analysis & FMEA

7.2 Safety Event Analysis: Root Cause Analysis & FMEA

Healthcare safety analysis operates across two complementary operational methodologies: reactive event analysis (investigating adverse events and sentinel occurrences after they occur to prevent recurrence) and proactive risk assessment (systematically evaluating new technologies, physical facilities, or clinical workflows to eliminate hazards before they reach the patient). Executive nurse leaders must master both the Root Cause Analysis and Action ($RCA^2$) framework and Failure Modes and Effects Analysis (FMEA), ensuring that clinical teams do not settle for superficial human fixes, but instead engineer robust, high-reliability safeguards.

---

Proactive vs. Reactive Risk Assessment

---

Root Cause Analysis and Action ($RCA^2$)

Developed by the Department of Veterans Affairs (VA) National Center for Patient Safety and endorsed by the National Patient Safety Foundation (NPSF) and the Institute for Healthcare Improvement (IHI), $RCA^2$ (Root Cause Analysis and Action) represents the national gold standard for investigating safety events. The superscript "Action" ($^2$) underscores that an analysis without sustainable, strong corrective action is an organizational failure.

                         THE RCA² LIFECYCLE
    ┌─────────────────────────────────────────────────────────────┐
    │ 1. EVENT IDENTIFICATION & IMMEDIATE SAFETY MITIGATION       │
    │    Secure patient, impound equipment, support clinicians    │
    ├─────────────────────────────────────────────────────────────┤
    │ 2. CHARTER MULTIDISCIPLINARY INVESTIGATION TEAM             │
    │    Frontline nurses, physicians, pharmacy, bio-eng, patient │
    ├─────────────────────────────────────────────────────────────┤
    │ 3. PROCESS MAPPING & TIMELINE RECONSTRUCTION                │
    │    EHR audit trails, physical layout review, interviews     │
    ├─────────────────────────────────────────────────────────────┤
    │ 4. ROOT CAUSE ANALYSIS TOOLS                                │
    │    • 5 Whys Iterative Root Cause Drilling                   │
    │    • Ishikawa Fishbone Diagram (6 Categories)               │
    ├─────────────────────────────────────────────────────────────┤
    │ 5. FORMULATE ACTION PLAN VIA HIERARCHY OF EFFECTIVENESS     │
    │    Prioritize Strong & Intermediate Actions over Weak Fixes │
    ├─────────────────────────────────────────────────────────────┤
    │ 6. EXECUTIVE MEASUREMENT & SUSTAINABILITY AUDIT             │
    │    Outcome, process, and balancing metrics over 12 months   │
    └─────────────────────────────────────────────────────────────┘

The $RCA^2$ Step-by-Step Methodology

1. Immediate Event Response and Evidence Preservation:
   • Provide immediate medical stabilization to the patient.
   • Isolate and impound involved medical devices (infusion pumps, medication vials, disposable sets) with exact settings and lot numbers preserved.
   • Provide immediate emotional first aid to involved clinicians (Second Victim support).
2. Team Chartering and Composition:
   • An effective $RCA^2$ team must be interprofessional: bedside registered nurses, attending physicians, clinical pharmacists, biomedical engineers, risk managers, and human factors experts.
   • Executive Requirement: The team must include frontline staff who understand real-world workflows, led by an experienced facilitator who creates a blameless, psychologically safe atmosphere.
3. Timeline Reconstruction and Process Mapping:
   • Construct an exact, objective chronological timeline of the event using EHR audit trails, automated dispensing cabinet access logs, monitor telemetry, and non-judgmental staff interviews.
4. Root Cause Analysis Tools:
   • The 5 Whys Technique: Repeatedly asking "Why?" (typically five or more times) to peel back proximal human symptoms and expose latent organizational and system defects.
   • Ishikawa (Fishbone / Cause-and-Effect) Diagram: Maps contributing factors across core operational categories:
     • People: Competency, staffing mix, fatigue, handoff communication, cognitive load.
     • Process / Methods: Unclear standard operating procedures, conflicting guidelines, lack of standardized handovers.
     • Equipment / Technology: Poor user interface, alarm configurations, hardware malfunction, lack of physical interoperability.
     • Environment / Milieu: Poor lighting, background noise, physical clutter, high-interruption zones.
     • Management / Organization: Resource allocation, safety culture, production pressure, training infrastructure.
5. Designing the Action Plan:
   • Every identified root cause must be paired with at least one corrective action item, an assigned executive owner, an explicit implementation deadline, and measurable success criteria.

---

The Hierarchy of Action Effectiveness

The National Center for Patient Safety (NCPS) established the Hierarchy of Action Effectiveness to evaluate and score proposed corrective actions. Executive nurse leaders must recognize that actions heavily reliant on human memory, attention, or vigilance will inevitably fail under conditions of clinical stress and fatigue.

                    HIERARCHY OF ACTION EFFECTIVENESS
    ┌─────────────────────────────────────────────────────────────┐
    │ STRONG ACTIONS (Highest Reliability)                        │
    │ • Architectural & physical plant redesign                   │
    │ • Physical forcing functions / Poka-Yoke engineering        │
    │ • Computerized hard-stops in EHR / CPOE                     │
    │ • Elimination of hazardous steps or look-alike products     │
    ├─────────────────────────────────────────────────────────────┤
    │ INTERMEDIATE ACTIONS (Moderate Reliability)                 │
    │ • Software enhancements / Clinical decision support alerts  │
    │ • Standardized cognitive aids & physical checklists         │
    │ • Elimination of look-alike / sound-alike (LASA) storage    │
    │ • Pre-packaged clinical kits & standardized visual cues     │
    │ • Independent redundancies / dual verification protocols    │
    ├─────────────────────────────────────────────────────────────┤
    │ WEAK ACTIONS (Low Reliability - Rely on Human Vigilance)    │
    │ • Retraining staff / Educational inservices                 │
    │ • Issuing policy memos, warnings, or emails                 │
    │ • Adding warning stickers or highlighted labels             │
    │ • Exhortations to "be more careful" or "double check"       │
    └─────────────────────────────────────────────────────────────┘

Hierarchy of Action Effectiveness Reference Table

---

Failure Mode and Effects Analysis (FMEA)

Originating in the aerospace industry and military engineering (MIL-STD-1629A), Failure Mode and Effects Analysis (FMEA) is a systematic, proactive technique used to identify where and how a new or revised process might fail, assess the relative impact of different failures, and identify the parts of the process that are most in need of change.

The 8-Step FMEA Methodology for Health Systems

                         THE FMEA EXECUTION CYCLE
    ┌─────────────────────────────────────────────────────────────┐
    │ 1. Select high-risk clinical process to evaluate            │
    │ 2. Assemble interprofessional subject-matter expert team    │
    │ 3. Construct detailed process flowchart (step-by-step)      │
    │ 4. Brainstorm potential failure modes for each step         │
    │ 5. Identify potential failure causes and clinical effects   │
    │ 6. Assign scores (1-10) for Severity, Occurrence, Detection │
    │ 7. Calculate Risk Priority Number (RPN = S × O × D)         │
    │ 8. Design strong redesign countermeasures & re-score RPN    │
    └─────────────────────────────────────────────────────────────┘

Calculating the Risk Priority Number (RPN)

For each identified failure mode, the multidisciplinary team assigns three scores on a standardized 1 to 10 scale:

$\text{Risk Priority Number (RPN)} = \text{Severity (S)} \times \text{Occurrence (O)} \times \text{Detection (D)}$

• Severity (S) [1 = Negligible, 10 = Catastrophic]:
  • Measures the clinical severity of the harm if the failure occurs. A score of 1 represents no harm or minor inconvenience; 10 represents catastrophic patient death, severe permanent disability, or massive regulatory sanction.
• Occurrence (O) [1 = Extremely Unlikely, 10 = Almost Inevitable]:
  • Measures the likelihood or frequency of the failure mode occurring based on baseline historical data or operational estimates. A score of 1 represents failure once in several years; 10 represents failure occurring multiple times daily.
• Detection (D) [1 = Certain Detection, 10 = Undetectable]:
  • Measures the likelihood that current control mechanisms, alarms, or human checks will detect the failure mode before it reaches the patient. Crucial Rule: A low score (1) means detection is virtually guaranteed; a high score (10) means the error is completely silent and undetectable until patient harm occurs.

RPN Scoring Scale and Prioritization

• RPN Range: Scales from 1 ($1 \times 1 \times 1$) to 1,000 ($10 \times 10 \times 10$).
• Executive Action Threshold: Healthcare organizations establish RPN thresholds (e.g., any failure mode with an $\text{RPN} \ge 100$, or any failure mode where Severity $\ge 9$ regardless of overall RPN) that mandate immediate process redesign.
• Post-Redesign Recalculation: After implementing strong engineering countermeasures, the team recalculates the post-implementation RPN to empirically confirm risk reduction.