Insulin Tenfold Error, a CPOE Default, and a Manager Who Wants a Final Warning
You are the clinical educator for a 32-bed adult medical-oncology unit. A new graduate in her fifth month off orientation administered regular insulin 10 units subcutaneously instead of the 4 units indicated by the sliding scale. The error was caught before the patient ate breakfast. Point-of-care glucose was 96 mg/dL, the patient received 15 g of oral carbohydrate, glucose was rechecked every 15 minutes four times and stayed between 88 and 142 mg/dL. No harm occurred. Chart review shows the 10-unit dose came from a CPOE quick-list default labeled 'Regular insulin before meals,' while the sliding scale lives in a separate order field. Two other insulin events on the unit in the past year had the same pattern. The nurse manager tells you she intends to issue a final written warning and asks you to 'run the remediation.' Staff are already saying, 'If you report anything, you're done.'
1. Using a Just Culture framework, how do you characterize this behavior, and what do you recommend to the manager?
Read the worked answer
This is system-induced at-risk behavior, not recklessness - and the outcome is irrelevant to the culpability analysis.
Recklessness requires a conscious disregard of a known, substantial risk. Nothing here suggests that. The nurse had a duty to reconcile the drug against the scale, and she did not - that is a real lapse and deserves coaching. But the design made the wrong action the path of least resistance: the default field pre-populated a dose, and the scale sat in a separate order. When two other nurses on the same unit make the identical error in a year, the recurrence is the evidence that the defect lives in the system, not in the individuals.
The fact that the patient came to no harm should not soften the remediation, and the fact that the error was caught should not increase discipline. Both facts are about outcome, not conduct.
My recommendation to the manager: no final written warning. Console the nurse, coach on order reconciliation, and treat this as a learning event with a system corrective action. A final warning here buys a short-term sense of accountability and costs years of suppressed reporting on a unit where you need near-miss data to find the next defect. If the nurse had bypassed a hard stop or overridden a barcode warning knowingly, that would be a different conversation.
2. What system fixes do you propose, and in what order of impact?
Read the worked answer
Fix the order before you fix the people.
Highest impact: eliminate the free-text 10-unit default entirely and rebuild so the sliding scale and the mealtime dose are one order, with a hard stop that will not release without a glucose parameter. A default that generates a plausible-looking wrong dose is worse than a blank field, because it defeats the nurse's verification instinct.
Second: force an independent double-check for insulin at administration, with barcode scanning against the administered dose rather than the order label. Third: segregate insulin storage and add auxiliary labels distinguishing concentrated from regular stock, since tenfold errors cluster around look-alike products. Fourth: have pharmacy validate insulin orders against the current glucose rather than entering them as a standing regimen.
The two prior events matter for sequencing: if both involved the same quick-list, this is a high-frequency, low-severity defect and belongs in the CPOE build queue now, not in the next quarterly release.
Measure the fix: number of insulin orders with a default dose, double-check compliance by audit, and near-miss reports per 1,000 insulin administrations. Do not measure 'modules completed.'
3. How do you rebuild reporting on this unit, given that staff already believe reporting gets people fired?
Read the worked answer
You cannot talk your way out of this; you have to demonstrate it once, visibly.
Start small and concrete. Ask the new graduate, with her consent and without naming the patient, to walk the staff through what the screen looked like at 0530 and what would have prevented it. Peer storytelling moves belief faster than a leader asserting that reporting is safe. Then show the fix: post the CPOE change request with a date and the ticket number in the break room, and follow up when it lands. A single visible 'you reported, we changed it' cycle does more than a year of safety huddles.
Change the leader behavior that staff actually observe. Ask the manager to stop opening meetings with error counts and start opening with defects found and closed. Add near-miss reports - not just harms - as a unit metric, and praise them explicitly at huddle.
Set a realistic expectation: after a punitive response was proposed, expect reporting to stay depressed for two to three months even if you do everything right. Watch for a rise in near-miss reports as the success signal; a flat or falling count is the warning sign, not reassurance.
Finally, have the manager say plainly to the group what she decided and why.