Match each clinical scenario describing a patient safety vulnerability or quality improvement intervention to the most appropriate human factors engineering concept.
- An electronic health record is configured to completely prevent a provider from signing an order for methotrexate unless a valid oncologic or rheumatologic diagnosis code is explicitly linked.Forcing function
- A hospitalist prescribes an inappropriate dose of a novel anticoagulant because they unquestioningly accepted the default dosage generated by the computerized physician order entry system.Automation bias
- Emergency department residents routinely document patient assessments under an attending's logged-in profile to avoid the lengthy two-factor authentication sequence required by the workstation.Workaround
- A pharmacist immediately clicks 'Proceed' on a pop-up warning regarding a severe drug-drug interaction without reading it, as they receive hundreds of similar low-yield notifications daily.Alert fatigue
- A healthcare network removes all varying concentrations of intravenous heparin from its formularies and implements a single, uniform concentration across all inpatient units.Standardization
Answer
The scenarios accurately map to Forcing function, Automation bias, Workaround, Alert fatigue, and Standardization, respectively.
Each scenario accurately illustrates a core principle of human factors engineering in healthcare. Forcing functions physically restrict unsafe actions. Automation bias is the uncritical acceptance of computer-generated data. Workarounds are unauthorized bypasses of safety protocols to save time. Alert fatigue is the desensitization to frequent, low-value warnings. Standardization minimizes risk by reducing unwarranted system variation.
Step-by-Step Solution
Key Concept
Human factors engineering principles are utilized in quality improvement to design systems that anticipate, prevent, and mitigate human error.