...
However, not all of these segments are importaint.
Important segments areBased on Grahame Grieve's recommendation, important segments for our messages would be-
MSH
PID
PVI PV1
ORC
OBR
OBX, (OBX)* )*
The MSH segment
The MSH Segment transmits the message’s source, purpose, destination, and certain syntax specifics.
It does not contain any patient centric data.
For a more detailed description, see here (http://www.corepointhealth.com/resource-center/hl7-resources/hl7-msh-message-header)
...
| Code Block | ||
|---|---|---|
| ||
<MSH>
<MSH.1>|</MSH.1>
<MSH.2>^~\&</MSH.2>
<MSH.3>
Sending Application
</MSH.3>
<MSH.4>
<HD.1>Sending Facility</HD.1>
</MSH.4>
<MSH.5>
Receiving Application
</MSH.5>
<MSH.6>
<HD.1>Receiving Facility</HD.1>
</MSH.6>
<MSH.7>
<TS.1>Date/Time of Message</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>Message Control Id</MSH.10>
<MSH.11>
<PT.1>D</PT.1>
<PT.2>C<2></PT.2> <!-- original value 'C' removed based on Grahame's recommendation -->
</MSH.11>
<MSH.12>
<VID.1>2.5</VID.1>
<VID.2>
<CE.1>RWA</CE.1>
<CE.2>HL70399</CE.2> <!-- Added on Grahame's recommendation -->
</VID.2>
</MSH.12>
</MSH>
|
Comments from Grahame Grieve:
...
The PID (patient identification) segment contains a host of patient information such as patient ID number, patient sex, address, marital status and citizenship.
For a more detailed description, see here (http://www.corepointhealth.com/resource-center/hl7-resources/hl7-pid-segment)
| Code Block | |||||
|---|---|---|---|---|---|
|
<PID>
| ||||
<PID>
<PID.1>1</PID.1> <!-- Added on Grahame's recommendation -->
<PID.3> <!-- PID.3 fields can be repeated. They represent patient identifier and identifier type pairs -->
<CX.1>1234</CX.1>
<CX.5>ECID</CX.5>
</PID.3>
<PID.3>
<CX.1>1235</CX.1>
<CX.5>PID</CX.5>
</PID.3>
<PID.5> <!-- PID.5 fields can be repeated. They represent patient names. Since each patient can have many names, each PID.5 segment can contain one of these -->
<XPN.1>
<FN.1>Patient</FN.1>
</XPN.1>
<XPN.2>John</XPN.2>
</PID.5>
<!-- PID.6 Date of birth -->
<!-- PID.7 Patients sex -->
<!-- PID.11 Patient address -->
</PID>
|
...
The PV1 segment
The PV1 Segment contains information on patient visits
...
| language | html/xml |
|---|
...
information on patient visits
| Code Block | ||
|---|---|---|
| ||
<PV1>
<PID.1>1</PID.1> <!-- Added on Grahame's recomendation -->
<PV1.2>0</PV1.2>
<PV1.3>
<PL.1>1</PL.1>
<PL.4>
<HD.1>Unknown Location</HD.1>
</PL.4>
</PV1.3>
<PV1.4>ADULTINITIAL</PV1.4>
<PV1.7>
<XCN.1>2</XCN.1>
<XCN.2>
<FN.1>Hornblower</FN.1>
</XCN.2>
<XCN.3>Horatio</XCN.3>
</PV1.7>
<PV1.44>
<TS.1>201206270137</TS.1>
</PV1.44>
</PV1>
|
...
Therefore, an ORU_R01 message which contains an encounter with two grouped observations can be represented with the following structure -
| Code Block |
|---|
<!-- Updated Structure --> <ORC> <!-- One ORC segment per each ORU_R01 --> <OBR> <!-- OBR for the obs grouping -- > <OBX> <!-- two obs which belong to the Obs group --> <OBR> |
...
| Code Block | ||
|---|---|---|
| ||
<OBX>
<OBX.1>6</OBX.1>
<OBX.2>NM</OBX.2>
<OBX.3>
<CE.1>1234</CE.1>
<CE.2>NEUTROPHILS</CE.2>
<CE.3>LOCAL</CE.3>
</OBX.3>
<OBX.5>45.0</OBX.5>
<OBX.6>
<CE.1>%</CE.1>
<CE.3>ucum<3>UCUM</CE.3> <!-- Updated value -->
</OBX.6>
<OBX.14>
<TS.1>20120627013717</TS.1>
</OBX.14>
</OBX>
|
...