speaking of titles that hide work... -- Dan
________________________________ From: Carnahan, Ryan M [ryan-carna...@uiowa.edu] Sent: Tuesday, May 22, 2018 9:45 AM To: Russ Waitman; Dan Connolly; ,; 'GPC-DEV@LISTSERV.KUMC.EDU'; Tamara McMahon Cc: McDowell, Bradley D Subject: RE: gpc-dev / RCR 22 May agenda and meeting notes... RCR question: Date shift and annotated data dictionaries Thanks, Russ. I just scanned this ticket and realized the responses from sites to the death data survey questions are toward the bottom. I didn’t expect to find it in this ticket based on the title. It looks like we have responses from everyone but Vanderbilt (I know KUMC has SS data). I can reach out to the folks at Vanderbilt separately. That just leaves the date shifting question for the dev call. Ryan From: Russ Waitman <rwait...@kumc.edu> Sent: Tuesday, May 22, 2018 8:32 AM To: Dan Connolly <dconno...@kumc.edu>; , <gpc-...@listserv.kumc.edu>; 'GPC-DEV@LISTSERV.KUMC.EDU' <GPC-DEV@LISTSERV.KUMC.EDU>; Tamara McMahon <tmcma...@kumc.edu> Cc: McDowell, Bradley D <bradley-mcdow...@uiowa.edu>; Carnahan, Ryan M <ryan-carna...@uiowa.edu> Subject: RE: gpc-dev / RCR 22 May agenda and meeting notes... RCR question: Date shift and annotated data dictionaries Hi Dev, Tamara, and Dan, Could this be added briefly to the agenda for RCR based on the RCR exec call this am? For the RCR Aim 1, Ryan is trying to understand sites death source integration (https://informatics.gpcnetwork.org/trac/Project/ticket/662 ) and date shifting to see which sites could be reliably be used for a survival analysis. If they didn’t have an external death source and only had local EMR info on death, using their death status would be questionable. For death, he will reference that ticket and the CDM Death table attributes. The other issue is date shifting and in particular if anyone shifts into the future. I can’t recall if this is documented on our site. If not, can you bring up on the call or sites could share their Annotated Data Dictionary responses to the questions obfuscate_yn other_questions yesno Do you obfuscate any dates (as documented in the HARVEST table)? obfusc_consistent other_questions yesno Are all dates obfuscated consistently for the same PATID (Answer yes if the only BIRTH_DATE is treated differently)? obfusc_txt other_questions notes Please provide describe your obfuscation process. Apologies if this is on a quick link on our sites. Russ From: Gpc-dev <gpc-dev-boun...@listserv.kumc.edu<mailto:gpc-dev-boun...@listserv.kumc.edu>> On Behalf Of Dan Connolly Sent: Monday, May 21, 2018 10:36 AM To: , <gpc-...@listserv.kumc.edu<mailto:gpc-...@listserv.kumc.edu>>; , <gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>> Subject: gpc-dev / RCR 22 May agenda and meeting notes Anything in particular for tomorrow's agenda? * 22 May gpc-dev/Cancer RCR Meeting Notes by MU<https://docs.google.com/document/d/1e_oY6d4dP0Egw3CnzcYUo_6mzyjw90oO3jKBh4CPLXQ/edit> RCR Aim 1 stuff (#704<https://informatics.gpcnetwork.org/trac/Project/ticket/704>) preempts my usual filtering through the 4 sources of agenda items, so the current snapshot lacks some detail: ________________________________ 1. 2. 3. Convene, take roll, review records 4. and plan next meeting(s) 1. 6. * b. c. 11:00am Central Time. d. Meeting<https://global.gotomeeting.com/meeting/join/817393381> e. ID and access code: 817-393-381<https://global.gotomeeting.com/meeting/join/817393381>; f. call +1 (571) 317-3131 * * i. j. Roll; comments on the agenda? k. (ref l. SoftwareDev#tracking<https://informatics.gpcnetwork.org/trac/Project/wiki/SoftwareDev#tracking>) m. Reminder - put site after n. your name in GoToMeeting preferences * p. * ii. iii. all 12 GPC iv. DevTeams<https://informatics.gpcnetwork.org/trac/Project/wiki/DevTeams> v. represented? KUMC, CMH, UIOWA, WISC, MCW, MCRF/MCRI, UMN, UNMC, UTHSCSA, UTSW, MU, IU * * viii. ix. Cancer RCR project sites? UFL, x. VUMC, MUSC * * xiii. xiv. Today's scribe: xv. MU * * * s. t. Comments on last week’s notes? u. (#12<https://informatics.gpcnetwork.org/trac/Project/ticket/12>) v. Recent<https://informatics.gpcnetwork.org/trac/Project/timeline> w. tickets opened/closed<https://informatics.gpcnetwork.org/trac/Project/timeline> x. - FYI (i.e. not intended for discussion) * z. * ii. iii. #589<https://informatics.gpcnetwork.org/trac/Project/ticket/589#comment:4> iv. (principal diagnosis 10% threshold in PCORNet CDM) closed <https://informatics.gpcnetwork.org/trac/Project/ticket/589#comment:4> worksforme * * * cc. dd. Next meeting(s): May 29; Scribe: ee. KUMC? MCW? ff. Note gg. scribe<https://docs.google.com/document/d/1ttXUveymyAZ9Hs0c84LXPjgHgz1bJ2IOaytuN3uJHjE/edit#heading=h.7048noacdrce> hh. rotation appendix<https://docs.google.com/document/d/1ttXUveymyAZ9Hs0c84LXPjgHgz1bJ2IOaytuN3uJHjE/edit#heading=h.7048noacdrce> * 1. 1. 2. 3. stuff from last week (15<http://listserv.kumc.edu/pipermail/gpc-dev/2018q2/004674.html> 4. May<http://listserv.kumc.edu/pipermail/gpc-dev/2018q2/004674.html>) (#12<https://informatics.gpcnetwork.org/trac/Project/ticket/12>) 1. 2. 7. 8. stuff from 9. tickets<https://informatics.gpcnetwork.org/trac/Project/wiki/SoftwareDev#tracking> 10. by milestone<https://informatics.gpcnetwork.org/trac/Project/wiki/SoftwareDev#tracking> 1. 2. 13. 14. stuff from 15. gpc-dev<https://informatics.gpcnetwork.org/trac/Project/timeline> 16. email<https://informatics.gpcnetwork.org/trac/Project/timeline> 1. 2. 19. 20. new/closed/reopened<https://informatics.gpcnetwork.org/trac/Project/timeline> 21. tickets<https://informatics.gpcnetwork.org/trac/Project/timeline> 1. ________________________________ -- Dan
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
