HL7 and FHIR: How the Two Major Standards for Healthcare Data Interoperability Work
HL7 与FHIR:医疗数据互操作协议如何运作
Summary
This article explains HL7 and FHIR, the two primary standards for exchanging data between electronic health records and hospital systems. While HL7 v2 supports internal communication using a message-based approach, FHIR utilizes REST APIs and resource models to facilitate external integration and new application development.
Details
Sharing data across different healthcare systems requires a common 'language.' This article details two major standards: HL7 (Health Level Seven) and FHIR. HL7 has provided communication standards since 1987 for various systems, such as EHRs and lab systems from different vendors. The widely used version is HL7 v2, which uses a message-based format where data is 'pushed' when an event occurs. This structure defines data fields by their sequential position, separated by characters like vertical bars. In contrast, FHIR (Fast Healthcare Interoperability Resources) is a newer standard built using common internet technologies: REST APIs and JSON format. It models medical data as discrete 'Resources,' giving each element—like patient information or observation results—its own network address (URL). This allows developers to retrieve only the necessary data on demand, using familiar HTTP methods like GET/POST. FHIR's significance lies in its pursuit of 'semantic interoperability.' By linking with common terminologies like LOINC and SNOMED CT, it ensures that a concept like 'blood glucose' means exactly the same thing across all systems. While HL7 v2 excels at internal 'message exchange,' FHIR is superior for external data exposure and developing new applications (e.g., patient portals).
Original content copyright by respective publishers