Dan – Please see the our IRB approved protocol attached. Best, Charon
From: Kho, Abel [mailto:abel....@nm.org] Sent: Monday, December 05, 2016 4:00 PM To: Dan Connolly <dconno...@kumc.edu>; Al'ona Furmanchuk <alona.furmanc...@northwestern.edu>; Charon Gladfelter <charon.gladfel...@northwestern.edu> Cc: <gpc-dev@listserv.kumc.edu> <gpc-dev@listserv.kumc.edu>; Bernard Black <bbl...@kellogg.northwestern.edu> Subject: Re: NEXT-D: de-identified encounter dates? excellent thanks Dan, I think we can make this work then. Abel ________________________________ From: Dan Connolly <dconno...@kumc.edu<mailto:dconno...@kumc.edu>> Sent: Monday, December 5, 2016 3:55 PM To: Kho, Abel; Furmanchuk, Al'ona (NU); Gladfelter, Charon (NU) Cc: <gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>>; Black, Bernard (NU) Subject: RE: NEXT-D: de-identified encounter dates? This is part of the GPC-wide answer to 3.14 Approaches to securely de-identify and re-identify patient data (#73<https://urldefense.proofpoint.com/v2/url?u=https-3A__informatics.gpcnetwork.org_trac_Project_ticket_73&d=CwMFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=QOQHWZx5Sz-AJWb90mGVpWfx_Df9M7se1epOO0F-axK5RyvV5G_k4hmNabWop33j&m=jyf9HYudLf5aCsV0HDlb5phlOHitdjzZEMMHsJ28zYY&s=5egn-VrKXAhsm25ttOR5NqRJU6LTNGKejQTA0Lglm-k&e=>): All dates will be obscured by applying a random (-1 to -365 day) date shift. This shift will be consistent on a per patient basis. I.e. all dates on a single patient will have the same date offset. As a rule, we don't do it across institutions. For that, one leaves the realm of the general GPC de-identified data sharing agreement<https://urldefense.proofpoint.com/v2/url?u=https-3A__informatics.gpcnetwork.org_trac_Project_wiki_GovernanceMaterials-23DSA&d=CwMFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=QOQHWZx5Sz-AJWb90mGVpWfx_Df9M7se1epOO0F-axK5RyvV5G_k4hmNabWop33j&m=jyf9HYudLf5aCsV0HDlb5phlOHitdjzZEMMHsJ28zYY&s=W-tooUjTOr2s7Rm7-A1OwxTsr0UZH_vpFOpQ1uAhJH8&e=> and enters the realm of a separate IRB approved protocol*, for example for GROUSE<https://urldefense.proofpoint.com/v2/url?u=https-3A__informatics.gpcnetwork.org_trac_Project_wiki_GROUSE&d=CwMFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=QOQHWZx5Sz-AJWb90mGVpWfx_Df9M7se1epOO0F-axK5RyvV5G_k4hmNabWop33j&m=jyf9HYudLf5aCsV0HDlb5phlOHitdjzZEMMHsJ28zYY&s=ghNto8Q09Xhor068IQI1Jqw4peRC0jJdJ7352UFOK-0&e=>. We haven't fully addressed any of our record-linkage issues<https://urldefense.proofpoint.com/v2/url?u=https-3A__informatics.gpcnetwork.org_trac_Project_query-3Fkeywords-3D-7Erecord-2Dlinkage-26col-3Did-26col-3Dsummary-26col-3Dkeywords-26col-3Dstatus-26col-3Downer-26col-3Dtype-26col-3Dpriority-26order-3Dpriority&d=CwMFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=QOQHWZx5Sz-AJWb90mGVpWfx_Df9M7se1epOO0F-axK5RyvV5G_k4hmNabWop33j&m=jyf9HYudLf5aCsV0HDlb5phlOHitdjzZEMMHsJ28zYY&s=cxMNHYmM247BmPXvD_J2l_kkCidfyPCYQD5sWJ0EudA&e=> yet. * As I mentioned earlier, it would be handy if we could all refer to the NEXT-D IRB protocol somewhere. -- Dan ________________________________ From: Kho, Abel [abel....@nm.org] Sent: Monday, December 05, 2016 3:35 PM To: Furmanchuk, Al'ona (NU); Dan Connolly; Gladfelter, Charon (NU) Cc: <gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>>; Black, Bernard (NU) Subject: Re: NEXT-D: de-identified encounter dates? Can we ask how you apply the date shift (we also date shift in CAPriCORN). Do you apply the same date shift consistently for all dates for a given patient? How do you apply the date shift across a institution? Is it consistently the same date shift for the whole population or is it a random date shift for each individual patient in the population? Thanks, Abel ________________________________ From: furmanc...@icnanotox.org<mailto:furmanc...@icnanotox.org> <furmanc...@icnanotox.org<mailto:furmanc...@icnanotox.org>> on behalf of Al'ona Furmanchuk <alona.furmanc...@northwestern.edu<mailto:alona.furmanc...@northwestern.edu>> Sent: Monday, December 5, 2016 10:35 AM To: Dan Connolly; Gladfelter, Charon (NU) Cc: Kho, Abel; <gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>>; Black, Bernard (NU) Subject: Re: NEXT-D: de-identified encounter dates? Technically, shifting is not a problem if we would know how it was applied (including values used for shifting). To be sure we are covered by official protocols, I am sending this to Charon. She will check approvals for the study and get back to all of us. On Mon, Dec 5, 2016 at 9:38 AM, Dan Connolly <dconno...@kumc.edu<mailto:dconno...@kumc.edu>> wrote: The PCORNet CDM at KUMC is built from our de-identified i2b2. So that means the queries in NextDextractionCode_12.1.16.sql<https://urldefense.proofpoint.com/v2/url?u=https-3A__informatics.gpcnetwork.org_trac_Project_attachment_ticket_539_NextDextractionCode-5F12.1.16.sql&d=CwMGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=-aRkmw3Ob1oZRrrYmR1wHysw9FWMRlmk_CMIVWKi32KhS_EbXW7cMBGcBAmqh95W&m=r-GiqD_lIFdFgdLEBI4y6C6NZqQNgJv_C_pzhqdkywA&s=79EPcqz-8A6_IfxO-XC14asoMX-GCxiBrXvZtG7_OtU&e=><https://urldefense.proofpoint.com/v2/url?u=https-3A__informatics.gpcnetwork.org_trac_Project_raw-2Dattachment_ticket_539_NextDextractionCode-5F12.1.16.sql&d=CwMGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=-aRkmw3Ob1oZRrrYmR1wHysw9FWMRlmk_CMIVWKi32KhS_EbXW7cMBGcBAmqh95W&m=r-GiqD_lIFdFgdLEBI4y6C6NZqQNgJv_C_pzhqdkywA&s=fnagdNpd6JgHpRRyWABOSdut8et1tZv33u1huzEJAic&e=> are going to get shifted dates. Is that as expected? -- Dan -- Al’ona Furmanchuk, Ph.D. Research Associate Department of Electrical Engineering and Computer Science Northwestern University 2145 Sheridan Road, Tech L359 Evanston, IL 60208 Web: http://furmanchuk.com/<https://urldefense.proofpoint.com/v2/url?u=http-3A__furmanchuk.com_&d=CwMFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=QOQHWZx5Sz-AJWb90mGVpWfx_Df9M7se1epOO0F-axK5RyvV5G_k4hmNabWop33j&m=jyf9HYudLf5aCsV0HDlb5phlOHitdjzZEMMHsJ28zYY&s=kczENAtw92USXjaGBQxX-rMu2a1RH9sU-8MdXTec50w&e=> E-mail: alona.furmanc...@northwestern.edu<mailto:furmanc...@icnanotox.org> Phone: 847-467-2299 This message and any included attachments are intended only for the addressee. The information contained in this message is confidential and may constitute proprietary or non-public information under international, federal, or state laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail. This message and any included attachments are intended only for the addressee. The information contained in this message is confidential and may constitute proprietary or non-public information under international, federal, or state laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail.
Black-Kho-CDC-Next-D Protocol_V1.2_7.26.16_clean.docx
Description: Black-Kho-CDC-Next-D Protocol_V1.2_7.26.16_clean.docx
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
