Philip, A quick comment on hashing MRN/encounter numbers: some institutes used an encryption algorithm to convert those numbers into a string. It seems more reliable than simple hash table.
Looking forward to some best practice used by others! Simon ================================================== Simon Lin, MD | Director, Biomedical Informatics Research Center | Marshfield Clinic Research Foundation | 1000 N Oak Ave, Marshfield, WI 54449 | 715-221-7299 | [email protected]<mailto:[email protected]> | www.marshfieldclinic.org/birc<http://www.marshfieldclinic.org/birc> For scheduling assistance, please contact Crystal Gumz, Administrative Secretary | 715-221-6403 | [email protected]<mailto:[email protected]> From: [email protected] [mailto:[email protected]] On Behalf Of Dan Connolly Sent: Monday, March 03, 2014 1:00 PM To: Phillip Reeder; Greater Plains Collaborative Software Development Subject: Re: [Gpc-dev] De-Identification Plan No, I'm not aware of a good example. Your suggested approach seems fine to me. I've assigned #73<http://informatics.gpcnetwork.org/trac/Project/ticket/73> to you to get the ball rolling; assign it to somebody else if that doesn't make sense or when you've done what you can think of doing -- Dan ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]] on behalf of Phillip Reeder [[email protected]] Sent: Monday, March 03, 2014 11:12 AM To: Greater Plains Collaborative Software Development Subject: [Gpc-dev] De-Identification Plan Dan, With regard to de-identification plan, is there an example out there of what they are looking for? If not, I think we should write up something simple as a starting point to use for the discussion. I'm assuming that the majority of how we will de-identify our data sets will be easy to agree to. For example, following safe harbor to remove 18 identifier, hashing MRN/encounter numbers, shifting dates, truncating zips, etc. We might have some good discussions on how we do some of these things, but it should be pretty easy to agree what we need to do them. Phillip From: Dan Connolly <[email protected]<mailto:[email protected]>> Reply-To: Greater Plains Collaborative Software Development <[email protected]<mailto:[email protected]>> Date: Monday, March 3, 2014 9:42 AM To: Greater Plains Collaborative Software Development <[email protected]<mailto:[email protected]>> Subject: Re: [Gpc-dev] Agenda items for Tuesday 3/4/14 Do you want to go ahead and chair this week's meeting? This looks like too much stuff for an hour. And things like the de-identification plan (#73<http://informatics.gpcnetwork.org/trac/Project/ticket/73>) are due to PCORI long before quality approaches (milestone:data-quality-plan<http://informatics.gpcnetwork.org/trac/Project/milestone/data-quality-plan>). So if I chair, I'm likely to decline a number of these suggestions. But I don't think anything is so urgent that it can't wait a week, so I'm fine with you chairing this week. You'd need to coordinate with Brittany about gotomeeting stuff, I suppose. -- Dan ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] on behalf of Campbell, James R [[email protected]<mailto:[email protected]>] Sent: Monday, March 03, 2014 5:55 AM To: [email protected]<mailto:[email protected]> Subject: [Gpc-dev] Agenda items for Tuesday 3/4/14 Hackathon minutes review Review of standardization principles and project plan from Hackathon Discussion of Visit dimension attributes Discussion of provider dimension: licensure and role Agenda discussion for Quality Assurance subcommittee and project planning Discussion of Diagnosis modifiers for data attribution; team input on pathologic diagnoses, radiologic diagnoses and lab diagnoses The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender. ________________________________ UT Southwestern Medical Center The future of medicine, today. ______________________________________________________________________ The contents of this message may contain private, protected and/or privileged information. If you received this message in error, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained within. Please contact the sender and advise of the erroneous delivery by return e-mail or telephone. Thank you for your cooperation.
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
