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: ^PXRM(810.2

Package: Clinical Reminders

Global: ^PXRM(810.2


Information

FileMan FileNo FileMan Filename Package
810.2 REMINDER EXTRACT DEFINITION Clinical Reminders

Description

Directly Accessed By Routines, Total: 18

Package Total Routines
Clinical Reminders 18 EDIT HISTORY    EXTRACT RULES    PXRMAPI1    PXRMEPED    PXRMETCO    PXRMETH    PXRMETHL    PXRMETM
PXRMETX    PXRMETXR    PXRMEUT    PXRMEXPS    PXRMLPP    PXRMP4I1    PXRMRULE    PXRMV2I
REMINDERS/COUNTING RULES    ^PXRM(810.2    

Accessed By FileMan Db Calls, Total: 4

Package Total Routines
Clinical Reminders 4 PXRMEPED    PXRMETX    PXRMEXPD    PXRMV2I    

Pointed To By FileMan Files, Total: 2

Package Total FileMan Files
Clinical Reminders 2 REMINDER PATIENT LIST(#810.5)[.05]    REMINDER EXTRACT SUMMARY(#810.3)[1]    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
Clinical Reminders 3 REMINDER DEFINITION(#811.9)[#810.22(1)]    REMINDER LIST RULE(#810.4)[#810.21(.02)]    REMINDER EXTRACT COUNTING RULE(#810.7)[#810.22(2)]    
Kernel 1 NEW PERSON(#200)[#810.24(1)]    

Fields, Total: 11

Field # Name Loc Type Details
.01 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:  MAY 29, 2009
  • HELP-PROMPT:  Answer must be 3-64 characters in length.
  • DESCRIPTION:  The NAME of the extract (VA-IHD QUERI, VA-MH QUERI etc.). Extracts for national rollup are prefixed with 'VA-'.
  • TECHNICAL DESCR:  The national extract definitions (VA-IHD QUERI, VA-MH QUERI) in this file are used in the rollup of compliance data to the Austin Automation Center (AAC).
    Extract runs transmit compliance totals as HL7 format messages but also store run totals in the REMINDER EXTRACT SUMMARY file #810.3 and extract patient lists in the REMINDER PATIENT
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • FIELD INDEX:  B (#739) REGULAR IR LOOKUP & SORTING
    Unique for: Key A (#18), File #810.2
    Short Descr: B Index
    Description: New-style B index.
    Set Logic: S ^PXRM(810.2,"B",$E(X,1,64),DA)=""
    Kill Logic: K ^PXRM(810.2,"B",$E(X,1,64),DA)
    Whole Kill: K ^PXRM(810.2,"B")
    X(1): NAME (810.2,.01) (Subscr 1) (Len 64) (forwards)
.02 TYPE OF TOTALS 0;2 SET
************************REQUIRED FIELD************************
  • 'CT' FOR COMPLIANCE TOTALS ONLY;
  • 'CF' FOR COMPLIANCE AND FINDING TOTALS;

  • LAST EDITED:  MAY 04, 2006
  • DESCRIPTION:  This is the type of extract totals that will be reported by the extract.
    Compliance Totals Only are similar to Reminder Due Summary reports, with the difference being multiple patient lists are used to evaluate multiple reminders, resulting in compliance totals based on the reminder status
    (applicable, not applicable (N/A), due, and not due).
    Example: PATIENT LIST 1
    REMINDER 1 COMPLIANCE TOTALS for Applicable, N/A, Due, Not Due
    REMINDER 2 COMPLIANCE TOTALS for Applicable, N/A, Due, Not Due
    PATIENT LIST 2
    REMINDER 1 COMPLIANCE TOTALS for Applicable, N/A, Due, Not Due
    REMINDER 3 COMPLIANCE TOTALS for Applicable, N/A, Due, Not Due
    Compliance and Finding Totals will additionally report on totals for findings found during reminder evaluation. Counting rules indicate how to count findings defined in a counting group. Counting Groups often group patient
    cohort findings, resolution findings and information findings in different groups. The finding counts are totaled based on the reminder's status (N/A, applicable, due, not due).
    Example: PATIENT LIST 1
    REMINDER 1 COMPLIANCE TOTALS for Applicable, N/A, Due, Not Due
    GROUP 1 (most recent finding counts each finding found in the group, regardless of when it was entered into VistA)
    FINDING 1 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 2 TOTALS for Applicable, N/A, Due, Not Due
    GROUP 2 (most recent finding patient counts one finding from the group for each patient, regardless of when it was entered in VistA)
    FINDING 1 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 2 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 3 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 4 TOTALS for Applicable, N/A, Due, Not Due
    GROUP 3 (utilitzation counts how many of the findings were entered during the reporting period)
    FINDING 3 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 4 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 5 TOTALS for Applicable, N/A, Due, Not Due
    REMINDER 2 COMPLIANCE TOTALS for Applicable, N/A, Due, Not Due
    GROUP 4 (most recent finding: counts each finding found in the group, regardless of when it was entered into VistA)
    FINDING 10 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 11 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 12 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 13 TOTALS for Applicable, N/A, Due, Not Due
    GROUP 5 (most recent finding patient: counts one finding from the group for each patient, regardless of when it was entered in VistA)
    FINDING 9 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 8 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 7 TOTALS for Applicable, N/A, Due, Not Due
    GROUP 6 (utilization: counts how many of the findings were entered during the reporting period)
    FINDING 11 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 12 TOTALS for Applicable, N/A, Due, Not Due
    PATIENT LIST 2
    REMINDER 1 COMPLIANCE TOTALS for Applicable, N/A, Due, Not Due
    GROUP 1 (utilization counts: how many of the findings were entered during the reporting period)
    FINDING 1 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 2 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 3 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 4 TOTALS for Applicable, N/A, Due, Not Due
    FINDING 5 TOTALS for Applicable, N/A, Due, Not Due
  • TECHNICAL DESCR:  
.03 DESCRIPTION 1;0 WORD-PROCESSING #810.23

  • DESCRIPTION:  
1 REPORT FREQUENCY 0;3 SET
************************REQUIRED FIELD************************
  • 'Q' FOR QUARTERLY;
  • 'M' FOR MONTHLY;
  • 'Y' FOR YEARLY;

  • LAST EDITED:  MAY 04, 2006
  • HELP-PROMPT:  Enter the report frequency.
  • DESCRIPTION:  This is the frequency of the extract run. The frequency may be monthly, quarterly, yearly or by financial year.
2 LAST REPORTING PERIOD/YEAR 0;4 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>8!($L(X)<4) X
  • LAST EDITED:  MAY 04, 2006
  • HELP-PROMPT:  Enter the period/year of the last extract run.
  • DESCRIPTION:  This is the date range of the last extract run. The format is period/year, e.g. Q1/2002 denotes first quarter of 2002.
3 LAST RUN DATE 0;5 DATE

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  APR 22, 2002
  • HELP-PROMPT:  Enter a valid date and time.
  • DESCRIPTION:  
    This is the date and time the latest extract was run.
4 NEXT REPORTING PERIOD/YEAR 0;6 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>8!($L(X)<4) X
  • LAST EDITED:  MAY 04, 2006
  • HELP-PROMPT:  Enter period/year of next extract run.
  • DESCRIPTION:  This is the date range of the next extract to be run. The format is period/year, e.g. Q1/2002 denotes first quarter of 2002..
    This field is updated automatically on the successful completion of each extract run.
5 NEXT RUN DATE 0;7 DATE

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:DT>X X
  • LAST EDITED:  MAY 04, 2006
  • HELP-PROMPT:  TYPE A DATE NOT EARLIER THAN CURRENT DATE.
  • DESCRIPTION:  Date of the next scheduled extract run. This field is only set for extracts that are scheduled to run as an option.
    Example: the two national extracts that are being released with 2.0, VA-IHD QUERI and VA-MH QUERI, are being released as options (PXRM EXTRACT VA-IHD QUERI and PXRM EXTRACT VA-MH QUERI) that sites will need to schedule
    using TaskMan. When the extract is done with processing, the extract code will determine the next run date and add that value to this field.
10 EXTRACT RULES 10;0 Multiple #810.21 810.21

  • LAST EDITED:  MAY 16, 2002
  • DESCRIPTION:  This multiple contains the sequential list of extract criteria: - list rule sets used by this extract to build
    patient lists - reminders that should be run against a
    patient list - counting rules for how findings should be
    counted.
  • IDENTIFIED BY:  LIST RULE SET(#.02)[R]
  • PRIMARY KEY:  A (#19)
    Uniqueness Index: B (#740)
    File, Field: 1) EXTRACT SEQUENCE (810.21,.01)
  • INDEXED BY:  EXTRACT SEQUENCE (B)
100 CLASS 100;1 SET
************************REQUIRED FIELD************************
  • 'N' FOR NATIONAL;
  • 'V' FOR VISN;
  • 'L' FOR LOCAL;

  • LAST EDITED:  MAY 04, 2006
  • HELP-PROMPT:  Enter the class.
  • DESCRIPTION:  This is the CLASS of the extract definition. National extract definitions cannot be edited.
110 EDIT HISTORY 110;0 DATE Multiple #810.24 810.24

Found Entries, Total: 3

NAME: VA-IHD QUERI    NAME: VA-MH QUERI    NAME: VA-OEF/OIF MONITOR    

External References

Name Field # of Occurrence
^%DT 3+1, 5+1
$$VNAME^PXRMINTR .01+1

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^PXRM(810.2 - [#810.2] IXBSL+1*, IXBKL+1!, IXBKEIC+1!

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> %DT 3+1*, 5+1*
>> DA IXBSL+1, IXBKL+1
DT 5+1
X IXBSL+1, IXBKL+1, .01+1!, 2+1!, 3+1*!, 4+1!, 5+1*!
>> Y 3+1, 5+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