Reference·EVN Segment·EVN-4
HL7 v2 Reference

EVN-4 in HL7 v2: A Field Guide to Event Reason Code

Jul 27, 2026 · 4 min read
← EVN-2 EVN-5 →

An admit is an admit, but why it happened can change how downstream systems route the message, and that context lives in EVN-4.

Quick answer

EVN-4 (Event Reason Code) is a short code that explains the circumstance behind the event carried in the segment, distinct from the event type itself. For an admit it might distinguish a scheduled admission from an emergency one; for a transfer it might flag a bed-management move versus a level-of-care change. Not every site populates this field consistently, since it is often locally defined rather than tightly bound to a single HL7 table, so test suites should treat its value set as configuration-dependent rather than universal.

Valid code values

A
Automatic/system generated — event was triggered by system logic rather than direct user action
C
Patient condition change — common on transfer or update events tied to a clinical status change
P
Preadmit — used when the event follows an existing preadmission record
R
Patient request — event initiated at the patient's own request, such as a requested transfer
Local/site-specific
Facility-defined codes — many organizations extend this field with their own values, so test data should mirror the sending site's actual table, not assume a universal set

Example

Synthetic example Generated by Synthibase
EVN|A01|20260726073000||ADM|8842^REYES^MONICA^L^^^MD|20260726072500

EVN-4 carries ADM here, a facility-defined code indicating a standard scheduled admission.

Where this trips people up

Because EVN-4 is loosely bound to a standard code table in practice, teams that copy another organization's reference values into their test data end up validating against a code set the receiving system has never seen. We routinely find test suites asserting on reason codes like "A" or "C" when the actual production feed uses entirely site-specific strings. Always source your EVN-4 test values from the sending system's real configuration rather than a generic reference table.

HL7 v2 EVN Segment Guide: Fields, Format, and Testing Gotchas
HL7 ADT Messages: A01 through A08 Explained
Synthetic Patient Data: Complete Guide for Software Testing
Model your actual reason codes, not generic ones
Synthibase lets you configure EVN-4 and other locally-extended code fields to match your real interface configuration, so your test data reflects what your systems actually send.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.