NeoTool — Singular Focus, Healthcare Integrated

Posted in What is HL7?, HL7 Standards, HL7 Standard

1. Decide if the HL7 standard Version 3 has true value in your environment. What do you expect V3 to do that existing V2 interfaces are not already doing?
2. Discuss interfacing strategy with your vendors. If you are moving towards HL7 V3, review existing vendors’ development plans to add V3 or pick new vendors with V3 interfaces.
3. Demand HL7 V3 from vendors only when there is a solid business or clinical motivation because the costs to have V3 in your environment will be high.
4. Expect that mapping between the HL7 standards (i.e., HL7 V2 and V3) will be challenging and expensive. Interface engines must be augmented with substantial data repository functionality in order to provide any mapping.
5. Weigh costs of continuing to build “80 percent standard” HL7 V2 interfaces against entering the expensive world of V3.
6. Understand how early your site will be in the HL7 V3 learning curve - ask any vendor who proposed a V3 interface how many other sites have the same V3 interface running and how many different applications are communicating using the interface.
7. Consider if your site should become an early adopter of the HL7 V3 standard – how much local interface expertise do you have? What is the backlog of interfaces? How will V3 help solve your business requirements short and long term?
8. Gain education on what is HL7 and how HL7 Version 3 fits in; start to understand the impact it will have on your interfacing environment.
9. Become involved in the HL7 standards organization – this will keep you up-to-date on the most recent developments and allow you to be part of the process.

Learn more details about the HL7 standard with the white paper entitled The Evolution of HL7.

Last 5 posts by Dave Shaver

• Massachusetts Hospitals Must Have CPOE by 2012 and CCHIT-Certified EHRs by 2015 - August 13th, 2008
• HL7 Dates and Times - July 25th, 2008
• HL7 Time Zone Qualification - July 25th, 2008
• RHIOs vs. Peer-to-Peer Communications - July 11th, 2008
• Hospitals Allowed to Pay for EMR Interfaces and Not Violate Stark - June 3rd, 2008