TR 2964-2010

This Technical Report explores methods of conveying archetyped data in HL7 V2 messages. The archetypes are those defined using the Archetype Definition Language (ADL) as specified by openEHR, and by EN 13606.

This Technical Report explores methods of conveying archetyped data in HL7 V2 messages. The archetypes are those defined using the Archetype Definition Language (ADL) as specified by openEHR, and by EN 13606. The archetypes are used to constrain a reference model, such as openEHR or EN 13606, to describe domain level concepts.In developing this report, the authors have used openEHR archetypes as the main focus. The proposed method however is intended to be generalized to other reference models including EN 13606.The focus of the proposed method is on using segments available in current HL7 V2 Standards. The suitability of these segments for conveying archetyped data is in scope for this Technical Report. Circumstances where the proposed approach falls outside the current standard will be documented in this report. This Technical Report does not provide definitions for-new segments;new message types;new fields; ornew data types.The use cases considered by the authors are based on conveying archetyped data in diagnostics and collaborative care messages, but it should be possible to generalize these to other domains.This report essentially deals with clinical document content, which is a snapshot of potentially rich clinical factual and management data, for communication in a message-based, workflow-oriented environment.The document will consider a number of approaches to convey archetyped data, descriptions of the use of ORC/OBR/OBX segments for conveying archetyped clinical data, as well as the new REL segment and instance identifiers when HL7 V2.6 is released.The report also states that archetypes should not be used to convey clinical information where there are currently HL7 V2 domain specific segments adequately covering particular health concepts.The report acknowledges that while the described methods enable archetyped data to be transported within existing messages, this is viewed by some as not an ideal situation. Subsequent to this report, a further report is to be produced examining the requirements and benefits of developing new segments (and perhaps messages) to transport archetyped data.

First published as TR 2964-2010.
Reissued incorporating Amendment No. 1 (November 2010).