Testing HL7 v2 DG1-15: What Diagnosis Priority Actually Needs to Handle
DG1-15 is the field that decides which diagnosis among several gets treated as primary, and it's one of the most commonly skipped fields in real-world DG1 segments — which means plenty of systems have never had to handle its absence gracefully.
DG1-15 is a numeric ranking that establishes priority among multiple diagnoses attached to the same encounter, with 1 typically meaning the primary diagnosis. When only one DG1 repetition is present, the field is often left blank or trivially set to 1, but on encounters with several diagnoses it determines which one downstream systems should treat as the main reason for care.
What this field contains
Example
A priority of 1, marking this diagnosis as primary among any others attached to the same encounter.
Where this trips people up
Because DG1-15 is frequently left blank, systems that need a primary diagnosis for reporting or claims often fall back to assuming the first DG1 repetition is primary — which is not a safe assumption, since some sending systems order diagnoses chronologically rather than by clinical importance. Test messages where DG1-15 is populated but contradicts the DG1-1 ordering, and separately test messages where it's absent entirely across multiple diagnoses, to see whether your fallback logic picks the diagnosis you'd actually expect.