| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | name(+) | 0;1 | FREE TEXT | B | This is the name of the event, used to uniquely identify it in the file; it is visible in the Event Editor only. | |
| .1 | short name | 0;10 | FREE TEXT | This field contains a shorter version of the Display Text, to be used for displaying and grouping delayed orders on the Orders tab where space is limited. | ||
| 1 | inactivated | 1;1 | DATE-TIME | This field contains the date and time that this event became inactive; once this date/time has passed, this event may no longer be selected for delaying orders, however any orders already delayed for this event will still be released when the event occurs. If this date/time is in the future, this event may continue to be selected for delaying orders until this time passes. | ||
| 1.5 | activation history | 2;0 | MULTIPLE | 100.52 | ||
| 2 | type of event(+) | 0;2 | SET OF CODES | A:ADMISSION T:TRANSFER D:DISCHARGE O:O.R. M:MANUAL RELEASE | ADT | This is the event that should cause delayed orders to be released to the service(s) for action; for OR (Surgery) events, the orders will be released when TIME PAT IN OR (#130,.205) is entered in the Surgery package. Orders delayed for Manual Release will not be automatically released by CPRS at all and can only be released via the "Release to Service" action by a user who is authorized to do so. Authorization is controlled by the parameter OREVNT MANUAL RELEASE CONTROL, which lets sites choose whether release is controlled by keys or by the parameter OREVNT MANUAL RELEASE or both. |
| 3 | division(+) | 0;3 | POINTER | 4 | This is the division that this event will apply to; for transfers across divisions, this should be the new division that the patient is going to. | |
| 4 | event order dialog | 0;4 | POINTER | 101.41 | This should be the dialog for a generic order requesting this event; if such an order is not necessary for this event, leave this empty. Unlike other delayed orders, the order created by this dialog will become active right away when signed and be visible on the Active Orders view as well as with the delayed orders on the Orders tab. | |
| 5 | order set/menu | 0;5 | POINTER | 101.41 | This is a menu or order set containing items that are either necessary or commonly ordered when this event occurs. It will be invoked right away when first placing delayed orders for this event; if an EVENT ORDER DIALOG was defined for this event, this order set will be presented to the user immediately following that dialog. You may enter any type of order dialog except prompt types. | |
| 6 | lapse in #days | 0;6 | NUMERIC | This is the number of days to allow orders for this event to remain delayed for a patient. Patient Events are evaluated whenever delayed orders are acted upon or viewed, and if this number of days has passed since delayed orders were entered for this event for the patient then the status of all orders delayed for this event will be changed to "lapsed" and the Patient Event itself will be terminated. The orders can no longer be released to the service then. | ||
| 7 | mas movement type | 0;7 | POINTER | 405.2 | This is an MAS Movement Type that can further define this event; it is optional, but if defined then it must match the patient's movement data to satisfy the event and cause any delayed orders to be released. For example, to have delayed orders released when a patient returns from pass enter the movement type of AUTH ABSENCE 96 HOURS OR LESS, or leave this field empty to have the transfer event defined by other criteria such as treating specialty or ward location. | |
| 8 | display text(+) | 0;8 | FREE TEXT | This field is the name of the event as it will appear to the user in CPRS. | ||
| 9 | ordering parameters location | 0;9 | POINTER | 44 | Many order dialogs use parameters that depend on location; this field will be used as the default location for retrieving those parameter values when delaying orders to this event. The patient's actual location will be saved with the order at the time of its release. | |
| 10 | included treating specialties | TS;0 | MULTIPLE | 100.51 | These are treating specialties that can satisfy this event; if the patient's new specialty matches one in this list then orders delayed for this event may be released. | |
| 11 | included locations | LOC;0 | MULTIPLE | 100.511 | These are ward locations that can satisfy this event; if the patient's new location matches one in this list then orders delayed for this event may be released. | |
| 12 | edit history | 9;0 | MULTIPLE | 100.512 | ||
| 13 | copy active orders | 0;11 | BOOLEAN | 1:YES 0:NO | This field determines whether or not the user will be presented with the patient's active orders, which may then be copied to the delayed event being created. If this field is set to no then the user will not see the patient's active orders and will not be allowed to copy any current orders. If this field is set to yes then the user will be shown the patient's active orders and the user may select orders to be copied to the delayed event. The list of active orders will be presented to the user after the ORDER DIALOG for the release event is processed (if it exists) and before the ORDER SET/MENU for the release event is processed (if it exists). | |
| 14 | parent | 0;12 | POINTER | 100.5 | DAD | For release events that have a common trigger event (e.g. same treating specialty or same locations) but require different names or display text a parent-child relationship can be set up. The parent contains the base trigger event logic while the child contains the information unique to this event. In a sense, the child events are "synonyms" to the parent event as all childen are related to the parent. When the trigger event occurs that would release orders for the parent all the child orders related to that parent are also released. |