# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | alert date/time | 0;1 | DATE-TIME | This is the date and time when the alert was generated. | ||
.02 | alert id | 0;2 | FREE TEXT | This is a field in which the package id passed during alert filing. This id may simply be a package namespace, or it may be a namespace followed by additional data to more accurately identify the type or purpose of the alert. | ||
.03 | message text | 0;3 | FREE TEXT | This field contains the text of the message to be presented to the user at the time when he cycles through the menu system the first time after the alert has been filed for the user, and when the user selects the VIEW ALERTS option. | ||
.04 | new alert flag | 0;4 | SET OF CODES | 1:NEW | This flag is used by the alert processing to indicate a new alert which has not previously been presented to the user. After the alert message text has been shown to the user, this flag is cleared and the user must then select the VIEW ALERTS option to process the alert. | |
.05 | action flag | 0;5 | SET OF CODES | D:DELETE R:RUN ROUTINE I:IMMEDIATE RUN | This flag is optional at the present time, since the need for action processing can be determined by the presence of an option name or a routine name for use during alert processing. | |
.06 | reserved1 | 0;6 | FREE TEXT | This field is reserved for future use by the alert system. | ||
.07 | entry point | 0;7 | FREE TEXT | While named ENTRY POINT, this is a dual function field. If the next field (#.08, AROUTINE NAME) contains a routine name, this field contains the desired entry point within that routine (this field may also be null, indicating that the entry point should be at the top of the routine). If field #.08 is null, then the contents of this field is interpreted as the name of an option which is to be entered when the alert is processed. | ||
.08 | aroutine name | 0;8 | FREE TEXT | If this field is not null, it contains the name of a routine which is to be used when the alert is processed. If there is also a value in field #.07, that value is used as an entry point into the routine specified in this field. If this field is null, field #.07 is interpreted as an option name which is to be used when the alert is processed. If both this field and field #.07 are null, the alert is processed as an information only alert. | ||
.09 | reserved | 0;9 | FREE TEXT | This field is reserved for future use in the alert processing system. | ||
.1 | can delete without processing | 0;10 | BOOLEAN | 1:YES | This field was added as a flag to identify alerts which the packages indicate may be deleted by the user without processing the alert. The value is optional and is passed by the package which generates the alert if they want to give permission for users to be able to delete the alert. The flag is checked in the code handling user deletion of alerts. If an alert involves an action (via an option or routine) it may not be deleted by the user unless this flag is set. | |
.13 | days for surrogate | 0;13 | NUMERIC | |||
.14 | days for supervisor | 0;14 | NUMERIC | |||
.15 | days for backup reviewer | 0;15 | NUMERIC | The 'DAYS FOR BACKUP REVIEWER' field contains a number of days, which if exceeded without the alert being processed will cause the alert to be forwarded to the designated 'XQAL BACKUP REVIEWER' in the PARAMETER file with a comment indicating that the alert had not been reviewed by the original recipient. This forwarding option is in addition to the SUPERVISOR (based on entries for CHIEF in the SECTION/SERVICE file) or e-mail surrogates, and was requested by sites to be able to forward unprocessed alerts to a known, interested individual. This could be someone in Quality Assurance or a specific nurse responsible for handling overdue unprocessed alerts. | ||
1 | data for alert | 1;E1,245 | FREE TEXT | This field and all following ^-separated fields are processed as a single entity and are returned in the variable XQADATA for use by the application which generated the alert. The package may pass a series of variables using any desired separator in the variable XQADATA at the time the alert is setup. When the alert is processed the value of XQADATA is returned to the application and may be used to establish parameters related to the alert without requiring interaction or provision of information by the user. In this way information related to patient entry number, specific internal numbers for the desired data, etc may be stored and returned. | ||
2.01 | comment for display | 2;1 | FREE TEXT | |||
3.01 | guid for gui | 3;1 | FREE TEXT | This field contains a Globally Unique IDentifier (GUID) which is used to identify the application which should be used in a graphical user interface environment (windows) to process the alert. This application must implement the IVAlert interface. The GUID should be of the form {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} where each x is a hexadecimal digit (0 through 9 or A through F). | ||
3.02 | patient | 3;2 | POINTER | 2 | This field is a pointer value to the PATIENT file, if the alert is patient related. It is not a required field for non-patient related alerts. | |
4 | long info text | 4;0 | WORD-PROCESSING |
Error: Invalid Global File Type: 8992.01