# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | dt/tm(+) | 0;1 | DATE-TIME | B | The date and time the event occurred. | |
.02 | type(+) | 0;2 | POINTER | 776.3 | ||
.03 | site(+) | 0;3 | POINTER | 4 | This is the location of the event. | |
.04 | id | 0;4 | FREE TEXT | This will uniquely identify the event across the entire VHA. | ||
.05 | action status(+) | 0;5 | SET OF CODES | 0:ACTION NOT REQUIRED 1:NOT YET INITIATED 2:IN PROGRESS 3:SUCCESS 4:FAILURE | ||
.06 | review status(+) | 0;6 | SET OF CODES | 0:NOT REQUIRED 1:REQUIRED 2:IF ACTION FAILS 3:PENDING 4:COMPLETED | ||
.07 | dt/tm reviewed | 0;7 | DATE-TIME | This documents when the event was manually reviewed. If never reviewed, the field is blank. | ||
.08 | reviewer | 0;8 | POINTER | 200 | ||
.09 | dt/tm action | 0;9 | DATE-TIME | |||
.1 | hl7 id | 0;10 | FREE TEXT | |||
.11 | count | 0;11 | NUMERIC | This field pertains only to conglomerated events, that is, events that represent a count of discrete events over some spefcific time period. | ||
.12 | urgent | 0;12 | SET OF CODES | 0:NO 1:YES 2:URGENT IF ACTION FAILS | ||
.13 | message type | 0;13 | FREE TEXT | |||
.14 | hl7 event type | 0;14 | FREE TEXT | |||
.15 | link | 0;15 | FREE TEXT | |||
.16 | sending application | 0;16 | FREE TEXT | |||
.17 | create dt/tm | 0;17 | DATE-TIME | |||
1 | notes | 1;0 | WORD-PROCESSING | |||
2 | 2;0 | MULTIPLE | 776.42 | |||
3 | application data | 3;0 | MULTIPLE | 776.43 | This allows an application to store its own information relevant to resolving the event along with the event. |
Not Referenced