The HL7 OBR segment transmits information about an exam, diagnostic study/observation, or assessment that is specific to an order or result. It is used most frequently in ORM (Order) and ORU (Observation Result) messages, and has an important role in carrying the placer and filler order numbers.
An OBR segment should always be included in orders where a request is made for a given set of observations. For lab tests and diagnostic studies, each OBR segment generally applies to a single specimen or diagnostic study only. With lab testing, there may not necessarily be a 1:1 relationship between test and specimen (i.e different test batteries may have multiple OBR segments even though it is a single specimen). ORU (Observation Result) messages should contain the OBR segment followed by the OBX segment for each observation.
Usage in the ORM Message
In an ORM message, the OBR segment is part of an optional group that provides details about the order. When the order placer creates the ORM message, they will include the Placer Order Number in the OBR-2 and/or ORC-2 fields. These two fields should contain the same information, and at least one of the two must contain the placer order number. The message may contain multiple orders for which the rules still apply.
The OBR segment (show in red) from an ORM message is shown below:
ORC|NW|2156286|||||||20060221061809|^MOUSE^MINNIE^A^^^RN||TBU^BUTLER JR MD^THOMAS^E^^^|||||CLINIC
OBR|1|2156286||MRSHLR-C^MR Shoulder right wo/contrast|||||||||R/O RCT VS TENDONITIS|||TBU^BUTLER JR MD^THOMAS^E^^^||…
Note that the Placer Order Number in the OBR-2 matches the Placer Order Number in the ORC-2.
Usage in the ORU Message
In an ORU message, the OBR segment is used as a report header and contains important information about the order being fulfilled (i.e. order number, request date/time, observation date/time, ordering provider, etc.). It is part of a group that can be used more than once for each observation result that is reported in the message.
When the filler creates the ORU message, they will include the Filler Order Number (such as an accession number) in the OBR-3 and/or ORC-3 fields. If the filler order number is not present in the ORC-3, it must be present in the OBR-3 because the ORC segment is optional in the ORU message.
The OBR segment (shown in red) from an ORU message is shown below:
ORC|RE|2156286|A140875||||||20060221061809|^MOUSE^MINNIE^^^^RN||TBU^BUTLER JR MD^THOMAS^E^^^|||||CLINIC
OBR|1|2156286|A140875|MRSHLR-C^MR Shoulder right wo/contrast||| 20060220141000|||||…
Note that the Filler Order Number in the OBR-3 matches the Filler Order Number in the ORC-3, and that the Placer Order Number is also included in the OBR-2 and ORC-2 fields. This is typically the case for ORU messages.
The fields in the OBR segment are as follows:
|1||4||SI||C||Set ID is a coded value data type. The value of such a field follows the formatting rules for a ST field... More – OBR|
|2||75||EI||C||Placer Order Number|
|3||75||EI||C||Filler Order Number|
|4||200||CE||R||Universal Service ID is a coded value data type. The value of such a field follows the formatting rules for a ST field... More|
|5||2||ID is a coded value data type. The value of such a field follows the formatting rules for a ST field... More||B||Priority|
|8||26||TS||O||Observation End Date/Time|
|11||1||ID is a coded value data type. The value of such a field follows the formatting rules for a ST field... More||O||Specimen Action Code|
|13||300||ST||O||Relevant Clinical Info.|
|14||26||TS||C||Specimen Received Date/Time|
|17||40||XTN||O||Y/2||Order Callback Phone Number|
|18||60||ST||O||Placer field 1|
|19||60||ST||O||Placer field 2|
|20||60||ST||O||Filler Field 1|
|21||60||ST||O||Filler Field 2|
|22||26||TS||C||Results Rpt/Status Chng – Date/Time|
|23||40||CM||O||Charge to Practice|
|24||10||ID is a coded value data type. The value of such a field follows the formatting rules for a ST field... More||O||Diagnostic Serv Sect ID is a coded value data type. The value of such a field follows the formatting rules for a ST field... More|
|28||150||XCN||O||Y/5||Result Copies To|
|31||300||CE||O||Y||Reason for Study|
|32||200||CM||O||Principal Result Interpreter|
|33||200||CM||O||Y||Assistant Result Interpreter|
|37||4||NM||O||Number of Sample Containers|
|38||60||CE||O||Y||Transport Logistics of Collected Sample|
|40||60||CE||O||Transport Arrangement Responsibility|
|43||200||CE||O||Y||Planned Patient Transport Comment|
*Note: For the complete HL7 Standard, please go to the HL7 organization website.
How Corepoint Integration Engine works with HL7
The #1 Integration Engine Nine Consecutive Years
Customers have confidence in Corepoint Health’s history of focusing on healthcare Interoperability refers to the ability of two or more systems or components to exchange information ... More, as evident by our #1 KLAS® ranking nine years in a row. Discover the power Corepoint Integration Engine offers healthcare providers of all sizes and specialties.