After the Upgrade: Alert Fatigue, Missing Labs, and a Too-Good Dashboard
A clinic's EHR was updated last month. Since then, the drug-allergy interaction alert for sulfonamides fires on every patient taking furosemide, and clinicians have begun clicking through alerts without reading them. The lab interface also maps outside creatinine results to the wrong field for patients whose middle name contains a hyphen; 12 results from the past two weeks never appeared in the EHR. At the monthly quality meeting, the diabetes A1c dashboard shows 92% compliance, up from 61% before the upgrade. The medical director wants to submit the dashboard to a payer incentive program next week and asks you to sign off.
1. How should the alert problem be handled?
Read the worked answer
Do not disable the alert as the first move.
- Reproduce the alert and inspect the rule logic: furosemide is not a sulfonamide, so the trigger is likely a cross-reactivity rule that is too broad or a mis-mapped drug class.
- Test a corrected rule in a non-production environment, with pharmacy or clinical review.
- Until it is fixed, give clinicians a written interim instruction so a true sulfa allergy is not missed; do not rely on click-through behavior.
- Document the change request, who approved it, and the date.
- Audit how often the alert fired and whether any true allergy was overridden.
- Alert fatigue is a patient-safety problem, not just an annoyance.
2. What must be done about the 12 missing creatinine results?
Read the worked answer
The missing results are a patient-safety and data-integrity failure.
- Identify the affected patients, retrieve the results from the lab, and get them into the chart through the correct workflow; notify the ordering clinicians.
- Correct the interface mapping for hyphenated middle names, then test with a sample of names before go-live.
- Reconcile orders and results to find any other results that failed silently; two weeks of missing labs may be the visible part only.
- Document the incident, the fix, and the notifications.
- Review whether the EHR flagged the missing results; if not, add an interface error queue that someone owns.
3. Should the dashboard be submitted to the payer next week?
Read the worked answer
Do not sign off on the dashboard yet.
- A jump from 61% to 92% after an upgrade is a red flag for a changed denominator or a data-source shift, not proof of improvement.
- Run the report definition against a manual chart sample, confirm the measurement period, and check whether the missing lab results are excluded from the denominator; if they are, the rate is overstated.
- Compare the query to the pre-upgrade version and document the differences.
- Submit only validated data; a payer incentive attestation based on a faulty report can trigger recoupment or audit risk.
- Tell the medical director the report is on hold pending validation, and give a date for the re-run.