Coded allergies are a condition for the alert to work

The correct answer: A. Allergy checking needs allergens recorded as coded entries linked to the drug knowledge base; free text cannot trigger the check

✅ Why this answer

Allergy checking is automatic: it compares the code of the allergen in the patient’s record with the drug’s ingredients and class in the drug knowledge base. Free text in a comment field, such as “PCN - hives”, is not understood by the system, so no alert fires, even though the information is “there” in the record.

❌ Why the other options are wrong

• (B): a scientific error; amoxicillin belongs to the same penicillin family, which is why the case is so dangerous.
• (C): allergy checking works for every route of administration.
• (D): pharmacist review is an important layer, but the system’s check is an independent first layer, and it does not work without coded data.

💡 Key concept

Information written as free text is read only by people. Decision support needs structured, coded data. So the allergy screen is designed to select the allergen from a coded list, along with the type and severity of the reaction, with a text field for details only.

Periodic cleanup of old allergies written as text, converting them into codes, also helps.

In the exam: when the information is “there” and the system did not act, look at the form of the data: is it coded, and in the right field?

🔗 Related facts and questions

• Medication checks in decision support (CDS): drug-allergy, drug-drug interaction, duplicate therapy, dose range, and the drug against the patient’s condition, such as kidney function or pregnancy. All of them work on coded data: the medication list, allergies, diagnoses and laboratory results.
  Practice question: a note says the patient takes warfarin; later a drug that interacts with it is prescribed and no alert appears. What is the most likely cause? → Warfarin is not on the coded medication list.
• Class matching and cross-sensitivity: the drug knowledge base knows that amoxicillin belongs to the penicillin class, so a coded penicillin allergy alerts on every drug in the class and not only on the name recorded. Cross-sensitivity goes one step further: a warning for a related class, such as cephalosporins for a patient allergic to penicillin. New drugs have to be added to these groups, which is one reason the knowledge base is updated regularly from its supplier.
• The standard terminologies behind the check: RxNorm for drug names and ingredients, SNOMED CT for diagnoses and the type of reaction, and LOINC for laboratory tests. Shared codes are what let an allergy list move between systems without losing its meaning.
• “No known allergies” is not an empty field: an empty field may mean nobody asked the patient. So “no known allergies” (NKA) is documented explicitly, and some systems block medication ordering until the allergy status is documented.
• Allergy versus side effect (intolerance): recording nausea from a drug as an allergy produces needless alerts, and physicians get used to overriding all of them.
  Practice question: physicians override 90% of allergy alerts (alert fatigue), and a review finds that most of the recorded “allergies” are nausea or stomach upset. What is the fix? → Record intolerances separately from true allergies, with the type and severity of the reaction.
• The safety layers in the medication process: the system’s check at ordering (CPOE), then pharmacist review, then bar-code scanning at the bedside (BCMA) and documentation in the eMAR. Each layer can catch an error the earlier ones missed, but the automatic checks in all of them rely on the same coded data.
• Checking the medication order against allergies: a related question in the full bank.
• SNOMED CT for structured clinical documentation: a related question in the full bank.
• Structured documentation versus free text: "Structured documentation versus free text" (in the full bank).