Sub-Field: 811.902

Parent File	Name	Number	Package
REMINDER DEFINITION(#811.9)	FINDINGS	811.902	Clinical Reminders

Details

Field #	Name	Loc	Type	Details
.01	FINDING ITEM	0;1	VARIABLE POINTER	DRUG(#50) EDUCATION TOPICS(#9999999.09) EXAM(#9999999.15) HEALTH FACTORS(#9999999.64) IMMUNIZATION(#9999999.14) LABORATORY TEST(#60) MH TESTS AND SURVEYS(#601.71) ORDERABLE ITEMS(#101.43) RAD/NUC MED PROCEDURES(#71) REMINDER COMPUTED FINDINGS(#811.4) REMINDER TAXONOMY(#811.2) REMINDER TERM(#811.5) SKIN TEST(#9999999.28) VA DRUG CLASS(#50.605) VA GENERIC(#50.6) GMRV VITAL TYPE(#120.51) REMINDER LOCATION LIST(#810.9) LAST EDITED: `JAN 07, 2015` HELP-PROMPT: `Enter a finding item in the format: Prefix.Name` DESCRIPTION: `This field identifies the finding items included in the reminder definition.` `Hint: To add a second occurrence of a finding, enclose it in quotes, i.e., "Prefix.Name"` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` CROSS-REFERENCE: `811.902^B` `1)= S ^PXD(811.9,DA(1),20,"B",$E(X,1,30),DA)=""` `2)= K ^PXD(811.9,DA(1),20,"B",$E(X,1,30),DA)` `3)= Required Index for Variable Pointer` RECORD INDEXES: `AE (#1644), AENODE (#1645)`
1	MINIMUM AGE	0;2	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>200)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `NOV 07, 2003` HELP-PROMPT: `Enter the minimum age for the frequency associated with this finding.` DESCRIPTION: `This field specifies the minimum age for defining an age range associated with a frequency. Leave it blank if there is no minimum age.` RECORD INDEXES: `AF (#1646), AI (#1649)`
2	MAXIMUM AGE	0;3	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>200)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `NOV 07, 2003` HELP-PROMPT: `Enter the maximum age for the frequency associated with this finding.` DESCRIPTION: `This field specifies the maximum age for defining an age range associated with a frequency. Leave it blank if there is no maximum age.` RECORD INDEXES: `AF (#1646), AI (#1649)`
3	REMINDER FREQUENCY	0;4	FREE TEXT	INPUT TRANSFORM: `K:'$$VFREQ^PXRMINTR(.X) X` LAST EDITED: `JUN 17, 2011` HELP-PROMPT: `Enter an integer followed by H (hours), D (days), W (weeks), M (months), or Y (years)` DESCRIPTION: `If this finding is true (found) then use this frequency and the age range specified by the MINIMUM AGE and MAXIMUM AGE to override the baseline frequency age range set.` `It is input as nU where n is an integer between 0 and 9999 inclusive and U is a unit. Allowed units are H (hours) D (days), W (weeks), M (months), and Y (years). If a reminder is only to be given once in a lifetime use` `a frequency of 99Y. The special frequency of 0Y will make a reminder never due.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` RECORD INDEXES: `AF (#1646), AI (#1649)`
4	FOUND TEXT	1;0	WORD-PROCESSING #811.9024	DESCRIPTION: `This is the text that will be displayed in the Clinical Maintenance output if this finding is found (true).` `WRITE AUTHORITY: ^` LAST EDITED: `MAR 25, 1999` HELP-PROMPT: `Enter the found text.`
5	NOT FOUND TEXT	2;0	WORD-PROCESSING #811.9025	DESCRIPTION: `This is the text that will be displayed in the Clinical Maintenance output if the finding is not found (false).` `WRITE AUTHORITY: ^` LAST EDITED: `MAR 25, 1999` HELP-PROMPT: `Enter the not found text.`
6	RANK FREQUENCY	0;5	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X` LAST EDITED: `MAR 25, 1999` HELP-PROMPT: `Enter an optional rank from 1 to 999 or leave blank.` DESCRIPTION: `This field is used to rank the frequency and age range sets associated with a finding. If there is more than one true finding that can override the baseline frequency age range set, then the determination of which` `one to use is made based on the finding with the highest rank. Ranks can range from 1 to 999 with 1 being the highest rank.` `When the Rank field is blank (null) for all true findings that can override the baseline frequency age range set, then the frequency that will cause the reminder to be given most often will be used. For example, if` `finding 1 has a frequency of 6 months, and finding 2 has a frequency of 1 year, finding 1 will be used to override the baseline.`
7	USE IN RESOLUTION LOGIC	0;6	SET	LAST EDITED: `NOV 07, 2003` HELP-PROMPT: `Enter the logic operator to be used in the default Internal Resolution Logic.` DESCRIPTION: `This optional field is used to indicate that this finding item should be included as part of the resolution logic for this reminder. Note - if the CUSTOMIZED RESOLUTION LOGIC is defined then this field is ignored.` `Valid entries for the USE IN RESOLUTION LOGIC field are:` `EQUATES TO BOOLEAN` `OPERATOR VALUE OPERATOR LOGIC` `-------- ----- ------------------` `BLANK not included in Resolution Logic` `(Use @ to delete value)` `& AND &(Finding)` `! OR !(Finding)` `&' AND NOT &'(Finding)` `!' OR NOT !'(Finding)` `All finding items that have a value in this field are automatically combined to create the DEFAULT RESOLUTION LOGIC.` `After all findings have been evaluated, the finding item is replaced by its true or false value in the resolution logic and the resolution logic is evaluated. If the resolution logic evaluates to true, then the last` `resolution date is determined. The applicable frequency is added to the resolution date to determine when the reminder is next due. If the resolution logic evaluates to false, then reminder is due.` RECORD INDEXES: `AG (#1647), AI (#1649)`
8	USE IN PATIENT COHORT LOGIC	0;7	SET	LAST EDITED: `NOV 07, 2003` HELP-PROMPT: `Enter the logic operator to be used in the default Internal Patient Cohort Logic` DESCRIPTION: `This optional field is used to indicate that this finding item should be included as part of the Patient Cohort Logic for this reminder. Note - if the CUSTOMIZED COHORT LOGIC is defined then this field is ignored.` `Valid entries for the USE IN PATIENT COHORT LOGIC field are:` `EQUATES TO BOOLEAN` `OPERATOR VALUE OPERATOR LOGIC` `-------- ----- ------------------` `BLANK not included in Patient Cohort Logic` `(Use @ to delete value)` `& AND &(Finding)` `! OR !(Finding)` `&' AND NOT &'(Finding)` `!' OR NOT !'(Finding)` `All finding items that have a value in this field are automatically combined to create the DEFAULT COHORT LOGIC. The default logic string initially includes (SEX)&(AGE), regardless of whether the baseline specifies` `SEX and AGE criteria. Each finding item with a value in the Use In Patient Cohort Logic field is appended to the string by using the operator and finding item. For example, if finding item 2 had an operator for this` `field of "&" then the string would be (SEX)&(AGE)&FI(2).` `After all findings have been evaluated, the finding item is replaced by its true or false value in the cohort logic and the cohort logic is evaluated. If the cohort logic evaluates to true, then the reminder is` `applicable to the patient. If the cohort logic evaluates to false, then reminder is non-applicable or N/A.` RECORD INDEXES: `AH (#1648), AI (#1649)`
9	BEGINNING DATE/TIME	0;8	FREE TEXT	INPUT TRANSFORM: `S X=$$COTN^PXRMDATE(X) K:(($L(X)<1)!($L(X)>30)!('$$VDT^PXRMINTR(X))) X` LAST EDITED: `JAN 03, 2011` HELP-PROMPT: `Enter the Beginning Date/Time` DESCRIPTION: `This is the beginning date/time to search for the finding. When combined with the ENDING DATE/TIME, they define a date range in which to search for the finding.` `This can be entered in any of the acceptable FileMan date/time formats and abbreviations. See the FileMan Getting Started Manual to learn about acceptable FileMan date/time formats and abbreviations.` `In addition, you can use the abbreviations T-NY or NOW-NY,where N is an integer and Y stands for years. The date of another finding in the form FIEVAL(M,"DATE") or FIEVAL(M,N,"DATE") where M is the number of the` `finding and N is an occurrence may also be used. For example, FIEVAL(M,"DATE")-3M would set the Beginning Date/Time to the date of finding M minus three months. Note that when this form is used and finding M is false` `no Beginning Date/Time can be determined so this finding will be set to false.` `If this field is null, then the beginning date/time will correspond with the date/time of the oldest entry in the patient's record.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` RECORD INDEXES: `ADATE (#1643), AENODE (#1645)`
10	USE INACTIVE PROBLEMS	0;9	SET	LAST EDITED: `MAR 25, 1999` HELP-PROMPT: `Enter a 1 or YES if you want inactive problems used.` DESCRIPTION: `Normally only active problems from the Problem List will be used in the reminder evaluation. If USE INACTIVE PROBLEMS is set to YES then both active and inactive problems will be used. Note that this field applies` `only to taxonomy findings.`
11	WITHIN CATEGORY RANK	0;10	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `MAY 01, 2000` HELP-PROMPT: `Enter a number between 0 and 999.` DESCRIPTION: `This field applies only to health factors. In order to understand how it works, you need to understand how health factors work in the reminder evaluation process. If you are not clear about this, see the health` `factor section of the Clinical Reminder Manager Manual.` `The default behavior is to use only the most recent health factor within a category. A problem can arise if there are two or more health factors within a category and they both have the same date. (This can happen` `if both health factors are given during the same encounter). When the dates are the same, the health factor with the highest WITHIN CATEGORY RANK will be used. This is a numerical value like RANK FREQUENCY, with 1` `being the highest rank.` `If WITHIN CATEGORY RANK has the special value of 0, then the categorization of health factors will be ignored and the health factor will be treated as a distinct finding.`
12	ENDING DATE/TIME	0;11	FREE TEXT	INPUT TRANSFORM: `S X=$$COTN^PXRMDATE(X) K:(($L(X)<1)!($L(X)>30)!('$$VDT^PXRMINTR(X))) X` LAST EDITED: `JAN 03, 2011` HELP-PROMPT: `Enter the Ending Date/Time` DESCRIPTION: `This is the ending date/time to search for findings. When combined with the BEGINNING DATE/TIME they define a date range in which to search for the finding. The ENDING DATE/TIME must be after the BEGINNING DATE/TIME.` `This can be entered in any of the acceptable FileMan date/time formats and abbreviations. See the FileMan Getting Started Manual to learn about acceptable FileMan date/time formats and abbreviations.` `In addition, you can use the abbreviations T-NY or NOW-NY,where N is an integer and Y stands for years. The date of another finding in the form FIEVAL(M,"DATE") or FIEVAL(M,N,"DATE") where M is the number of the` `finding and N is an occurrence may also be used. For example, FIEVAL(M,"DATE")+3M would set the Ending Date/Time to the date of finding M plus three months. Note that when this form is used and finding M is false no` `Ending Date/Time can be determined so this finding will be set to false.` `If this field is null, then the ending date/time will be the end of day on the reminder evaluation date.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` RECORD INDEXES: `ADATE (#1643), AENODE (#1645)`
13	MH SCALE	0;12	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999999999999999)!(X<1)!('$$VSCALEF^PXRMMH(X)) X` LAST EDITED: `APR 30, 2007` HELP-PROMPT: `Enter the scale number.` DESCRIPTION: `This applies only to Mental Health Instrument findings. It sets the default scale, i.e., the value for V in the Condition.` EXECUTABLE HELP: `D SCHELPF^PXRMMH` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER`
14	CONDITION	3;1	FREE TEXT	INPUT TRANSFORM: `K:($L(X)<3)!($L(X)>225)!('$$VCOND^PXRMCOND(X)) X` LAST EDITED: `SEP 23, 2003` HELP-PROMPT: `Answer must be 3-225 characters in length.` DESCRIPTION: `The CONDITION must be written in M code based on the value returned from the patient results for the finding. Each type of finding has a specific field that provides the value available to use in the CONDITION logic.` `If the finding value is text, enclose the condition value in quotes (e.g., "positive"). If the finding value is numeric, do not use quotes (e.g., 3).` `An IF statement is used to evaluate the value. The value is always identified as V in the statement regardless of the type of finding. If the condition logic statement evaluates to true, the finding is considered as` `found (true); otherwise the finding is considered as not found (false).` `Relational operators that may be used include: = equals, < less than, > greater than, [ contains, ] follows and ? pattern matches. Logical operators may be used to check multiple values: & And, ! Or, ' Not.` `Typical examples of M code are as follows:` `I V=3 for Education Topic's Level of Understanding = 3` `I V="H" for Health Factor's Level/Severity="H"` `I ($P(V,"/",1)>140)&($P(V,"/",2)>90) for elevated blood pressure` `systolic and diastolic values` `I ($P(V,"/",1)>140)!($P(V,"/",2)>90) for elevated blood pressure` `systolic or diastolic values` `I V["BLACK" for VA-RACE computed finding where race contains BLACK` `Below is a brief summary for each finding type, the related field to use for the value, and examples:` `Finding type Field Value Used Example M Code` `Drug None` `Education Topic Level of understanding I V=3` `Exam Result I V="N"` `Health Factor Level/severity I V="H"` `Immunization Series I V="P"` `Laboratory Test Result Value I V>130` `Mental Health Instrument Raw score I V=1` `Orderable Item Status I V="complete"` `Radiology Procedure None` `Reminder Computed Finding Determined by programmer-See Manager Manual` `Reminder Taxonomy None` `Skin Test Result I V="N"` `VA Drug Class None` `VA Generic None` `Vital Measurement Rate I V>27` `For details about allowed CONDITIONS for each finding type, see the Clinical Reminders Manager Manual.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` FIELD INDEX: `ACOND (#1642) MUMPS IR ACTION` `Short Descr: Build the internal condition structure` `Set Logic: D SICOND^PXRMCOND(.X,.DA,811.9)` `Kill Logic: D KICOND^PXRMCOND(.X,.DA,811.9)` `X(1): CONDITION (811.902,14) (Subscr 1) (Len 30) (forwards)`
15	CONDITION CASE SENSITIVE	3;2	SET	LAST EDITED: `SEP 07, 2004` HELP-PROMPT: `Enter NO to make the condition case insensitive.` DESCRIPTION: `When CONDITION CASE SENSITIVE is NO, then the CONDITION will be evaluated without regard to case. The default is YES, so that CONDITION evaluation is case sensitive.` FIELD INDEX: `ACASE (#1641) MUMPS IR ACTION` `Short Descr: Reset internal condition whenever case sensitive field changes.` `Set Logic: D CASESEN^PXRMCOND(X,.DA,811.9)` `Kill Logic: D CASESEN^PXRMCOND(X,.DA,811.9)` `X(1): CONDITION CASE SENSITIVE (811.902,15) (Subscr 1) (forwards)`
16	RXTYPE	0;13	FREE TEXT	INPUT TRANSFORM: `S X=$$UP^XLFSTR(X) K:($L(X)>20)!($L(X)<1)!('$$VRXTYPE^PXRMRXTY(X)) X` LAST EDITED: `SEP 24, 2004` HELP-PROMPT: `Enter the RXTYPE string.` DESCRIPTION: `RXTYPE applies only to drug findings; it controls the search for patient medications. The possible values for RXTYPE are "I" for inpatient, "N" for non-VA meds, and "O" for outpatient. RXTYPE can be any combination` `of these such as "NO" which will search for non-VA meds and outpatient medications. If RXTYPE is blank it is equivalent to a value of "INO".` EXECUTABLE HELP: `D RXTYXHLP^PXRMRXTY` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` FIELD INDEX: `AWARNSL (#1650) MUMPS IR ACTION` `Short Descr: Warn the user to review the status list if RXTYPE field is changed.` `Set Logic: D WARN^PXRMSTA1` `Set Cond: S X=$S(X2'="":1,1:0)` `Kill Logic: D WARN^PXRMSTA1` `Kill Cond: S X=$S(X2="":1,1:0)` `X(1): RXTYPE (811.902,16) (Subscr 1) (forwards)`
17	OCCURRENCE COUNT	0;14	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>99)!(X<-99)!(X?.E1"."1N.N) X` LAST EDITED: `SEP 22, 2003` HELP-PROMPT: `Type a Number between -99 and 99, 0 Decimal Digits` DESCRIPTION: `This is the maximum number of occurrences of the finding in the date range to return. If the OCCURRENCE COUNT is input as a positive number, N, up to N of the most recent occurrences will be returned and the finding` `will take the value of the most recent occurrence. If the OCCURRENCE COUNT is input as a negative number then this behavior is reversed. Up to N of the oldest occurrences will be returned and the finding will take` `the value of the oldest occurrence in the list.`
18	USE STATUS/COND IN SEARCH	3;3	SET	LAST EDITED: `MAY 09, 2006` HELP-PROMPT: `Enter a "Yes" if you want the STATUS LIST and/or CONDITION used in the finding search.` DESCRIPTION: `Give this field a value of "YES" if you want the STATUS LIST and/or CONDITION applied to each result found in the date range for this finding. Only results that have a status on the list or for which the CONDITION is` `true will be retained. The maximum number to retain is specified by the OCCURRENCE COUNT.` `Note - if the finding has both a STATUS LIST and a CONDITION the status check will be made first; the CONDITION will be applied only if the finding passes the status check.`
21	STATUS LIST	5;0	Multiple #811.90221	811.90221 DESCRIPTION: `This field applies to finding types that have an associated status. When the search for patient findings is done only those findings that have a status on the list can be true. The allowable values depend on the` `finding type. If no statuses are specified then the default list for each finding type will be used. The default lists can be found in the Clinical Reminders Manager Manual.` `WRITE AUTHORITY: ^`
22	INTERNAL CONDITION	10;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>245!($L(X)<3) X` LAST EDITED: `SEP 15, 2003` HELP-PROMPT: `Do not edit this field.` DESCRIPTION: `This is the internal form of the condition. It is set automatically and should never be set by hand.`
23	V SUBSCRIPT LIST	11;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>245!($L(X)<1) X` LAST EDITED: `SEP 15, 2003` HELP-PROMPT: `Do not edit this field.` DESCRIPTION: `This is a list of V value subscripts used in the CONDITION. It is used when the CONDITION is not case sensitive. This should never be set by hand.`
24	NO. OF FOUND TEXT LINES	6;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>5!($L(X)<1) X` LAST EDITED: `OCT 17, 2003` HELP-PROMPT: `Do not edit this field.` DESCRIPTION: `This is the number of lines in the found text. If the number ends with "T" then the text contains TIU objects. This field is set automatically during reminder edit and should never be edited by hand.` `WRITE AUTHORITY: ^`
25	NO. NOT FOUND TEXT LINES	6;2	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>5!($L(X)<1) X` LAST EDITED: `OCT 17, 2003` HELP-PROMPT: `Do not edit this field.` DESCRIPTION: `This is the number of lines in the not found text. If the number ends with "T" then the text contains TIU objects. This field is set automatically during reminder edit and should never be edited by hand.` `WRITE AUTHORITY: ^`
26	COMPUTED FINDING PARAMETER	15;E1,245	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>245!($L(X)<1) X` LAST EDITED: `JUN 09, 2006` HELP-PROMPT: `Answer must be 1-245 characters in length.` DESCRIPTION: `This field is used to pass a parameter into the computed finding.`
27	USE START DATE	0;15	SET	LAST EDITED: `JUL 08, 2005` HELP-PROMPT: `Enter YES if you want to use the Start Date as the date of the finding` DESCRIPTION: `For findings that have a Start Date and a Stop Date the default is to use the Stop Date as the date of the finding. Enter a YES for this field if you want to use the Start Date as the date of the finding.`
28	INCLUDE VISIT DATA	0;16	SET	LAST EDITED: `JAN 27, 2006` HELP-PROMPT: `Enter YES or NO` DESCRIPTION: `This applies only to V file findings; if it is "YES" then data from the associated visit will be available for use in a Condition. The default is "NO."`
29	IMMUNIZATION SEARCH CRITERIA	0;17	SET	LAST EDITED: `APR 01, 2021` HELP-PROMPT: `Enter the Immunization Search Criteria` DESCRIPTION: `This finding modifier applies only to immunization findings. It is a set of codes that controls how an immunization is searched for in the patient's record. The codes are:` `CVX - Search for all immunizations that have the same CVX code as the` `immunization finding.` `IMM - Search only for the immunization finding. This is the default.` `VGN - Search for all immunizations that are in the same vaccine group as the` `immunization finding.` EXECUTABLE HELP: `D ISCXHELP^PXRMIMM(.DA,811.9)`

Customize PDF page

Package: Clinical Reminders

REMINDER DEFINITION(#811.9)-->811.902

Sub-Field: 811.902

Information

Details