MMHA 6600 Week 7 Allergy Alert Fatigue Case Example

Healthcare Informatics and Technology Management Walden University Free custom sample in 24 to 48h

This MMHA 6600 Week 7 alert fatigue case example traces why prescribers dismiss penicillin allergy alerts to an allergy list that stores an upset stomach and a history of hives in the same field. Walden MMHA 6600 asks MHA students to find the system cause behind a habit, and the case begins with two overrides that look identical in the log but carried very different risk. Drawing on published override studies from Topaz's group and from a Dutch review, the paper reviews 200 illustrative penicillin entries and finds fewer than a third consistent with true immediate allergy. Macy and Contreras and Blumenthal and colleagues show the label's own harms. Using Sittig and Singh's sociotechnical view, it proposes reaction types, tiered alerts, pharmacist cleanup and tolerance documentation, each with an owner and measure.

CourseMMHA 6600 Healthcare Informatics and Technology Management
WeekWeek 7
Paper typeAlert fatigue case analysis
LengthAbout 1,050 words, 6 pages
FormatAPA 7 student paper
SchoolWalden University
ProgramMaster of Healthcare Administration (MHA)
UpdatedOctober 2026

Free sample paper for MMHA 6600 Week 7

1

The Rash and the Reaction Look the Same on Screen: An Alert Fatigue Case Traced to How the Allergy List Is Built

Student Name

Walden University

MMHA 6600: Healthcare Informatics and Technology Management

Instructor Name

Month Day, Year

What this page is doingThe title places the cause in the allergy list rather than in prescriber behavior, which is the argument the case develops.
2

The Rash and the Reaction Look the Same on Screen: An Alert Fatigue Case Traced to How the Allergy List Is Built

The Case

On a medical unit at Bramble Creek Hospital, the composite hospital used for this course's assignments, a hospitalist ordered cefazolin before a minor procedure for a man whose allergy list read "penicillin." The record fired an interruptive cross-sensitivity alert. The hospitalist overrode it, as she had overridden the same alert many times that month, and wrote "tolerated before" in the override reason. The patient did well. A week later, on the same unit, a different prescriber overrode an identical-looking alert for a woman whose penicillin entry recorded hives and throat tightness years earlier. She also did well, after a nurse questioned the order and the dose was given with monitoring.

Both overrides looked the same in the alert log. The difference between the two patients, a stomach upset in one and a history consistent with true allergy in the other, was visible to nobody at the moment of decision. This case analysis traces the habit of overriding to that invisibility and proposes changes to how the allergy list is built.

What this page is doingOpening with two near-identical overrides makes the problem concrete: the system gave the same signal for very different risks.
3

How Common Overrides Are

Overriding drug allergy alerts is the norm rather than the exception. A study of a decade of alerts at two academic centers found that override rates for drug allergy alerts rose over time and that most overrides were judged appropriate, frequently because the patient had tolerated the drug before or the listed reaction was not allergic (Topaz et al., 2016). Earlier work on drug safety alerts in general found override rates between about half and almost all alerts, with prescribers citing irrelevance and repetition (van der Sijs et al., 2006). At Bramble Creek, the pharmacy's review of the past quarter found that 91 percent of penicillin cross-sensitivity alerts on adult units were overridden. That figure is illustrative for this sample paper, but it sits within the published range.

What this page is doingPlacing the local rate beside published rates shows the problem is typical, which strengthens the case for a system fix.
4

Root Cause: One Field for Two Kinds of Entry

A review of 200 adult penicillin entries on the allergy list found the pattern summarized in Table 1. The list stores intolerances, side effects, family history and true allergies in the same field, with the same severity default, and the alert logic treats them all alike.

This mix is consistent with the wider literature. When people carrying a penicillin label are formally tested, the large majority turn out to tolerate the drug, and the label does damage of its own: labeled patients receive broader-spectrum antibiotics and have higher rates of resistant infections and longer stays (Macy & Contreras, 2014; Blumenthal et al., 2019).

Table 1

Recorded Reactions on 200 Penicillin Allergy Entries (Illustrative)

Recorded reactionEntriesType
Nausea, vomiting or diarrhea38Intolerance or side effect
Unknown or blank52Unclassifiable
Childhood rash, unspecified41Low risk, often not allergic on testing
Family history only9Not a patient allergy
Hives or itching44Possible immediate allergy
Swelling, breathing difficulty or anaphylaxis16High risk

Fewer than one entry in three described a reaction consistent with true immediate allergy, yet every entry produced the same interruptive alert.

What this page is doingThe table moves the case from the alert to the data feeding it, which is where the root cause lies.
5

Why Prescribers Learn to Override

An alert teaches through repetition. When most alerts concern entries that are not true allergies, prescribers learn that the alert is usually wrong, and the learned response, override, is applied to the rare alert that matters. The hospitalist in the first case was behaving reasonably given her experience. The prescriber in the second case was doing the same thing. Nothing in the alert distinguished the patient with hives and throat tightness from the patient with an upset stomach.

In sociotechnical terms, the failure belongs to the interaction between content, interface and people, not to any single part (Sittig & Singh, 2010). Retraining prescribers to read alerts more carefully would ask them to work harder against a system that keeps teaching the opposite lesson.

What this page is doingExplaining the override as learned behavior keeps blame off individuals and points toward design.
6

Proposed Changes

Four changes address the list rather than the prescriber.

First, split the entry. Require a reaction type when an allergy is entered, chosen from a short list: intolerance or side effect, low-risk reaction, possible immediate allergy, severe reaction. Second, tie alert behavior to the type. Severe and possible immediate reactions keep an interruptive alert; low-risk reactions show a passive notice; intolerances show nothing at ordering. Third, clean the existing list. A pharmacist-led review of penicillin entries on admission, using the patient interview, can reclassify most entries and identify patients for allergy testing. Fourth, record tolerance. When a patient receives a drug in the same class without reaction, the record should prompt the nurse to note it, so the next prescriber sees evidence rather than a bare label.

Table 2

Changes, Owners and Measures

ChangeOwnerMeasure
Required reaction type on new entriesRecord build teamShare of new entries with a type
Alert tiering by reaction typePharmacy and therapeutics committeeInterruptive alerts per 100 orders
Admission review of penicillin entriesClinical pharmacyEntries reclassified per month
Tolerance documentation promptNursing informaticsEntries updated after tolerated doses

Each measure can be pulled from existing reports, so progress can be shown within one quarter.

What this page is doingLinking each change to an owner and a measure makes the proposal something a committee can approve and follow.
7

Risks

Fewer alerts could mean a missed true allergy if entries are misclassified. The safeguard is that uncertain or blank entries default to the possible immediate allergy tier until reviewed. The review workload for pharmacy is real; starting with patients who are about to receive a beta-lactam limits it. A third risk is cultural: some prescribers may distrust a passive notice at first and ask for the old alert back. The pharmacy and therapeutics committee should publish the first quarter's results, including any reaction in a patient whose entry had been downgraded, so the change is judged on evidence. If a downgraded entry is ever followed by a true reaction, the case should go through the same review as any other safety event, and the tier rules adjusted if needed.

Conclusion

The overrides at Bramble Creek are not careless. They are the predictable response to an alert that cannot tell a rash from a reaction because the allergy list records both in the same way. Building the list to carry reaction type, and letting alerts follow that type, gives the rare dangerous entry the attention it needs and stops teaching prescribers to ignore every alert.

What this page is doingThe conclusion restates the causal chain from list to habit, which is the case's main contribution.
8

References

Blumenthal, K. G., Peter, J. G., Trubiano, J. A., & Phillips, E. J. (2019). Antibiotic allergy. The Lancet, 393(10167), 183-198. https://doi.org/10.1016/S0140-6736(18)32218-9

Macy, E., & Contreras, R. (2014). Health care use and serious infection prevalence associated with penicillin "allergy" in hospitalized patients: A cohort study. Journal of Allergy and Clinical Immunology, 133(3), 790-796. https://doi.org/10.1016/j.jaci.2013.09.021

Sittig, D. F., & Singh, H. (2010). A new sociotechnical model for studying health information technology in complex adaptive healthcare systems. Quality and Safety in Health Care, 19(Suppl 3), i68-i74. https://doi.org/10.1136/qshc.2010.042085

Topaz, M., Seger, D. L., Slight, S. P., Goss, F., Lai, K., Wickner, P. G., Blumenthal, K. G., Dhopeshwarkar, N., Chang, F., Bates, D. W., & Zhou, L. (2016). Rising drug allergy alert overrides in electronic health records: An observational retrospective study of a decade of experience. Journal of the American Medical Informatics Association, 23(3), 601-608. https://doi.org/10.1093/jamia/ocv143

van der Sijs, H., Aarts, J., Vulto, A., & Berg, M. (2006). Overriding of drug safety alerts in computerized physician order entry. Journal of the American Medical Informatics Association, 13(2), 138-147. https://doi.org/10.1197/jamia.M1809

What the MMHA 6600 Week 7 instructions ask for

Case analyses in informatics ask you to explain a recurring problem through the system rather than through individual mistakes. Open with a specific event or pair of events that shows the problem. Place it in context with published data on how common it is. Then look for the root cause in the data, interface or workflow, using evidence such as a review of records. Explain how the system teaches the behavior you observed. Use a framework to show that the cause spans technology and people. Propose changes that address the cause, and give every one a responsible person and a number to watch. Name the risks of your proposal and how they will be controlled. Avoid recommending retraining alone when the design keeps teaching the old habit.

Inside the MMHA 6600 Week 7 example

The case opens with two overrides of the same alert, one for nausea and one for a history of hives. A section sets the local override rate next to two published studies, one following a decade of alerts and one reviewing why prescribers override. Table 1 sorts 200 penicillin entries by recorded reaction, and a paragraph cites Macy and Contreras and Blumenthal and colleagues on the harm of inaccurate labels. A section explains overriding as learned behavior, using Sittig and Singh's model. Four changes follow, with Table 2 giving owners and measures. A risks section covers misclassification and resistance from prescribers. The conclusion restates the chain from list to habit. Each proposed change is paired with a measure the pharmacy can already pull.

MMHA 6600 Week 7 rubric: what earns full marks

Expect the rubric to weight root cause above description. Moving from the event to the data that produced it earns the core credit. Evidence such as a record review, even on a small sample, shows the cause was found rather than assumed. Placing local data beside published rates demonstrates context. Explaining behavior as learned from the system, without blaming individuals, reflects graduate-level analysis. Proposals are judged on whether they address the cause, sit with a responsible person and can be measured over a quarter. Naming risks and safeguards shows maturity. The remaining marks depend on organization, with tables that summarize evidence and references that match the citations in the text.

MMHA 6600 Week 7 help from the desk

Alert fatigue papers often recommend turning alerts off or retraining prescribers. Look upstream first. Ask what data the alert reads and how that data is entered. Review a sample of entries, even fifty, and sort them. You will often find that most alerts concern entries that are not what the alert assumes. Explain why clinicians learn to override, without blaming them. Propose changes to the data and to alert tiers together. Plan for the risk that a true allergy slips through. We can help you design a small record review and turn a frustrating alert into a clear case analysis for your pharmacy and therapeutics committee.

Get a MMHA 6600 Week 7 example written to your instructions

Send the Week 7 case prompt and the rubric, and mention the alert type your section focuses on if one is named; the desk writes the case around it and returns it in 24-48h, with nothing charged for the first. The prescriber and the patient in it are fictional. Incident reports from your workplace stay confidential and are never requested.

More MMHA 6600 papers and MHA samples

MMHA 6600 Week 7 questions, answered

Where can I find a free MMHA 6600 Week 7 sample paper?

The allergy alert case analysis is free to read here, including the entry review table and five references.

What root cause does the MMHA 6600 Week 7 case identify?

An allergy list that records intolerances, family history and true allergies in one field, so every entry fires the same alert.

How many penicillin entries suggested true allergy?

Fewer than a third of 200 illustrative entries described hives, swelling or anaphylaxis.

Why is retraining prescribers not enough?

The alert keeps teaching that it is usually wrong, so retraining works against what prescribers see every day.

What safeguard prevents a missed true allergy?

Blank or uncertain entries default to the interruptive tier until a pharmacist reviews them.