The Allergy That Arrived as a Picture: Standards and Interoperability Behind a Near-Miss After Interhospital Transfer
Student Name
Doctor of Nursing Practice Program, Aspen University
DNP865: Healthcare Technologies and Informatics
Instructor Name
Month Day, Year
The Allergy That Arrived as a Picture: Standards and Interoperability Behind a Near-Miss After Interhospital Transfer
Interoperability is often discussed abstractly, as systems exchanging data. Its importance becomes concrete when a piece of safety-critical information fails to travel. This paper analyzes a composite near-miss in which a patient's documented penicillin anaphylaxis did not reach the receiving hospital's allergy list after transfer, identifies the levels of interoperability that failed, explains the standards and terminologies that would have carried the allergy correctly, and recommends changes.
The Event
Mr. K., 58, was transferred from a community hospital to a tertiary center for cardiac surgery. The community hospital's electronic record listed a coded allergy to penicillin with the reaction "anaphylaxis." The transfer packet, sent through a document exchange service, included a discharge summary as a scanned PDF, in which the allergy appeared in a paragraph of text. At the receiving hospital, the admitting nurse asked Mr. K. about allergies; groggy and short of breath, he said "none that I know of." The allergy list was recorded as no known allergies. Two days later, a physician ordered piperacillin-tazobactam for a suspected pneumonia. The pharmacist, reviewing outside records for another reason, found the allergy in the scanned summary and stopped the order before it was given.
Why Allergy Data Matter
Drug allergy entries are everywhere in health records, and they do real work. Across the records of more than 1.7 million patients in one large health system, 35.5 percent had at least one documented drug allergy, with penicillins the most common at 12.8 percent (Zhou et al., 2016). Allergy lists drive automated checks in ordering and dispensing, so a missing entry disables a safety system that clinicians assume is working. At the same time, many allergy labels are inaccurate: current practice guidance distinguishes immune-mediated allergy from intolerance and encourages evaluation of labels such as penicillin allergy that often do not reflect true hypersensitivity (Khan et al., 2022). An interoperable record should therefore carry not only the allergen but also the reaction and its severity, so that the receiving team can tell anaphylaxis from nausea.
Layers of Interoperability That Failed
Lehne et al. (2019) describe interoperability in layers: foundational interoperability, the technical ability to transmit data; structural interoperability, the use of common formats so that data can be parsed into fields; semantic interoperability, the use of shared terminologies so that meaning is preserved; and organizational interoperability, the policies, processes, and trust that allow exchange to be used in practice.
In this event, foundational interoperability worked: the document arrived. Structural interoperability failed, because the allergy traveled inside a scanned image rather than in a structured allergy section that the receiving system could import. Semantic interoperability was never tested, because nothing coded reached the receiving system. Organizational interoperability also failed: the receiving hospital's process relied on the patient's recall at admission and did not require reconciliation of outside allergy data before the list was finalized. The allergy crossed the network successfully and was still lost, because it arrived as something a person had to read rather than something a system could use.
The Standards That Would Have Carried It
Existing standards could have prevented the failure. A structured continuity of care document based on the HL7 Consolidated Clinical Document Architecture includes a dedicated allergies and intolerances section with coded entries. The newer HL7 Fast Healthcare Interoperability Resources standard defines an allergy and intolerance resource that can carry the substance, the type of reaction, its severity, the criticality, and whether it was verified, and it can be exchanged through modern application programming interfaces. Terminologies give each element shared meaning: RxNorm identifies the drug or drug ingredient, and SNOMED CT codes the reaction, such as anaphylaxis. Had the community hospital sent a structured document or FHIR resource with these codes, the receiving system could have displayed the allergy for reconciliation and fired an alert when piperacillin-tazobactam was ordered, since the penicillin class would be recognized.
The Human Factors at Admission
Technology was not the only layer that failed. The admitting nurse asked a breathless, sedated patient about allergies and accepted his answer, a reasonable step that nonetheless relied on the least reliable source available at that moment. Patients often forget or misremember allergies, especially when ill, and family members were not present. The admission screen allowed "no known allergies" to be selected in one click, with no prompt to check outside records, while the outside documents sat in a separate media tab that required several clicks to open. The design made the fast answer easy and the thorough answer hard. Human factors principles suggest reversing that: when outside records exist, the admission screen should display their allergy content, or at least a flag that outside allergies were found, before "no known allergies" can be recorded. Such a prompt does not depend on the exchange being fully structured, so it can be implemented while the technical work on structured exchange proceeds.
Recommendations
Technical: the two hospitals should exchange structured summaries rather than scanned documents, using the national exchange framework both participate in, and the receiving hospital should enable import of outside allergy entries into a reconciliation queue. Organizational: allergy reconciliation should be a required step within 24 hours of transfer admission, performed by a nurse or pharmacist using both patient report and outside records, and the allergy list should not be marked as reviewed until outside records have been checked. Clinical: allergy entries should always include the reaction and severity, since a label without a reaction invites both overcaution and dangerous dismissal. Measurement: the receiving hospital should audit a sample of transfer admissions monthly for discrepancies between outside and local allergy lists.
Conclusion
Mr. K.'s penicillin anaphylaxis traveled from one hospital to another and still disappeared, because it moved as an image rather than as structured, coded data, and because the receiving process relied on memory. Standards for structured documents, allergy resources, and shared terminologies exist to prevent exactly this failure. DNP-prepared leaders can close the gap by insisting on structured exchange and by building reconciliation into the workflow that uses it.
References
Khan, D. A., Banerji, A., Blumenthal, K. G., Phillips, E. J., Solensky, R., White, A. A., Bernstein, J. A., Chu, D. K., Ellis, A. K., Golden, D. B., Greenhawt, M. J., Horner, C. C., Ledford, D., Lieberman, J. A., Oppenheimer, J., Rank, M. A., Shaker, M. S., Stukus, D. R., Wallace, D., ... Wang, J. (2022). Drug allergy: A 2022 practice parameter update. Journal of Allergy and Clinical Immunology, 150(6), 1333-1393. https://doi.org/10.1016/j.jaci.2022.08.028
Lehne, M., Sass, J., Essenwanger, A., Schepers, J., & Thun, S. (2019). Why digital medicine depends on interoperability. npj Digital Medicine, 2, Article 79. https://doi.org/10.1038/s41746-019-0158-1
Zhou, L., Dhopeshwarkar, N., Blumenthal, K. G., Goss, F., Topaz, M., Slight, S. P., & Bates, D. W. (2016). Drug allergies documented in electronic health records of a large healthcare system. Allergy, 71(9), 1305-1313. https://doi.org/10.1111/all.12881
How this DNP 865 Module 2 example is structured
DNP865 Module 2 papers typically examine standards and interoperability behind a real exchange failure. Aspen does not publish module deliverables, so check your classroom for the exact prompt. This example describes one failure, establishes why the data matter, applies a layered interoperability model, explains the standards that would have worked and recommends technical, organizational and clinical changes.
DNP865 Module 2 questions, answered
What does DNP865 Module 2 usually ask for?
The module typically asks you to analyze standards and interoperability, often through an example of a data exchange failure, and explain what standards and terminologies would have prevented it. Aspen does not publish module deliverables, so your classroom's instructions govern.
What are the layers of interoperability?
Foundational, the ability to transmit data; structural, common formats so data can be parsed; semantic, shared terminologies so meaning is preserved; and organizational, the policies and processes that let exchange work in practice.
How should allergies be exchanged between systems?
As structured, coded entries, for example in a C-CDA allergies section or a FHIR allergy and intolerance resource, with RxNorm for the substance and SNOMED CT for the reaction, including severity and verification status.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official Aspen University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.