| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | code(+) | 0;1 | FREE TEXT | B | This is the code assigned by an application to a particular type of event. The combination of fields, Code and Assigning Package, should be unique. | |
| .02 | package(+) | 0;2 | POINTER | 9.4 | ||
| .03 | category(+) | 0;3 | SET OF CODES | 1:HL7 SYSTEM MESSAGE ERROR 2:APPLICATION MESSAGE ERROR 3:OPERATIONAL ERROR 4:EVENT MONITOR NOTIFICATION | HL7 System Message Errors are errors discovered by the HL7 system while processing a particular message. Application Message Errors are errors discovered by an appication while processing a particular message. This type of error is defined by the application and usually involve application-specific business rules. Operational Errors are not related to a specific message, rather,they are related to a site. An common example is a logical link that fails. An Event Monitor Notification is any sort of status update message that may be posted by the Event Monitors. | |
| .04 | urgent | 0;4 | SET OF CODES | 0:NO 1:YES 2:URGENT IF ACTION FAILS | ||
| .05 | conglomerate | 0;5 | BOOLEAN | 0:NO 1:YES | This field determines whether or not discrete events of this type are counted over a defined period of time and reported as a single event along with the count. Events that are conglomerated can not store application-specific data with the event. | |
| .06 | hours covered | 0;6 | NUMERIC | If events of this type are to be conglomerated, this field defines the period in hours over which the events of this type are to be counted. | ||
| .07 | review | 0;7 | SET OF CODES | 0:NOT REQUIRED 1:REQUIRED 2:ONLY IF ACTION FAILS | ||
| .08 | package name | 0;8 | FREE TEXT | This field will be used in the key definition rather then the field PACKAGE because KIDS will not resolve the pointers in the PACKAGE file if the field is part of the key. | ||
| .09 | days till purge(+) | 0;9 | NUMERIC | |||
| .1 | active | 0;10 | BOOLEAN | 0:NO 1:YES | This field can be used to disable a particular event type. It is a safety feature - if large numbers of events of a particular tye are generated and it is discovered that logging them is not useful then the logging can be turned off via this field. | |
| 1 | action | 1;E1,20 | FREE TEXT | The action will be executed when the event occurs. For conglomerated events, the action is executed when the time period expires. | ||
| 2 | server locations | 2;0 | MULTIPLE | 776.32 | ||
| 3 | full description | 3;0 | WORD-PROCESSING | |||
| 4.01 | brief description | 4;1 | FREE TEXT |