Methods
Root Cause Analysis and Action (RCA²)
Examining adverse events to identify contributing system failures and develop effective corrective actions.
RCA² was published by the National Patient Safety Foundation in 2015 to address a common weakness of traditional root cause analysis: investigations that end with a list of causes but no actions strong enough to prevent the event from happening again.
The approach treats an adverse event as a symptom of system vulnerabilities rather than individual failure, and puts as much weight on the corrective actions and their measurement as on the analysis itself.
- Blame-free focus
- The goal is to understand why the system allowed the error, not to identify who to discipline.
- Interdisciplinary review
- People with different roles in the process look at the event together, so no single perspective dominates.
- Action hierarchy
- Actions are ranked as stronger (e.g. forcing functions, standardization), intermediate (e.g. checklists, software enhancements) or weaker (e.g. training, new policies).
- Measurement
- Each action gets a process or outcome measure so the organization can tell whether it worked.
Human Factors Engineering
Examining the interaction between people, technology, environments, and organizational systems.
Human factors engineering applies what is known about human capabilities and limitations (perception, attention, memory, decision-making and physical abilities) to the design of tasks, tools and environments.
In healthcare it is often organized around work-system models such as SEIPS (Systems Engineering Initiative for Patient Safety), which describes how the person, tasks, tools and technology, physical environment and organization interact to shape care processes and outcomes.
- Design for real users
- Interfaces and procedures should fit how people actually perceive, think and act, especially under time pressure.
- Error types
- Slips and lapses (execution failures) need different fixes than mistakes (planning or knowledge failures).
- Usability evaluation
- Methods such as task analysis, heuristic evaluation and usability testing reveal where a design invites error.
Failure Mode and Effects Analysis (FMEA)
Prospectively evaluating how processes might fail and prioritizing risk reduction strategies.
Where root cause analysis looks back at an event that happened, FMEA looks ahead: it maps a process step by step and asks how each step could fail, what the effect would be, and how likely the failure is to be caught.
Healthcare organizations use FMEA and adaptations such as Healthcare FMEA (HFMEA) to assess high-risk processes before harm occurs, for example when introducing a new device or redesigning a workflow.
- Process mapping
- The process is broken into steps and sub-steps, ideally by the people who do the work.
- Failure modes and effects
- For each step: how could it fail, what would happen, and what currently prevents or detects it.
- Prioritization
- Failure modes are scored, commonly by severity, occurrence and detectability (risk priority number = S × O × D), to decide where to act first.
Systems Analysis
Understanding how interconnected processes and organizational structures influence safety outcomes.
Safety is an emergent property of the whole system, not of any single component. Systems analysis looks at how processes, people, technology and organizational decisions interact, including how pressures and trade-offs at one level create conditions for error at another.
Common tools include process and swimlane mapping, James Reason's “Swiss cheese” model of layered defenses, and systems-theoretic approaches such as STAMP/STPA, which treat accidents as failures of control rather than chains of component failures.
- Layered defenses
- Most adverse events pass through several weakened barriers; the analysis looks for each hole, not just the last one.
- Latent conditions
- Staffing, scheduling, procurement and policy decisions can set up errors long before they occur.
- Feedback and control
- Asks whether the people managing a process have accurate, timely information about its state.
Cognitive Workload Assessment
Evaluating how workload, stress, fatigue, and information processing demands influence performance.
Cognitive workload describes the mental resources a task demands relative to what a person has available. When demand exceeds capacity, through interruptions, time pressure, fatigue or poorly designed information, error likelihood rises.
Workload can be assessed with subjective scales such as the NASA Task Load Index (NASA-TLX), performance measures such as secondary-task accuracy, and physiological measures such as heart-rate variability.
- NASA-TLX
- Rates six dimensions: mental demand, physical demand, temporal demand, performance, effort and frustration.
- Interruptions
- Interruptions during safety-critical tasks such as medication preparation are a well-documented source of error.
- Fatigue and stress
- Long shifts and high stress degrade attention and memory, which affects how barriers perform in practice.
References
- Carayon, P., Schoofs Hundt, A., Karsh, B.-T., Gurses, A. P., Alvarado, C. J., Smith, M., & Flatley Brennan, P. (2006). Work system design for patient safety: The SEIPS model. Quality & Safety in Health Care, 15(Suppl 1), i50–i58.
- Hart, S. G., & Staveland, L. E. (1988). Development of NASA-TLX (Task Load Index): Results of empirical and theoretical research. Advances in Psychology, 52, 139–183.
- Leveson, N. G. (2011). Engineering a safer world: Systems thinking applied to safety. MIT Press.
- National Patient Safety Foundation. (2015). RCA²: Improving root cause analyses and actions to prevent harm. National Patient Safety Foundation.
- Reason, J. (1990). Human error. Cambridge University Press.