edits.seer.internal.rules.IF216.xml Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of validation-edits-seer Show documentation
Show all versions of validation-edits-seer Show documentation
Java implemenation of the SEER edits.
The newest version!
<rule id="IF216" name="CS Lymph Nodes, SSF 3, Nodes Eval, MelanomaSkin (CS)" tag="N0964" java-path="lines.line" category="inter-field" depends="Behavior_Code_ICD-O-3,CS_Lymph_Nodes,CS_Reg_Node_Eval,CS_Site-Specific_Factor_25,CS_Site-Specific_Factor_3,Histologic_Type_ICD-O-3,Primary_Site"> <expression><![CDATA[if (line.csLymphNodes == null || line.csSiteSpecificFactor3 == null || line.csSiteSpecificFactor3 == '988' || line.behaviorCodeIcdO3 == '0' || line.behaviorCodeIcdO3 == '1') return true if (line._csSchemaId == 'melanoma_skin') { if (Functions.matches(line.csSiteSpecificFactor3, /^000|005$/)) return !(Functions.matches(line.csLymphNodes, /^121|128$/)) if (Functions.matches(line.csLymphNodes, /^121|128$/)) return Functions.matches(line.csLymphNodesEval, /^0|1|5|9$/) if (Functions.matches(line.csLymphNodes, /^12[234]|15[238]$/)) return Functions.matches(line.csLymphNodesEval, /^2|3|6|8|9$/) if (Functions.matches(line.csSiteSpecificFactor3, /^0[25]0|04[358]|1[05]0$/)) return line.csLymphNodesEval != '8' } return true]]></expression> <message>CS Lymph Nodes, SSF3, Nodes Eval, and Melanoma of Skin Schema conflict</message> <description><![CDATA[The purpose of this edit is to compare CS Lymph Nodes, CS Site-Specific 3, and CS Lymph Nodes Eval for cases coded using the Melanoma of Skin Schema. If schema is MelanomaSkin: 1. If CS Site-Specific Factor 3 = 000 or 005 (see definitions below) then CS Lymph Nodes must not = 121 or 128 (codes that indicate case evaluated clinically) 2. If CS Lymph Nodes = 121 or 128 (codes that indicate case evaluated clinically) then CS Lymph Nodes Eval must = 0, 1, 5 (codes that indicate case does not meet criteria for AJCC pathological stage)or 9 (unknown) 3. If CS Lymph Nodes = 122, 123, 124, 152, 153, or 158 (codes that indicate case was evaluated pathologically) then CS Lymph Nodes Eval must = 2, 3, 6, 8 (codes that indicate case meets requirement for AJCC pathologic staging) or 9 (unknown) 4. If CS Site-Specific Factor 3 = 020, 043, 045, 048, 050, 100, or 150 (codes indicating 'clinically apparent') then CS Lymph Nodes Eval must not = 8 (diagnosed at autopsy) ************************************************************** CS Site-Specific Factor 3 definitions for codes 000 and 005: 000 = OBSOLETE DATA RETAINED V0204 No lymph node metastasis 005 = Clinically negative lymph node metastasis AND No pathologic examination performed Or unknown if pathologic examination performed Or nodes negative on pathologic examination ************************************************************* This edit is skipped if any of the following conditions are true: 1. CS Lymph Nodes is empty 2. CS Site-Specific Factor 3 is empty or = 988 3. Behavior Code ICD-O-3 = 0 (benign) or 1 (borderline) 4. CS schema is invalid This edit first determines the correct CS schema by doing a function call to the CS Dynamic Link Library (dll). The function call passes Primary Site, Histologic Type ICD-O-3, and CS Site-Specific Factor25 (schema discriminator) to the dll and the CS schema name is returned.]]></description> <history> <event version="SE11-001-23" user="greend" date="2009-01-13">This edit was created.</event> <event version="SE12-002-01" user="murphyr" date="2010-01-12">Changed extension constants to three digits, removed a skip condition, and now use a schema name lookup function.</event> <event version="SE12-002-01" user="murphyr" date="2010-02-03">Updated documentation.</event> <event version="SE12-004-01" user="murphyr" date="2011-02-14">Updated edit for CSv2 version 02.03.02.</event> <event version="SE12-006-01" user="murphyr" date="2011-12-20" ref="66599">Logic re-worked for CSv0204.</event> <event version="SE16-015-01" user="kirbyk" date="2016-05-04" ref="67370">Changed edit to use schema IDs instead of schema names</event> <event version="SE16-016-08" user="depryf" date="2017-11-22" ref="67674">Edit syntax updated to allow pre-compilation optimization; no change in behavior.</event> <event version="SE18-018-02" user="schadega" date="2018-05-17" ref="67760">Name change.</event> <event version="SE18-020-01" user="depryf" date="2020-02-04" ref="68281">Changed property names to align with NAACCR XML IDs.</event> </history> </rule>