HL7 ORM Overview

Elation will send an HL7 ORM message when providers in the application make a lab order. The ORM will contain the following information:

Segment	Description	Notes
Message Header (MSH)	This segment contains basic order message information.	There will only be 1 MSH segment.
Patient Identification (PID)	This segment contains patient identification information.	There will only be 1 PID segment.
Next Of Kin (NK1)	This segment contains patient next-of-kin information.	There will only be 1 NK1 segment and is only sent if the patient is less than 18 years old. Please note that the practice may not have documented the next of kin for a minor patient in Elation.
Insurance (IN1)	This segment contains the patient’s insurance information.	There can up to two IN1 segments if a patient has multiple insurances documented in Elation.
Guarantor (GT1)	This segment contains the patient’s insurance guarantor information.	If no guarantor is explicitly documented in Elation, the segment will default to the patient’s information.
Patient General Clinical Information (ZCI)	This segment contains patient clinical information at the time of the order.	If the patient’s height and weight are documented in Elation, the most recent measurements will be transmitted in the ZCI segment. The order fasting status will also be specified as yes or no.
Common Order (ORC)	This segment contains information about the ordering provider.	ORC and OBR segments are “paired” with an ORC for each OBR in the message.
Observation Request (OBR)	This segment contains the ordered lab panel information.
Diagnosis (DG1)	This segment contains the diagnosis ICD-10 code(s) specified for the order.	There can be multiple DG1 segments, one for each diagnosis provided on the order form.
Ask on Entry (OBX)	This segment contains the Ask on Entry (AOE) questions and answers, if relevant, for the panel.	If the order does not have an AOE question, no OBX segments will be sent for the ORC and OBR pair.
Notes and Comments (NTE)	This segment contains order-level notes, if specified, for the order.	There will only be 1 NTE segment.

Elation will send information when it is present in Elation. Fields denoted with an “R” (required) are always sent as part of the ORM. Fields denoted with an “O” (optional) may not be sent. The optional fields are typically sent as part of the order but there may be cases where Elation doesn’t have the information and therefore cannot send as part of the ORM. Important Note: Elation requires that the requisition number sent in the orders ORC & OBR segments be returned in the ORC and OBR segment of the resulting HL7 ORU. This allows for Elation to display and filter the orders that are outstanding or fulfilled to the practice. Additional Notes:

‘R’ = Required, ‘O’ = Optional
YYYYMMDDhhmm are in 24hr format
char(x) means maximum x characters
Lines are ended with CR+LF i.e. “\r\n”

API Reference

REST API

FHIR API

HL7 Interface