Understanding HL7 v2 EVN-6: Event Occurred in Practice
If your test data always sets EVN-6 equal to EVN-2, you have never actually tested this field.
EVN-6 (Event Occurred) records the date and time the real-world event actually took place, as opposed to EVN-2, which records when the message was logged or recorded. The two are often the same in a real-time system, but they diverge whenever an event is entered late, backdated, or corrected, such as a nurse documenting an admission twenty minutes after the patient physically arrived. Systems that rely on EVN-2 for sequencing but should be reporting clinical timing off EVN-6 are a common source of subtle reporting bugs.
What this field contains
Example
EVN-6 shows 20260726072500, five minutes before the EVN-2 recorded time of 20260726073000, reflecting a short documentation delay.
Where this trips people up
The single biggest gap we see in ADT test coverage is the absence of any test case where EVN-6 and EVN-2 differ. Reporting logic that assumes the two are interchangeable will misstate clinical timing whenever real-world events are backdated, which happens constantly in emergency departments and during downtime documentation catch-up. Build test cases with a deliberate gap between the two fields, including cases where EVN-6 is blank and the receiver must fall back to EVN-2.