Action hierarchy after RCA: reduce reliance on memory

Why this matters

A completed investigation is not the endpoint if work remains unchanged. IHI uses RCA² to emphasise both analysis and action on system vulnerabilities. ^[1] The useful question is which conditions allowed the event to reach the patient and whether those conditions have changed.

Evidence and important boundaries

IHI’s Action Hierarchy supports consideration of action strength. ^[1] AHRQ groups environmental redesign, process simplification and engineering controls as stronger actions, while reminders, training and new policies rely more on people remembering. ^[4] NHS England links system issues, actions and effectiveness monitoring. ^[2][3] The hierarchy supports design choices; it does not establish suitability in every context.

Suggested local application

ICORP offers a design example: if similar screen entries contribute to wrong selections, another warning or training session leaves that condition intact. Teams could investigate clearer differentiation, fewer unnecessary steps or a constraint that stops a mismatch, then test usability and unintended effects with real users. This is a hypothetical improvement option, not a reported experiment or an instruction to install a specific system.

What to monitor

Review implementation and effectiveness separately: was the action completed, and did it reduce the vulnerability? Combine observation, near-miss information and staff feedback. Absence of reports alone does not prove safety. Revise actions if they introduce new problems or do not work as intended; no approach guarantees that all recurrence will be prevented.