edits.seer.internal.rules.IF271.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="IF271" name="Obsolete Codes - CS Tumor Size/Ext Eval (CS)" tag="N1259" java-path="lines.line" category="inter-field" depends="CS_Tumor_Size_Ext_Eval,CS_Version_Input_Original,Year_of_Diagnosis">
<expression><![CDATA[if (line.csTumorSizeExtEval == null || line.dateOfDiagnosisYear == null || line.csVersionInputOriginal == null)
return true
if (line._csSchemaId == null)
return false
String code = Functions.getCsObsoleteReason(line, 'csTumorSizeExtEval', line.csTumorSizeExtEval)
if (code != null) {
if (code == '1' || code == '5' || code == '6' || code == '7' || code == '16' || code == '18') {
if (line.dateOfDiagnosisYear >= '2010')
return false
if (line.csVersionInputOriginal >= '020100')
return false
}
else if (code == '13' || code == '14' || code == '15') {
if (line.dateOfDiagnosisYear >= '2011')
return false
if (line.csVersionInputOriginal >= '020300')
return false
}
else if (code == '17') {
if (line.dateOfDiagnosisYear >= '2011')
return false
if (line.csVersionInputOriginal >= '020200')
return false
}
else if (code == '21' || code == '22') {
if (line.dateOfDiagnosisYear >= '2012')
return false
if (line.csVersionInputOriginal >= '020440')
return false
}
else
return false
}
return true]]></expression>
<message>Obsolete Codes - Invalid CS Tumor Size/Ext Eval</message>
<description><![CDATA[This edit checks for all obsolete CS Tumor Size Ext/Eval codes. Obsolete codes
should be re-coded per Collaborative Stage guidelines.
This edit is skipped if any of the following coditions are true:
1. CS Tumor Size/Ext Eval is empty.
2. Year of Diagnosis is blank.
3. CS Version Input Original is blank.
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.
Using the returned schema name, CS table number (CS Tumor Size/Ext Eval is table
number 3, and CS Tumor Size/Ext Eval code, a table lookup is performed. If the
code for a particular schema is determined to be obsolete based on the table
lookup, the type of obsolete code must be evaluated. There are several types of
obsolete codes:
1. OBSOLETE DATA CONVERTED AND RETAINED V0200
2. OBSOLETE DATA CONVERTED V0102
3. OBSOLETE DATA CONVERTED V0104
4. OBSOLETE DATA CONVERTED V0200
5. OBSOLETE DATA RETAINED V0100
6. OBSOLETE DATA RETAINED V0102
7. OBSOLETE DATA RETAINED V0200
8. OBSOLETE DATA REVIEWED AND CHANGED V0102
9. OBSOLETE DATA REVIEWED AND CHANGED V0103
10. OBSOLETE DATA REVIEWED AND CHANGED V0200
11. OBSOLETE DATA CONVERTED V0203
12. OBSOLETE DATA REVIEWED AND CHANGED V0203
13. OBSOLETE DATA REVIEWED V0203
14. OBSOLETE DATA RETAINED AND REVIEWED V0203
15. OBSOLETE DATA RETAINED V0203
16. OBSOLETE DATA RETAINED V0104
17. OBSOLETE DATA RETAINED V0202
18. OBSOLETE DATA RETAINED AND REVIEWED V0200
19. OBSOLETE DATA CONVERTED V0204
20. OBSOLETE DATA REVIEWED AND CHANGED V0204
21. OBSOLETE DATA RETAINED AND REVIEWED V0204
22. OBSOLETE DATA RETAINED V0204
1. If the type of obsolete code = OBSOLETE DATA CONVERTED AND RETAINED V0200:
EditWriter - NAACCR_v12_EW4 Edit Detail Report 2/18/2010 10:40:04 AM
Obsolete Codes - CS Tumor Size/Ext Eval (CS) (continued)
A. If Year Of Diagnosis is 2010 or higher
an error is generated.
B. If CS Version Input Original is 020100 or greater (indicating the case was originally
coded using CSv2), an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
2. If the type of obsolete code = OBSOLETE DATA CONVERTED V0102:
an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
3. If the type of obsolete code = OBSOLETE DATA CONVERTED V0104:
an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
4. If the type of obsolete code = OBSOLETE DATA CONVERTED V0200:
an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
5. If the type of obsolete code = OBSOLETE DATA RETAINED V0100:
A. If Year Of Diagnosis is 2010 or higher
an error is generated.
B. If CS Version Input Original is 020100 or greater (indicating the case was originally
coded using CSv2), an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
6. If the type of obsolete code = OBSOLETE DATA RETAINED V0102:
A. If Year Of Diagnosis is 2010 or higher
an error is generated.
B. If CS Version Input Original is 020100 or greater (indicating the case was originally
coded using CSv2), an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
7. If the type of obsolete code = OBSOLETE DATA RETAINED V0200:
A. If Year Of Diagnosis is 2010 or higher
an error is generated.
B. If CS Version Input Original is 020100 or greater (indicating the case was originally
coded using CSv2), an error is generated.
[Example: Schema = MelanomaEyeOther, CS Tumor Size/Ext Eval = 0]
8. If the type of obsolete code = OBSOLETE DATA REVIEWED AND CHANGED V0102:
an error is generated.
(Obsolete codes from CSV01 are expected to have been recoded prior to conversion
to CSV02.)
[Example: none for CS Tumor Size/Ext Eval]
9. If the type of obsolete code = OBSOLETE DATA REVIEWED AND CHANGED V0103:
an error is generated.
(Obsolete codes from CSV01 are expected to have been recoded prior to conversion
to CSV02.)
[Example: none for CS Tumor Size/Ext Eval]
10.If the type of obsolete code = OBSOLETE DATA REVIEWED AND CHANGED V0200:
an error is generated.
(These particular obsolete codes require review after conversion from CSV01 to
CSV02.)
[Example: none for CS Tumor Size/Ext Eval]
11. If the type of obsolete code = OBSOLETE DATA CONVERTED V0203:
an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
12. If the type of obsolete code = OBSOLETE DATA REVIEWED AND CHANGED V0203:
an error is generated.
(These particular obsolete codes require review after conversion from CSV02xx to CSV0203.)
[Example: none for CS Tumor Size/Ext Eval]
13. If the type of obsolete code = OBSOLETE DATA REVIEWED V0203:
A. If year of Diagnosis is 2011 or higher, an error is generated.
B. If CS version Input Original is 020300 or higher (indicating the case was originally coded using CSv0203), an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
14. If the type of obsolete code = OBSOLETE DATA RETAINED AND REVIEWED V0203:
A. If year of Diagnosis is 2011 or higher, an error is generated.
B. If CS version Input Original is 020300 or higher (indicating the case was originally coded using CSv0203), an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
15. If the type of obsolete code = OBSOLETE DATA RETAINED V0203:
A. If year of Diagnosis is 2011 or higher, an error is generated.
B. If CS version Input Original is 020300 or higher (indicating the case was originally coded using CSv0203), an error is generated.
[Example: none for CS Tumor Size/Ext Eval]
16. If the type of obsolete code = OBSOLETE DATA RETAINED V0104:
A. If year of Diagnosis is 2010 or higher, an error is generated.
B. If CS version Input Original is 020100 or higher (indicating the case was originally coded using CSv02), an error is generated.
17. If the type of obsolete code = OBSOLETE DATA RETAINED V0202:
A. If year of Diagnosis is 2011 or higher, an error is generated.
B. If CS version Input Original is 020200 or higher (indicating the case was originally coded using CSv0202), an error is generated.
18. If the type of obsolete code = OBSOLETE DATA RETAINED AND REVIEWED V0200:
A. If year of Diagnosis is 2010 or higher, an error is generated.
B. If CS version Input Original is 020100 or higher (indicating the case was originally coded using CSv2), an error is generated.
19. If the type of obsolete code = OBSOLETE DATA CONVERTED V0204:
an error is generated.
20. If the type of obsolete code = OBSOLETE DATA REVIEWED AND CHANGED V0204:
an error is generated.
(These particular obsolete codes require review after conversion from CSV0203xx to CSV0204.)
21. If the type of obsolete code = OBSOLETE DATA RETAINED AND REVIEWED V0204:
A. If year of Diagnosis is 2012 or higher, an error is generated.
B. If CS version Input Original is 020440 or higher (indicating the case was originally coded using CSv0204), an error is generated.
22. If the type of obsolete code = OBSOLETE DATA RETAINED V0204:
A. If year of Diagnosis is 2012 or higher, an error is generated.
B. If CS version Input Original is 020440 or higher (indicating the case was originally coded using CSv0204), an error is generated.]]></description>
<history>
<event version="SE12-002-01" user="murphyr" date="2010-02-17">Edit created.</event>
<event version="SE12-002-01" user="murphyr" date="2010-06-01">The logic for #1,5,6, and 7 was updated with the following: A. If year of diagnosis is 2010 or higher, an error is genereated. B. if CS Version Input Original is 020100 (incidating the case was originally coded using CSv2), an error is generated.</event>
<event version="SE12-002-05" user="murphyr" date="2010-10-08">Edit modified to CS Input Original '>= 020100' instead of '=020100' for cases originally coded using CsV2.</event>
<event version="SE12-004-01" user="murphyr" date="2011-01-25">Updated for CSv2 version 02.03.02.</event>
<event version="SE12-006-01" user="murphyr" date="2011-12-19" ref="66632">Updated for CSv0204 obsolete codes</event>
<event version="SE13-010-01" user="murphyr" date="2013-07-12" ref="66904">Edit now fails if schema is blank.</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> © 2015 - 2024 Weber Informatics LLC | Privacy Policy