This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Migration from HL7 v2 to HL7 v3"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 10: | Line 10: | ||
*The issue is also covered by a module in the 'HL7 v3 implementation training' (module xx, available at xxxURL) | *The issue is also covered by a module in the 'HL7 v3 implementation training' (module xx, available at xxxURL) | ||
*See also [http://www.ringholm.de/docs/04300_en.htm], a whitepaper which contains examples translated between HL7 v2 and HL7 v3. | *See also [http://www.ringholm.de/docs/04300_en.htm], a whitepaper which contains examples translated between HL7 v2 and HL7 v3. | ||
| + | *See also [http://www.hl7standards.com/blog/2010/11/16/converting-from-an-hl7-version-2-message-to-cda/] a blogpost about v2.x to CDA conversion. | ||
==Analysis== | ==Analysis== | ||
Revision as of 15:38, 16 November 2010
Summary
This page contains information about the migration from HL7 version 2 to HL7 version 3. This includes the following aspects:
- The translation from HL7 version 2 messages to HL7 version 3 message structures
- This includes the strategy of extending the current HL7 version 2 messages to facilitate the translation process.
- The implementation of a HL7 version 3 interfaces next to existing HL7 version 2 interfaces
References
- The following page needs to be sourced for concepts: Implementation FAQ:Migration from version 2
- The issue is also covered by a module in the 'HL7 v3 implementation training' (module xx, available at xxxURL)
- See also [1], a whitepaper which contains examples translated between HL7 v2 and HL7 v3.
- See also [2] a blogpost about v2.x to CDA conversion.
