Perhaps you could back up and explain your overall approach to the NAACCR ETL? 
What code are you using? Where can I look at it? Perhaps you've discussed this 
before, but I don't see any pointers to context in this message. Did you try 
the HERON code? If not, why not? If so, what happened when you tried?

As to this specific question, it's documented on the 
TumorRegistry<https://informatics.kumc.edu/work/wiki/TumorRegistry> page:

We reviewed the data we get by section to eliminate potentially sensitive data, 
including free-text; the sections with a -- below are not loaded into HERON:

followed the relevant code excerpt from 
source:heron_load/naaccr_txform.sql#L67<https://informatics.kumc.edu/work/browser/heron_load/naaccr_txform.sql#L67>​<https://informatics.kumc.edu/work/export/HEAD/heron_load/naaccr_txform.sql#L67>

--
Dan

________________________________
From: gpc-dev-boun...@listserv.kumc.edu [gpc-dev-boun...@listserv.kumc.edu] on 
behalf of Lenon Patrick [ple...@uwhealth.org]
Sent: Monday, March 09, 2015 9:17 AM
To: gpc-dev@listserv.kumc.edu
Subject: NAACCR - Free text fields

In trying to ensure all my Tumor Registry fact table items have corresponding 
concept codes in the Concept Dimension, I found NAACCR item 310 (Text-Usual 
Occupation) which has a format of “Free text.”  As you’d expect there are no 
entries in the NAACCR metadata for that.  However, following the Heron fact 
load code, I created a whole bunch of facts with concept codes like 
“NAACCR|310:(n)TH GRADE TEACHER – (small Wisconsin town) SCHOOL DISTRICT”

To my semi-trained eye this looks like it would be pretty useless to I2B2.  So 
I’m wondering what other sites do in similar situations.  Possibilities that 
have occurred to me already are:

1)      Exclude all “free text” format fields from the fact load.

2)      Leave them in, hoping for codification someday

Is there any reason NOT to exclude free text fields?  Or some criteria to 
include some and exclude others?


Patrick Lenon
HIMC Informatics Specialist
608 890 5671

_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to