HL7 v2 EVN-2 (Recorded Date/Time): Format, Values, and Testing Notes
Of every field in EVN, EVN-2 is the one your interface engine is most likely to log, sort, and alert on, so getting its format wrong breaks more than one downstream system.
EVN-2 (Recorded Date/Time) is a timestamp marking when the sending application logged the triggering event, expressed in HL7's standard YYYYMMDDHHMMSS format, optionally with a timezone offset. It is functionally the "as of" clock for the message and is frequently used by receiving systems to sequence events, detect out-of-order delivery, or drive SLA alerting. Because it is so heavily relied on operationally, test suites should exercise edge cases like missing seconds, missing timezone offsets, and midnight-boundary rollovers.
What this field contains
Example
EVN-2 shows 20260726073000, meaning the event was recorded at 7:30:00 AM on July 26, 2026.
Where this trips people up
Teams frequently build test data with a fixed-width timestamp and never test what happens when a real sender omits seconds or the timezone offset. Interface engines vary wildly here: some pad missing components with zeros, others reject the message outright. If your regression suite only ever sends full-precision, offset-included timestamps, you will not find out your parser mishandles a minute-precision EVN-2 until a legacy feed sends one in production.