Implementation FAQ:Implementer Organization
This page contains questions and recommendations related to the organization or project that is responsible for the implementation.
Back to Implementation FAQ
(add a question if you so desire)
Overcome steep 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. Implementers have to understand the RIM classes and attributes.
Need a "keeper of the vision"
Designate one person to keep the architecture and the business requirements (as a whole) on a consistent track. Otherwise scope creep will ensure they are disjunctive.
Exchange experiences with other v3 implementers
The exchange of experience in a forum with other implementers/vendors saves money. HL7 affiliate organizations offer a platform for such a forum.
Dealing with being an early adopter
If the scope of your implementation is broad you should anticipate being an early adopter of the Standard and breaking new ground. It's worth it, but you must factor into your plans a steep learning curve; ongoing participation in the HL7 organization to move your designs through membership approval; and retrofitting of early installations to the approved specifications.