edits.seer.internal.rules.IF215.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.
<rule id="IF215" name="CS Extension, Mycosis Fungoides Schema (CS)" tag="N0963" java-path="lines.line" category="inter-field" depends="Behavior_Code_ICD-O-3,CS_Extension,CS_Site-Specific_Factor_25,Histologic_Type_ICD-O-3,Primary_Site"> <expression><![CDATA[if (line.csExtension == null || line.behaviorCodeIcdO3 == '0' || line.behaviorCodeIcdO3 == '1') return true if (line._csSchemaId == 'mycosis_fungoides') { if (Functions.matches(line.primarySite, /^C44[0-8]$/)) return line.csExtension != '300' } return true]]></expression> <message>CS Extension and Mycosis Fungoides Schema conflict</message> <description><![CDATA[The purpose of this edit is to verify that CS Extension is coded properly for the Mycosis Fungoides and Sezary Disease schema per Note 4 for CS Extension: Use code 150 when skin involvement is present but only a general location/site is mentioned (i.e. face, legs, torso, arms). Use code 300 when there is skin involvement but there is no mention of location/site. This edit is skipped if: 1. CS Extension is empty. 2. Behavior Code ICD-O-3 is 0 (benign) or 1 (borderline). 3. CS schema is invalid If schema is Mycosis Fungoides: If Primary Site = C440-C448 (specified skin sites), then CS Extension must not = 300 (Skin involvement, NOS).]]></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="SE15-013-01" user="kirbyk" date="2015-01-07" ref="67123">Updated description.</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-020-01" user="depryf" date="2020-02-04" ref="68281">Changed property names to align with NAACCR XML IDs.</event> </history> </rule>