STANDARD DATA DICTIONARY #811.5 -- REMINDER TERM FILE 6/27/25 PAGE 1
STORED IN ^PXRMD(811.5, (747 ENTRIES) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 2.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
This file defines Clinical Reminder terms. Terms have a number of uses, including as findings in a reminder definition, as finding
rules for building patient lists, and as elements of extract finding groups.
This file contains a combination of national, local, and VISN level terms. Nationally distributed entries will have a CLASS of
"National" and the name is prefixed with "VA-". Any terms created at your site should have a CLASS of "Local". Terms created for
VISN use will have a CLASS of "VISN"
Before a term can be used, it must have findings mapped to it. The findings that can be mapped to a term are any of the standard
Clinical Reminder findings with the exception of terms.
Reminder terms are useful for national reminders involving findings that are based on local file definitions (e.g., laboratory
test, drug file, radiology). National reminder terms have limited editing capabilities, which allow sites to map their local
finding items to a term. Sites may create local reminder terms, providing an easy way to group a variety of findings and treat them
the same way in a reminder.
When a reminder with terms is evaluated, the finding items mapped to the term are used to find the patient data, but the patient
data is reported based on the term the data is mapped to.
DD ACCESS: @
RD ACCESS:
WR ACCESS: @
DEL ACCESS: @
LAYGO ACCESS: @
AUDIT ACCESS: @
IDENTIFIED BY: CLASS (#100)[R]
PRIMARY KEY: A (#47)
Uniqueness Index: B (#768)
File, Field: 1) NAME (811.5,.01)
POINTED TO BY: REMINDER TERM field (#3) of the WV PROCEDURE TYPE File (#790.2)
REMINDER TERM field (#20) of the REMINDER ORDER CHECK RULES File (#801.1)
EVALUATION ITEM field (#1) of the BRANCHING LOGIC sub-field (#801.41143) of the REMINDER DIALOG File (#801.41)
TERM field (#.03) of the EXTRACT FINDINGS sub-field (#810.31) of the REMINDER EXTRACT SUMMARY File (#810.3)
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)
REMINDER TERM field (#.02) of the FINDING TOTALS sub-field (#810.331) of the COMPLIANCE TOTALS sub-field (#810.33)
of the REMINDER EXTRACT SUMMARY File (#810.3)
REMINDER TERM field (#1) of the REMINDER LIST RULE File (#810.4)
TERM field (#1) of the GROUP FINDINGS sub-field (#810.801) of the REMINDER COUNTING GROUP File (#810.8)
FINDING ITEM field (#.01) of the FINDINGS sub-field (#811.902) of the REMINDER DEFINITION File (#811.9)
INDEXED BY: NAME (ADEL), FINDING ITEM (AF), NAME (B)
LAST MODIFIED: OCT 5,2022@14:55:06
811.5,.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: Enter the name of the term, 3-64 characters.
DESCRIPTION:
This is the name of the term. The names of national terms are prefixed with "VA-".
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
FIELD INDEX: ADEL (#766) MUMPS ACTION
Short Descr: Set PXRMTMD=1 when the entire term is being deleted.
Description: PXRMTMD is set to 1 when a term is being deleted. This provides a flag that can be used to control
various actions, such as execution of cross-references, on fields in the term file.
Set Logic: Q
Kill Logic: I X2="" S PXRMTMD=1
X(1): NAME (811.5,.01) (Subscr 1) (forwards)
FIELD INDEX: B (#768) REGULAR IR LOOKUP & SORTING
Unique for: Key A (#47), File #811.5
Short Descr: New style B cross-reference
Set Logic: S ^PXRMD(811.5,"B",$E(X,1,64),DA)=""
Kill Logic: K ^PXRMD(811.5,"B",$E(X,1,64),DA)
Whole Kill: K ^PXRMD(811.5,"B")
X(1): NAME (811.5,.01) (Subscr 1) (Len 64) (forwards)
811.5,.04 DATE CREATED 0;4 DATE (Required)
INPUT TRANSFORM: S %DT="E" D ^%DT S X=Y K:Y<1 X
LAST EDITED: MAY 05, 2000
DESCRIPTION:
This is the date when the term was created.
811.5,1 DESCRIPTION 1;0 WORD-PROCESSING #811.51
DESCRIPTION:
This is a description of the term.
LAST EDITED: MAY 12, 1999
HELP-PROMPT: Enter the description of the term.
811.5,20 FINDINGS 20;0 VARIABLE POINTER Multiple #811.52
LAST EDITED: SEP 14, 1999
DESCRIPTION: This multiple identifies which finding items have been selected to represent the term. If there is
more than one finding item, they will all be evaluated and the most recent finding will represent
the term.
INDEXED BY: CONDITION CASE SENSITIVE (ACASE), CONDITION (ACOND), BEGINNING DATE/TIME & ENDING DATE/TIME
(ADATE), RXTYPE (AWARN)
811.52,.01 FINDING ITEM 0;1 VARIABLE POINTER (Multiply asked)
FILE ORDER PREFIX LAYGO MESSAGE
50 5 DR n DRUG
9999999.09 10 ED n EDUCATION TOPICS
9999999.15 15 EX n EXAM
9999999.64 20 HF n HEALTH FACTOR
9999999.14 25 IM n IMMUNIZATION
60 30 LT n LABORATORY TEST
601.71 35 MH n MH TESTS AND SURVEYS
101.43 40 OI n ORDERABLE ITEM
71 45 RP n RADIOLOGY PROCEDURE
811.4 50 CF n REMINDER COMPUTED FINDING
811.2 55 TX n REMINDER TAXONOMY
9999999.28 65 ST n SKIN TEST
50.605 70 DC n VA DRUG CLASS
50.6 75 DG n VA GENERIC
120.51 80 VM n VITAL MEASUREMENT
810.9 16 RL n REMINDER LOCATION LIST
INPUT TRANSFORM: K:'$$VFINDING^PXRMINTR(X) X
LAST EDITED: DEC 23, 2010
HELP-PROMPT: Enter a finding item in the format: Prefix.Name
DESCRIPTION: This field identifies the finding items included in the reminder term.
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.52^B
1)= S ^PXRMD(811.5,DA(1),20,"B",$E(X,1,30),DA)=""
2)= K ^PXRMD(811.5,DA(1),20,"B",$E(X,1,30),DA)
3)= Required Index for Variable Pointer
CROSS-REFERENCE: 811.52^E^MUMPS
1)= D SENODE^PXRMENOD(.X,.DA)
2)= D KENODE^PXRMENOD(.X,.DA)
This cross-reference is used to group findings by type. The index it creates has the form:
^PXRMD(811.5,DA(1),20,"E",GLOBAL,IEN,DA)
where
DA(1) is the internal entry number in file # 811.5.
GLOBAL is the global name of the global that defines the finding.
For example, the global name for file #811.5 is ^PXRMD(811.5,.
IEN is the internal entry number of the finding in GLOBAL.
DA is the finding number.
Some examples:
^PXRMD(811.5,2,20,"E","AUTTHF(",73,1)=
^PXRMD(811.5,7,20,"E","PXD(811.2,",2,1)=
^PXRMD(811.5,10,20,"E","PSNDF(50.6,",183,1)=
FIELD INDEX: AF (#767) REGULAR IR SORTING ONLY WHOLE FILE (#811.5)
Short Descr: Whole File Reference on Finding Items
Description: Finding Item,Reminder Term,Multiple Ien
Set Logic: S ^PXRMD(811.5,"AF",$E(X,1,30),DA(1),DA)=""
Kill Logic: K ^PXRMD(811.5,"AF",$E(X,1,30),DA(1),DA)
Whole Kill: K ^PXRMD(811.5,"AF")
X(1): FINDING ITEM (811.52,.01) (Subscr 1) (Len 30) (forwards)
811.52,9 BEGINNING DATE/TIME 0;8 FREE TEXT
INPUT TRANSFORM: S X=$$COTN^PXRMDATE(X) K:(($L(X)<1)!($L(X)>20)!('$$VDT^PXRMINTR(X))) X
LAST EDITED: SEP 24, 2004
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 acceptable FileMan date/time formats and abbreviations. In addition, you
may use the abbreviations T-NY or NOW-NY, where N is an integer and Y stands for years. If this
is null, then the beginning date/time will correspond with the date/time of the oldest entry.
See the FileMan Getting Started Manual to learn about acceptable FileMan date/time formats and
abbreviations.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
RECORD INDEXES: ADATE (#771)
811.52,10 USE INACTIVE PROBLEMS 0;9 SET
'1' FOR YES;
'0' FOR NO;
LAST EDITED: MAR 14, 2000
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.
811.52,11 WITHIN CATEGORY RANK 0;10 NUMBER
INPUT TRANSFORM: K:+X'=X!(X>999)!(X<0)!(X?.E1"."1N.N) X
LAST EDITED: MAY 05, 2000
HELP-PROMPT: Type a number between 0 and 999, 0 decimal digits.
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 Reminders 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.
811.52,12 ENDING DATE/TIME 0;11 FREE TEXT
INPUT TRANSFORM: S X=$$COTN^PXRMDATE(X) K:(($L(X)<1)!($L(X)>20)!('$$VDT^PXRMINTR(X))) X
LAST EDITED: SEP 24, 2004
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 acceptable FileMan date/time formats and abbreviations. In addition, you
may use the abbreviations T-NY or NOW-NY, where N is an integer and Y stands for years. If this
is null, then the end date/time will correspond with the date/time of the most recent entry.
See the FileMan Getting Started Manual to learn about acceptable FileMan date/time formats and
abbreviations.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
RECORD INDEXES: ADATE (#771)
811.52,13 MH SCALE 0;12 NUMBER
INPUT TRANSFORM: K:+X'=X!(X>99999999999999)!(X<1)!('$$VSCALET^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 SCHELPT^PXRMMH
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
811.52,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 (#770) MUMPS IR ACTION
Short Descr: Store the internal condition.
Set Logic: D SICOND^PXRMCOND(.X,.DA,811.5)
Kill Logic: D KICOND^PXRMCOND(.X,.DA,811.5)
X(1): CONDITION (811.52,14) (Subscr 1) (forwards)
811.52,15 CONDITION CASE SENSITIVE 3;2 SET
'0' FOR NO;
'1' FOR YES;
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 (#769) MUMPS IR ACTION
Short Descr: Reset internal condition whenever case sensitive field changes.
Set Logic: D CASESEN^PXRMCOND(X,.DA,811.5)
Kill Logic: D CASESEN^PXRMCOND(X,.DA,811.5)
X(1): CONDITION CASE SENSITIVE (811.52,15) (Subscr 1) (forwards)
811.52,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: JUL 19, 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: AWARN (#772) MUMPS ACTION
Short Descr: Warn the user to review the status list if Rx Type 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.52,16) (Subscr 1) (forwards)
811.52,17 OCCURRENCE COUNT 0;14 NUMBER
INPUT TRANSFORM: K:+X'=X!(X>99)!(X<-99)!(X?.E1"."1N.N) X
LAST EDITED: MAY 13, 2004
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.
811.52,18 USE STATUS/COND IN SEARCH 3;3 SET
'1' FOR YES;
'0' FOR NO;
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.
811.52,21 STATUS LIST 5;0 Multiple #811.54
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: ^
811.54,.01 STATUS 0;1 FREE TEXT (Multiply asked)
INPUT TRANSFORM: K:$L(X)>64!($L(X)<1) X
LAST EDITED: JAN 24, 2005
HELP-PROMPT: Enter a status.
DESCRIPTION: This multiple is used to store a list of possible statuses that the reminder will look for when
evaluating a finding item. This field should only be populated if the finding item is a Drug,
Radiology Procedure, Order, or Taxonomy. This field is designed to be populated only through
the Reminder Definition/Term editors; this field should not be edited using FileMan. The reason
for this is because each finding item can only have certain possible statuses assigned to it.
The editors will evaluate the finding items and allow the users to select a status only from an
appropriate list of statuses for that finding item.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
CROSS-REFERENCE: 811.54^B
1)= S ^PXRMD(811.5,DA(2),20,DA(1),5,"B",$E(X,1,30),DA)=""
2)= K ^PXRMD(811.5,DA(2),20,DA(1),5,"B",$E(X,1,30),DA)
811.52,22 INTERNAL CONDITION 10;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>245!($L(X)<3) X
LAST EDITED: JAN 24, 2005
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.
811.52,23 V SUBSCRIPT LIST 11;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>245!($L(X)<1) X
LAST EDITED: JAN 24, 2005
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.
811.52,26 COMPUTED FINDING PARAMETER 15;E1,245 FREE TEXT
INPUT TRANSFORM: K:$L(X)>245!($L(X)<1) X
LAST EDITED: JAN 24, 2005
HELP-PROMPT: Answer must be 1-245 characters in length.
DESCRIPTION:
This field is used to pass a parameter into the computed finding.
811.52,27 USE START DATE 0;15 SET
'0' FOR NO;
'1' FOR YES;
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.
811.52,28 INCLUDE VISIT DATA 0;16 SET
'0' FOR NO;
'1' FOR YES;
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."
811.52,29 IMMUNIZATION SEARCH CRITERIA 0;17 SET
'CVX' FOR CVX;
'IMM' FOR IMM;
'VGN' FOR VGN;
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.5)
811.5,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 the term. Possible classes are "N" for national, "V" for VISN, and "L" for
local. For national terms, only the finding list can be edited.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
811.5,101 SPONSOR 100;2 POINTER TO REMINDER SPONSOR FILE (#811.6)
LAST EDITED: APR 27, 2001
HELP-PROMPT: Enter the SPONSOR.
DESCRIPTION:
This is the organization, group, or individual that sponsors this definition.
811.5,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: Review Date is used to determine when the term should be reviewed to verify that it is current with
the latest standards and guidelines. You can find all terms whose review date has passed using the
Clinical Reminder Review Date Report.
811.5,110 EDIT HISTORY 110;0 DATE Multiple #811.53
DESCRIPTION:
This multiple is used to record a history of changes made to the term.
811.53,.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
HELP-PROMPT: Do not edit this field.
DESCRIPTION: This is the date and time when the editing was done. This field is set automatically and should
not be changed by the user.
CROSS-REFERENCE: 811.53^B
1)= S ^PXRMD(811.5,DA(1),110,"B",$E(X,1,30),DA)=""
2)= K ^PXRMD(811.5,DA(1),110,"B",$E(X,1,30),DA)
811.53,1 EDIT BY 0;2 POINTER TO NEW PERSON FILE (#200)
LAST EDITED: APR 19, 2001
HELP-PROMPT: Do not edit this field.
DESCRIPTION: This is the person who did the editing. This field is set automatically and should not be changed
by the user.
811.53,2 EDIT COMMENTS 1;0 WORD-PROCESSING #811.532
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)
Subfile #811.52
Record Indexes:
ADATE (#771) RECORD MUMPS IR ACTION
Short Descr: Give a warning if the ending date is before the beginning date.
Set Logic: D COMPARE^PXRMDATE(.X)
Kill Logic: Q
X(1): BEGINNING DATE/TIME (811.52,9) (forwards)
X(2): ENDING DATE/TIME (811.52,12) (forwards)
INPUT TEMPLATE(S):
PXRM EDIT NATIONAL TERM MAR 29, 2002@10:32 USER #0
PXRM EDIT REMINDER TERM MAR 29, 2002@10:34 USER #0
PRINT TEMPLATE(S):
PXRM TERM INQUIRY JAN 14, 2020@12:12 USER #0 REMINDER TERM LIST
This template prints a single reminder term definition.
PXRM TERM LIST APR 27, 2001@12:27 USER #0 REMINDER TERM LIST
This print template is used to list reminder terms.
SORT TEMPLATE(S):
PXRM EPI LAB AND MED TERMS AUG 15, 2000@02:05 USER #0 NUMBER EQUALS 3 Or NUMBER GREATER THAN 4
and NUMBER LESS THAN 26
These are the reminder terms used for Hepatitis C extracts of lab and
medication terms. They include an updated description for the PREVIOUSLY
ASSESSED HEP C RISK term (previously called PREV POSITIVE TEST FOR HEP C).
PXRM HEP C EXTRACT TERMS AUG 15, 2000@00:55 USER #0 NUMBER GREATER THAN 0 and NUMBER LESS THAN 26
PXRM NATIONAL TERMS MAY 08, 2000@12:54 USER #0 TERM TYPE EQUALS "N"^National
This search template contains the names of the reminder terms distributed
with the Clinical Reminders 1.5 package.
FORM(S)/BLOCK(S):