edits.seer.internal.rules.IF196.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="IF196" name="CS TS/Ext Eval, Surgery, Prostate Schema (CS)" tag="N0898" java-path="lines.line" category="inter-field" depends="Behavior_Code_ICD-O-3,CS_Tumor_Size_Ext_Eval,Histologic_Type_ICD-O-3,Primary_Site,RX_Summ--Surg_Prim_Site">
<expression><![CDATA[if (line.csTumorSizeExtEval == null || line.behaviorCodeIcdO3 == '0' || line.behaviorCodeIcdO3 == '1' || line.rxSummSurgPrimSite == null)
return true
if (line._csSchemaId == 'prostate') {
if (line.rxSummSurgPrimSite == '22')
return line.csTumorSizeExtEval == '1' || line.csTumorSizeExtEval == '2'
if (Functions.between(line.rxSummSurgPrimSite,'19', '26'))
return line.csTumorSizeExtEval == '0' || line.csTumorSizeExtEval == '1' || line.csTumorSizeExtEval == '2'
if (Functions.between(line.csTumorSizeExtEval,'4', '6'))
return Functions.between(line.rxSummSurgPrimSite,'30', '80')
}
return true]]></expression>
<message>Conflict between CS TS/EXT Eval, Surgery, and Prostate Schema</message>
<description><![CDATA[This edit is skipped if any of the following conditions are true:
1. CS Tumor Size/Ext Eval is blank
2. Behavior Code ICD-O-3 = 0 (benign) or 1 (borderline)
3. RX Summ--Surg Prim Site is blank.
For cases using the CS Prostate Schema (Primary Site [400] = C619), if RX Summ--Surg Prim Site = 22
(TURP, cancer is incidental finding during surgery for benign disease), then the CS Tumor Size/Ext Eval
should be coded as 1 (No prostatectomy done. Evalutation based on endoscopic examination,
diagnostic biopsy, including fine needle aspiration biopsy, or other invasive techniques including surgical
observation without biopsy) or 2 (No prostatectomy done, but positive biopsy of extraprostatic
tissue allows assignment to CS Extension Codes 410-700); otherwise if only a TURP is performed
(RX Summ--Surg Prim Site = 19-26), then the CS Tumor Size/Ext Eval should be coded as 0
[No prostatectomy done. Evalutation based on physical examination including digital rectal examination (DRE),
imaging examination, or other non-invasive clinical evidence. No autopsy evidence used], 1 or 2.
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.
The logic is:
If the schema is Prostate schema:
If RX Summ--Surg Prim Site = 22, then
CS Tumor Size/Ext Eval must = 1 or 2.
ELSE If RX Summ--Surg Prim Site = 19-26, then
CS Tumor Size/Ext Eval must = 0, 1, or 2.
ELSE If Tumor Size/Ext Eval = 4, 5, or 6 (prostatectomy performed) then
RX Summ--Surg Prim Site must = 30-80]]></description>
<history>
<event version="SE11-001-22" user="greend" date="2008-07-10">Changed the range of surgery codes for "only TURP is performed" from 19-30 to 19-26. Also, removed logic stating that if surgery code is 18, then CS Tumor Size Eval must be 0 or 1.</event>
<event version="SE11-001-23" user="greend" date="2009-01-06">Added "2" to CS Tumor Size/Ext Eval codes allowed if RX Summ-Surg Prim Site = 19-26.</event>
<event version="SE12-002-01" user="murphyr" date="2010-02-03">Added skip condition "RX Summ--Surg Prim Site is blank".</event>
<event version="SE12-002-04" user="murphyr" date="2010-07-21">Added if RX Summ-Surg Prim Site is 22 than CS Tumor Size Eval muat be 0 or 1. Edit now uses schema name instead of just site.</event>
<event version="SE12-005-08" user="murphyr" date="2011-12-15" ref="66603">Changed documentation. Added logic for eval values 4, 5 and 6</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-020-01" user="depryf" date="2020-02-04" ref="68281">Changed property names to align with NAACCR XML IDs.</event>
</history>
</rule>