STANDARD DATA DICTIONARY #100.6 -- OE/RR AUTO-DC RULES FILE 3/24/25 PAGE 1
STORED IN ^ORD(100.6, (10 ENTRIES) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 3.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
This file contains the locally-defined rules that control if and when active orders are automatically discontinued within each
division.
It is strongly recommended that this file not be edited using File Manager. Please use the edit options provided in CPRS.
IDENTIFIED BY: TYPE OF EVENT (#2)[R], DIVISION (#3)[R]
POINTED TO BY: AUTO-DC RULE field (#13) of the OE/RR PATIENT EVENT File (#100.2)
CROSS
REFERENCED BY: NAME(B), DIVISION(D)
INDEXED BY: DIVISION & INACTIVATED (AC), DIVISION & TYPE OF EVENT & INACTIVATED (AE)
LAST MODIFIED: JUN 24,2020@12:14:45
100.6,.01 NAME 0;1 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>50!($L(X)<3) X
LAST EDITED: APR 26, 2002
HELP-PROMPT: Answer must be 3-50 characters in length.
DESCRIPTION: This is the name of the rule, used to identify it uniquely in the file; it is visible in the Rule
Editor only.
DELETE TEST: .01,0)= I $$CANDEL^OREV1(100.6)
CROSS-REFERENCE: 100.6^B
1)= S ^ORD(100.6,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,"B",$E(X,1,30),DA)
100.6,1 INACTIVATED 1;1 DATE
INPUT TRANSFORM: S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
LAST EDITED: JUL 09, 2002
HELP-PROMPT: Enter the date/time this rule was inactivated.
DESCRIPTION: This is the date/time this rule is no longer considered active; after this date/time, this rule
will no longer apply.
RECORD INDEXES: AC (#25), AE (#26)
100.6,1.5 ACTIVATION HISTORY 2;0 DATE Multiple #100.61 (Add New Entry without Asking)
INDEXED BY: ACTIVATION DATE/TIME & INACTIVATION DATE/TIME (ACT)
100.61,.01 ACTIVATION DATE/TIME 0;1 DATE
INPUT TRANSFORM: S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
LAST EDITED: JUL 09, 2002
CROSS-REFERENCE: 100.61^B
1)= S ^ORD(100.6,DA(1),2,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(1),2,"B",$E(X,1,30),DA)
CROSS-REFERENCE: 100.61^ACT^MUMPS
1)= S ^ORD(100.6,DA(1),2,"ACT",DA)=""
2)= Q
FIELD INDEX: ACT (#27) MUMPS IR SORTING ONLY
Short Descr: Describes current multiple for activation of rule/event
Description: This cross reference provides a quick way to identify which multiple is the current
active/inactive pair for the rule/event.
Set Logic: S:X(1) ^ORD(100.6,DA(1),2,"ACT",DA)="" K:X(2) ^ORD(100.6,DA(1),2,"ACT")
Kill Logic: Q
X(1): ACTIVATION DATE/TIME (100.61,.01) (forwards)
X(2): INACTIVATION DATE/TIME (100.61,1) (forwards)
100.61,1 INACTIVATION DATE/TIME 0;2 DATE
INPUT TRANSFORM: S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
LAST EDITED: JUL 09, 2002
CROSS-REFERENCE: 100.61^ACT^MUMPS
1)= K ^ORD(100.6,DA(1),2,"ACT")
2)= Q
FIELD INDEX: ACT (#27) MUMPS IR SORTING ONLY
Short Descr: Describes current multiple for activation of rule/event
Description: This cross reference provides a quick way to identify which multiple is the current
active/inactive pair for the rule/event.
Set Logic: S:X(1) ^ORD(100.6,DA(1),2,"ACT",DA)="" K:X(2) ^ORD(100.6,DA(1),2,"ACT")
Kill Logic: Q
X(1): ACTIVATION DATE/TIME (100.61,.01) (forwards)
X(2): INACTIVATION DATE/TIME (100.61,1) (forwards)
100.6,2 TYPE OF EVENT 0;2 SET (Required)
'A' FOR ADMISSION;
'T' FOR TRANSFER;
'D' FOR DISCHARGE;
'S' FOR SPECIALTY TRANSFER;
'O' FOR O.R.;
LAST EDITED: FEB 06, 2014
HELP-PROMPT: Enter the type of event that should trigger orders to be auto-dc'd.
DESCRIPTION: This is the event that should cause orders to be automatically discontinued; for OR events, the
orders will be discontinued when the TIME PAT IN OR field is entered in the Surgery package.
RECORD INDEXES: AE (#26)
100.6,3 DIVISION 0;3 POINTER TO INSTITUTION FILE (#4) (Required)
LAST EDITED: MAY 23, 2002
HELP-PROMPT: Enter the division this auto-dc rule applies to.
DESCRIPTION: This is the division that this auto-dc rule should be applied to; for a transfer across divisions,
this should be the new division that the patient is going to.
CROSS-REFERENCE: 100.6^D
1)= S ^ORD(100.6,"D",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,"D",$E(X,1,30),DA)
RECORD INDEXES: AC (#25), AE (#26)
100.6,4 DC REASON 0;4 POINTER TO ORDER REASON FILE (#100.03)
LAST EDITED: JAN 26, 2002
HELP-PROMPT: Enter the reason to be saved with the order when dc'd.
DESCRIPTION: This is the reason that will be saved with the order indicating why it was automatically
discontinued.
100.6,5 DISPLAY TEXT 0;5 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>60!($L(X)<3) X
LAST EDITED: MAR 01, 2002
HELP-PROMPT: Answer must be 3-60 characters in length.
DESCRIPTION:
This field is the name of the rule as it will appear to the user in CPRS.
100.6,6 EXCEPT FROM OBSERVATION 0;6 SET
'0' FOR NO;
'1' FOR IF READMITTING;
'2' FOR YES;
LAST EDITED: MAR 12, 2002
HELP-PROMPT: If discharge from an observation specialty should be an exception to this rule, enter YES or IF
READMITTING.
DESCRIPTION: This indicates if an observation treating specialty should prevent this rule from being applied,
when the patient is discharged from it. Enter YES if an observation specialty should always be
considered an exception to this rule, or NO to never consider it. IF READMITTED will cause the
clerk to be asked if the patient will be immediately admitted again, and a response of YES will
prevent this rule from being applied; because it requires user interaction, this value should only
be used with the non- tasked OR GUA EVENT PROCESSOR NOTASK protocol on DGPM MOVEMENT EVENTS,
otherwise a value of NO will be assumed and this rule will be applied without exception.
100.6,30 MAS MOVEMENT TYPES 3;0 POINTER Multiple #100.63
LAST EDITED: JUN 08, 2009
DESCRIPTION: These are the MAS Movement Types that define this event; when an MAS event occurs for one of these
types, this rule will be processed if active.
100.63,.01 MAS MOVEMENT TYPE 0;1 POINTER TO MAS MOVEMENT TYPE FILE (#405.2) (Multiply asked)
INPUT TRANSFORM: D SCR^OREV1 D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
LAST EDITED: MAY 23, 2002
HELP-PROMPT: Enter a movement type to further define this rule.
DESCRIPTION: Movement Type(s) more completely define the trigger event for this rule, to allow for different
rules on various types of MAS events. For example, to define a rule for cancelling orders when a
patient dies enter the movement types DEATH and DEATH WITH AUTOPSY; a movement type may only be
used in one active rule, so omit these types when creating other Discharge rules.
SCREEN: D SCR^OREV1
EXPLANATION: Select an MAS MOVEMENT TYPE that can be used with the TYPE OF EVENT that you selected.
CROSS-REFERENCE: 100.63^B
1)= S ^ORD(100.6,DA(1),3,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(1),3,"B",$E(X,1,30),DA)
100.6,40 EXCLUDED TREATING SPECIALTIES 4;0 POINTER Multiple #100.64
DESCRIPTION: These are treating specialties that will cause this rule to not be processed, if the EXCEPT FROM
and TO specialties match the patient's transfer.
100.64,.01 EXCEPT FROM SPECIALTY 0;1 POINTER TO FACILITY TREATING SPECIALTY FILE (#45.7) (Multiply asked)
INPUT TRANSFORM: S:$G(X) DINUM=X
LAST EDITED: JAN 28, 2002
HELP-PROMPT: Enter a specialty that is an exception to this rule, when the patient is transferred from it.
DESCRIPTION: This is a treating specialty that will prevent this rule from being applied; specialty transfer
rules will discontinue active orders unless the patient is being transferred from this specialty
to one listed in the TO SPECIALTY multiple.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 100.64^B
1)= S ^ORD(100.6,DA(1),4,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(1),4,"B",$E(X,1,30),DA)
100.64,1 TO SPECIALTY 1;0 POINTER Multiple #100.641
DESCRIPTION: These are treating specialties that will cause this rule to not be processed, if the EXCEPT FROM
and TO specialties match the patient's transfer.
100.641,.01 TO SPECIALTY 0;1 POINTER TO FACILITY TREATING SPECIALTY FILE (#45.7) (Multiply asked)
INPUT TRANSFORM: S:$G(X) DINUM=X
LAST EDITED: JAN 28, 2002
HELP-PROMPT: Enter a specialty that is an exception to this rule, when the patient is transferred to it.
DESCRIPTION: This is a treating specialty that will prevent this rule from being applied; specialty transfer
rules will discontinue active orders unless the patient is being transferred to this specialty
from the EXCEPT FROM SPECIALTY.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 100.641^B
1)= S ^ORD(100.6,DA(2),4,DA(1),1,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(2),4,DA(1),1,"B",$E(X,1,30),DA)
100.6,50 INCLUDED LOCATIONS 5;0 Multiple #100.62
INDEXED BY: FROM ALL LOCATIONS & FROM LOCATION & TO ALL LOCATIONS & TO LOCATION (ADC)
100.62,.01 INCLUDED LOCATIONS ID 0;1 FREE TEXT (Multiply asked)
INPUT TRANSFORM: K:$L(X)>70!($L(X)<1) X
LAST EDITED: MAY 23, 2002
HELP-PROMPT: Answer must be 1-70 characters in length. FROM - TO entries included in this multiple will cause
orders to auto-dc.
DESCRIPTION: Enter an ID (free text) that will represent an entry in the FROM - TO location matrix. The value
of the ID field is insignificant as it simply represents a place holder. You can use any naming
or numbering convention that you want.
Orders will not auto-dc for location (ward) type transfers unless the transfer from and transfer
to locations are identified within the INCLUDED LOCATIONS from - to entries. If the transfer
from and to locations are found in this multiple then orders will auto-dc.
CROSS-REFERENCE: 100.62^B
1)= S ^ORD(100.6,DA(1),5,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(1),5,"B",$E(X,1,30),DA)
100.62,1 FROM ALL LOCATIONS 0;2 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: MAY 23, 2002
HELP-PROMPT: Enter 1 or Yes if want to select ALL locations for the FROM field.
DESCRIPTION: This is a hospital location that will cause this rule to be applied; if no specialty change
occurs with the transfer, then the patient must be moving from this location to one listed in the
TO LOCATION multiple for active orders to be discontinued.
RECORD INDEXES: ADC (#166)
100.62,2 FROM LOCATION 0;3 POINTER TO HOSPITAL LOCATION FILE (#44)
LAST EDITED: MAY 23, 2002
HELP-PROMPT: Enter location patient is coming FROM.
DESCRIPTION: If you did not select YES for the FROM ALL LOCATIONS field then you must select an individual
field for the patient to be coming FROM.
This is a hospital location that will cause this rule to be applied; if no specialty change
occurs with the transfer, then the patient must be moving from this location to one listed in the
TO LOCATION multiple for active orders to be discontinued.
RECORD INDEXES: ADC (#166)
100.62,3 TO ALL LOCATIONS 0;4 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: MAY 23, 2002
HELP-PROMPT: Enter 1 or Yes if want to select ALL locations for the TO field.
DESCRIPTION: This is a hospital location that will cause this rule to be applied; if no specialty change
occurs with the transfer, then the patient must be moving to this location from the FROM LOCATION
for active orders to be discontinued.
RECORD INDEXES: ADC (#166)
100.62,4 TO LOCATION 0;5 POINTER TO HOSPITAL LOCATION FILE (#44)
LAST EDITED: MAY 23, 2002
HELP-PROMPT: Enter location patient is moving TO
DESCRIPTION: If you did not set the TO ALL LOCATIONS field to YES then you must specify the location the
patient is moving TO that will match with the selection made for the FROM location (either all or
individual).
This is a hospital location that will cause this rule to be applied; if no specialty change
occurs with the transfer, then the patient must be moving to this location from the FROM LOCATION
for active orders to be discontinued.
RECORD INDEXES: ADC (#166)
100.6,60 INCLUDED DIVISIONS 6;0 POINTER Multiple #100.66
DESCRIPTION: These are the divisions that will cause this rule to be processed, if the FROM division matches the
patient's transfer.
100.66,.01 FROM DIVISION 0;1 POINTER TO INSTITUTION FILE (#4) (Multiply asked)
INPUT TRANSFORM: S:$G(X) DINUM=X
LAST EDITED: JAN 28, 2002
HELP-PROMPT: Enter a division that will satisfy this rule, when the patient is transferred from it.
DESCRIPTION: This is a division that will cause this rule to be applied; if no specialty change occurs with
the transfer, then the patient must be moving from this division for active orders to be
discontinued.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 100.66^B
1)= S ^ORD(100.6,DA(1),6,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(1),6,"B",$E(X,1,30),DA)
100.6,70 INCLUDED PACKAGES 7;0 POINTER Multiple #100.67
DESCRIPTION: These are the packages whose orders are to be automatically discontinued when this rule is
processed.
100.67,.01 TYPE OF ORDERS TO DC 0;1 POINTER TO PACKAGE FILE (#9.4) (Multiply asked)
INPUT TRANSFORM:S DIC("S")="I ""^GMRC^FH^LR^PSJ^PSO^PSIV^RA^OR^VBEC^""[(""^""_$P(^(0),U,2)_""^"")" D ^DIC K DIC S D
IC=DIE,X=+Y K:Y<0 X
LAST EDITED: JUN 08, 2009
HELP-PROMPT: Enter a package whose orders should be dc'd by this rule.
DESCRIPTION: This is a package whose active orders are to be automatically discontinued when the conditions of
this rule are satisfied.
SCREEN: S DIC("S")="I ""^GMRC^FH^LR^PSJ^PSO^PSIV^RA^OR^VBEC^""[(""^""_$P(^(0),U,2)_""^"")"
EXPLANATION: Choose a package whose orders can be entered within CPRS
CROSS-REFERENCE:100.67^B
1)= S ^ORD(100.6,DA(1),7,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(1),7,"B",$E(X,1,30),DA)
100.6,80 EXCLUDED ORDERABLE ITEMS 8;0 POINTER Multiple #100.68
DESCRIPTION: These are the orderable items that are NOT to be automatically discontinued when this rule is
processed, even if an order for it belongs to a package in the INCLUDED PACKAGES multiple.
100.68,.01 EXCEPT FOR ORDERABLE ITEM 0;1 POINTER TO ORDERABLE ITEMS FILE (#101.43) (Multiply asked)
INPUT TRANSFORM: S DIC("S")="I '$G(^ORD(101.43,Y,.1))" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
LAST EDITED: JUL 03, 2002
HELP-PROMPT: Enter an orderable item that should not be dc'd by this rule.
DESCRIPTION: This is an orderable item that will be exempt from any automatic discontinuing of orders normally
triggered by this rule; if an active order for this item is encountered while processing this
rule, it will be skipped and not discontinued.
SCREEN: S DIC("S")="I '$G(^ORD(101.43,Y,.1))"
EXPLANATION: Only "active" orderable items can be selected
CROSS-REFERENCE: 100.68^B
1)= S ^ORD(100.6,DA(1),8,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(1),8,"B",$E(X,1,30),DA)
100.68,1 LOCK 0;2 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: MAY 21, 2015
100.6,81 EDIT HISTORY 9;0 DATE Multiple #100.681 (Add New Entry without Asking)
100.681,.01 EDIT HISTORY 0;1 DATE
INPUT TRANSFORM: S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
LAST EDITED: APR 23, 2002
DESCRIPTION:
Tracks the entering and editing of rules.
CROSS-REFERENCE: 100.681^B
1)= S ^ORD(100.6,DA(1),9,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(1),9,"B",$E(X,1,30),DA)
100.681,1 WHO ENTERED/EDITED 0;2 POINTER TO NEW PERSON FILE (#200)
LAST EDITED: APR 23, 2002
DESCRIPTION:
Name of person who added or edited this rule
100.681,2 ACTION 0;3 SET
'N' FOR NEW;
'E' FOR EDIT;
LAST EDITED: APR 23, 2002
DESCRIPTION:
What action was taken on the rule?
100.6,100 EXCLUDED DISPLAY GROUP 10;0 POINTER Multiple #100.65
100.65,.01 EXCEPT ORDERS IN DISPLAY GROUP 0;1 POINTER TO DISPLAY GROUP FILE (#100.98) (Multiply asked)
LAST EDITED: JUL 03, 2002
HELP-PROMPT: Orders related to this display group will not be auto-discontinued
DESCRIPTION: Any order related to the display group entered in the excluded display group multiple will be
exempt from any auto-discontinuing normally triggered by this rule.
You can use the excluded display group to protect a group of orders from being auto-discontinued.
If an order belonging to this display group is found while processing this rule it will be
skipped and not be auto-discontinued.
SCREEN: S DIC("S")="I $P($G(^(0)),U,3)=""OR"""
EXPLANATION: Only allow selection of operating room type entries
CROSS-REFERENCE: 100.65^B
1)= S ^ORD(100.6,DA(1),10,"B",$E(X,1,30),DA)=""
2)= K ^ORD(100.6,DA(1),10,"B",$E(X,1,30),DA)
FILES POINTED TO FIELDS
DISPLAY GROUP (#100.98) EXCLUDED DISPLAY GROUP:EXCEPT ORDERS IN DISPLAY GROUP (#.01)
FACILITY TREATING SPECIALTY
(#45.7) EXCLUDED TREATING SPECIALTIES:EXCEPT FROM SPECIALTY (#.01)
TO SPECIALTY:TO SPECIALTY (#.01)
HOSPITAL LOCATION (#44) INCLUDED LOCATIONS:FROM LOCATION (#2)
TO LOCATION (#4)
INSTITUTION (#4) DIVISION (#3)
INCLUDED DIVISIONS:FROM DIVISION (#.01)
MAS MOVEMENT TYPE (#405.2) MAS MOVEMENT TYPES:MAS MOVEMENT TYPE (#.01)
NEW PERSON (#200) EDIT HISTORY:WHO ENTERED/EDITED (#1)
ORDER REASON (#100.03) DC REASON (#4)
ORDERABLE ITEMS (#101.43) EXCLUDED ORDERABLE ITEMS:EXCEPT FOR ORDERABLE ITEM (#.01)
PACKAGE (#9.4) INCLUDED PACKAGES:TYPE OF ORDERS TO DC (#.01)
File #100.6
Record Indexes:
AC (#25) RECORD MUMPS IR SORTING ONLY
Short Descr: Active rules by movement type within each division
Set Logic: N ORI,ORX S ORI=0 F S ORI=+$O(^ORD(100.6,DA,3,ORI)) Q:ORI<1 S ORX=+$P($G(^(ORI,0)),U) S:ORX ^ORD(100.6,"AC",X
(1),ORX,DA)=""
Set Cond: S X=$S('X(2):1,1:0)
Kill Logic: N ORI,ORX S ORI=0 F S ORI=+$O(^ORD(100.6,DA,3,ORI)) Q:ORI<1 S ORX=+$P($G(^(ORI,0)),U) K:ORX ^ORD(100.6,"AC",X
(1),ORX,DA)
Kill Cond: S X=$S('X(2):1,1:0)
Whole Kill: K ^ORD(100.6,"AC")
X(1): DIVISION (100.6,3) (Subscr 1) (forwards)
X(2): INACTIVATED (100.6,1) (forwards)
AE (#26) RECORD REGULAR IR SORTING ONLY
Short Descr: Active events by division
Set Logic: S ^ORD(100.6,"AE",X(1),X(2),DA)=""
Set Cond: S X=$S(X(3)<1:1,X(3)>$$NOW^XLFDT:1,1:0)
Kill Logic: K ^ORD(100.6,"AE",X(1),X(2),DA)
Kill Cond: S X=$S(X(3)<1:1,X(3)>$$NOW^XLFDT:1,1:0)
Whole Kill: K ^ORD(100.6,"AE")
X(1): DIVISION (100.6,3) (Subscr 1) (forwards)
X(2): TYPE OF EVENT (100.6,2) (Subscr 2) (forwards)
X(3): INACTIVATED (100.6,1) (forwards)
Subfile #100.62
Record Indexes:
ADC (#166) RECORD MUMPS IR SORTING ONLY
Short Descr: Allow quick access to from/to pairs
Set Logic: S ^ORD(100.6,DA(1),5,"ADC",X(5),X(6),DA)=""
Kill Logic: K ^ORD(100.6,DA(1),5,"ADC",X(5),X(6),DA)
Whole Kill: K ^ORD(100.6,DA(1),5,"ADC")
X(1): FROM ALL LOCATIONS (100.62,1) (forwards)
X(2): FROM LOCATION (100.62,2) (forwards)
X(3): TO ALL LOCATIONS (100.62,3) (forwards)
X(4): TO LOCATION (100.62,4) (forwards)
X(5): Computed Code: S X=$S(X(2):X(2),X(1):"ALL",1:"NONE")
(Subscr 1)
X(6): Computed Code: S X=$S(X(4):X(4),X(3):"ALL",1:"NONE")
(Subscr 2)
INPUT TEMPLATE(S):
OREV AUTO DC MAY 28, 2015@14:33 USER #0
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):