Understanding HL7 v2 DG1-5: Diagnosis Date/Time in Practice
DG1-5 gets treated as an afterthought copy of the admission date, but it's supposed to record when the diagnosis itself was established — a distinction that matters once you're reconciling a diagnosis timeline against a multi-day inpatient stay.
DG1-5 is a timestamp recording when the diagnosis was established or recorded, formatted as an HL7 date/time value such as YYYYMMDDHHMM. It is not the encounter date and doesn't have to match DG1-1's ordering — a working diagnosis added on day three of a stay should carry day three's timestamp, not the admission date.
What this field contains
Example
A diagnosis timestamped 08:30 on July 25, 2026 — recorded, in this scenario, the morning after the patient was admitted.
Where this trips people up
Because this field is easy to leave blank without triggering a validation error, plenty of production messages carry no DG1-5 at all, and systems that assume a timestamp will always be present end up sorting diagnoses arbitrarily or crashing on a null date parse. It's also worth testing partial-precision values — a date with no time component — since some parsers assume full HHMM precision and mishandle a bare YYYYMMDD. If your organization exchanges messages across time zones, confirm whether the offset is expected and what happens to a value that omits it.