Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables |  All
Print Page as PDF
Global: ^PXD(801.1

Package: PCE Patient Care Encounter

Global: ^PXD(801.1


Information

FileMan FileNo FileMan Filename Package
801.1 REMINDER ORDER CHECK RULES PCE Patient Care Encounter

Description

Directly Accessed By Routines, Total: 10

Package Total Routines
Clinical Reminders 8 PXRMEXPS    PXRMFRPT    PXRMOCG    PXRMOCR    PXRMORCH    PXRMORED    PXRMORXR    PXRMP22I
PCE Patient Care Encounter 2 EDIT HISTORY    ^PXD(801.1    

Accessed By FileMan Db Calls, Total: 4

Package Total Routines
Clinical Reminders 4 PXRMEXPD    PXRMOCR    PXRMP22I    PXRMREV    

Pointed To By FileMan Files, Total: 2

Package Total FileMan Files
Order Entry Results Reporting 1 ORDER CHECK INSTANCES(#100.05)[86]    
PCE Patient Care Encounter 1 REMINDER ORDER CHECK ITEMS GROUP(#801)[#801.04(.01)]    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
Clinical Reminders 3 REMINDER DEFINITION(#811.9)[30]    REMINDER TERM(#811.5)[20]    REMINDER SPONSOR(#811.6)[101]    
Kernel 1 NEW PERSON(#200)[#801.13(1)]    

Fields, Total: 18

Field # Name Loc Type Details
.01 RULE NAME 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:($L(X)>64)!($L(X)<3)!'(X'?1P.E)!('$$VNAME^PXRMINTR(.X)) X
  • LAST EDITED:  JAN 31, 2012
  • HELP-PROMPT:  Answer must be 3-64 characters in length.
  • DESCRIPTION:  This is the internal name of the rule. The name may not start with "VA-", as that is reserved for national reminder components. The name you enter will be made upper case.
  • DELETE TEST:  1,0)= I $$RULEIUSE^PXRMORED(DA)=0 D EN^DDIOL($C(7)_"RULE IN USE - CANNOT BE DELETED")
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • FIELD INDEX:  B (#1042) REGULAR IR LOOKUP & SORTING
    Unique for:  Key A (#121), File #801.1
    Short Descr:  This is the "B" cross-reference redone as a new style cross-reference.
    Set Logic:  S ^PXD(801.1,"B",$E(X,1,64),DA)=""
    Kill Logic:  K ^PXD(801.1,"B",$E(X,1,64),DA)
    Whole Kill:  K ^PXD(801.1,"B")
    X(1):  RULE NAME  (801.1,.01)  (Subscr 1)  (Len 64)  (forwards)
1 DISPLAY NAME 0;2 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>64!($L(X)<3) X
  • LAST EDITED:  NOV 01, 2011
  • HELP-PROMPT:  Answer must be 3-64 characters in length.
  • DESCRIPTION:  
    This is the name that will display in the CPRS Order Check Window.
2 STATUS 0;3 SET
************************REQUIRED FIELD************************
  • 'I' FOR INACTIVE;
  • 'P' FOR PRODUCTION;
  • 'T' FOR TESTING;

  • LAST EDITED:  MAY 01, 2012
  • HELP-PROMPT:  Select if the rule is inactive, for production use only, or testing use only.
  • DESCRIPTION:  This field determines if the rule is inactive, set for production use, or for testing use. If the rule is set to INACTIVE, then the rule will not be evaluated for the orderable item list. The value should be set to TESTING
    when a rule is first created so the creator of the rule can test it before turning it on for the entire facility. To turn it on for the entire facility, this field must be set to PRODUCTION.
4 SEVERITY 0;5 SET
************************REQUIRED FIELD************************
  • '3' FOR LOW;
  • '2' FOR MEDIUM;
  • '1' FOR HIGH;

  • LAST EDITED:  JAN 31, 2012
  • HELP-PROMPT:  What's the severity of the order check?
  • DESCRIPTION:  Enter a severity for the order check. If multiple reminder order checks are run against an orderable item, the results are displayed by order of severity, from high to low. Also, a severity of HIGH requires the user to
    enter an override reason when signing the order.
10 RULE DESCRIPTION 1;0 WORD-PROCESSING #801.11

  • DESCRIPTION:  This is the description of what the creator is trying to accomplish with this particular rule.
20 REMINDER TERM 2;1 POINTER TO REMINDER TERM FILE (#811.5) REMINDER TERM(#811.5)

  • LAST EDITED:  JAN 27, 2012
  • HELP-PROMPT:  Select the reminder term.
  • DESCRIPTION:  If a reminder term is defined in this field when an order is placed in CPRS, the reminder term will be evaluated. The reminder term evaluation will return either a TRUE or FALSE value. The value returned by the reminder
    term evaluation is used in conjunction with the TERM EVALUATION STATUS field.
  • FIELD INDEX:  AT (#1041) MUMPS IR ACTION
    Short Descr:  Delete the associated field when the term is deleted.
    Description:  This cross-reference will delete the value in the TERM EVALUATION STATUS field (#21).
    Set Logic:  Q
    Kill Logic:  D TDEL^PXRMOCR(DA,X1,X2)
    X(1):  REMINDER TERM  (801.1,20)  (forwards)
  • FIELD INDEX:  T (#1044) REGULAR IR LOOKUP & SORTING
    Short Descr:  Quick look up of terms in the rules
    Set Logic:  S ^PXD(801.1,"T",X,DA)=""
    Kill Logic:  K ^PXD(801.1,"T",X,DA)
    Whole Kill:  K ^PXD(801.1,"T")
    X(1):  REMINDER TERM  (801.1,20)  (Subscr 1)  (forwards)
21 TERM EVALUATION STATUS 2;2 SET
  • '1' FOR TRUE;
  • '0' FOR FALSE;

  • LAST EDITED:  JAN 31, 2012
  • HELP-PROMPT:  Enter the value for the reminder term results that should trigger an order check.
  • DESCRIPTION:  This field is used in conjunction with the REMINDER TERM field; it will be used to determine if the rule should appear in the order check window in CPRS. When the reminder term is defined in field #20, the TRUE/FALSE
    result of the term evaluation will be compared to the value defined in this field. If the value matches, the text defined in the Order Check Text field will appear in the order check window with the DISPLAY NAME.
  • TECHNICAL DESCR:  This field is deleted by the AT index of the REMINDER TERM (#20) field.
30 REMINDER DEFINITION 3;1 POINTER TO REMINDER DEFINITION FILE (#811.9) REMINDER DEFINITION(#811.9)

  • INPUT TRANSFORM:  S DIC("S")="I $P($G(^(100)),U,4)[""O""" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  JAN 27, 2012
  • HELP-PROMPT:  Select the reminder definition.
  • DESCRIPTION:  If a reminder definition is defined in this field when an order is placed in CPRS, the reminder definition will be evaluated. The reminder definition evaluation will return an evaluation status. The value of the status
    returned by the reminder definition evaluation is used in conjunction with the DEFINITION EVALUATION STATUS field.
  • SCREEN:  S DIC("S")="I $P($G(^(100)),U,4)[""O"""
  • EXPLANATION:  This screen only allows selection of reminder definitions with a USAGE value of Order Check.
  • FIELD INDEX:  AD (#1040) MUMPS IR ACTION
    Short Descr:  Delete the associated fields when the definition is deleted.
    Description:  This cross-reference will delete the values in the DEFINITION EVALUATION STATUS (#31) and OUTPUT TEXT (#32) fields.
    Set Logic:  Q
    Kill Logic:  D DDEL^PXRMOCR(DA,X1,X2)
    X(1):  REMINDER DEFINITION  (801.1,30)  (forwards)
  • FIELD INDEX:  R (#1043) REGULAR IR LOOKUP & SORTING
    Short Descr:  Quick lookup of reminder definition in the rules.
    Set Logic:  S ^PXD(801.1,"R",X,DA)=""
    Kill Logic:  K ^PXD(801.1,"R",X,DA)
    Whole Kill:  K ^PXD(801.1,"R")
    X(1):  REMINDER DEFINITION  (801.1,30)  (Subscr 1)  (forwards)
31 DEFINITION EVALUATION STATUS 3;2 SET
  • 'D' FOR DUE;
  • 'A' FOR APPLICABLE;
  • 'N' FOR N/A;

  • LAST EDITED:  JAN 31, 2012
  • HELP-PROMPT:  Enter the value for the reminder definition evaluation status that should trigger an order check.
  • DESCRIPTION:  This field is used in conjunction with the REMINDER DEFINITION field. It will be used to determine if the rule should appear in the order check window in CPRS. When a reminder definition is defined in field #30, the status
    value from the definition evaluation will be compared to the value defined in this field. If the evaluation status value matches then the rule will appear in the order check window. This field can have one of three
    possible values: DUE, APPLICABLE, and N/A.
    DUE includes the status of DUE NOW and DUE SOON.
    APPLICABLE includes the status of DUE NOW, DUE SOON, and RESOLVED.
    N/A includes the status of N/A and NEVER.
  • TECHNICAL DESCR:  This field is deleted by the AD index on the REMINDER DEFINITION (#30) field.
32 OUTPUT TEXT 3;3 SET
  • 'O' FOR ORDER CHECK TEXT ONLY;
  • 'D' FOR DEFINITION TEXT ONLY;
  • 'B' FOR BOTH ORDER CHECK AND DEFINITION TEXT;

  • LAST EDITED:  JAN 31, 2012
  • HELP-PROMPT:  Select what text should appear in the order check window.
  • DESCRIPTION:  This field controls which text will appear in the order check window.
    ORDER CHECK TEXT ONLY will display the text defined in the ORDER CHECK TEXT field in the Order Check Window.
    DEFINITION TEXT ONLY will display the text returned from the reminder evaluation. This text is similar to the Clinical Maintenance Output, but without the status line and the frequency line in the output.
    BOTH ORDER CHECK and DEFINITION TEXT: This value will display both the text defined in the ORDER CHECK TEXT field and the text returned by the reminder evaluation, without the Status Line and the Frequency Line. The text
    defined in the ORDER CHECK TEXT field will appear first in the output.
  • TECHNICAL DESCR:  This field is deleted by the AD index on the REMINDER DEFINITION (#30) field.
40 ORDER CHECK TEXT 4;0 WORD-PROCESSING #801.12

  • DESCRIPTION:  This field stores the text that should display in the Order Check Window. This text will only appear if the rule is true and the evaluation is done for a reminder term or if the evaluation is done for a reminder
    definition and the value of the OUTPUT TEXT field is not DEFINITION TEXT ONLY.
45 NO. OF ORDER CHECK TEXT LINES 5;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>5!($L(X)<1) X
  • LAST EDITED:  OCT 16, 2011
  • HELP-PROMPT:  Answer must be 1-5 characters in length.
  • DESCRIPTION:  
    This is the number of lines in the ORDER CHECK TEXT. If the number ends with "T" then the text contains a TIU object. This field is set automatically during the rule edit and should never be edited by hand.
46 NO. OF FORMATTED LINES 5;2 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  NOV 21, 2011
  • HELP-PROMPT:  Type a number between 0 and 99, 0 decimal digits.
  • DESCRIPTION:  This is the number of formatted Order Check Text lines, it is set automatically. If the Order Check Text contains a TIU Object it cannot be formatted and this will be set to 0.
47 FORMATTED ORDER CHECK TEXT 6;0 WORD-PROCESSING #801.147

  • DESCRIPTION:  This word-processing field contains the formatted Order Check Text. This speeds up order checking because the text does not have to be formatted every time. This field is set automatically by the software.
100 CLASS 100;1 SET
************************REQUIRED FIELD************************
  • 'L' FOR LOCAL;
  • 'V' FOR VISN;
  • 'N' FOR NATIONAL;

  • INPUT TRANSFORM:  K:'$$VCLASS^PXRMINTR(X) X
  • LAST EDITED:  JAN 27, 2012
  • HELP-PROMPT:  Enter a class.
  • DESCRIPTION:  This is the CLASS of the Orderable Item Group.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
101 SPONSOR 100;2 POINTER TO REMINDER SPONSOR FILE (#811.6) REMINDER SPONSOR(#811.6)

  • LAST EDITED:  OCT 16, 2011
  • HELP-PROMPT:  Select the sponsor.
  • DESCRIPTION:  
    This is the organization or group that sponsors this orderable item group.
102 REVIEW DATE 100;3 DATE

  • INPUT TRANSFORM:  S %DT="E" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  OCT 16, 2011
  • HELP-PROMPT:  Enter the date the order check group should be reviewed.
  • DESCRIPTION:  
    The REVIEW DATE is used to determine when the orderable item group should be reviewed to verify that it is current with the latest standards and guidelines.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
110 EDIT HISTORY 110;0 DATE Multiple #801.13 801.13

  • DESCRIPTION:  This multiple is used to record a history of changes made to the order check rule.

Found Entries, Total: 2

RULE NAME: VA-TERATOGENIC MEDICATIONS ORDER CHECK (CAT D) RULE    RULE NAME: VA-TERATOGENIC MEDICATIONS ORDER CHECK (CAT X) RULE    

External References

Name Field # of Occurrence
^%DT 102+1
EN^DDIOL .01DEL1+1
^DIC 30+1
$$VNAME^PXRMINTR .01+1
DDEL^PXRMOCR IXADKL+1
TDEL^PXRMOCR IXATKL+1
$$RULEIUSE^PXRMORED .01DEL1+1

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^PXD(801.1 - [#801.1] IXBSL+1*, IXBKL+1!, IXBKEIC+1!, IXRSL+1*, IXRKL+1!, IXRKEIC+1!, IXTSL+1*, IXTKL+1!, IXTKEIC+1!

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> %DT 102+1*
>> DA IXADKL+1, IXATKL+1, IXBSL+1, IXBKL+1, IXRSL+1, IXRKL+1, IXTSL+1, IXTKL+1, .01DEL1+1
DIC 30+1!*
DIC("S" 30+1*, 30SCR+1*
>> DIE 30+1
X IXBSL+1, IXBKL+1, IXRSL+1, IXRKL+1, IXTSL+1, IXTKL+1, .01+1!, 1+1!, 30+1*!, 45+1!
, 46+1!, 102+1*!
>> X1 IXADKL+1, IXATKL+1
>> X2 IXADKL+1, IXATKL+1
>> Y 30+1, 102+1
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables |  All