HLTH 2120 Week 8 Interoperability Brief Example

Why the Hospital and the Clinic Disagree About the Same Patient's Weight and Allergies: An Interoperability Brief Written at the Level of the Field

Student Name

Walden University

HLTH 2120: Health Informatics

Instructor Name

Month Day, Year

Why the Hospital and the Clinic Disagree About the Same Patient's Weight and Allergies: An Interoperability Brief Written at the Level of the Field

The Problem

A patient discharged from the hospital's medical-surgical unit visits his primary care clinic a week later. The clinic uses a different electronic health record system from the hospital, and the two exchange a summary of care document at discharge. The clinic nurse notices that the hospital summary lists his weight as 82 kilograms while the clinic's own record shows 194 pounds from three months ago, and that the hospital lists an allergy to sulfa drugs with a reaction of rash while the clinic lists "sulfa" with no reaction. She also sees that the hospital summary does not show an allergy to lisinopril that the clinic recorded a year ago. The patient is the same person. Why do the systems report different things?

It is tempting to answer with the name of a standard, such as saying the systems are not interoperable or that they need to adopt a newer exchange format. That answer does not tell anyone what to fix. This brief answers at the level of the field: what each system stores, how each defines it and what the exchange between them carries and drops. The scenario is a composite, and the systems are described generically.

The discrepancies matter clinically. A clinician deciding whether to prescribe a sulfonamide antibiotic, or an angiotensin-converting enzyme inhibitor similar to lisinopril, needs to know which allergy list to trust and why they differ.

Weight: Same Patient, Three Differences in the Field

What each system stores. The hospital stores weight as a number in kilograms with a timestamp and a method of measurement. The clinic stores weight as a number in pounds with a visit date and no method field.

How each defines it. The hospital summary sends the dosing weight, which its rules set to the most recent measured weight. The clinic shows the most recent weight from any clinic visit.

What the exchange carries. The summary of care document carries the weight with its unit and date. The clinic system displays it in a separate section for outside records and does not convert or compare it with its own value.

Result. 82 kilograms is about 181 pounds, so the two values differ by about 13 pounds, and they come from different dates three months apart. Neither system is wrong. The discrepancy is real weight change plus a unit difference plus a display that keeps outside data apart. A nurse who did not convert units would think the difference was much larger or much smaller than it is.

Allergies: Coded Versus Free Text

What each system stores. The hospital records allergies as coded entries: the substance from a standard drug terminology, a reaction from a list and a severity. The clinic records some allergies as coded entries and others, especially older ones, as free text typed by staff.

How each defines it. The hospital's sulfa allergy is coded to the sulfonamide antibiotic class with a rash reaction. The clinic's "sulfa" entry is free text, so the clinic system cannot tell whether it means sulfonamide antibiotics, other sulfur-containing drugs or something the patient described vaguely. Free text keeps the writer's words but cannot be matched, counted or checked by software without further processing (Rosenbloom et al., 2011).

What the exchange carries and drops. The summary of care document can carry coded allergies with substance, reaction and severity. When the clinic sends records to the hospital, its free-text entries may be sent as text only or may not be sent in a form the receiving system can reconcile. That is the likeliest explanation for the missing lisinopril allergy: if it existed in the clinic only as free text and was not part of what the clinic transmitted to the hospital at admission, the hospital never received it in a usable form.

Result. The allergy discrepancies are a field-level problem: coded data travel and can be reconciled; free text either does not travel or arrives as a sentence a computer cannot match.

Where Standards Fit

Standards matter, but only at the level of fields. A federal list known as USCDI sets out the kinds of data, allergies and body weight among them, that certified record systems have to be able to send and receive, and it names the code sets to use (Office of the National Coordinator for Health Information Technology, n.d.). Exchange formats such as HL7 FHIR define how those elements are packaged and sent. A standard can require that weight be sent with a unit and that allergies be coded. It cannot make a clinic recode a decade of free-text allergies, and it cannot decide which of two weights a clinician should trust.

Research on hospital interoperability has found steady progress in hospitals sending, receiving, finding and integrating outside data, but integration, actually bringing outside data into the record where clinicians use it, has lagged behind sending and receiving (Holmgren et al., 2017). The clinic in this scenario received the hospital's data but kept it in a separate section, which is exactly that gap.

What Would Fix the Discrepancies

Three changes, each at the field level, would resolve most of what the clinic nurse saw. First, the clinic should display outside weights converted into its own unit beside its own most recent value, with both dates, so differences are visible and interpretable. Second, the clinic should run a one-time project to convert free-text allergies into coded entries, starting with drug allergies, so that they can be sent and reconciled. Third, both organizations should use the allergy reconciliation step their systems already offer at each transition, in which a clinician reviews outside entries and accepts, merges or rejects them, rather than leaving outside data in a separate section. None requires a new standard. Each requires deciding that the meaning of a field is shared between systems, not just its value.

The clinic nurse in the scenario can act today, before any of these changes: ask the patient which weight and which allergies are current and record the answers in coded form.

References

Holmgren, A. J., Patel, V., & Adler-Milstein, J. (2017). Progress in interoperability: Measuring US hospitals' engagement in sharing patient data. Health Affairs, 36(10), 1820-1827. https://doi.org/10.1377/hlthaff.2017.0546

Office of the National Coordinator for Health Information Technology. (n.d.). United States Core Data for Interoperability (USCDI). HealthIT.gov. https://www.healthit.gov/isp/united-states-core-data-interoperability-uscdi

Rosenbloom, S. T., Denny, J. C., Xu, H., Lorenzi, N., Stead, W. W., & Johnson, K. B. (2011). Data from clinical notes: A perspective on the tension between structure and flexible documentation. Journal of the American Medical Informatics Association, 18(2), 181-186. https://doi.org/10.1136/jamia.2010.007237