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

Difference between revisions of "Implementation FAQ"

From HL7Wiki
Jump to navigation Jump to search
 
(42 intermediate revisions by 7 users not shown)
Line 1: Line 1:
−
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.
+
There are a considerable number of implementations of HL7 version 3 based on a [[Development Edition]], a [[Normative Edition]] (e.g. 2010) or a Project Specific Edition (e.g. the NHS). This document aims to describe the most important lessons learned from these implementations, as well as some of the frequently asked questions related to the implementation of HL7 version 3.  
  
−
== Source and target systems lack rich semantics ==
+
As with all FAQs some of the documentation provided on these pages may sound "obvious" to you; this may not necessarily be true for other implementers.
−
Black and white TV to HDTV to black and white
 
  
−
== cost benefit ratio - startup costs are very high ==
+
Note: parts of this FAQ are currently (November 2010) undergoing major changes/updates.
−
Have a running system using V2, how do I justify moving to V3, esp as V2 just keeps getting better.
 
  
−
 
+
This FAQ is organized into a number of categories, mainly in order to limit the size of the individual pages:
−
 
+
*General:
−
== version 3 documentation not as easy to use as V2 documents ==
+
**[[Implementation FAQ:Getting started|Getting started]] (getting to know the HL7v3 standard; education; resources)
−
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.
+
**[[Implementation FAQ:Implementer Organization|Implementer Organization]] (organizational recommendations for v3 implementer organizations)
−
: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. [[User:Rene spronk|Rene spronk]] 12:46, 21 May 2006 (CDT)
+
*Localization:
−
 
+
**[[Implementation FAQ:Localized specifications|Localized specifications]] (localizing the HL7 v3 standard)
−
== information overload ==
+
*Implementation: (architecture and design)
−
How much information has to be shared with a trading partner.  If the trading partner is V3 knowledgeable is it easier to do.
+
**[[Implementation FAQ:Interface Development|Interface Development]] (software implementation)
−
== learning curve ==
+
*Deployment:
−
Implementers have to understand the RIM classes and attributes
+
**[[Implementation FAQ:Interface Deployment|Interface Deployment]]
−
 
+
*Special topics:
−
== fill the blanks transforms ==
+
**[[Implementation FAQ:Use of Transports with HL7 v3|Use of Transports with HL7 v3]]
−
V3 startup for implementers can be done by creating “fill the blanks” transforms.
+
**[[Implementation FAQ:Framework Issues|Framework Issues]] (national/regional infrastructures)
−
:This is very pragmatic. I'm not aware that this approach is being addressed in any of the implementation oriented Tutorial. It probably needs to be discussed, as quick-and-dirty implementation methods tend to be used more than theoretically flawless implementations... [[User:Rene spronk|Rene spronk]] 12:59, 21 May 2006 (CDT)
+
**[[Implementation FAQ:Migration from version 2|Migration from version 2]] (e.g. mapping)
−
 
+
**[[Implementation FAQ:Encryption and Security|Encryption and Security]] and [[Implementation FAQ:Digital Signatures|Digital Signatures]]
−
== V2 implementation profiles are easy to read ==
 
−
It is
 
−
:What does this mean for v3 implementations? We just have to make sure v3 implementation guides are easy to read. [[User:Rene spronk|Rene spronk]] 12:49, 21 May 2006 (CDT)
 
−
 
 
−
== get some example implementation guides on the wiki ==
 
−
:Good idea, the only ones I have on offer are however in Dutch. The use of a realm-specific language is one of the key features of an implementation guide. [[User:Rene spronk|Rene spronk]] 12:57, 21 May 2006 (CDT)
 
−
 
 
−
== 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.
 
−
 
 
−
Two documents from the Marketing Committee's document page:
 
−
*[http://www.hl7.org/Library/Committees/marketing/20041210%5Fv3%5Fvalue%5Fproposition%2Edoc Draft HL7 v3 Value Proposition Document]
 
−
*[http://www.hl7.org/Library/Committees/marketing/Canada%5FInfosheet%2Ezip Canada Infoway v3 Infosheet]
 

Latest revision as of 14:33, 10 November 2010

There are a considerable number of implementations of HL7 version 3 based on a Development Edition, a Normative Edition (e.g. 2010) or a Project Specific Edition (e.g. the NHS). This document aims to describe the most important lessons learned from these implementations, as well as some of the frequently asked questions related to the implementation of HL7 version 3.

As with all FAQs some of the documentation provided on these pages may sound "obvious" to you; this may not necessarily be true for other implementers. 

Note: parts of this FAQ are currently (November 2010) undergoing major changes/updates.

This FAQ is organized into a number of categories, mainly in order to limit the size of the individual pages:

Retrieved from "https://wiki.hl7.org/w/index.php?title=Implementation_FAQ&oldid=43293"