CIS 450 Module 4 Data Standards and Interoperability Example

One Lab Result, Four Systems: How Data Standards Make Interoperability Possible

Student Name

Health Care Administration Program, Aspen University

CIS 450: Informatics in Healthcare

Instructor Name

Month Day, Year

One Lab Result, Four Systems: How Data Standards Make Interoperability Possible

Interoperability, the ability of systems to exchange information and use it, depends on standards: shared ways of naming, coding and packaging data. Without standards, a result sent from one system arrives as text another system cannot interpret. This paper traces one laboratory result through four systems to show how standards work and where they fall short.

The Result

Mr. P., 66, takes a diuretic and a blood pressure medicine. His primary care physician orders a basic metabolic panel. A reference laboratory reports his potassium as 3.1 mmol/L, below normal. The result must reach the clinic's record, trigger an alert, flow to the regional health information exchange for other clinicians and appear in the patient's phone app.

Levels of Interoperability

Interoperability is often described in levels. At the most basic level, called foundational, one system can simply transmit data to another. At the structural level, the message follows an agreed layout so each field can be located. Semantic interoperability means both systems understand the meaning of the data, so a potassium result is recognized as potassium, with its units and reference range, and can drive alerts and trends. Organizational interoperability adds the policies and agreements that allow exchange.

Standards Along the Way

The table lists the main standards involved.

LOINC

Laboratories use their own local test names, so a clinic may receive dozens of different names for the same test. LOINC provides universal identifiers for laboratory and clinical observations; a five-year update described how it had become widely adopted for identifying laboratory observations across institutions (McDonald et al., 2003). When the lab maps its potassium test to the LOINC code, the clinic's record can recognize it regardless of the lab's local name.

Messaging the Result

The reference lab sends the result to the clinic in an HL7 version 2 message, a long-established format that structures patient identifiers, the test code, value, units, reference range and abnormal flag into defined segments. The clinic's interface engine receives the message, matches Mr. P. by identifiers and files the result in his chart, flagged as low.

FHIR and Apps

Newer exchange increasingly uses FHIR, which represents data as web resources such as Observation and MedicationRequest that applications can request through standard interfaces. The SMART on FHIR platform showed how third-party apps could run across different electronic record systems by combining FHIR with standard authorization, demonstrated with multiple vendors in 2014 (Mandel et al., 2016). Mr. P.'s phone app retrieves his potassium result through such an interface.

The Health Information Exchange

The clinic sends a summary to the regional exchange, where the hospital's emergency department can see it if Mr. P. arrives. Exchanges rely on patient matching, consent policies and agreements among participants, the organizational layer of interoperability.

Where It Breaks Down

Standards reduce but do not eliminate problems. Labs may map tests to the wrong code, units may differ, patient matching can fail and receiving systems may file results as documents rather than structured data. When researchers measured hospital exchange nationally, integration of outside data was the weakest link and showed no gain from one year to the next (Holmgren et al., 2017).

Why Semantic Interoperability Matters

If Mr. P.'s potassium arrived as a scanned document, the clinic's record could not trend it, trigger a low-potassium alert or check it against his diuretic. Only coded, structured data support decision support, quality measurement and research. The difference between sending data and making it usable is the difference between structural and semantic interoperability.

Policy Drivers

Federal policy has pushed standards adoption through certification requirements for electronic records, required use of standard application programming interfaces and rules against information blocking. These policies aim to make data flow to patients and between providers by default rather than by special arrangement.

What Administrators Should Require

When selecting or contracting for systems, administrators should require support for current standards, including FHIR-based interfaces, LOINC and SNOMED CT mapping, participation in exchange networks and the ability to import structured data, not only documents. They should also budget for interface maintenance and data quality checks, since standards require ongoing work.

Data Quality

Standards work only with good data. The clinic periodically reviews incoming results for unmapped tests, mismatched units and filing errors, and reports problems to the lab. Clean mappings at the source prevent errors everywhere downstream.

Information Blocking Rules

Federal rules now prohibit information blocking, practices that unreasonably interfere with access, exchange or use of electronic health information, with defined exceptions. For administrators, that means policies and contracts must not restrict appropriate sharing, and systems must support patient access through standard interfaces.

Terminology Mapping Work

Mapping local codes to standard terminologies takes skilled staff and ongoing effort. When the laboratory added a new test, the clinic's interface analyst had to confirm its LOINC mapping before results could file correctly. Budgeting for terminology maintenance is part of the real cost of interoperability.

Patient Matching

Even perfectly coded data are useless if attached to the wrong patient. Exchanges use demographic matching, and errors occur with common names, typos and changed addresses. Consistent registration practices, verified identifiers and review of possible matches reduce the risk.

Conclusion

One potassium result showed how LOINC, units standards, SNOMED CT, ICD-10-CM, RxNorm, HL7 messaging and FHIR work together to move and interpret data across a laboratory, a clinic, an exchange and a patient's app. Standards make semantic interoperability possible, but national data show integration still lags. Administrators can close the gap by requiring standards, supporting exchange and investing in data quality.

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

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

McDonald, C. J., Huff, S. M., Suico, J. G., Hill, G., Leavelle, D., Aller, R., Forrey, A., Mercer, K., DeMoor, G., Hook, J., Williams, W., Case, J., & Maloney, P. (2003). LOINC, a universal standard for identifying laboratory observations: A 5-year update. Clinical Chemistry, 49(4), 624-633. https://doi.org/10.1373/49.4.624