HITECH. Meaningful Use. HIE. IHE. Many words and acronyms, but there is one often overlooked — Health Level Seven or HL7.
While HITECH and Meaningful Use, Stage 1, primarily focused on get certified EHRs installed and operational, lingering in Stage 2 is actually exchanging patient data. Health Information Exchanges, or HIEs, are receiving a lot of attention and funding, and IHE Profiles are now finding real adoption in how data will be exchanged. IHE Profiles are getting respect, finally, which they may deserve.
To get the patient data flowing within any health care provider organization, though, requires HL7. HL7 is the clinical data standard, and many will scoff at the idea that this is a standard. It has been called a “framework for negotiation” more often than a healthcare standard.
Regardless, HL7 is part of the foundation in which any healthcare interface, integration, or interoperability initiative can begin. There are no “out-of-the-box” HL7 templates between two or more applications, since each application is implemented a little differently and HL7 is used with just a little modification. This is what creates the joy and opportunity for many healthcare interfacing teams in the essential work they do.
The key points to remember are:
- There is software to make HL7 easier. In the commercial world, this software is usually called middleware. In healthcare, it is typically called an interface engine.
- As it relates to Meaningful Use Stage 1, HL7 version 2.3.1 and HL7 version 2.5.1 are specifically called out as the ones to use. In the proposed Meaningful Use Stage 2 requirements, it is narrowed to just HL7 version 2.5.1.
- HL7 is also responsible for the Continuity of Care Document, or CCD, standard as well as the Consolidated CDA initiative. This will be essential to deliver patient summary data to other providers as a patient transitions through a cycle of care. CCD is also the standard used to give patients their own data.
To answer the question in this post, yes, HL7 is still meaningful and relevant. It is time to dig in deeper to understand what this really means. Our own blogger, Rob Brull, was recently interviewed by Healthcare IT News on the 8 Common Questions about HL7. Check it out to gain additional insights.
If you want to review some of the basics, below are links to the common HL7 message types and an overview of what is really involved in an HL7 interface.
- What is an HL7 ADT message? (Hint: patient demographics)
- What is an HL7 ORM message? (Hint: patient orders)
- What is an HL7 ORU message? (Hint: patient test results)
- What is an HL7 DFT message? (Hint: patient billing)
- What is an HL7 interface? (Hint: what makes patient data flow between healthcare applications)
It is important to get a better grasp of HL7 and what it delivers in healthcare integration and in the new world of Meaningful Use. Enjoy!
Latest posts by Jon Mertz (see all)
- 5 things I learned in 10 years in healthcare - June 14, 2016
- Millennials on a Mission: Health IT Leader, Jenny Sabol - February 3, 2016
- Giving #HITthanks. Share Your Health IT Gratitude! - November 24, 2014