...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0"?>
<ORU_R01 xmlns="urn:hl7-org:v2xml">
<MSH>
<MSH.1>|</MSH.1>
<MSH.2>^~\&amp;</MSH.2>
<MSH.4>
<HD.1>363</HD.1>
</MSH.4>
<MSH.6>
<HD.1>Shared Health Record</HD.1>
</MSH.6>
<MSH.7>
<TS.1>20120918160235</TS.1>
</MSH.7>
<MSH.9>
<MSG.1>ORU</MSG.1>
<MSG.2>R01</MSG.2>
<MSG.3>ORU_R01</MSG.3>
</MSH.9>
<MSH.10>63357449-6a6c-4faa-af7a-e8843a545c31</MSH.10>
<MSH.11>
<PT.1>D</PT.1>
<PT.2>C</PT.2>
</MSH.11>
<MSH.12>
<VID.1>2.5</VID.1>
<VID.2>
<CE.1>RWA</CE.1>
</VID.2>
</MSH.12>
<MSH.21>
<EI.1>CLSM_V0.83</EI.1>
</MSH.21>
</MSH>
<ORU_R01.PATIENT_RESULT>
<ORU_R01.PATIENT>
<PID>
<PID.3>
<CX.1>1234567890456789</CX.1>
<CX.5>NID</CX.5>
</PID.3>
<PID.3>
<CX.1>3630NX3X-J</CX.1>
<CX.5>OMRS363</CX.5>
</PID.3>
<PID.5>
<XPN.1>
<FN.1>Umurwayi</FN.1>
</XPN.1>
<XPN.2>Test</XPN.2>
</PID.5>
</PID>
<ORU_R01.VISIT>
<PV1>
<PV1.2>0</PV1.2>
<PV1.3>
<PL.1>111</PL.1>
<PL.4>
<HD.1>Ruhunda</HD.1>
</PL.4>
</PV1.3>
<PV1.4>ANC</PV1.4>
<PV1.7>
<XCN.1>3525410</XCN.1>
<XCN.2>
<FN.1>doctor</FN.1>
</XCN.2>
<XCN.3>john</XCN.3>
<XCN.13>NID</XCN.13>
</PV1.7>
<PV1.44>
<TS.1>201209180402</TS.1>
</PV1.44>
</PV1>
</ORU_R01.VISIT>
</ORU_R01.PATIENT>
<ORU_R01.ORDER_OBSERVATION>
<ORC>
<ORC.1>RE</ORC.1>
<ORC.9>
<TS.1>201209181602</TS.1>
</ORC.9>
<ORC.12>
<XCN.1>259086</XCN.1>
</ORC.12>
<ORC.16>
<CE.1>Identifier</CE.1>
<CE.2>Text</CE.2>
<CE.3>Name of Coding System</CE.3>
</ORC.16>
</ORC>
<OBR>
<OBR.1>0</OBR.1>
<OBR.3>
<EI.1>1437</EI.1>
</OBR.3>
<OBR.4>
<CE.2>ANC</CE.2>
</OBR.4>
<OBR.7>
<TS.1>201209180000</TS.1>
</OBR.7>
<OBR.20>111</OBR.20>
<OBR.21>Ruhunda</OBR.21>
</OBR>
</ORU_R01.ORDER_OBSERVATION>
<ORU_R01.ORDER_OBSERVATION>
<OBR>
<OBR.1>1</OBR.1>
<OBR.18>0</OBR.18>
<OBR.29>
<EIP.2>
<EI.3>1437</EI.3>
</EIP.2>
</OBR.29>
</OBR>
<ORU_R01.OBSERVATION>
<OBX>
<OBX.1>0</OBX.1>
<OBX.2>CE</OBX.2>
<OBX.3>
<CE.1>72179-5</CE.1>
<CE.2>Given Sulfadoxin Pyrimethamine</CE.2>
<CE.3>LOINC</CE.3>
</OBX.3>
<OBX.5>
<CE.1>1065</CE.1>
<CE.2>YES</CE.2>
<CE.3>RWCS</CE.3>
</OBX.5>
<OBX.14>
<TS.1>20120918160235</TS.1>
</OBX.14>
</OBX>
</ORU_R01.OBSERVATION>
<ORU_R01.OBSERVATION>
<OBX>
<OBX.1>1</OBX.1>
<OBX.2>CE</OBX.2>
<OBX.3>
<CE.1>8406</CE.1>
<CE.2>Given Mebendazole</CE.2>
<CE.3>RWCS</CE.3>
</OBX.3>
<OBX.5>
<CE.1>1065</CE.1>
<CE.2>YES</CE.2>
<CE.3>RWCS</CE.3>
</OBX.5>
<OBX.14>
<TS.1>20120918160235</TS.1>
</OBX.14>
</OBX>
</ORU_R01.OBSERVATION>
<ORU_R01.OBSERVATION>
<OBX>
<OBX.1>2</OBX.1>
<OBX.2>CE</OBX.2>
<OBX.3>
<CE.1>72187-8</CE.1>
<CE.2>Given tetanus vaccine</CE.2>
<CE.3>LOINC</CE.3>
</OBX.3>
<OBX.5>
<CE.1>1065</CE.1>
<CE.2>YES</CE.2>
<CE.3>RWCS</CE.3>
</OBX.5>
<OBX.14>
<TS.1>20120918160235</TS.1>
</OBX.14>
</OBX>
</ORU_R01.OBSERVATION>
<ORU_R01.OBSERVATION>
<OBX>
<OBX.1>3</OBX.1>
<OBX.2>CE</OBX.2>
<OBX.3>
<CE.1>72180-3</CE.1>
<CE.2>Was the woman given iron and folic acid?</CE.2>
<CE.3>LOINC</CE.3>
</OBX.3>
<OBX.5>
<CE.1>1065</CE.1>
<CE.2>YES</CE.2>
<CE.3>RWCS</CE.3>
</OBX.5>
<OBX.14>
<TS.1>20120918160235</TS.1>
</OBX.14>
</OBX>
</ORU_R01.OBSERVATION>
<ORU_R01.OBSERVATION>
<OBX>
<OBX.1>4</OBX.1>
<OBX.2>CE</OBX.2>
<OBX.3>
<CE.1>72178-7</CE.1>
<CE.2>Given Mosquito Nets</CE.2>
<CE.3>LOINC</CE.3>
</OBX.3>
<OBX.5>
<CE.1>1065</CE.1>
<CE.2>YES</CE.2>
<CE.3>RWCS</CE.3>
</OBX.5>
<OBX.14>
<TS.1>20120918160235</TS.1>
</OBX.14>
</OBX>
</ORU_R01.OBSERVATION>
</ORU_R01.ORDER_OBSERVATION>
</ORU_R01.PATIENT_RESULT>
</ORU_R01> |
HL7 v3
Overview
HL7v3 attempts to solve the semantic interoperability problem by employing the use of a generic reference information model (the RIM) that all HL7v3 message must conform to. This, however, led to the message size growing very large and made HL7v3 difficult to understand and implement due to the generality of the data model. HL7v3 requires that one restricts the base standard down to a usable subset that is to be used. For low resource setting this becomes difficult due to the limited number of informatics experts available to do this and the time required to do so. HL7v3 messages take the form of large structured XML messages.
...
- Very large message size
- HL& v3 needs extensive work by informatics specialists to be usable for a domain
- Not a large amount of tooling support
- Difficult to understand and use
Sample messages
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<PRPA_IN403001 xmlns="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hl7-org:v3 PRPA_IN403001.xsd">
<id root="1.1.2.3.4.5" extension="5929" assigningAuthorityName="Litware Inc."/>
<creationTime value="20050303180027"/>
<versionCode code="V3PR1"/>
<interactionId root="1.1.6.7.8" extension="PRPA_IN403001" assigningAuthorityName="HL7"/>
<processingCode code="D"/>
<processingModeCode code="T"/>
<acceptAckCode code="AL"/>
<receiver typeCode="RCV">
<device classCode="DEV" determinerCode="INSTANCE">
<id root="1.4.7.8.3"/>
</device>
</receiver>
<sender typeCode="SND">
<device classCode="DEV" determinerCode="INSTANCE">
<id root="1.45.6.7.98"/>
</device>
</sender>
<controlActProcess classCode="CACT" moodCode="EVN">
<subject typeCode="SUBJ" contextConductionInd="false">
<encounterEvent classCode="ENC" moodCode="EVN">
<id root="1.56.3.4.7.5" extension="122345" assigningAuthorityName="Maple Hospital Emergency"/>
<code code="EMER" codeSystem="2.16.840.1.113883.5.4"/>
<statusCode code="active"/>
<subject contextControlCode="OP">
<patient classCode="PAT">
<id root="1.56.3.4.7.9" extension="55321" assigningAuthorityName="Maple Hospital Patients"/>
<patientPerson classCode="PSN" determinerCode="INSTANCE">
<name>
<given>Rob</given>
<given>P</given>
<family>Young</family>
</name>
<administrativeGenderCode code="M" codeSystem="2.16.840.1.113883.5.1"/>
<birthTime value="19800309"/>
</patientPerson>
</patient>
</subject>
</encounterEvent>
</subject>
</controlActProcess>
</PRPA_IN403001> |
Resources
- HL7 needs a fresh look because V3 has failed: http://www.healthintersections.com.au/?p=476
- HL7 can have a fresh look because v3 succeeded: http://www.healthintersections.com.au/?p=482
...