| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | name(+) | 0;1 | FREE TEXT | This is the name of the list rule. National list rules are prefixed VA- and class national. | ||
| .02 | short description | 0;2 | FREE TEXT | This is a short description of the list rule. | ||
| .03 | type(+) | 0;3 | SET OF CODES | 1:FINDING RULE 3:RULE SET 5:PATIENT LIST 2:REMINDER RULE | There are three types of rules in the file. Patient List Rules define an existing patient list. Finding Rules define reminder terms. Rule Sets contain both Finding and Patient List rules. | |
| 1 | reminder term | 0;7 | POINTER | 811.5 | Finding rules (type 1) use a reminder term (#811.5) to select patients via the reminder package indexes. | |
| 2 | list rule beginning date/time | 0;4 | FREE TEXT | Enter an exact date, symbolic date, or 0 (zero) for no beginning date. Symbolic dates can use "T" to represent the build end date or "BDT" for build beginning date. This field is the beginning date/time (BDT) to use when searching for findings that match a List Finding Rule. In order for patient data to meet the List Finding Rule criteria, the findings must have been documented on or after the BDT. Reminder Rules and Patient List Rules do not use the Beginning date/time field. The BDT defined for a finding rule will be overridden if the term in the finding rule has a mapped finding with a BDT or Ending Date/Time (EDT). The rules for overriding date ranges is represented by the following equation, where "<" should be interpreted as "is overridden by": Build < rule set sequence < list rule < term's finding If the BDT and EDT are not defined on the list rule set sequence, nor the list finding rule, nor the Reminder Term's mapped finding, then the patient list tools will use the List Build's date range to find a match on findings. The List Build date range is the date range specified by the user when the list build action is selected. The list build date range is the Extract reporting period if an extract is being run. If no date range limits should be used to match findings for this finding rule, the finding rule needs to be defined with a zero in the BDT or EDT fields, or both. The term referenced in the list rule should not have BDT and EDT fields defined. If zero is defined in the BDT, and the EDT is left blank, the list build tools will assume both BDT and EDT should not have date range limits, and vice versa if EDT has the 0 and the BDT is blank. The use of "T" in the finding rule BDT field will always represent the ending date/time specified for the list build process or the extract reporting period, depending on whether a reminder patient list or extract option is being used to build the list. For example, T-1Y is one year prior to the list build's ending date/time. "BDT" may also be used in the BDT or EDT fields and represents the beginning date/time specified by the user processing the list build action. For example, BDT-5Y creates a beginning date for the list rule that is five years prior to the list build's beginning date/time. A fixed date may be defined in the BDT (e.g. 09/11/02). If the beginning date/time is later than the ending date/time, then no finding matches will be found. | ||
| 3 | list rule ending date/time | 0;5 | FREE TEXT | Enter an exact date, symbolic date, or 0 (zero) for no ending date. Symbolic dates can use "T" to represent the build end date, or "BDT" for build beginning date. This field is the ending date/time to use when searching for findings that match this list rule criteria. Findings must have been documented before the ending date/time. If no time is included, 11:59PM is assumed to be the time. The rules for overriding date ranges is represented by the following equation, where "<" should be interpreted as "is overridden by": Build < rule set sequence < list rule < term's finding The Ending Date/Time (EDT) defined for this list rule will be overridden if the term in the list rule has a mapped finding with a Beginning Date/Time (BDT) or Ending Date/Time (EDT). If the BDT and EDT are not defined on the list rule, nor the rule set sequence, nor the Reminder Term's mapped finding, then the patient list tools will use the List Build date range to find a match on findings. The List Build date range is the date range specified by the user when the list build action is selected. The list build date range is the Extract reporting period if an extract is being run. If no date range limits should be used to match findings for this list rule, the list rule needs to be defined with a zero in the BDT or EDT fields, or both. The term referenced in the list rule should not have BDT and EDT fields defined. If zero is defined in the list rule BDT, and the EDT is left blank, the list build tools will assume both BDT and EDT should not have date range limits, and vice versa if EDT has the 0 and the BDT is blank. The use of "T" in the List rule EDT field will always represent the ending date/time specified for the list build process or the extract reporting period, depending on whether a reminder patient list or extract option is being used to build the list. T-1Y is one year prior to the list build's ending date/time. "BDT" may also be used in the BDT or EDT fields and represents the beginning date/time specified by the user processing the list build action. For example "BDT-5Y" in the list rule beginning date, and "BDT" in the list rule ending date will create a five year date range ending on the list build's beginning date/time. A fixed date may also be defined in the EDT (e.g. 09/11/02). If the ending date/time is earlier than the beginning date/time, then no finding matches will be found. | ||
| 4 | use existing pt list | 0;8 | POINTER | 810.5 | This field is used by Patient List rules to identify an existing patient list in the Reminder Patient List file. The existing patient list is used as the patient source to perform the ADD, SELECT, or REMOVE operation on the list rule. The existing patient list is used to modify the temporary patient list built during list build processing. For the ADD operation the patients in the source list will be added to the temporary patient list. For the SELECT operation, the patients in the source list will be compared to the temporary patient list. Patient's in the temporary list that are not in the source list will be removed from the temporary patient list. For the REMOVE operation, the patients in the source list, that match a patient in the temporary patient list will be removed from the temporary patient list. If the USE EXISTING PT LIST and USE EXTRACT PT LIST NAMED field are both defined in the list rule, the USE EXTRACT PT LIST NAMED will be used as the patient source for extract processing, and the USE EXISTING PT LIST will be used when the build processing is started from the Reminder Patient List option. | |
| 7 | use extract pt list named | 1;1 | FREE TEXT | This is a free-text field that contains the name of the patient list to use when processing this list rule during an extract run. The patient list has not been created at the time the list rule is defined. In contrast, the USE EXISTING PT LIST field is used by patient list rule tools to reference a patient list already existing in the REMINDER PATIENT LIST file. The name specified in the USE EXTRACT PT LIST NAMED will contain 'yyyy' for year and 'pnn' for reporting period. The nn is either the month (01-12) or calendar quarter (01-04), and p is either M for monthly, Q for quarterly, or Y for yearly. When an extract is run for a particular reporting period, the extract tool will use the USE EXTRACT PT LIST NAMED to find the patient list matching the name and then use this patient list to create the starting temporary patient list. The starting temporary patient list will be modified by add, select, and delete operations defined in the remaining list rules defined in the rule set. The same extract patient list name is also named in the REMINDER EXTRACT DEFINITION file (#810.2). The extract definition is used to create the extract patient list during an extract run. The 'yyyy' and 'pnn' ensures the extract process for the reporting year and period consistently uses the appropriate extract patient list created for the reporting period. Example: The patient list 'VA-*IHD QUERI yyyy pnn PATIENTS WITH QUALIFYING VISIT' is created during 'VA-IHD QUERI' extract processing by a rule set defined in the extract definition. Then a subsequent rule set defined in the 'VA-IHD QUERI' extract definition references a REMINDER LIST RULE entry with the same extract patient list name in the USE EXTRACT PT LIST NAMED field. During the extract run, the named list will be used to find the patient list created during the extract run in process. This list is used with the ADD operation in the rule set to create the temporary patient list to process the remaining rules in the rule set. In this example, the temorary patient list is modified to include patients that have both a QUALIFYING VISIT and an ANCHOR visit, creating a new patient list, 'VA-*IHD QUERI yyyy nn PATIENTS WITH QUALIFYING AND ANCHOR VISIT'. The new patient list created by the rule set processing is defined in the extract definition. | ||
| 9 | reminder definition | 0;10 | POINTER | 811.9 | This is a pointer to the Reminder Definition file #811.9. Reminders used to build patient lists must have an "L" in their USAGE field. | |
| 30 | sequence | 30;0 | MULTIPLE | 810.41 | ||
| 100 | class(+) | 100;1 | SET OF CODES | N:NATIONAL V:VISN L:LOCAL | This is the CLASS of the rule. National rules cannot be edited. | |
| 110 | edit history | 110;0 | MULTIPLE | 810.42 | This multiple is used to record a history of changes to the rule. |