STANDARD DATA DICTIONARY #811.4 -- REMINDER COMPUTED FINDINGS FILE 3/24/25 PAGE 1
STORED IN ^PXRMD(811.4, (79 ENTRIES) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 2.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
When none of the standard Clinical Reminder finding types will work, a computed finding can be created. There are two steps in
creating a computed finding. First a MUMPS routine must be written. Information about how to do this can be found in the Clinical
Reminders Manager Manual. The second step is to make an entry in this file, which contains a list of reminder computed findings.
There are four fields for each entry; they are:
NAME - this is the name of the computed finding. When adding a computed finding as finding to a reminder definition or term, it is
done using the name. For example, you would type CF.VA-BMI to add the exported VA-BMI computed finding to your reminder definition.
ROUTINE - this is the name of the MUMPS routine.
ENTRY - this is the entry point in the MUMPS routine.
PRINT NAME - this will be displayed on the Clinical Maintenance component as the name of the computed finding. If it is blank, then
NAME will be used.
TYPE - this is a set of codes that specifies what type of computed finding this is. "S" stands for single occurrence, "M" for
multiple occurrence, and "L" for list. If it is blank, single will be assumed.
This file contains a combination of nationally distributed and local entries. Nationally distributed entries have their name
prefixed with VA-. Local entry names cannot start with VA-.
IDENTIFIED BY: CLASS (#100)[R]
PRIMARY KEY: A (#117)
Uniqueness Index: B (#998)
File, Field: 1) NAME (811.4,.01)
POINTED TO BY: FINDING ITEM field (#.04) of the EXTRACT FINDINGS sub-field (#810.31) of the REMINDER EXTRACT SUMMARY File (#810.3)
FINDING ITEM field (#.01) of the LREPI FINDING TOTALS sub-field (#810.32) of the REMINDER EXTRACT SUMMARY File
(#810.3)
FINDING ITEM field (#.01) of the FINDINGS sub-field (#811.52) of the REMINDER TERM File (#811.5)
FINDING ITEM field (#.01) of the FINDINGS sub-field (#811.902) of the REMINDER DEFINITION File (#811.9)
INDEXED BY: NAME (B)
LAST MODIFIED: NOV 18,2023@18:56:12
811.4,.01 NAME 0;1 FREE TEXT (Required) (Key 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: This is the name of the computed finding and is the name the User will use when adding a computed
finding to a reminder definition or a term.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
FIELD INDEX: B (#998) REGULAR IR LOOKUP & SORTING
Unique for: Key A (#117), File #811.4
Short Descr: New style B cross-reference
Set Logic: S ^PXRMD(811.4,"B",$E(X,1,64),DA)=""
Kill Logic: K ^PXRMD(811.4,"B",$E(X,1,64),DA)
Whole Kill: K ^PXRMD(811.4,"B")
X(1): NAME (811.4,.01) (Subscr 1) (Len 64) (forwards)
811.4,.02 ROUTINE 0;2 FREE TEXT
INPUT TRANSFORM: K:$L(X)>16!($L(X)<3) X
MAXIMUM LENGTH: 16
LAST EDITED: MAY 11, 2022
HELP-PROMPT: Answer must be 3-16 characters in length.
DESCRIPTION: This is the name of an M routine that contains the code for the computed finding. The entry point
to use is specified in the ENTRY POINT field.
DELETE AUTHORITY: @
WRITE AUTHORITY: @
811.4,.03 ENTRY POINT 0;3 FREE TEXT
INPUT TRANSFORM: K:$L(X)>16!($L(X)<2) X
MAXIMUM LENGTH: 16
LAST EDITED: MAY 11, 2022
HELP-PROMPT: Answer must be 2-16 characters in length.
DESCRIPTION:
This is the entry point in the routine specified in the ROUTINE field.
DELETE AUTHORITY: @
WRITE AUTHORITY: @
811.4,.04 PRINT NAME 0;4 FREE TEXT
INPUT TRANSFORM: K:$L(X)>64!($L(X)<1) X
LAST EDITED: AUG 20, 2010
HELP-PROMPT: Answer must be 1-64 characters in length.
DESCRIPTION:
The PRINT NAME will be displayed in the Clinical Maintenance output for computed findings.
811.4,1 DESCRIPTION 1;0 WORD-PROCESSING #811.41
DESCRIPTION: This is the description of the computed finding. It should explain its purpose and how it is to be
used including what data is returned for use in a Condition.
LAST EDITED: APR 05, 2000
HELP-PROMPT: Enter a description for this computed finding.
811.4,5 TYPE 0;5 SET
'M' FOR MULTIPLE;
'L' FOR LIST;
'S' FOR SINGLE;
LAST EDITED: JAN 29, 2003
DESCRIPTION: This is the type of computed finding; the possible values are "S" for single, "M" for multiple, and
"L" for list. The default value is "S". For a detailed explanation of the computed finding types
see the Clinical Reminder Manager manual.
811.4,6 CF PARAMETER REQUIRED 0;6 SET
'0' FOR NO;
'1' FOR YES;
LAST EDITED: JUN 14, 2011
HELP-PROMPT: Enter 'YES' if the computed finding parameter must be defined for this computed finding to work.
DESCRIPTION: This field should be set to "YES" if the computed finding requires a value in the COMPUTED FINDING
PARAMETER (#6) field of the definition or term in order to function properly. It is used by the
integrity checker to determine whether or not to issue an error if the COMPUTED FINDING PARAMETER
is not defined.
The default is "NO".
811.4,100 CLASS 100;1 SET (Required)
'N' FOR NATIONAL;
'V' FOR VISN;
'L' FOR LOCAL;
INPUT TRANSFORM: K:'$$VCLASS^PXRMINTR(X) X
LAST EDITED: MAY 18, 2001
HELP-PROMPT: Enter the class.
DESCRIPTION: This is the class of computed finding. Possible values are "N" for national, "V" for VISN, and "L"
for local. National computed findings will be prefixed with VA- and cannot be edited. Local or
VISN entry names cannot start with VA-.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
811.4,101 SPONSOR 100;2 POINTER TO REMINDER SPONSOR FILE (#811.6)
LAST EDITED: APR 19, 2001
HELP-PROMPT: Enter the sponsor.
DESCRIPTION:
This is the organization or group that sponsors this computed finding.
811.4,102 REVIEW DATE 100;3 DATE
INPUT TRANSFORM: S %DT="E" D ^%DT S X=Y K:Y<1 X
LAST EDITED: APR 19, 2001
HELP-PROMPT: Enter the review date.
DESCRIPTION: The REVIEW DATE is used to determine when the computed finding should be reviewed to verify that it
is current with the latest standards and guidelines. You can find all computed findings whose
review date has passed using the Reminder Review Date report.
811.4,110 EDIT HISTORY 110;0 DATE Multiple #811.42
DESCRIPTION:
This multiple is used to record a history of changes made to the computed finding.
811.42,.01 EDIT DATE 0;1 DATE
INPUT TRANSFORM: S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
LAST EDITED: APR 19, 2001
DESCRIPTION: This is the date and time when editing was done. This field is set automatically and should not
be changed by the user.
CROSS-REFERENCE: 811.42^B
1)= S ^PXRMD(811.4,DA(1),110,"B",$E(X,1,30),DA)=""
2)= K ^PXRMD(811.4,DA(1),110,"B",$E(X,1,30),DA)
811.42,1 EDIT BY 0;2 POINTER TO NEW PERSON FILE (#200)
LAST EDITED: APR 19, 2001
DESCRIPTION: This is the person who did the editing. This field is set automatically and should not be changed
by the user.
811.42,2 EDIT COMMENTS 1;0 WORD-PROCESSING #811.422
LAST EDITED: APR 25, 2001
DESCRIPTION:
This word-processing field can be used to record the changes made during the editing session.
LAST EDITED: APR 25, 2001
HELP-PROMPT: Enter your edit comments.
FILES POINTED TO FIELDS
NEW PERSON (#200) EDIT HISTORY:EDIT BY (#1)
REMINDER SPONSOR (#811.6) SPONSOR (#101)
INPUT TEMPLATE(S):
PXRM EDIT REMINDER CF JAN 29, 2003@10:46 USER #0
Edit template for REMINDER COMPUTED FINDINGS.
PRINT TEMPLATE(S):
PXRM COMPUTED FINDING INQUIRY FEB 08, 2013@13:46 USER #0 REMINDER COMPUTED FINDINGS LIST
PXRM COMPUTED FINDING LIST JAN 29, 2003@11:07 USER #0 Computed Finding List
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):