The Master Data Model for Veteran Care

Developer Documentation » VDM » Reminder_Definition-811_9

Reminder Definition (811.9)

This file contains Clinical Reminder definitions. For a detailed description of the contents of this file, see the Clinical Reminders Manager Manual. Additional information may be found at the Clinical Reminders web site: http//vista.domain.ext/reminders This file contains a combination of nationally distributed and local entries. Any local entries are assigned an internal entry number prefixed with your site number. Nationally distributed entries have their name prefixed with VA-. Local entry names cannot start with VA-.

Global: ^PXD(811.9,

Domain: Non-Clinical

Properties

Label/Field Name Field # Description Datatype Attributes Range
Name
  name
.01 This field is the name of a clinical reminder definition. Nationally
distributed reminder definition names are prefixed with “VA-“. The
VA- prefixed reminder definitions cannot be altered by a site, but
may be inactivated so they will not be selectable or evaluated in
the CPRS GUI.

Local modifications can be made to any “VA-“ reminder definition by
copying the definition to a new one with a unique name and then
making modifications to the new definition which meet local
criteria.
STRING REQUIRED  
Print Name
  print_name
1.2 This is the name that is used when the results of a reminder evaluation
are displayed.
STRING    
Do In Advance Time Frame
  do_in_advance_time_frame
1.3 This field is used to let a reminder become due earlier than the
date determined by adding the frequency to the date when the
reminder was last resolved. For example, if the frequency is 1Y (one
year) and the DO IN ADVANCE TIME FRAME is 1M (one month), the
reminder would have a status of “DUE SOON” 11 months after it was
last resolved. After one year has passed, the STATUS would be “DUE”.

Frequencies have the form IU where I is an integer and U is one of
the following units: H (hours), D (days), W (weeks), M (months), and
Y (years).
STRING    
Related Reminder Guideline
  related_reminder_guideline
1.4 If a local reminder replaces a national reminder, this field can be
used to identify the related national reminder.
POINTER   Reminder_Definition-811_9
Inactive Flag
  inactive_flag
1.6 Reminders that are inactive will not be evaluated. The Clinical
Maintenance component will return a message stating the reminder is
inactive and the date when it was made inactive.

Other applications that use reminders may use this flag to determine
if a reminder can be selected for inclusion.
ENUMERATION   INACTIVE: 1
Inactive Change Date
  inactive_change_date
1.7 This is the date and time when the INACTIVE FLAG was last changed. It
is set automatically. Users should never edit this field.
DATE-TIME    
Ignore On N/a
  ignore_on_n_a
1.8 This field allows the user to stop reminders from being printed in
the Clinical Maintenance component if the reminder is N/A. This is a
free text field that can contain any combination of the following
codes:

Code Description
A N/A due to not meeting age criteria.
I N/A due to inactive reminder.
R N/A due to the wrong race.
S N/A due to the wrong sex.
* N/A for any reason.
STRING    
Sex Specific
  sex_specific
1.9 This field is used to make a reminder sex specific. If an “F” is
entered, the reminder applies only to females. If an “M” is entered,
the reminder applies only to males. If it is left blank, then the
reminder is applicable to either sex.

If CUSTOM COHORT LOGIC is defined and it does not contain SEX, then
this field will be ignored.
ENUMERATION   MALE: M
FEMALE: F
Priority
  priority
1.91 REMINDER PRIORITY is used by the CPRS GUI for sorting purposes. ENUMERATION   HIGH: 1
MEDIUM: 2
LOW: 3
Description
  description
2 This field contains a description of the clinical reminder. It is
used to document its purpose and intended usage.
STRING    
Technical Description
  technical_description
3 The TECHNICAL DESCRIPTION is for documenting how a reminder is
supposed to function and why the definition is set up the way it is.
STRING    
Baseline Age Findings
  baseline_age_findings
7 This multiple is for defining reminder frequency age ranges sets. It
can be used to specify different frequencies for different ages. For
example, you could define a frequency of every 3 years for ages 40
to 49 as the first age range set, a frequency of every 2 years for
ages 50 to 59 as the second, and a frequency of once a year for ages
60 to 75. With this set the reminder would be due every 3 years for
ages 40 to 49, every 2 years for ages 50 to 59, and once a year for
ages 60 to 75.
OBJECT   Baseline_Age_Findings-811_97
Findings
  findings
20 This multiple identifies which finding items to use when evaluating the
reminder. Finding items may be categorized into 4 types of findings:
age, patient cohort, resolution, and informational. How patient findings
are used depends on the values given to the various fields associated with
findings. See the description of those fields to learn what they do.
OBJECT   Findings-811_902
Function Findings
  function_findings
25 This multiple is used to define function findings; each function
finding is labeled by an integer: the FUNCTION FINDING NUMBER. The
user defines a function finding by inputting a FUNCTION FINDING
NUMBER and associated FUNCTION STRING. Function Findings are then
used in the reminder definition logic by reference to FF(FUNCTION
FINDING NUMBER). For example, if function findings 1 and 2 were
defined, then they could be used in the cohort or resolution logic as
FF(1) and FF(2).

Function findings can be used in the resolution logic with one
caveat. They do not have a date associated with them; therefore, the
resolution logic must be written so that it cannot be made true
solely by a function finding.
OBJECT   Function_Findings-811_925
Customized Cohort Logic
  customized_cohort_logic
30 This field may be used to define a customized Patient Cohort Logic
string. Typically this is done when the USE IN PATIENT COHORT LOGIC
fields associated with each finding do not provide the ability to
create the required logic string. The requirement for custom logic
arises when the required logic is more complex than can be
represented by simple concatenation of Boolean logical operators and
findings.

Detailed information on how to create the custom logic string can be
found in the Clinical Reminders Manager Manual.
STRING    
Internal Patient Cohort Logic
  internal_patient_cohort_logic
31 This field is computed by the Clinical Reminders software and should
never be edited by hand.
STRING    
Patient Cohort Findings Count
  patient_cohort_findings_count
32 This field is computed by the Clinical Reminders software and should
never be edited by hand.
NUMERIC    
Patient Cohort Findings List
  patient_cohort_findings_list
33 This field is computed by the Clinical Reminders software and should
never be edited by hand.
STRING    
Customized Resolution Logic
  customized_resolution_logic
34 This field may be used to define a customized Resolution Logic
string. Typically this is done when the USE IN RESOLUTION LOGIC
fields associated with each finding do not provide the ability to
create the required logic string. The requirement for custom logic
arises when the required logic is more complex than can be
represented by simple concatenation of Boolean logical operators and
findings.

Detailed information on how to create the custom logic string can be
found in the Clinical Reminders Manager Manual.
STRING    
Internal Resolution Logic
  internal_resolution_logic
35 This field is computed by the Clinical Reminders software and should
never be edited by hand.
STRING    
Resolution Findings Count
  resolution_findings_count
36 This field is computed by the Clinical Reminders software and should
never be edited by hand.
NUMERIC    
Resolution Findings List
  resolution_findings_list
37 This field is computed by the Clinical Reminders software and should
never be edited by hand.
STRING    
Age Findings Count
  age_findings_count
40 This field is computed by the Clinical Reminders software and should
never be edited by hand.
NUMERIC    
Age Findings List
  age_findings_list
41 This field is computed by the Clinical Reminders software and should
never be edited by hand.
STRING    
Information Findings Count
  information_findings_count
42 This field is computed by the Clinical Reminders software and should
never be edited by hand.
NUMERIC    
Information Findings List
  information_findings_list
43 This field is computed by the Clinical Reminders software and should
never be edited by hand.
STRING    
Custom Date Due
  custom_date_due
45 When a CUSTOM DATE DUE is defined, it takes precedence over the
standard date due calculation. This means the normal date due
calculation that is based on the dates of the resolution findings
and the final frequency is not done. Only the dates of the findings
and the frequencies specified in the Custom Date Due string are
used. Any finding that is in the reminder definition can be used in
the Custom Date Due string; it is not limited to those defined as
resolution findings.

The final age range will still be used to determine if the patient
is in the cohort; however, the frequency associated with this age
range is not used. Only the frequencies specified in the Custom Date
Due String are used. They are added to the date of the associated
finding to determine the dates used by either the MIN_DATE or
MAX_DATE functions.
STRING    
Custom Date Due Function
  custom_date_due_function
46 This field contains the function used in the CUSTOM DATE DUE. It is
created automatically and should not be set by hand.
STRING    
Number Of Arguments
  number_of_arguments
47 This is the number of arguments (findings) used in the CUSTOM DATE
DUE. It is created automatically and should not be set by hand.
NUMERIC    
Custom Date Due Arg List
  custom_date_due_arg_list
48 This is the list of arguments (findings) used in the CUSTOM DATE
DUE. It is used to efficiently calculate the resolution date from
the custom date due string. It is created automatically and should
not be set by hand.
OBJECT   Custom_Date_Due_Arg_List-811_948
Web Sites
  web_sites
50 This multiple contains Web sites that have information related to
this reminder. The list of web sites will be displayed in the CPRS
GUI if the user right-clicks on a reminder and then selects
reference information. If a particular web site is clicked on, the
GUI will open a browser at that web site.
OBJECT   Web_Sites-811_9002
Linked Reminder Dialog
  linked_reminder_dialog
51 This is the Reminder Dialog that will be used when the reminder is
processed in the CPRS GUI.
POINTER INDEXED Reminder_Dialog-801_41
General Cohort Found Text
  general_cohort_found_text
60 This optional field defines the detailed text to display when the
Patient Cohort Logic is true. Detailed text is used for components
such as Clinical Maintenance and MyHealtheVet Detailed.
STRING    
General Cohort Not Found Text
  general_cohort_not_found_text
61 This optional field defines the detailed text to display when the
Patient Cohort Logic is false. Detailed text is used for components
such as Clinical Maintenance and MyHealtheVet Detailed.
STRING    
# Of Gen. Cohort Found Lines
  number_of_gen_cohort_found_lines
62 This is the number of lines in the GENERAL COHORT 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.
STRING    
# Gen. Cohort Not Found Lines
  number_gen_cohort_not_found_lines
63 This is the number of lines in the GENERAL COHORT 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.
STRING    
General Res. Found Text
  general_res_found_text
65 This optional field defines the detailed text to display when the
Resolution Logic is true. Detailed text is used for components such as
Clinical Maintenance and MyHealtheVet Detailed.
STRING    
General Res. Not Found Text
  general_res_not_found_text
66 This optional field defines the detailed text to display when the
Resolution Logic is false. Detailed text is used for components such as
Clinical Maintenance and MyHealtheVet Detailed.
STRING    
# Gen. Res. Found Lines
  number_gen_res_found_lines
67 This is the number of lines in the GENERAL RESOLUTION 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.
STRING    
# Gen. Res. Not Found Lines
  number_gen_res_not_found_lines
68 This is the number of lines in the GENERAL RESOLUTION 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.
STRING    
Rescission Date
  rescission_date
69 This is the rescission date for this reminder definition. DATE-TIME    
Summary Cohort Found Text
  summary_cohort_found_text
70 This optional field defines the summary text to display when the
Patient Cohort Logic is true. Summary text is used for components such
as MyHealtheVet Summary.
STRING    
Summary Cohort Not Found Text
  summary_cohort_not_found_text
71 This optional field defines the summary text to display when the
Patient Cohort Logic is false. Summary text is used for components such
MyHealtheVet Summary.
STRING    
# Sum. Cohort Found Lines
  number_sum_cohort_found_lines
72 This is the number of lines in the SUMMARY COHORT 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.
STRING    
# Sum. Cohort Not Found Lines
  number_sum_cohort_not_found_lines
73 This is the number of lines in the SUMMARY COHORT 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.
STRING    
Summary Res. Found Text
  summary_res_found_text
75 This optional field defines the summary text to display when the
Resolution Logic is true. Summary text is used for components such
as MyHealtheVet Summary.
STRING    
Summary Res. Not Found Text
  summary_res_not_found_text
76 This optional field defines the summary text to display when the
Resolution Logic is false. Summary text is used for components such
as MyHealtheVet Summary.
STRING    
# Sum. Res. Found Lines
  number_sum_res_found_lines
77 This is the number of lines in the SUMMARY RESOLUTION 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.
STRING    
# Sum. Res. Not Found Lines
  number_sum_res_not_found_lines
78 This is the number of lines in the SUMMARY RESOLUTION 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.
STRING    
Class
  class
100 This is the CLASS of the definition. Possible classes are “N” for
national, “V” for VISN, and “L” for local. National definitions cannot
be edited by sites.

ENUMERATION REQUIRED LOCAL: L
NATIONAL: N
VISN: V
Sponsor
  sponsor
101 This is the organization or group that sponsors this definition. POINTER   Reminder_Sponsor-811_6
Review Date
  review_date
102 The REVIEW DATE is used to determine when the definition should be
reviewed to verify that it is current with the latest standards and
guidelines. You can find all reminder definitions whose review date
has passed using the Clinical Reminders Review Date Report.
DATE-TIME    
Usage
  usage
103 The Usage field describes how the reminder definition can be
used. This field must contain C or * if the reminder is to be selected
in CPRS. The L or the O values will override all other values. For
example, if L and C are defined in the Usage field, the Reminder
will not show on the cover sheet in CPRS, because L is in the
Usage field.

This is free text field and can contain any combination of the
following codes:

Code Usage
C CPRS
L Reminder Patient List
O Reminder Order Checks
P Patient
R Reminder Reports
X Reminder Extracts
* All of the above, except L, O, and P.
STRING REQUIRED  
Edit History
  edit_history
110 This multiple is used to record a history of changes made to the
definition.
OBJECT   Edit_History-811_9001

↑ Return to top

Sub-Files

Baseline Age Findings (811.97)

ID
Baseline_Age_Findings-811_97

Properties

Label/Field Name Field # Description Datatype Attributes Range
Reminder Frequency
  reminder_frequency
.01 This is the frequency for the reminder. 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.

STRING INDEXED
REQUIRED
 
Minimum Age
  minimum_age
1 This field specifies the minimum age for defining an age range
associated with a frequency. Leave it blank if there is no minimum age.
NUMERIC    
Maximum Age
  maximum_age
2 This field specifies the maximum age for defining an age range
associated with a frequency. Leave it blank if there is no maximum age.
NUMERIC    
Age Match Text
  age_match_text
3 This is the text that will be displayed in the Clinical Maintenance
component if the patient’s age falls within the age range.
STRING    
Age No Match Text
  age_no_match_text
4 This is the text that will be displayed in the Clinical Maintenance
component if the patient’s age does not fall in the age range.
STRING    
No. Of Age Match Lines
  no_of_age_match_lines
5 This is the number of lines in the age match 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.
STRING    
No. Of Age No Match Lines
  no_of_age_no_match_lines
6 This is the number of lines in the age no match 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.
STRING    

↑ Return to top

Findings (811.902)

ID
Findings-811_902

Properties

Label/Field Name Field # Description Datatype Attributes Range
Finding Item
  finding_item
.01 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”

POINTER INDEXED
REQUIRED
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
Minimum Age
  minimum_age
1 This field specifies the minimum age for defining an age range
associated with a frequency. Leave it blank if there is no minimum age.
NUMERIC    
Maximum Age
  maximum_age
2 This field specifies the maximum age for defining an age range
associated with a frequency. Leave it blank if there is no maximum age.
NUMERIC    
Reminder Frequency
  reminder_frequency
3 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.

STRING    
Found Text
  found_text
4 This is the text that will be displayed in the Clinical Maintenance
output if this finding is found (true).
STRING    
Not Found Text
  not_found_text
5 This is the text that will be displayed in the Clinical Maintenance
output if the finding is not found (false).
STRING    
Rank Frequency
  rank_frequency
6 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.
NUMERIC    
Use In Resolution Logic
  use_in_resolution_logic
7 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.
ENUMERATION   AND: &
AND NOT: &'
OR: !
OR NOT: !'
Use In Patient Cohort Logic
  use_in_patient_cohort_logic
8 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.
ENUMERATION   AND: &
AND NOT: &'
OR: !
OR NOT: !'
Beginning Date/time
  beginning_date_time
9 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.
STRING    
Use Inactive Problems
  use_inactive_problems
10 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.
ENUMERATION   YES: 1
N: 0
Within Category Rank
  within_category_rank
11 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.
NUMERIC    
Ending Date/time
  ending_date_time
12 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.
STRING    
Mh Scale
  mh_scale
13 This applies only to Mental Health Instrument findings. It sets the
default scale, i.e., the value for V in the Condition.
NUMERIC    
Condition
  condition
14 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.
STRING    
Condition Case Sensitive
  condition_case_sensitive
15 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.
BOOLEAN   false: 1
true: 0
Rxtype
  rxtype
16 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”.
STRING    
Occurrence Count
  occurrence_count
17 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.
NUMERIC    
Use Status/cond In Search
  use_status_cond_in_search
18 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.

BOOLEAN   false: 0
true: 1
Status List
  status_list
21 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.
STRING    
Internal Condition
  internal_condition
22 This is the internal form of the condition. It is set automatically and
should never be set by hand.
STRING    
V Subscript List
  v_subscript_list
23 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.
STRING    
No. Of Found Text Lines
  no_of_found_text_lines
24 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.
STRING    
No. Not Found Text Lines
  no_not_found_text_lines
25 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.
STRING    
Computed Finding Parameter
  computed_finding_parameter
26 This field is used to pass a parameter into the computed finding. STRING    
Use Start Date
  use_start_date
27 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.
BOOLEAN   false: 1
true: 0
Include Visit Data
  include_visit_data
28 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.”

BOOLEAN   false: 1
true: 0

↑ Return to top

Function Findings (811.925)

ID
Function_Findings-811_925

Properties

Label/Field Name Field # Description Datatype Attributes Range
Function Finding Number
  function_finding_number
.01 This is the number of the function finding you want to create or
edit.
NUMERIC INDEXED
REQUIRED
 
Found Text
  found_text
1 This is the text that will be displayed in the Clinical Maintenance
output if this function finding is found (true).
STRING    
Not Found Text
  not_found_text
2 This is the text that will be displayed in the Clinical Maintenance output if
the function finding is not found (false).
STRING    
Function String
  function_string
3 FUNCTION STRING is input by the user and it defines a function finding.
STRING    
Function List
  function_list
5 FUNCTION LIST is a data structure that is used to efficiently
evaluate function findings. It is generated automatically and should
never be edited by user.
OBJECT   Function_List-811_9255
Logic
  logic
10 This is the internal representation of the function string. For
example, if the function string is MIN_DATE(1,2)>MAX_DATE(3) then
the LOGIC field would be FN(1)>FN(2).
STRING    
Use In Resolution Logic
  use_in_resolution_logic
11 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.
ENUMERATION   AND: &
AND NOT: &'
OR: !
OR NOT: !'
Use In Patient Cohort Logic
  use_in_patient_cohort_logic
12 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.
ENUMERATION   AND: &
AND NOT: &'
OR: !
OR NOT: !'
Minimum Age
  minimum_age
13 This field specifies the minimum age for defining an age range
associated with a frequency. Leave it blank if there is no minimum age.
NUMERIC    
Maximum Age
  maximum_age
14 This field specifies the maximum age for defining an age range
associated with a frequency. Leave it blank if there is no maximum age.
NUMERIC    
Reminder Frequency
  reminder_frequency
15 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.

STRING    
Rank Frequency
  rank_frequency
16 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.
NUMERIC    
Name
  name
40 If the NAME field is present it will be displayed with the function
finding result in the Clinical Maintenance output. The format is
Function Finding: NAME
If NAME is null then the format will be:
Function Finding: function
where function is the name of the function used in the function
finding.
STRING    
No. Found Text Lines
  no_found_text_lines
41 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.
STRING    
No. Not Found Text Lines
  no_not_found_text_lines
42 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.
STRING    

↑ Return to top

Function List (811.9255)

ID
Function_List-811_9255

Properties

Label/Field Name Field # Description Datatype Attributes Range
Function Number
  function_number
.01 FUNCTION NUMBER is an internal counter of the functions used in the
function string. For example, if the function string is
MIN_DATE(1,2)>MAX_DATE(3) then function number 1 is MIN_DATE and
function number 2 is MAX_DATE. The function numbers correspond with
the internal number used in field #10 LOGIC. For the above function
string the LOGIC field would be FN(1)>FN(2).
NUMERIC REQUIRED  
Function
  function
.02 FUNCTION is a pointer to the Function File, #802.4. For example, if
the function string is MIN_DATE(1,2)>MAX_DATE(3) then function
number 1 is MIN_DATE and FUNCTION is the pointer to the MIN_DATE
funtion in file #802.4
POINTER   Reminder_Function_Finding_Functions-802_4
Function Argument List
  function_argument_list
20 The FUNCTION ARGUMENT LIST multiple is the list of arguments
(finding numbers) for each function in the function string. For
example, if the function string is MIN_DATE(1,2)>MAX_DATE(3) then
the argument list for function number 1 is 1 and 2 and the argument
list for function 2 is 3.
NUMERIC    

↑ Return to top

Custom Date Due Arg List (811.948)

ID
Custom_Date_Due_Arg_List-811_948

Properties

Label/Field Name Field # Description Datatype Attributes Range
Finding
  finding
.01 This is the number of a finding used in the custom date due string.
It is created automatically and should not be set by hand.
NUMERIC INDEXED
REQUIRED
 
Frequency
  frequency
.02 This is the frequency that is associated with the finding defined in
the .01 field of the CUSTOM DATE DUE ARGUMENT LIST. It is created
automatically and should never be set by hand.
STRING    
Operator
  operator
.03 This is the operator ‘+” or ‘-‘ that is associated with the finding
defined in the .01 field of the CUSTOM DATE DUE ARGUMENT LIST. It is
created automatically and should never be set by hand.
STRING    

↑ Return to top

Web Sites (811.9002)

ID
Web_Sites-811_9002

Properties

Label/Field Name Field # Description Datatype Attributes Range
Url
  url
.01 This is the URL for the web site. STRING INDEXED
REQUIRED
 
Web Site Title
  web_site_title
.02 This is the web site title that is used by the CPRS GUI. It will
appear after a right click, allowing the user to select the web
site.
STRING    
Web Site Description
  web_site_description
1 This field contains a description of the Web site. STRING    

↑ Return to top

Edit History (811.9001)

ID
Edit_History-811_9001

Properties

Label/Field Name Field # Description Datatype Attributes Range
Edit Date
  edit_date
.01 This is the date and time when the editing was done. This field is set
automatically and should not be changed by the user.
DATE-TIME INDEXED
REQUIRED
 
Edit By
  edit_by
1 This is the person who did the editing. This field is set automatically
and should not be changed by the user.
POINTER   New_Person-200
Edit Comments
  edit_comments
2 This word-processing field can be used to record the changes made
during the editing session.
STRING    

↑ Return to top


Document generated on August 31st 2017, 2:55:41 pm