# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | event id(+) | 0;1 | FREE TEXT | B | The name of this VDEF Event. This MUST consist of the HL7 Message Type, HL7 Event Type and a VDEF subtype. Valid examples are: ORU-R01-VTLS, RDS-O13-PPAR, ADT-A01-DEMG. | |
.02 | event type(+) | 0;2 | POINTER | 779.001 | HL7 Event Type for this VDEF Event. | |
.03 | event subtype(+) | 0;3 | POINTER | 577.4 | The event sup-type associated with this event. | |
.06 | message type | 0;6 | POINTER | 771.2 | Message type for this HL7 Event, such as ADT or ORU | |
.07 | vista hl7 protocol | 0;7 | POINTER | 101 | Protocol for this HL7 event. Protocols should be in VDEF | |
.09 | custodial package | 0;9 | POINTER | 579.6 | Custodial package for this event, such as REGISTRATION or LAB SERVICE | |
.2 | api event active flag(+) | 0;11 | SET OF CODES | A:ACTIVE I:INACTIVE | ||
.3 | extraction program(+) | 0;12 | FREE TEXT | This field specifies the name of the program VDEF will use to extract the data from VistA files and construct the HL7 message. If not in use yet, this field must be valued to "INACTIVE". | ||
1 | event description(+) | 1;1 | FREE TEXT | This should describe in non-HL7 terminology what the VDEF Event is used for and what kind of message it will create. |
Not Referenced