Health Level 7 (HL7) International is an ANSI-accredited, standards-developing organization founded in 1987 with members in more than 50 countries. HL7 International was created with the goal of developing a framework and standards that support the exchange and sharing of electronic health information among applications. Without a standard, consistent framework for exchanging data, exchanging data between healthcare systems required the development of custom interfacing systems, which are costly and time-consuming to develop. Jump to resource links -->
The HL7 standards are a set of messaging standards that aim to create a consistent messaging framework to allow clinical applications to seamlessly exchange data. More than 90% of healthcare facilities and the largest health information system vendors today use the HL7 standards. HL7 is used by clinical interface specialists, healthcare application vendors, government entities, and medical informaticists. There are several versions of the HL7 standards, including:
The HL7 standards are grouped into four primary reference categories:
The HL7 protocol defines how data is packaged and exchanged by setting the language type, data structure, and types of data to support seamless integration between applications and systems. The HL7 protocol aims to allow healthcare organizations and applications using the HL7 messaging standard – even those that speak different languages – to communicate and share data.
A common language and consistent data structure eliminate ambiguity and the risk of misinterpretation, while also eliminating the need to develop custom interfacing systems. As a result, healthcare information systems vendors can eliminate lengthy and costly integration projects, bringing applications to market faster and giving healthcare organizations more choices when adopting new information systems.
The HL7 protocol was designed to be flexible, allowing extensive customization for easy adoption, and applications can use different HL7 formats or adopt different aspects of the HL7 protocol. As a result, there are unique implementations of the framework from one organization or application to the next, making interfacing between disparate applications difficult. Overcoming these integration challenges requires a significant investment in integration development.
While HL7 Version 2 remains the most widely used, industry-accepted protocol for exchanging clinical data between systems and applications, there’s a continued push for greater interoperability. Continued adoption of HL7 and the emergence of FHIR create opportunities for developers to create new and innovative tools to support the seamless exchange of healthcare data.
HL7 is the most important standard currently used in healthcare but, while it is used in almost every health application and health system, there is still confusion over what it actually is and how it works. This article provides a high level summary of HL7, its strengths, weaknesses, and how APIs are changing the entire healthcare interoperability industry.
Dave Levin, MD
RESTful APIs are the backbone of many webservices today. Having the tools to integrate an not-natively-RESTful interface engine with this common standard opens a lot of possibilities. In the healthcare space, queuing the HL7 properly is critical. In this article, we explore ways to do this properly.