| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | name(+) | 0;1 | FREE TEXT | 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. | ||
| 1.2 | print name | 0;3 | FREE TEXT | This is the name that is used when the results of a reminder evaluation are displayed. | ||
| 1.3 | do in advance time frame | 0;4 | FREE TEXT | 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). | ||
| 1.4 | related reminder guideline | 0;5 | POINTER | 811.9 | If a local reminder replaces a national reminder, this field can be used to identify the related national reminder. | |
| 1.6 | inactive flag | 0;6 | SET OF CODES | 1:INACTIVE | 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. | |
| 1.7 | inactive change date | 0;7 | DATE-TIME | This is the date and time when the INACTIVE FLAG was last changed. It is set automatically. Users should never edit this field. | ||
| 1.8 | ignore on n/a | 0;8 | FREE TEXT | 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. | ||
| 1.9 | sex specific | 0;9 | SET OF CODES | F:FEMALE M:MALE | 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. | |
| 1.91 | priority | 0;10 | SET OF CODES | 1:HIGH 2:MEDIUM 3:LOW | REMINDER PRIORITY is used by the CPRS GUI for sorting purposes. | |
| 2 | description | 1;0 | WORD-PROCESSING | This field contains a description of the clinical reminder. It is used to document its purpose and intended usage. | ||
| 3 | technical description | 2;0 | WORD-PROCESSING | The TECHNICAL DESCRIPTION is for documenting how a reminder is supposed to function and why the definition is set up the way it is. | ||
| 7 | baseline age findings | 7;0 | MULTIPLE | 811.97 | 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. | |
| 20 | findings | 20;0 | MULTIPLE | 811.902 | 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. | |
| 25 | function findings | 25;0 | MULTIPLE | 811.925 | 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. | |
| 30 | customized cohort logic | 30;1 | FREE TEXT | 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. | ||
| 31 | internal patient cohort logic | 31;1 | FREE TEXT | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 32 | patient cohort findings count | 32;1 | NUMERIC | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 33 | patient cohort findings list | 32;2 | FREE TEXT | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 34 | customized resolution logic | 34;1 | FREE TEXT | 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. | ||
| 35 | internal resolution logic | 35;1 | FREE TEXT | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 36 | resolution findings count | 36;1 | NUMERIC | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 37 | resolution findings list | 36;2 | FREE TEXT | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 40 | age findings count | 40;1 | NUMERIC | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 41 | age findings list | 40;2 | FREE TEXT | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 42 | information findings count | 42;1 | NUMERIC | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 43 | information findings list | 42;2 | FREE TEXT | This field is computed by the Clinical Reminders software and should never be edited by hand. | ||
| 45 | custom date due | 45;1 | FREE TEXT | 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. | ||
| 46 | custom date due function | 46;1 | FREE TEXT | This field contains the function used in the CUSTOM DATE DUE. It is created automatically and should not be set by hand. | ||
| 47 | number of arguments | 46;2 | NUMERIC | This is the number of arguments (findings) used in the CUSTOM DATE DUE. It is created automatically and should not be set by hand. | ||
| 48 | custom date due arg list | 47;0 | MULTIPLE | 811.948 | 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. | |
| 50 | web sites | 50;0 | MULTIPLE | 811.9002 | 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. | |
| 51 | linked reminder dialog | 51;1 | POINTER | 801.41 | AG | This is the Reminder Dialog that will be used when the reminder is processed in the CPRS GUI. |
| 60 | general cohort found text | 60;0 | WORD-PROCESSING | 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. | ||
| 61 | general cohort not found text | 61;0 | WORD-PROCESSING | 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. | ||
| 62 | # of gen. cohort found lines | 62;1 | FREE TEXT | 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. | ||
| 63 | # gen. cohort not found lines | 62;2 | FREE TEXT | 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. | ||
| 65 | general res. found text | 65;0 | WORD-PROCESSING | 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. | ||
| 66 | general res. not found text | 66;0 | WORD-PROCESSING | 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. | ||
| 67 | # gen. res. found lines | 67;1 | FREE TEXT | 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. | ||
| 68 | # gen. res. not found lines | 67;2 | FREE TEXT | 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. | ||
| 69 | rescission date | 0;11 | DATE-TIME | This is the rescission date for this reminder definition. | ||
| 70 | summary cohort found text | 70;0 | WORD-PROCESSING | 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. | ||
| 71 | summary cohort not found text | 71;0 | WORD-PROCESSING | 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. | ||
| 72 | # sum. cohort found lines | 72;1 | FREE TEXT | 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. | ||
| 73 | # sum. cohort not found lines | 72;2 | FREE TEXT | 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. | ||
| 75 | summary res. found text | 75;0 | WORD-PROCESSING | 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. | ||
| 76 | summary res. not found text | 76;0 | WORD-PROCESSING | 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. | ||
| 77 | # sum. res. found lines | 77;1 | FREE TEXT | 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. | ||
| 78 | # sum. res. not found lines | 77;2 | FREE TEXT | 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. | ||
| 100 | class(+) | 100;1 | SET OF CODES | N:NATIONAL V:VISN L:LOCAL | 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. | |
| 101 | sponsor | 100;2 | POINTER | 811.6 | This is the organization or group that sponsors this definition. | |
| 102 | review date | 100;3 | DATE-TIME | 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. | ||
| 103 | usage(+) | 100;4 | FREE TEXT | 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. | ||
| 110 | edit history | 110;0 | MULTIPLE | 811.9001 | This multiple is used to record a history of changes made to the definition. |