Files > SEQUENCE

parent
810.4
name
SEQUENCE
number
810.41
Fields
#NameLocationTypeDetailsIndexDescription
.01sequence(+)0;1NUMERICA rule set is defined with one or more sequences of list rules that indicate the sequence the list rules should be processed when the patient list is created. This is the sequence number associated with the list rule. The patient list created while processing each sequential list rule is stored in ^TMP("PXRMRULE"_sequence,$J). After the rule set is processed, the patient list is stored in the Reminder Patient List file.
.02list rule0;2POINTER810.4ADThis is the finding rule to be used to select patients.
.03operation(+)0;3SET OF CODESA:ADD PATIENT
F:INSERT FINDING
R:REMOVE
S:SELECT
This is the condition used in processing the sequence/finding rule. Each processing step will have a start and end list, a finding rule and an operation The possible operations are: ADD - Patients with findings in the rule are added to the start list to create the end list. REMOVE - Patients with findings in the rule are removed from the start list to create the end list. SELECT - Patients without findings in the rule are removed from the start list to create the end list. The end list is always stored in ^TMP("PXRMRULE"_sequence,$J). The start list may be the end list from another finding rule in the rule set or, alternatively, may be a patient list (#810.5). Patient lists may be merged using the ADD operation.
2sequence beginning date/time1;1FREE TEXTThis field is the beginning date/time (BDT) to use when searching for findings that match the rule set sequence criteria. In order for patient data to meet the rule set sequence criteria, the findings must have been documented on or after the beginning date/time. The rules for overriding date ranges can be defined with the following equation, where "<" should be interpreted as "is overridden by": List Build < rule set sequence < list rule < term's finding The Beginning Date/Time (BDT) defined for a rule set sequence will be overridden if the finding list rule, or term in the finding 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 rule set sequence, nor the list rule, 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 rule set sequence, the rule set sequence (or its list rule) needs to be defined with a zero in the BDT and/or EDT fields. 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. Both BDT and EDT may be set to zero. The use of "T" in the rule set sequence 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. 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. BDT-5Y creates a beginning date for the rule set sequence that is five years prior to the list build's beginning date/time. A fixed date may also 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.
3sequence ending date/time1;2FREE TEXTThis field is the ending date/time to use when searching for findings that match this rule set sequence 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 can be defined with the following equation, where "<" should be interpreted as "is overridden by": List Build < rule set sequence < list rule < term's finding The Ending Date/Time (EDT) defined for this rule set sequence will be overridden if the list rule, or term referenced 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 rule set sequence, nor the list rule, 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 selecting the list build action. 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 rule set sequence, the rule set sequence needs to be defined with a zero in the BDT or EDT fields, or both fields. Alternatively, the list build referenced by the sequence can be defined with a zero in its BDT or EFDT fields. The term referenced in the list rule should not have BDT and EDT fields defined. If zero is defined in the rule set sequence or 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 rule set sequence 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 rule set sequence beginning date, and BDT in the list rule set sequence 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.

Error: Invalid Global File Type: 810.41