Reference·OBR Segment·OBR-2
HL7 v2 Reference

OBR-2 in HL7 v2: A Field Guide to Placer Order Number

Jul 27, 2026 · 4 min read
← OBR-1 OBR-3 →

OBR-2 is the identifier the ordering system assigns and expects to see again when the result comes back. If a filling system regenerates or truncates it along the way, the EHR that placed the order has no reliable way to match the result to the original request.

Quick answer

OBR-2 is the second field of the HL7 v2 OBR segment — the Placer Order Number, a unique identifier assigned by the ordering (placer) system to track a specific order through its lifecycle.

What this field contains

component 1
Order number — the actual identifier string, often alphanumeric
component 2
Namespace ID — identifies which system assigned the number, to avoid collisions across systems
uniqueness
Scope — must be unique within the placer application, not globally

Example

Synthetic example Generated by Synthibase
OBR|1|ORD44219^SYNTHIB|FIL98831^SYNTHIB|CBC^Complete Blood Count^L|||20260726090000|||||||||3021^HAYES^DEREK^A^^^MD||||||||CH|F||||||R/O anemia

OBR-2 carries ORD44219^SYNTHIB — the order number the ordering system assigned, with SYNTHIB as its namespace. Synthetic order — not a real patient.

Where this trips people up

Some interface engines strip or rewrite the namespace component of OBR-2 while passing a message between systems, leaving the order number intact but the full identifier no longer an exact match against what the placer system stored. Order-status lookups that compare the full field as a string then fail even though the human-readable order number looks identical on both sides. Always test component-level comparison, not just eyeballing the field.

HL7 v2 OBR Segment Guide: Fields, Format, and Testing Gotchas
How to Write EDI Test Cases That Actually Catch Go-Live Failures
Healthcare API Testing Guide: FHIR and X12
Generate realistic placer and filler order numbers
Synthibase generates synthetic OBR segments with consistent, realistic placer and filler order numbers across an entire test message set.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.