The EVN segment is used to communicate necessary trigger event information to receiving applications. Valid event types for all chapters are contained in HL7 table 0003 - Event type .
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
1 |
3 |
ID |
B |
0003 |
00099 |
Event Type Code |
|
2 |
26 |
TS |
R |
00100 |
Recorded Date/Time |
||
3 |
26 |
TS |
O |
00101 |
Date/Time Planned Event |
||
4 |
3 |
IS |
O |
0062 |
00102 |
Event Reason Code |
|
5 |
60 |
XCN |
O |
0188 |
00103 |
Operator ID |
|
6 |
26 |
TS |
O |
01278 |
Event Occurred |
Definition: This field has been retained for backward compatibility only. We recommend using the second component (trigger event) of MSH-9-message type to transmit event type code information. This field contains the events corresponding to the trigger events described in this section, e.g., admission, transfer, or registration. Refer to Chapter 2, HL7 table 0003 - Event type for valid values.
Definition: Most systems will default to the system date/time when the transaction was entered, but they should also permit an override.
Definition: This field contains the date/time that the event is planned. We recommend that the PV2-expected admit date and PV2-9-expected discharge date be used whenever possible.
Definition: This field contains the reason for this event (e.g., patient request, physician order, census management, etc.). Refer to user-defined table 0062 - Event reason for suggested values.
User-defined Table 0062 - Event reason
Value |
Description |
01 |
Patient request |
02 |
Physician order |
03 |
Census management |
Components: <ID number (ST)> ^<family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^<assigning authority (HD)> ^<name type code(ID)> ^<identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>
Definition: This field identifies the individual responsible for triggering the event. Refer to user-defined table 0188 - Operator ID for suggested values.
Definition: This field contains the date/time that the event actually occurred. For example, on a transfer (A02), this field would contain the date/time the patient was actually transferred. On a cancellation event, this field should contain the date/time that the event being canceled occurred.