Understanding HL7 v2 OBX-1: Set ID in Practice
A single ORU message can carry dozens of OBX segments for one order, and OBX-1 is the only field that tells a receiving system what order they belong in — miss that, and a results-review screen can display a panel with the values shuffled.
OBX-1 is the first field of the HL7 v2 OBX segment — a sequence number that identifies the position of a given OBX segment among the repeating OBX segments in a message.
What this field contains
Example
The 1 right after OBX| marks this as the first result segment in the message. Synthetic result — not a real patient.
Where this trips people up
Some parsers assume OBX segments will always arrive in the order they were performed and ignore OBX-1 entirely, appending each result to a list as it is read. That works until a message gets reordered or retransmitted out of sequence by an intermediate interface engine — at which point a lab panel can render with the wrong labels next to the wrong values, and nothing in the message itself flags the mismatch except the Set ID a parser never checked.