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 |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables  | All
Print Page as PDF
Global: ^PXRM(810.4

Package: Clinical Reminders

Global: ^PXRM(810.4


Information

FileMan FileNo FileMan Filename Package
810.4 REMINDER LIST RULE Clinical Reminders

Description

Directly Accessed By Routines, Total: 21

Package Total Routines
Clinical Reminders 19 PXRMEPM    PXRMEUT1    ^PXRM(810.4    EDIT HISTORY    EXTRACT RULES    PXRM EDIT RULE SET    PXRMDESCAPI    PXRMEUT
PXRMEXPS    PXRMFRPT    PXRMGEVA    PXRMLCR    PXRMLPP    PXRMLRED    PXRMLREX    PXRMLRM
PXRMP6I    PXRMRULE    SEQUENCE    
Order Entry Results Reporting 2 ORLPREM    ORLPREML    

Accessed By FileMan Db Calls, Total: 4

Package Total Routines
Clinical Reminders 4 PXRMEXPD    PXRMEXSP    PXRMLRED    PXRMLREX    

Pointed To By FileMan Files, Total: 6

Package Total FileMan Files
Clinical Reminders 3 REMINDER EXTRACT DEFINITION(#810.2)[#810.21(.02)]    REMINDER LIST RULE(#810.4)[#810.41(.02)]    REMINDER PATIENT LIST(#810.5)[.06]    
Enterprise Health Management Platform 2 HMP PANEL(#800001)[.01]    HMP ROSTER(#800001.2)[#800001.21(.02)]    
Order Entry Results Reporting 1 OE/RR LIST(#100.21)[12.2]    

Pointer To FileMan Files, Total: 5

Package Total FileMan Files
Clinical Reminders 4 REMINDER DEFINITION(#811.9)[9]    REMINDER LIST RULE(#810.4)[#810.41(.02)]    REMINDER TERM(#811.5)[1]    REMINDER PATIENT LIST(#810.5)[4]    
Kernel 1 NEW PERSON(#200)[#810.42(1)]    

Fields, Total: 12

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

  • INPUT TRANSFORM:  K:$L(X)>96!($L(X)<3)!'(X'?1P.E)!('$$VNAME^PXRMINTR(.X)) X
  • LAST EDITED:  JUN 03, 2009
  • HELP-PROMPT:  Answer must be 3-96 characters in length
  • DESCRIPTION:  This is the name of the list rule.
    National list rules are prefixed VA- and class national.
  • DELETE TEST:  1,0)= I +$G(PXRMEXCH)=0,$D(^PXRMD(810.4,"AD",DA)) D EN^DDIOL($C(7)_"IN USE - CANNOT BE DELETED")
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • FIELD INDEX:  B (#741) REGULAR IR LOOKUP & SORTING
    Unique for: Key A (#22), File #810.4
    Short Descr: B Index
    Set Logic: S ^PXRM(810.4,"B",$E(X,1,96),DA)=""
    Kill Logic: K ^PXRM(810.4,"B",$E(X,1,96),DA)
    Whole Kill: K ^PXRM(810.4,"B")
    X(1): NAME (810.4,.01) (Subscr 1) (Len 96) (forwards)
.02 SHORT DESCRIPTION 0;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>64!($L(X)<3) X
  • LAST EDITED:  OCT 10, 2002
  • HELP-PROMPT:  Answer must be 3-64 characters in length.
  • DESCRIPTION:  
    This is a short description of the list rule.
.03 TYPE 0;3 SET
************************REQUIRED FIELD************************
  • '1' FOR FINDING RULE;
  • '3' FOR RULE SET;
  • '5' FOR PATIENT LIST;
  • '2' FOR REMINDER RULE;

  • LAST EDITED:  NOV 29, 2004
  • DESCRIPTION:  
    There are three types of rules in the file. Patient List Rules define an existing patient list. Finding Rules define reminder terms. Rule Sets contain both Finding and Patient List rules.
1 REMINDER TERM 0;7 POINTER TO REMINDER TERM FILE (#811.5) REMINDER TERM(#811.5)

  • LAST EDITED:  OCT 10, 2002
  • DESCRIPTION:  
    Finding rules (type 1) use a reminder term (#811.5) to select patients via the reminder package indexes.
2 LIST RULE BEGINNING DATE/TIME 0;4 FREE TEXT

  • INPUT TRANSFORM:  K:(($L(X)<1)!($L(X)>20)!('$$DATECHK^PXRMRUL1(X))) X
  • LAST EDITED:  MAY 04, 2006
  • HELP-PROMPT:  Enter an exact date, symbolic date, or 0 (zero) for no beginning date. Symbolic dates can use "T" to represent the build end date or "BDT" for build beginning date.
  • DESCRIPTION:  Enter an exact date, symbolic date, or 0 (zero) for no beginning date. Symbolic dates can use "T" to represent the build end date or "BDT" for build beginning date.
    This field is the beginning date/time (BDT) to use when searching for findings that match a List Finding Rule. In order for patient data to meet the List Finding Rule criteria, the findings must have been documented on or
    after the BDT.
    Reminder Rules and Patient List Rules do not use the Beginning date/time field.
    The BDT defined for a finding rule will be overridden if the term in the finding rule has a mapped finding with a BDT or Ending Date/Time (EDT).
    The rules for overriding date ranges is represented by the following equation, where "<" should be interpreted as "is overridden by":
    Build < rule set sequence < list rule < term's finding
    If the BDT and EDT are not defined on the list rule set sequence, nor the list finding rule, nor the Reminder Term's mapped finding, then the patient list tools will use the List Build's date range to find a match on
    findings. The List Build date range is the date range specified by the user when the list build action is selected. The list build date range is the Extract reporting period if an extract is being run.
    If no date range limits should be used to match findings for this finding rule, the finding rule needs to be defined with a zero in the BDT or EDT fields, or both. The term referenced in the list rule should not have BDT
    and EDT fields defined. If zero is defined in the BDT, and the EDT is left blank, the list build tools will assume both BDT and EDT should not have date range limits, and vice versa if EDT has the 0 and the BDT is blank.
    The use of "T" in the finding rule BDT field will always represent the ending date/time specified for the list build process or the extract reporting period, depending on whether a reminder patient list or extract option
    is being used to build the list. For example, T-1Y is one year prior to the list build's ending date/time.
    "BDT" may also be used in the BDT or EDT fields and represents the beginning date/time specified by the user processing the list build action. For example, BDT-5Y creates a beginning date for the list rule that is five
    years prior to the list build's beginning date/time.
    A fixed date may be defined in the BDT (e.g. 09/11/02).
    If the beginning date/time is later than the ending date/time, then no finding matches will be found.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
3 LIST RULE ENDING DATE/TIME 0;5 FREE TEXT

  • INPUT TRANSFORM:  K:(($L(X)<1)!($L(X)>20)!('$$DATECHK^PXRMRUL1(X))) X
  • LAST EDITED:  MAY 26, 2006
  • HELP-PROMPT:  Enter an exact date, symbolic date, or 0 (zero) for no ending date. Symbolic dates can use "T" to represent the build end date or "BDT" for build beginning date.
  • DESCRIPTION:  Enter an exact date, symbolic date, or 0 (zero) for no ending date. Symbolic dates can use "T" to represent the build end date, or "BDT" for build beginning date.
    This field is the ending date/time to use when searching for findings that match this list rule criteria. Findings must have been documented before the ending date/time. If no time is included, 11:59PM is assumed to be the
    time.
    The rules for overriding date ranges is represented by the following equation, where "<" should be interpreted as "is overridden by":
    Build < rule set sequence < list rule < term's finding
    The Ending Date/Time (EDT) defined for this list rule will be overridden if the term in the list rule has a mapped finding with a Beginning Date/Time (BDT) or Ending Date/Time (EDT).
    If the BDT and EDT are not defined on the list rule, nor the rule set sequence, nor the Reminder Term's mapped finding, then the patient list tools will use the List Build date range to find a match on findings. The List
    Build date range is the date range specified by the user when the list build action is selected. The list build date range is the Extract reporting period if an extract is being run.
    If no date range limits should be used to match findings for this list rule, the list rule needs to be defined with a zero in the BDT or EDT fields, or both. The term referenced in the list rule should not have BDT and EDT
    fields defined. If zero is defined in the list rule BDT, and the EDT is left blank, the list build tools will assume both BDT and EDT should not have date range limits, and vice versa if EDT has the 0 and the BDT is blank.
    The use of "T" in the List rule EDT field will always represent the ending date/time specified for the list build process or the extract reporting period, depending on whether a reminder patient list or extract option is
    being used to build the list. T-1Y is one year prior to the list build's ending date/time.
    "BDT" may also be used in the BDT or EDT fields and represents the beginning date/time specified by the user processing the list build action. For example "BDT-5Y" in the list rule beginning date, and "BDT" in the list
    rule ending date will create a five year date range ending on the list build's beginning date/time.
    A fixed date may also be defined in the EDT (e.g. 09/11/02).
    If the ending date/time is earlier than the beginning date/time, then no finding matches will be found.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
4 USE EXISTING PT LIST 0;8 POINTER TO REMINDER PATIENT LIST FILE (#810.5) REMINDER PATIENT LIST(#810.5)

  • LAST EDITED:  MAY 26, 2006
  • HELP-PROMPT:  Select an existing reminder patient list from the Reminder Patient List file.
  • DESCRIPTION:  This field is used by Patient List rules to identify an existing patient list in the Reminder Patient List file. The existing patient list is used as the patient source to perform the ADD, SELECT, or REMOVE operation on
    the list rule. The existing patient list is used to modify the temporary patient list built during list build processing.
    For the ADD operation the patients in the source list will be
    added to the temporary patient list.
    For the SELECT operation, the patients in the source list will be
    compared to the temporary patient list. Patient's in the
    temporary list that are not in the source list will be removed
    from the temporary patient list.
    For the REMOVE operation, the patients in the source list, that
    match a patient in the temporary patient list will be removed
    from the temporary patient list.
    If the USE EXISTING PT LIST and USE EXTRACT PT LIST NAMED field
    are both defined in the list rule, the USE EXTRACT PT LIST NAMED
    will be used as the patient source for extract processing,
    and the USE EXISTING PT LIST will be used when the build
    processing is started from the Reminder Patient List option.
7 USE EXTRACT PT LIST NAMED 1;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>96!($L(X)<1) X
  • LAST EDITED:  MAY 26, 2006
  • HELP-PROMPT:  Enter the name of the extract patient list defined in the extract definition.
  • DESCRIPTION:  This is a free-text field that contains the name of the patient list to use when processing this list rule during an extract run. The patient list has not been created at the time the list rule is defined. In contrast, the
    USE EXISTING PT LIST field is used by patient list rule tools to reference a patient list already existing in the REMINDER PATIENT LIST file.
    The name specified in the USE EXTRACT PT LIST NAMED will contain 'yyyy' for year and 'pnn' for reporting period. The nn is either the month (01-12) or calendar quarter (01-04), and p is either M for monthly, Q for
    quarterly, or Y for yearly.
    When an extract is run for a particular reporting period, the extract tool will use the USE EXTRACT PT LIST NAMED to find the patient list matching the name and then use this patient list to create the starting temporary
    patient list. The starting temporary patient list will be modified by add, select, and delete operations defined in the remaining list rules defined in the rule set.
    The same extract patient list name is also named in the REMINDER EXTRACT DEFINITION file (#810.2). The extract definition is used to create the extract patient list during an extract run. The 'yyyy' and 'pnn' ensures the
    extract process for the reporting year and period consistently uses the appropriate extract patient list created for the reporting period.
    Example: The patient list 'VA-*IHD QUERI yyyy pnn PATIENTS WITH QUALIFYING VISIT' is created during 'VA-IHD QUERI' extract processing by a rule set defined in the extract definition. Then a subsequent rule set defined in
    the 'VA-IHD QUERI' extract definition references a REMINDER LIST RULE entry with the same extract patient list name in the USE EXTRACT PT LIST NAMED field. During the extract run, the named list will be used to find the
    patient list created during the extract run in process. This list is used with the ADD operation in the rule set to create the temporary patient list to process the remaining rules in the rule set. In this example, the
    temorary patient list is modified to include patients that have both a QUALIFYING VISIT and an ANCHOR visit, creating a new patient list, 'VA-*IHD QUERI yyyy nn PATIENTS WITH QUALIFYING AND ANCHOR VISIT'. The new patient
    list created by the rule set processing is defined in the extract definition.
9 REMINDER DEFINITION 0;10 POINTER TO REMINDER DEFINITION FILE (#811.9) REMINDER DEFINITION(#811.9)

  • INPUT TRANSFORM:  S DIC("S")="I $P($G(^(100)),U,4)[""L""" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  JAN 21, 2005
  • HELP-PROMPT:  Enter a Reminder Definition that can be used to build a patient list.
  • DESCRIPTION:  This is a pointer to the Reminder Definition file #811.9. Reminders used to build patient lists must have an "L" in their USAGE field.
  • SCREEN:  S DIC("S")="I $P($G(^(100)),U,4)[""L"""
  • EXPLANATION:  The Reminder Definition must have an "L" for patient list in its USAGE field.
30 SEQUENCE 30;0 Multiple #810.41 810.41

  • LAST EDITED:  AUG 11, 2003
  • IDENTIFIED BY:  LIST RULE(#.02)
  • PRIMARY KEY:  A (#23)
    Uniqueness Index: B (#742)
    File, Field: 1) SEQUENCE (810.41,.01)
  • INDEXED BY:  SEQUENCE (B)
100 CLASS 100;1 SET
************************REQUIRED FIELD************************
  • 'N' FOR NATIONAL;
  • 'V' FOR VISN;
  • 'L' FOR LOCAL;

  • LAST EDITED:  JUL 02, 2002
  • HELP-PROMPT:  Enter the class,
  • DESCRIPTION:  
    This is the CLASS of the rule. National rules cannot be edited.
110 EDIT HISTORY 110;0 DATE Multiple #810.42 810.42

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

Found Entries, Total: 23

NAME: VA-*IHD QUERI DIAGNOSIS    NAME: VA-*IHD QUERI AMI DIAGNOSIS WITHIN 60 DAYS    NAME: VA-*IHD QUERI QUALIFYING VISIT    NAME: VA-*IHD QUERI ANCHOR VISIT    NAME: VA-*IHD QUERI ASSOCIATE PRIMARY CARE STATION    NAME: VA-*IHD QUERI PTS WITH QUALIFY AND ANCHOR VISIT    NAME: VA-*IHD QUERI PTS WITH QUALIFY VISIT    NAME: VA-*MH QUERI QUALIFY PC VISIT    
NAME: VA-*MH QUERI QUALIFY MH VISIT    NAME: VA-*MH QUERI QUALIFYING PC VISIT    NAME: VA-*IHD QUERI 412 DIAGNOSIS    NAME: VA-*IHD QUERI 412 PTS WITH QUALIFY AND ANCHOR VISIT    NAME: VA-*IHD QUERI LIPID LOWERING MEDS    NAME: VA-*IHD QUERI PTS WITH QUALIFY AND ANCHOR VISIT ON LLA MEDS    NAME: VA-*IHD QUERI 412 PTS WITH QUALIFY AND ANCHOR VISIT ON LLA MEDS    NAME: VA-*IHD QUERI PATIENT LIST (QUALIFY AND ANCHOR)    
NAME: VA-*IHD QUERI 412 PATIENTS LIST    NAME: VA-*IHD QUERI PATIENT LIST (QUALIFY VISIT, NO ANCHOR)    NAME: VA-*MH QUERI QUALIFYING MH VISIT    NAME: VA-OEF/OIF PERIOD OF SERVICE    NAME: VA-OEF/OIF CLINIC VISIT 1Y    NAME: VA-OEF/OIF PERIOD OF SERVICE AND RECENT VISIT    NAME: VA-FR-DATE OF DEATH    

ICR, Total: 1

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #6762
  • Order Entry Results Reporting
    		•  NAME (.01).
    Access: Direct Global Read & w/Fileman

    External References

    Name Field # of Occurrence
    EN^DDIOL .01DEL1+1
    ^DIC 9+1
    $$VNAME^PXRMINTR .01+1
    $$DATECHK^PXRMRUL1 2+1, 3+1

    Global Variables Directly Accessed

    Name Line Occurrences  (* Changed,  ! Killed)
    ^PXRM(810.4 - [#810.4] IXBSL+1*, IXBKL+1!, IXBKEIC+1!
    ^PXRMD(810.4 .01DEL1+1

    Local Variables

    Legend:

    >> Not killed explicitly
    * Changed
    ! Killed
    ~ Newed

    Name Field # of Occurrence
    >> DA IXBSL+1, IXBKL+1, .01DEL1+1
    DIC ID.03+1, 9+1!*
    DIC("S" 9+1*, 9SCR+1*
    >> DIE 9+1
    >> PXRMEXCH .01DEL1+1
    X IXBSL+1, IXBKL+1, .01+1!, .02+1!, 2+1!, 3+1!, 7+1!, 9+1*!
    >> Y 9+1
    Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables  | All