In HL7 messaging, there are different HL7 standards from which to choose. HL7 terms like V2 and V3 are often used. Outlined below are the benefits of each of these HL7 standards.
HL7 V2 Benefits:
- Reflects the complex “everyone is special” world of healthcare
- Much less expensive to build HL7 interfaces compared to custom interfaces
- Provides 80 percent of the interface and a framework to negotiate the remaining 20 percent on an interface-by-interface basis
- Historically built in an ad hoc way, allowing the most critical areas to be defined first
- Generally provides compatibility between 2.X versions
HL7 V3
- More of a “true standard” and less of a “framework for negotiation”
- Model-based standard provides consistency across entire standard
- Application roles well defined
- Much less message optionality
- Less expensive to build and maintain mid-to-long term interfaces
- Many decades of effort over ten year period reflecting “best and brightest” thinking
Learn more about the HL7 standards, including HL7 v3, with an in-depth white paper entitled The Evolution of HL7 (long version).
The following two tabs change content below.
Dave Shaver is the CTO for Corepoint Health. Dave has more than 20 years experience in training, consulting, and software development. He’s deeply involved in the HL7 standards community, including co-chair of HL7 Infrastructure and Messaging committee and co-chair of the HL7 FHIR Governance Board.
Latest posts by Dave Shaver (see all)
- HL7 ADT Q&A with Dave Shaver - July 2, 2014
- Health Standards Community Membership Archetypes: Who uses HL7? - August 6, 2013
- Note from the Field: Meditech 6.0 HL7 Integration - September 6, 2011
Pingback: HL7 Beginners Guide Article()
Pingback: Who Is Using HL7 3.X Messaging? | HL7 Standards()