NUR 5310 Module 2 Interoperability Analysis Example

How a Pharmacy Fill Reaches the Admission Screen: Four Levels of Interoperability Explained Without Vendor Language

Student Name

Master of Science in Nursing (MSN), Thomas Edison State University

NUR-5310: Nursing Informatics: Concepts and Issues

Mentor Name

Month Day, Year

How a Pharmacy Fill Reaches the Admission Screen: Four Levels of Interoperability Explained Without Vendor Language

The first module showed that an admission medication list often contains three versions of the same drug from three sources. This paper asks how those sources could reach the admitting nurse automatically, and why they often do not. It explains the levels of interoperability, the standards that carry medication data between systems, the networks and rules that govern exchange, and the practical gaps that remain on our medical units. The aim is to explain exchange in terms of concepts and standards rather than the names of commercial products, so that the analysis would hold regardless of which electronic record a hospital uses.

Four Levels of Interoperability

Interoperability is usually described in layers. At the foundational level, a message can travel from sender to receiver and the receiver to accept it, without any requirement that the receiver understand it. Structural interoperability defines the format of the data so that fields arrive in predictable places, for example a message in which the drug name, dose and frequency always occupy defined positions. At the semantic level, the receiving system must grasp what each data element means, which depends on shared terminologies such as RxNorm for drugs and SNOMED CT for allergies. Organizational interoperability covers the agreements, policies and trust arrangements that let organizations exchange data at all, including consent and governance.

A failure at any level stops useful exchange. A pharmacy can send a fill history that arrives intact, satisfying the first two levels, but if the receiving system cannot map the pharmacy's product code to its own drug catalog, the nurse sees a string of text rather than a reconcilable medication, a failure of semantic interoperability. If the two organizations have no agreement to share data, nothing arrives at all.

The Standards That Carry Medication Data

Several standards carry medication information. Retail pharmacies and prescription networks exchange prescriptions and fill histories using a standard developed for pharmacy transactions, which lets a hospital query recent dispensing records for an admitted patient. Hospital systems have long exchanged orders, results and administrative events using Health Level Seven version 2 messages, which are flexible but loosely defined, so implementations differ from site to site. Clinical summaries move between organizations as structured documents, such as continuity of care documents, which include a medications section.

The newest standard, Fast Healthcare Interoperability Resources, organizes data into small, defined resources, such as a medication request, a medication dispense and a medication statement, that an application can request over the same kind of web connection a banking app uses. Mandel et al. (2016) described a platform built on this standard that allows third-party applications to run inside different electronic records through a common interface, showing how a standardized programming interface could let the same medication reconciliation tool work across vendors. The resource model matters for nursing because it separates what was prescribed, what was dispensed and what the patient reports taking, three facts that the admission interview must reconcile.

Networks, Rules and Information Blocking

Exchange also needs networks and rules. Health information exchanges, regional or national, connect hospitals, clinics and pharmacies so that records can be queried across organizations. Federal policy has pushed exchange forward. The rule implementing the interoperability provisions of the 21st Century Cures Act requires certified health information technology to support a standardized application programming interface based on the new standard and prohibits information blocking, practices by providers, developers and networks that unreasonably interfere with access, exchange or use of electronic health information, subject to defined exceptions (Office of the National Coordinator for Health Information Technology, 2020). In principle, this means a hospital should be able to obtain a patient's medication data from other organizations with fewer barriers than a decade ago.

For nurses, the practical meaning of these rules is that a patient's medication data held by another provider or pharmacy should, in most cases, be obtainable when it is needed for care, and that an organization cannot refuse to share it simply because sharing is inconvenient or commercially unattractive. The rules do not guarantee that the data will be clean, complete or coded in a form the receiving system can use, which is the gap the rest of this paper examines. They also leave room for patients to restrict certain disclosures, and nurses should not assume that an empty external history means the patient has no prescriptions; it may mean only that the patient's pharmacy does not participate in the network our hospital uses.

What Still Fails on Our Units

In practice, three gaps remain on our medical units. First, external medication data arrive in a separate tab that the admitting nurse must open, rather than appearing beside the interview, so they are often missed during a busy admission. Second, fill histories show what was dispensed, not what the patient takes; a patient who stopped a drug last month still shows a recent fill. Third, data from small independent pharmacies and from cash purchases are often absent, and over-the-counter products never appear. These gaps matter because, as Cornish et al. (2005) found, unintended discrepancies at admission are common and many carry potential for harm; better data can reduce them only if the data are visible at the moment of the interview and interpreted with the patient.

Interoperability, in other words, is necessary but not sufficient. The standards and rules can deliver more data to the admission screen; whether the data improve safety depends on workflow design, nurse interpretation and the patient's own account, which is why the medication interview remains a nursing skill rather than a data transfer.

Conclusion

A pharmacy fill reaches an admission screen only if systems connect, formats align, meanings are shared and organizations agree to exchange, the four levels of interoperability. Standards for pharmacy transactions, messaging, documents and the newer resource model carry the data, and federal rules now discourage blocking it. The remaining gaps on our units are less about standards than about where and how the data appear in the nurse's workflow. The next module turns to the privacy and security questions raised by moving this information across organizations.

Interoperability, in other words, is not a single switch the hospital turns on but a set of levels that must each work for the admitting nurse to trust the screen.

References

Cornish, P. L., Knowles, S. R., Marchesano, R., Tam, V., Shadowitz, S., Juurlink, D. N., & Etchells, E. E. (2005). Unintended medication discrepancies at the time of hospital admission. Archives of Internal Medicine, 165(4), 424-429. https://doi.org/10.1001/archinte.165.4.424

Mandel, J. C., Kreda, D. A., Mandl, K. D., Kohane, I. S., & Ramoni, R. B. (2016). SMART on FHIR: A standards-based, interoperable apps platform for electronic health records. Journal of the American Medical Informatics Association, 23(5), 899-908. https://doi.org/10.1093/jamia/ocv189

Office of the National Coordinator for Health Information Technology. (2020). 21st Century Cures Act: Interoperability, information blocking, and the ONC Health IT Certification Program [Final rule]. 85 Fed. Reg. 25642. https://www.federalregister.gov/d/2020-07419