Testing HL7 v2 OBX-3: What Observation Identifier Actually Needs to Handle
OBX-3 is how a receiving system knows what was actually measured, and most integrations key their result-mapping logic directly off the code in this field — a mismatched or missing coding system here means a perfectly valid result never gets matched to anything.
OBX-3 is the third field of the HL7 v2 OBX segment — a coded field that identifies what observation the result represents, typically a LOINC code paired with a human-readable text description.
What this field contains
Example
2823-3^Potassium^LN identifies the observation as a LOINC-coded potassium test. Synthetic result — not a real patient.
Where this trips people up
Not every source system sends a LOINC code in OBX-3 — some send a local or proprietary code with LN left blank or replaced with a local coding-system identifier. Mapping logic that assumes every OBX-3 is LOINC-coded will fail to match those results against a reference catalog, and the observation ends up bucketed as "unrecognized" even though the data itself is perfectly valid.