real DOB

The DOB column comes from GDIT's documentation; presumably they use it along 
with SSN and HIC to match their patient records.

And yes, those are the right fields. (I'm not sure why we didn't organize 
documentation in that format. Oh well...)

--
Dan

________________________________
From: Gpc-dev [[email protected]] on behalf of French, Tony 
[[email protected]]
Sent: Wednesday, January 25, 2017 5:42 PM
To: Sravani Chandaka; '<[email protected]>'
Subject: GROUSE Finder File - DOB

Should the DOB values be offset to match our I2B2 and CDM data or is it 
supposed to be the actual DOB?

The Finder file should have all of the following fields, correct?

PATIENT_NUM:      Patient Identifier that aligns with our I2B2 and CDM data
SSN:              Social Security Number with no hyphens
GENDER:           M, F, or 0
DOB:              Offset or not Offset???   Format=mm/dd/yyyy
HIC:              Medicare beneficiary’s identification number
PATIENT_NUM_HASH: Hashed version of PATIENT_NUM per the grouse/obfuscate.py 
output.


Thanks,
Tony


Tony French  |  Software Development Manager
                               Tools and Shared Resources
                               Center for Biomedical Informatics
[cid:[email protected]]
1101 West Tenth Street
Indianapolis, IN, 46202
Tel 317-274-9087 | Fax: 317-274-9305
Twitter: @Regenstrief  |  
Facebook.com/regenstriefinstitute<http://facebook.com/regenstriefinstitute>
www.regenstrief.org<http://www.regenstrief.org/>

Confidentiality Notice: The contents of this message and any files transmitted 
with it may contain confidential and/or privileged information and are intended 
solely for the use of the named addressee(s). Additionally, the information 
contained herein may have been disclosed to you from medical records with 
confidentiality protected by federal and state laws. Federal regulations and 
State laws prohibit you from making further disclosure of such information 
without the specific written consent of the person to whom the information 
pertains or as otherwise permitted by such regulations. A general authorization 
for the release of medical or other information is not sufficient for this 
purpose.
If you have received this message in error, please notify the sender by return 
e-mail and delete the original message. Any retention, disclosure, copying, 
distribution or use of this information by anyone other than the intended 
recipient is strictly prohibited.

_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to