Greg, Very interesting question, there is actually working being done within Standards Australia to determine how to represent archetyped content in HL7 V2. This work is not yet complete, but your suggestion is one of the options except the [at0000] is not required as all archetype root nodes have this node ID. The code system (3rd component of CE) is the Archetype ID.
Regards Heath > -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces at openehr.org] On Behalf Of Greg Caulton > Sent: Wednesday, 7 November 2007 3:51 PM > To: For openEHR technical discussions > Subject: Exchanging codified content via HL7 > > So I have completed a first pass at parsing the OpenEHR content, > extracting some initial information I would import into to my > application. More work to be done but if you look at this text file > as a preliminary output from the process: > > http://www.patientos.org/forum_temp/openehr.txt > > My question is if I send the information out via HL7 in say OBX > segments, what 'code' would I assign to the data elements. > > For example if my message is sending the 'Anaesthetic evaluation and > history date/time of last liquid intake' - is the unique, > interoperable identifier for that data element: > > [at0000]/data[at0001]/items[at0005]/items[at0006] > > > thanks > > Greg > http://www.patientos.org > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
