Question

Difficulty: HardPatient Safety Culture and Reporting Systems

Match each clinical scenario describing a patient safety incident to the most accurate event classification and its corresponding administrative or clinical next step.

  • A pharmacist intercepts a physician's order for a tenfold overdose of methotrexate before the medication is dispensed or administered.Near Miss: Submit an internal incident report to proactively identify vulnerabilities and improve system safeguards without external regulatory notification.
  • An electronic health record interface requires physicians to scroll down to view patient allergies, a flaw that has contributed to multiple prescribing mistakes.Latent Condition: Initiate system-wide workflow redesign and evaluation to address the underlying design flaw that predisposes operators to mistakes.
  • A patient dies from a hemolytic transfusion reaction after receiving ABO-incompatible blood due to a processing mix-up in the laboratory.Sentinel Event: Immediately initiate a multidisciplinary Root Cause Analysis (RCA) and notify appropriate regulatory bodies.
  • A patient develops a mild, reversible rash after a resident physician inadvertently prescribes a medication to which the patient has a documented allergy.Preventable Adverse Event: Disclose the error openly to the patient, provide appropriate clinical care, and submit an internal incident report.

Answer

The intercepted methotrexate order is a near miss; the EHR flaw is a latent condition; the fatal transfusion is a sentinel event; and the allergic reaction is a preventable adverse event requiring open disclosure.
Proper classification of medical errors dictates the appropriate administrative and clinical response. A near miss highlights system resilience but requires reporting to address the vulnerability. Latent conditions are systemic flaws that predispose to mistakes and require redesign. Sentinel events are severe outcomes requiring formal root cause analysis. Preventable adverse events require immediate open disclosure to the patient, clinical management, and internal reporting.

Step-by-Step Solution

1
Analyze each scenario to determine if the error reached the patient and the severity of the outcome.
The methotrexate order did not reach the patient; the EHR is an underlying flaw; the transfusion caused death; the allergy prescription caused a mild rash.
Determining patient impact is essential for distinguishing between near misses, adverse events, and sentinel events.
2
Match the intercepted error to its classification and next step.
Intercepted methotrexate order matches 'Near Miss', requiring an internal incident report.
Errors caught before patient exposure are near misses, which provide valuable data for system improvement without causing harm.
3
Match the systemic flaw to its classification and next step.
The EHR scrolling issue matches 'Latent Condition', requiring workflow redesign.
Latent conditions are built-in system vulnerabilities that set up front-line workers for active errors.
4
Match the fatal outcome to its classification and next step.
The fatal transfusion matches 'Sentinel Event', requiring a formal Root Cause Analysis and regulatory notification.
Sentinel events involve unexpected death or severe injury and mandate rigorous, standardized investigation.
5
Match the error causing mild harm to its classification and next step.
The allergic reaction matches 'Preventable Adverse Event', requiring patient disclosure and clinical care.
When an error reaches the patient and causes harm, ethical principles mandate open disclosure alongside incident reporting.

Key Concept

Classification of Patient Safety Events and Administrative Pathways
Rate this question