HL7 v2 OBR Segment Guide: Fields, Format, and Testing Gotchas
Get the OBR-2/OBR-3 order number pairing wrong and your lab results silently stop matching back to the original order, leaving clinicians staring at an orphaned result with no context.
OBR is the HL7 v2 segment that carries the details of a single observation or diagnostic order, such as the test being requested, who ordered it, when it was collected, and who is responsible for the result.
The fields that actually matter in practice
Example
A synthetic OBR segment for a complete blood count order, showing the placer/filler order number pairing, ordering provider, and a final result status.
Where this trips people up
A shockingly common integration bug is treating OBR-2 (placer order number) and OBR-3 (filler order number) as interchangeable or optional. When a lab system generates its own filler number but the interface layer forgets to echo the original placer number back on the result message, the ordering EHR has no reliable way to match the incoming result to the pending order it created. The result either gets dropped, queued as unmatched, or gets manually reconciled by staff against the wrong patient encounter. Any test suite for OBR handling should explicitly verify that both identifiers survive the full order-to-result round trip unchanged.