Overcoming the Learning Curve

HL7 v3 is generally seen as having a steep learningcurve.

The following is some advice from those that have implemented v3 on how to overcome the learning curve:

• Make sure to invest both time and resources in the initial phase. The cost to entry is significant, however once you know the basics it is relatively easy to extend. The HL7 object model introduces complexity for simple messages on the one hand, but provides a unified model for complex clinical messages.
• Use the introductory presentations on the HL7.org website (although these are fragmented at the moment, have inconsistent design/presentation, are confusing when read "out of context", and some are quite old)
• Read Understanding Version 3 (the primer)
• Use a (Framework-) Implementation Guide (one single domain within the implementation guide) as a starter document for those new to v3, and not a Normative/Development Edition. The implementation guide describes a subset of the standard and is implementation oriented, which makes it easier on the reader. The Normative/Development Editions are useful at a later stage.
• Have one or more HL7 v3 experts on your team. They play the role of catalyst and keep the rest of the team on track through peer review and collaborative design.
• Attend HL7 training outside of normal peer-based learning
• Use the contents of the HL7 Wiki, especially for areas such as Lore. It presents a consensus of ideas in plain english (as opposed to standards-speak).
• Familiarity with healthcare workflows, as well as messaging in general is a plus.
• HL7 is an open community, which allows for Peer Knowledge Transfer, between countries/organizations. Avoid re-inventing the wheel.