________________________________
From: Nadkarni, Prakash [[email protected]]
Sent: Thursday, February 19, 2015 4:06 PM
To: Dan Connolly
Subject: Possible bugs in SEER_Recode.sql
We've been using the code in SEER_Recode.sql to add the SEER classification to 
our ETL, and we applied it to our registry data, and then eyeballed the 
"invalid" (99999) entries. (We've rewritten it to make it table-driven, to 
avoid a giant case statement and use indexing on the histology and site to 
rapidly narrow down the possibilities.)

The original code appears to have the following glitches:
1. Lines 188-191

 Peritoneum, Omentum and Mesentery */ when (site between 'C481' and 'C482')
and  not
(histology between '9050' and '9055'

   or histology = '9140'

   or histology between '9590' and '9992')
then '21120'


This has the effect of flagging mesothelioma (range 9050-9055) of the 
peritoneum as invalid, which is wrong. (Try Googling "mesothelioma of 
peritoneum - one of the hits you get is 
http://www.mesothelioma.com/mesothelioma/types/peritoneal.htm

2. Lines 236-240
   /* Soft Tissue including Heart */ when (site = 'C380'or site between 'C470' 
and 'C479'

   or site between 'C490' and 'C499')

  and  not (histology between '9050' and '9055'

   or histology = '9140'

   or histology between '9590' and '9992') then '24000'

As in the above case, this flags mesothelioma (range 9050-9055) of the 
pericardium (C380) as invalid - also wrong. See
http://www.asbestos.com/mesothelioma/pericardial.php

I believe the fix in both cases is to remove the range 9050-9055 from the check.

Prakash




________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.
________________________________
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to