CPOE Order-Set Redesign and a Wrong-Patient Near Miss
During a CPOE rollout, a nurse reports a near miss: an order set for 'heparin infusion' defaulted the dose and the patient-selection field retained the prior patient because the screen did not clear between sessions on a shared workstation. The pharmacist caught it before administration. A follow-up review finds 14 shared workstations in the ED where the timeout is set to 60 minutes, and the order set has 3 fields pre-populated with defaults. The vendor says the patient-context retention is 'working as designed.' Two clinicians say the order set saves them time and want it kept as-is. Go-live for two more units is in 10 days.
1. Apply a human-factors and safety-analysis lens to this event. What failure modes are present and how do you classify them?
Read the worked answer
This is a classic use-error, not user error. Failure modes: (1) patient-context not clearing on shared workstations - a mode/state error where the system does not make the active patient unmistakable; (2) pre-populated default doses in a high-alert medication order set - a default-bias hazard; (3) 60-minute timeout on shared ED workstations - too long for high-turnover shared use. Classify with a safety-assessment approach (e.g., a failure modes and effects analysis or SEIPS-style work-system analysis): the workstation, the interface, the order-set design, and the policy all contribute. The near miss was caught by a human barrier (pharmacist), which is not a reliable control. The 'working as designed' response is not acceptable for a high-alert medication.
2. What immediate and structural mitigations do you recommend before the 10-day go-live, and what must be true to proceed?
Read the worked answer
Immediate: reduce workstation timeout on shared ED devices to a short interval (e.g., 2-5 minutes) with re-authentication; require explicit patient confirmation before order-set entry; remove pre-populated defaults from high-alert medication fields or require active entry; add a prominent persistent patient banner. Structural: add a hard stop or confirmation for high-alert meds, and test the change on the shared-workstation configuration specifically. Go/no-go criteria for the two units: verified timeout change, tested patient-context behavior on shared devices, and a re-run of the order-set with a test patient. If these are not met, delay the two-unit go-live - the risk of a wrong-patient high-alert medication event outweighs a schedule slip.
3. How do you handle the two clinicians who want the order set unchanged, and what do you report?
Read the worked answer
Acknowledge the efficiency benefit and preserve it where safe - keep the order set but remove only the hazardous defaults and add confirmation, which retains most of the time savings. Explain the near miss and the high-alert medication context. Report the event through the patient safety reporting system as a near miss with the contributing factors and corrective actions, and track the mitigation to closure. Share de-identified lessons with the CPOE governance group and the two upcoming units so the fix propagates before go-live.