HL7 - ORU Message

Sample ORU Message

Below is an example of an HL7 version 2.4 ORU^R01 message:

MSH|^~\&|MESA_RPT_MGR|EAST_RADIOLOGY|iFW|XYZ|||ORU^R01|MESA3b|P|2.4||||||||
PID|||CR3^^^ADT1||CRTHREE^PAUL|||||||||||||PatientAcct||||||||||||
PV1||1|CE||||12345^SMITH^BARON^H|||||||||||
OBR|||||||20010501141500.0000||||||||||||||||||F||||||||||||||||||
OBX|1|HD|SR Instance UID||1.113654.1.2001.30.2.1||||||F||||||
OBX|2|TX|SR Text||Radiology Report History Cough Findings PA evaluation of the chest demonstrates the lungs to be expanded and clear.  Conclusions Normal PA chest x-ray.||||||F||||||
CTI|study1|^1|^10_EP1

Segment	Description
MSH	Message Header. This segment is a mandatory part of an ORU message, and contains information about the message sender and receiver, the date and time that the message was created. This segment is required.
PID	Patient Identification. An ORU message is a patient-specific message type, and must be linked to a particular patient. Therefore, patient information such as the patient identifier, name, date of birth, etc. must be included in an ORU. This segment is required.
PV1	Patient Visit. This segment contains information about patient visit details such as servicing facility, attending doctor, and visit ID. This segment is required.
OBR	Observation Request. This segment identifies the observation that was ordered in order to generate the ORU message. This segment is required.
[{OBX}]	Observation Segment. Here is where information about the observation results is held. An OBX segment is used to communicate a single observation, so multiple observations would require this segment to repeat. This segment is optional and can be repeating.
[{CTI}]	Clinical Trial Identification. This is an optional segment and is only used if the results need to be linked to a clinical trial. Information such as the trial ID, study phase, and time point is included here. This segment is optional and can be repeating.
[ ] = optional, { } = repeating

For more information on implementing various HL7 message types, please refer to the HL7 Messaging Standard Implementation Guides corresponding to your required version.

Working With ORU Messages

Are you working with HL7 ORU messages? In order to successfully process these messages, it's important to understand the specific format that the sending and receiving facilities are expecting the ORU messages to adhere to. Discrepancies can occur due to the version of HL7, system input error, or even simply human error when the messages were created.

How does Iguana ensure that ORU messages are properly formatted to ensure system compatibility?

Iguana is a data integration platform that allows you to easily customize the format, structure, and field values of your HL7 messages so that they are normalized, ensuring compatibility with any system you might need to interact with.

The Complete Guide to HL7

HL7 ORU

Contents

ORU (Observation Result)

Sample ORU Message

Working With ORU Messages

How does Iguana ensure that ORU messages are properly formatted to ensure system compatibility?

Get a demo: See Iguana in action

Other HL7 Message Types

REFERENCES: