Home Package List Routine Alphabetical List Global Alphabetical List FileMan Files List FileMan Sub-Files List Package Component Lists Package-Namespace Mapping

Print Page as PDF

Sub-Field: 810.41

Package: Clinical Reminders

REMINDER LIST RULE(#810.4)-->810.41

Sub-Field: 810.41

Information

Parent File	Name	Number	Package
REMINDER LIST RULE(#810.4)	SEQUENCE	810.41	Clinical Reminders

Details

Field #	Name	Loc	Type	Details
.01	SEQUENCE	0;1	NUMBER	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X` LAST EDITED: `JUL 02, 2007` HELP-PROMPT: `Type a Number between 1 and 999, 0 Decimal Digits` DESCRIPTION: `A 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.` FIELD INDEX: `B (#742) REGULAR IR LOOKUP & SORTING` `Unique for: Key A (#23), File #810.41` `Short Descr: Uniqueness Index for Key 'A' of Subfile #810.41` `Set Logic: S ^PXRM(810.4,DA(1),30,"B",X,DA)=""` `Kill Logic: K ^PXRM(810.4,DA(1),30,"B",X,DA)` `Whole Kill: K ^PXRM(810.4,DA(1),30,"B")` `X(1): SEQUENCE (810.41,.01) (Subscr 1)`
.02	LIST RULE	0;2	POINTER TO REMINDER LIST RULE FILE (#810.4)	REMINDER LIST RULE(#810.4) INPUT TRANSFORM: `D SCREEN^PXRMLRED D ^DIC K DIC S DIC=$G(DIE),X=+Y K:Y<0 X` LAST EDITED: `JUL 03, 2002` DESCRIPTION: `This is the finding rule to be used to select patients.` SCREEN: `D SCREEN^PXRMLRED` EXPLANATION: `RULE SETS MAY NOT CONTAIN OTHER RULE SETS` CROSS-REFERENCE: `810.4^AD` `1)= S ^PXRM(810.4,"AD",$E(X,1,30),DA(1),DA)=""` `2)= K ^PXRM(810.4,"AD",$E(X,1,30),DA(1),DA)` `This index is used to determine which rule sets a list rule belongs to.` CROSS-REFERENCE: `810.41^D` `1)= S ^PXRM(810.4,DA(1),30,"D",$E(X,1,30),DA)=""` `2)= K ^PXRM(810.4,DA(1),30,"D",$E(X,1,30),DA)`
.03	OPERATION	0;3	SET	**********************REQUIRED FIELD********************** 'A' FOR ADD PATIENT; 'F' FOR INSERT FINDING; 'R' FOR REMOVE; 'S' FOR SELECT; LAST EDITED: `MAY 21, 2004` DESCRIPTION: `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.`
2	SEQUENCE BEGINNING DATE/TIME	1;1	FREE TEXT	INPUT TRANSFORM: `K:(($L(X)<1)!($L(X)>20)!('$$DATECHK^PXRMRUL1(X))) X` LAST EDITED: `MAY 04, 2006` HELP-PROMPT: `Answer must be 1-20 characters in length.` DESCRIPTION: `This 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.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER`
3	SEQUENCE ENDING DATE/TIME	1;2	FREE TEXT	INPUT TRANSFORM: `K:(($L(X)<1)!($L(X)>20)!('$$DATECHK^PXRMRUL1(X))) X` LAST EDITED: `MAY 04, 2006` HELP-PROMPT: `Answer must be 1-20 characters in length.` DESCRIPTION: `This 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.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER`