| .01 | patient(+) | 0;1 | POINTER | 2 | B | This is a pointer to the patient file and is the patient associated with
this event. |
| 1 | activity | 10;0 | MULTIPLE | 100.25 | | This multiple contains a log of actions taken on this event that are
relevant to the release or discontinuance of orders. |
| 2 | event | 0;2 | POINTER | 100.5 | E | This field is a pointer to the OE/RR RELEASE EVENTS file, which defines
the conditions under which delayed orders are to be released for this
patient event, if delayed orders are related to this event. |
| 3 | admission | 0;3 | POINTER | 405 | | This field is a pointer to the Admission movement for which this event
is valid; this will be the current admission if the patient is an
inpatient when delayed orders are written, otherwise the admission
movement will be stuffed in when the patient is admitted and the orders
released. If the patient is discharged without this event having been
processed, it will be retired and any orders still delayed will be lapsed. |
| 4 | order | 0;4 | POINTER | 100 | AO | This field is a pointer to the doctor's order requesting that this event
occur for this patient when delayed orders are written. |
| 5 | created on | 0;5 | DATE-TIME | | | This field is the timestamp of when this event was entered into the file
for this patient. |
| 6 | created by | 0;6 | POINTER | 200 | | This field is a pointer to the user who entered this event into the file
for this patient. |
| 11 | event date/time | 1;1 | DATE-TIME | | | This field is the date and time that this event occurred for this patient;
if the event is an MAS movement, this time will be the DATE/TIME from
the PATIENT MOVEMENT file which may be slightly different than the
actual time that this event was processed by the event driver. |
| 12 | patient movement | 1;2 | POINTER | 405 | | This field is a pointer to the MAS Patient Movement that satisfied this
event for this patient; any changes to this movement that alter the
conditions of the event will be tracked in the Activity log. |
| 13 | auto-dc rule | 1;3 | POINTER | 100.6 | DC | This field is the Auto-DC Rule from file #100.6 that was used to
automatically discontinue active orders when this event occurred. Those
orders that were dc'd are listed in the Discontinued Orders multiple of
this file. |
| 14 | surgery | 1;4 | POINTER | 130 | ASR | This field is a pointer to the Surgery case that satisfied this event for
this patient when the TIME PAT OUT OR field was entered (for events prior
to the instllation of patch SR*3*157) or when the TIME PAT IN OR field
was entered (for events after the installation of patch SR*3*157); any
changes to this field will be tracked in the Activity log. |
| 15 | parent | 1;5 | POINTER | 100.2 | DAD | This field is a "parent" event, allowing multiple Patient Events to be
collected together for release at the same time based on the same criteria;
the parent event tracks the release criteria, while each "child" event
defines a particular set of orders to be released on that event. |
| 20 | released orders | 2;0 | MULTIPLE | 100.26 | | This multiple field contains the delayed orders that were released based
on the release event defined in the OE/RR RELEASE EVENTS file #100.5 when
this event occurred. |
| 30 | discontinued orders | 3;0 | MULTIPLE | 100.27 | | This multiple contains the orders that were automatically discontinued
based on the rules defined in the OE/RR AUTO-DC RULES file #100.6 when
this event occurred. |