Conformance and Guidance for Implementation/Testing

HL7 Implementation Committee Page

This currently contains a set of brainstormed points that can be turned into a FAQ for implementation

• Source and target systems lack rich semantics

Black and white TV to HDTV to black and white

• cost benefit ratio - startup costs are very high

Have a running system using V2, how do I justify moving to V3, esp as V2 just keeps getting better.

• version 3 documentation not as easy to use as V2 documents

In v2.3.1 as a PDF -- one big document and using the find button is a great way to find what you want. This is particularly good as a single document.

• information overload

How much information has to be shared with a trading partner. If the trading partner is V3 knowledgeable is it easier to do.

• learning curve

Implementers have to understand the RIM classes and attributes

• fill the blanks transforms

V3 startup for implementers can be done by creating “fill the blanks” transforms.

• V2 implementation profiles are easy to read

It is

• get some example implementation guides on the wiki

• how to write an implementation guide

Added technical guide Added conformance profile guide Added wrapper documentation

• selling point for V3

What is the real value of the reference model in V3 – what is the life of the system – this can be a long time for strategic programs. These need to be future-proofed. Action: what does the marketing committee have on the rationale for using V3.