See also Nov 7 discussion. http://listserv.kumc.edu/pipermail/gpc-dev/2014q4/000778.html
-- Dan ________________________________________ From: gpc-dev-boun...@listserv.kumc.edu [gpc-dev-boun...@listserv.kumc.edu] on behalf of Bushee, Glenn [gbus...@mcw.edu] Sent: Friday, January 16, 2015 1:29 PM To: Tim Meyer; gpc-dev@listserv.kumc.edu Subject: Re: NAACCR dates in i2b2 Tim, thank you for the reminder on this — I knew that there was something I forgot to note for our data set. For the 4 date fields, we populated the UPDATE_DATE field in the OBSERVATION_FACT table to contain the referenced data from the underlying de-identified NAACCR source. This applied to: NAACCR|1750 NAACCR|390 NAACCR|1860 NAACCR|240 - Glenn Medical Informatics Senior Analyst CTSI – Clinical & Translational Science Institute gbus...@mcw.edu (414) 805-7239 From: Tim Meyer <tme...@umn.edu<mailto:tme...@umn.edu>> Date: Friday, January 16, 2015 at 1:18 PM To: "gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>" <gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>> Subject: NAACCR dates in i2b2 I'm wondering how other sites are representing dates from NAACCR in i2b2. At UMN all our observation_fact records from NAACCR are loaded with a start_date of the date_of_diagnosis. We are also loading facts that have concept_cd values like "NAACCR:390|YYYYMMDD" for all 3 date fields. I appreciate any input that can be provided. Thanks, -- Tim Meyer Programmer / Analyst Academic Health Center - Information Systems Phone: 612.624.8386 tme...@umn.edu<mailto:tme...@umn.edu> _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev