Add instructions to collect needed participant information for GUIDs if upload to NDA is expected #26
Description
guid tool says following fields supported for batch generation
Supported PII Fields:
- FIRSTNAME -- Complete legal given FIRST name of the subject at birth
- SUBJECTHASMIDDLENAME -- When the subject has a legal given MIDDLE name enter YES else enter NO
- MIDDLENAME -- Complete legal given MIDDLE name of the subject at birth (If applicable)
- LASTNAME -- Complete legal given LAST name of the subject at birth
- MOB -- Subject's month of birth
- DOB -- Subject's day of birth
- YOB -- Subject's year of birth
- COB -- Name of CITY/MUNICIPALITY in which the subject was born
- SEX -- Physical SEX of the subject at birth
- GUID -- The invalid GUID (pseudoGUID) to convert. The field is only applicable when converting pseudoGUID(s).
- USEEXEISTINGGUID -- When a close match for your subject is found, this other subject matches all data fields
except one of first name, middle name, year of birth or community of birth. For this field enter NO to create a new
GUID or YES to use a matching subjects GUID if found. This field is NOT applicable to batch operations.
Batch operations CSV file format details:
The first line of the file should contain column names separated by commas. The allowed PII fields are the same as
defined above, with the addition of a required ID (number) field. The IDs are used in the GUID output to map from
the original subject to each generated GUID.
Example batch CSV data to create GUIDs:
ID,FIRSTNAME,MIDDLENAME,LASTNAME,MOB,DOB,YOB,SEX,COB,SUBJECTHASMIDDLENAME
1,John,Quincy,Adams,12,31,1988,M,Roanoke,YES
2,Jane,,Smith,11,24,1900,F,Baltimore,NO
note that COB is required