HL7 Versions Defined
Thanks to Sam Forouzi (HL7 Subject Matter Expert at eHealth FORCAST), email@example.com, for this contribution!
The objectives needs to get defined clearly first. The certificates are valuable only when gained on top of existing knowledge, experience, and/or expertise. There are many training options available for someone new to HL7. These training programs may be customized for a specific audience. Please feel free to ping me later for any additional information.
There are markets for each of the three topics mentioned:
• A very large majority of hospitals, laboratories, clinics, and EMRs, in North America use HL7 v2.x for integrating both internal systems / devices and also integration with external parties.
• The majority of clinical information systems and administration systems are fully supporting HL7 2.x.
• Most integration engines fully support v2.x.
• Most jurisdictional EHR projects are using v3 for internal integration; however still use v2.x and middleware/mapping to integrate to POS.
• Vendors are beginning to adapt to v3, but not yet widely available
• V3 is being localized for different jurisdictions, so there are much opportunities for education and also contribution with the local affiliates
• The main vehicle for CDA is XML/XLS and most web browsers that may parse clinical documentation and display using HTML. So generally speaking there are much opportunities in this area.
The most demanding jobs that I see these days are for hands-on HL7 specialist with specific tools and/or interface engines.
Hope this provides your classmate some starting pointers. Good luck to you both.