Hi Dan,
If you mean you have NAACCR data with the same date shift as the data provided
via the RCR SAS query then that should be fine. Another route would be to
provide the relative differences in date shifts for each person in the original
NAACCR finder file vs. the SAS data sets returned by the query. This may be
more complicated than just providing NAACCR data with the same date shift as
the SAS files, in which case it's not necessary.
Thanks,
Ryan
-----Original Message-----
From: GPC Informatics <d...@madmode.com>
Sent: Thursday, June 21, 2018 5:38 PM
To: Gryzlak, Brian M <brian-gryz...@uiowa.edu>; dconno...@kumc.edu
Cc: Carnahan, Ryan M <ryan-carna...@uiowa.edu>; catec...@kumc.edu;
rwait...@kumc.edu; tmcma...@kumc.edu
Subject: Re: [gpc-informatics] #705: KUMC CDM-NAACCR death date mismatch
#705: KUMC CDM-NAACCR death date mismatch
-----------------------+---------------------------
Reporter: bgryzlak | Owner: bgryzlak
Type: problem | Status: assigned
Priority: major | Milestone: cancer-rcr-1
Component: data-stds | Resolution:
Keywords: | Blocked By:
Blocking: |
-----------------------+---------------------------
Changes (by dconnolly):
* cc: dconnolly (added)
* owner: dconnolly => bgryzlak
* status: new => assigned
Comment:
I can provide NAACCR data corresponding to the recently submitted CDM DEATH
table (based on HERON Calamus). Does that help?
It seems to match pretty well:
Of about 16K in the cohort, around 3300 are recorded as dead in both CDM
DEATH and NAACCR; over 3200 of the death dates match; the distribution in the
number of digits in the difference (DELTA_LOG10) is as follows:
||=DELTA_LOG10 =||=COUNT(*)
||0 ||3214
||1 ||65
||2 ||25
||3 ||8
||4 ||1
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/705#comment:2>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
