edits.seer.internal.rules.IF263.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="IF263" name="CS SSF 2, Dx Conf, KidneyRenalPelvis (CS)" tag="N1063" java-path="lines.line" category="inter-field" depends="Histologic_Type_ICD-O-3,Primary_Site"> <expression><![CDATA[if (line.csSiteSpecificFactor2 == null || line.histologicTypeIcdO3 == null || line.primarySite == null) return true if (line.behaviorCodeIcdO3 == '0' || line.behaviorCodeIcdO3 == '1') return true if (line._csSchemaId == 'kidney_renal_pelvis') { if (((line.csSiteSpecificFactor2 >= '000' && line.csSiteSpecificFactor2 <= '980') || line.csSiteSpecificFactor2 == '991') && line.diagnosticConfirmation != '1') return false } return true]]></expression> <message>CS SSF2 and Dx conf conflict for KidneyRenalPelvis schema</message> <description><![CDATA[This edit verifies that for cases coded using the KidneyRenalPelvis schema, CS Site-Specific Factor 2 (depth of renal parenchymal invasion) and Diagnostic Confirmation are coded consistently. This edit is skipped if any of the following conditions are true: 1. Site-Specific Factor 2 is blank 2. Behavior Code ICD-O-3 = 0 (benign) or 1 (borderline) 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. For cases using the KidneyRenalPelvis schema: If CS Site-Specific Factor 2 = 000-980 or 991 (positive statement about invasion), Diagnostic Confirmation must = 1 (positive histology).]]></description> <history> <event version="SE12-002-01" user="murphyr" date="2010-02-03">Edit created.</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="SE18-018-01" user="schadega" date="2018-04-11" ref="67741">Edit 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> <event version="SE24-024-06" user="kirbyk" date="2024-07-22" ref="69326">Removed some edit dependencies.</event> </history> </rule>