This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Implementation FAQ

From HL7Wiki
Jump to navigation Jump to search

This currently contains a set of brainstormed points that can be turned into a FAQ for implementation. The first draft of this page was created on the fly in the Implementation Committee, partly as a group learning exercise to establish that we could develop the content in this way.

The following text will be retained as a record of the session, and then a new set of pages will be created to form a basis for the FAQ


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.

It would seem the implementers need to press Pubs/tooling somewhat harder to get a search option in the standard publication. This has been discussed before as far as I know, but the timing of such a sloution is unclear. Rene spronk 12:46, 21 May 2006 (CDT)

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.