STANDARD DATA DICTIONARY #100.2 -- OE/RR PATIENT EVENT FILE 3/24/25 PAGE 1
STORED IN ^ORE(100.2, *** NO DATA STORED YET *** SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 3.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
This file is used by CPRS to track what happened to a patient's orders as a result of an event, such as an MAS movement or
returning from the OR.
IDENTIFIED BY: EVENT (#2), EVENT DATE/TIME (#11)
POINTED TO BY: EVENT field (#15) of the ORDER File (#100)
DC EVENT field (#68) of the ORDER File (#100)
PARENT field (#15) of the OE/RR PATIENT EVENT File (#100.2)
CROSS
REFERENCED BY: ORDER(AO), SURGERY(ASR), PATIENT(B), PARENT(DAD), AUTO-DC RULE(DC), EVENT(E)
INDEXED BY: PATIENT & EVENT DATE/TIME (AC), PATIENT MOVEMENT (ADT), PATIENT & EVENT & EVENT DATE/TIME (AE)
100.2,.01 PATIENT 0;1 POINTER TO PATIENT FILE (#2) (Required)
LAST EDITED: MAY 08, 2002
HELP-PROMPT: Enter the name of the patient.
DESCRIPTION:
This is a pointer to the patient file and is the patient associated with this event.
CROSS-REFERENCE: 100.2^B
1)= S ^ORE(100.2,"B",$E(X,1,30),DA)=""
2)= K ^ORE(100.2,"B",$E(X,1,30),DA)
RECORD INDEXES: AC (#188), AE (#190)
100.2,1 ACTIVITY 10;0 DATE Multiple #100.25 (Add New Entry without Asking)
DESCRIPTION: This multiple contains a log of actions taken on this event that are relevant to the release or
discontinuance of orders.
100.25,.01 DATE/TIME OF ACTIVITY 0;1 DATE
INPUT TRANSFORM: S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the date and time that action was taken on this event.
DESCRIPTION:
This is the actual date and time that the activity occurred.
CROSS-REFERENCE: 100.25^B
1)= S ^ORE(100.2,DA(1),10,"B",$E(X,1,30),DA)=""
2)= K ^ORE(100.2,DA(1),10,"B",$E(X,1,30),DA)
100.25,2 TYPE OF EVENT ACTIVITY 0;2 SET (Required)
'NW' FOR NEW;
'ED' FOR EDITED;
'RE' FOR REENTERED;
'MN' FOR MANUALLY RELEASED;
'LP' FOR LAPSED;
'DL' FOR DELETED;
'CA' FOR CANCELLED;
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the type of action that was taken on this event.
DESCRIPTION: This field is a code indicating the type of activity that occurred. This may be new, edited,
re-entered, manually released, deleted or cancelled.
An event may also be "lapsed" if it stays unprocessed beyond the time frame defined by the "Lapse
in #Days" field of the OE/RR RELEASE EVENTS file #100.5 for this event.
100.25,3 USER 0;3 POINTER TO NEW PERSON FILE (#200)
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the user taking this action on the event.
DESCRIPTION:
This field is the user who entered or modified the activity.
100.25,4 EVENT TYPE 0;4 SET
'A' FOR ADMISSION;
'T' FOR TRANSFER;
'D' FOR DISCHARGE;
'O' FOR O.R.;
'S' FOR SPECIALTY CHANGE;
LAST EDITED: MAY 30, 2007
HELP-PROMPT: Enter the type of event that was processed.
DESCRIPTION: This field is the type of event that was processed. This could be admission, discharge,
transfer, O.R. (surgery), or specialty change.
100.25,5 MAS MOVEMENT TYPE 0;5 POINTER TO MAS MOVEMENT TYPE FILE (#405.2)
LAST EDITED: APR 25, 2002
HELP-PROMPT: If this event is an MAS patient movement, enter the movement type.
DESCRIPTION: This field is the MAS Movement Type of the activity that was processed, if it was an MAS patient
movement.
100.25,6 TREATING SPECIALTY 0;6 POINTER TO FACILITY TREATING SPECIALTY FILE (#45.7)
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the treating specialty associated with this event.
DESCRIPTION: This field is the treating specialty associated with this activity, if it is an MAS patient
movement.
100.25,7 WARD LOCATION 0;7 POINTER TO WARD LOCATION FILE (#42)
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the ward location associated with this event.
DESCRIPTION:
This field is the ward location associated with this activity, if it is an MAS patient movement.
100.2,2 EVENT 0;2 POINTER TO OE/RR RELEASE EVENTS FILE (#100.5)
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter an event for which delayed orders are to be released for this patient.
DESCRIPTION: 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.
CROSS-REFERENCE: 100.2^E
1)= S ^ORE(100.2,"E",$E(X,1,30),DA)=""
2)= K ^ORE(100.2,"E",$E(X,1,30),DA)
RECORD INDEXES: AE (#190)
100.2,3 ADMISSION 0;3 POINTER TO PATIENT MOVEMENT FILE (#405)
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the admission during which this event is to occur.
DESCRIPTION: 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.
100.2,4 ORDER 0;4 POINTER TO ORDER FILE (#100)
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the number of the doctor's order for this event.
DESCRIPTION: This field is a pointer to the doctor's order requesting that this event occur for this patient
when delayed orders are written.
CROSS-REFERENCE: 100.2^AO
1)= S ^ORE(100.2,"AO",$E(X,1,30),DA)=""
2)= K ^ORE(100.2,"AO",$E(X,1,30),DA)
100.2,5 CREATED ON 0;5 DATE
INPUT TRANSFORM: S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the date and time this event was created for this patient.
DESCRIPTION:
This field is the timestamp of when this event was entered into the file for this patient.
100.2,6 CREATED BY 0;6 POINTER TO NEW PERSON FILE (#200)
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the name of the user that created this event for this patient.
DESCRIPTION:
This field is a pointer to the user who entered this event into the file for this patient.
100.2,11 EVENT DATE/TIME 1;1 DATE
INPUT TRANSFORM: S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the date and time this event occurred.
DESCRIPTION: 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.
RECORD INDEXES: AC (#188), AE (#190)
100.2,12 PATIENT MOVEMENT 1;2 POINTER TO PATIENT MOVEMENT FILE (#405)
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the MAS Movement that satisfied this event for this patient.
DESCRIPTION: 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.
RECORD INDEXES: ADT (#189)
100.2,13 AUTO-DC RULE 1;3 POINTER TO OE/RR AUTO-DC RULES FILE (#100.6)
LAST EDITED: APR 26, 2002
HELP-PROMPT: Enter the rule that was used when auto-dc'ing orders for this event.
DESCRIPTION: 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.
CROSS-REFERENCE: 100.2^DC
1)= S ^ORE(100.2,"DC",$E(X,1,30),DA)=""
2)= K ^ORE(100.2,"DC",$E(X,1,30),DA)
100.2,14 SURGERY 1;4 POINTER TO SURGERY FILE (#130)
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the surgery case that satisfied this event for this patient.
DESCRIPTION: 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.
CROSS-REFERENCE: 100.2^ASR
1)= S ^ORE(100.2,"ASR",$E(X,1,30),DA)=""
2)= K ^ORE(100.2,"ASR",$E(X,1,30),DA)
100.2,15 PARENT 1;5 POINTER TO OE/RR PATIENT EVENT FILE (#100.2)
LAST EDITED: AUG 23, 2002
HELP-PROMPT: Enter the Patient Event that will trigger the release of this one.
DESCRIPTION: 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.
CROSS-REFERENCE: 100.2^DAD
1)= S ^ORE(100.2,"DAD",$E(X,1,30),DA)=""
2)= K ^ORE(100.2,"DAD",$E(X,1,30),DA)
100.2,20 RELEASED ORDERS 2;0 POINTER Multiple #100.26 (Add New Entry without Asking)
DESCRIPTION: 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.
100.26,.01 RELEASED ORDER 0;1 POINTER TO ORDER FILE (#100) (Multiply asked)
INPUT TRANSFORM: S:$D(X) DINUM=X
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the number of a delayed order that was released by this event.
DESCRIPTION: This field is a pointer to the Orders file #100 of an order that was released as a result of the
event occurring.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
100.26,2 BY ACTION 0;2 SET
'MN' FOR MANUAL RELEASE;
'ES' FOR SIGNATURE;
LAST EDITED: SEP 23, 2002
HELP-PROMPT: Enter the action that released this order.
DESCRIPTION: This is the CPRS action that released this order to the service, instead of the specified OE/RR
RELEASE EVENT. These orders are tracked here so that they can all be displayed in the
"Auto-DC/Release Events" view, including the complete movement data in the Detailed Display.
100.2,30 DISCONTINUED ORDERS 3;0 POINTER Multiple #100.27 (Add New Entry without Asking)
DESCRIPTION: 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.
100.27,.01 DISCONTINUED ORDER 0;1 POINTER TO ORDER FILE (#100) (Multiply asked)
INPUT TRANSFORM: S:$D(X) DINUM=X
LAST EDITED: APR 25, 2002
HELP-PROMPT: Enter the number of an order that was automatically discontinued by this event.
DESCRIPTION:
This field is the number of the order in the Orders file #100.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
100.27,2 BY PACKAGE 0;2 SET
'FH' FOR DIETETICS;
'LR' FOR LABORATORY;
'PS' FOR PHARMACY;
LAST EDITED: SEP 16, 2002
HELP-PROMPT: Enter the package that auto-dc'd this order.
DESCRIPTION: This is the VistA package whose protocol on the DGPM MOVEMENT EVENTS driver caused this order to
auto-dc, instead of the OE/RR AUTO-DC RULE. These orders are tracked here so that they can all
be displayed in the "Auto-DC/Release Events" view, including the complete movement data in the
Detailed Display.
FILES POINTED TO FIELDS
FACILITY TREATING SPECIALTY
(#45.7) ACTIVITY:TREATING SPECIALTY (#6)
MAS MOVEMENT TYPE (#405.2) ACTIVITY:MAS MOVEMENT TYPE (#5)
NEW PERSON (#200) CREATED BY (#6)
ACTIVITY:USER (#3)
OE/RR AUTO-DC RULES (#100.6) AUTO-DC RULE (#13)
OE/RR PATIENT EVENT (#100.2) PARENT (#15)
OE/RR RELEASE EVENTS (#100.5) EVENT (#2)
ORDER (#100) ORDER (#4)
RELEASED ORDERS:RELEASED ORDER (#.01)
DISCONTINUED ORDERS:DISCONTINUED ORDER (#.01)
PATIENT (#2) PATIENT (#.01)
PATIENT MOVEMENT (#405) ADMISSION (#3)
PATIENT MOVEMENT (#12)
SURGERY (#130) SURGERY (#14)
WARD LOCATION (#42) ACTIVITY:WARD LOCATION (#7)
File #100.2
Record Indexes:
AC (#188) RECORD REGULAR IR SORTING ONLY
Short Descr: Processed events by patient, reverse date/time
Set Logic: S ^ORE(100.2,"AC",X(1),X(2),DA)=""
Kill Logic: K ^ORE(100.2,"AC",X(1),X(2),DA)
Whole Kill: K ^ORE(100.2,"AC")
X(1): PATIENT (100.2,.01) (Subscr 1) (forwards)
X(2): EVENT DATE/TIME (100.2,11) (Subscr 2) (forwards)
Transform (Storage): S X=9999999-X
ADT (#189) RECORD MUMPS IR SORTING ONLY
Short Descr: Activity on MAS movements
Set Logic: N I,XD S I=0 F S I=+$O(^ORE(100.2,DA,10,I)) Q:I<1 S XD=+$P($G(^(I,0)),U) S:XD ^ORE(100.2,"ADT",X(1),XD,DA,I)=
""
Kill Logic: N I,XD S I=0 F S I=+$O(^ORE(100.2,DA,10,I)) Q:I<1 S XD=+$P($G(^(I,0)),U) K:XD ^ORE(100.2,"ADT",X(1),XD,DA,I)
Whole Kill: K ^ORE(100.2,"ADT")
X(1): PATIENT MOVEMENT (100.2,12) (Subscr 1) (forwards)
AE (#190) RECORD REGULAR IR SORTING ONLY
Short Descr: Pending events by patient
Set Logic: S ^ORE(100.2,"AE",X(1),X(2),DA)=""
Set Cond: S X=$S(X(3):0,1:1)
Kill Logic: K ^ORE(100.2,"AE",X(1),X(2),DA)
Kill Cond: S X=$S(X(3):0,1:1)
Whole Kill: K ^ORE(100.2,"AE")
X(1): PATIENT (100.2,.01) (Subscr 1) (forwards)
X(2): EVENT (100.2,2) (Subscr 2) (forwards)
X(3): EVENT DATE/TIME (100.2,11) (forwards)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):