ID assignment standards

[edilbertoamorim]

We would like to get ideas about how IDs should be assigned to patients locally at each CHORUS site, so it is easier to put everything together for the central repository. This would also involve methods involving lookup table creation that have PHI locally and not available to CHORUS, so unwarranted re-identification is not possible within each center.

[clermontg]

At our 1-1 with Standards office hours, it was conveyed to us that sites should have full freedom to assign their person_id's. These will be reassigned centrally anyways.

[JXu768]

@clermontg is there limit on how many digits we can use in the person_ID? Our current naming convention has 19 digits.

[clermontg]

We are limited to the length of the person_id field in the OMOP PERSON schema, which I am pretty sure is int(11). Please verify though. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: JXu768 ***@***.***> Sent: Tuesday, January 30, 2024 5:01:22 PM To: chorus-ai/data_acq_SOP ***@***.***> Cc: Clermont, Gilles ***@***.***>; Mention ***@***.***> Subject: Re: [chorus-ai/data_acq_SOP] ID assignment standards (Discussion #12) @clermontg<https://github.com/clermontg> is there limit on how many digits we can use in the person_ID? Our current naming convention has 19 digits. — Reply to this email directly, view it on GitHub<#12 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL33RKSNLOCENOF7FFV2ESLYRFUTFAVCNFSM6AAAAAA5LKVOAGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGMJRHAYDI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[clermontg]

More information: If you already have a 19 digit person identifier, the suggestion is to keep this identifier in the the person_source_value varchar(50) field in your local version. You DO NOT need to export this person_source_value field to CHoRUS. In fact, it could be construed as PHI. Whether it is construed as PHI does depend on local security rules. So, you can push data with this field as NULL. The person_id field has to be an int(11) of your creation. Your local copy of PERSON needs to include both so it could be linked back if there are problems. The same applies to visit_occurence_id From: JXu768 ***@***.***> Sent: Tuesday, January 30, 2024 5:01 PM To: chorus-ai/data_acq_SOP ***@***.***> Cc: Clermont, Gilles ***@***.***>; Mention ***@***.***> Subject: Re: [chorus-ai/data_acq_SOP] ID assignment standards (Discussion #12) @clermontg<https://github.com/clermontg> is there limit on how many digits we can use in the person_ID? Our current naming convention has 19 digits. - Reply to this email directly, view it on GitHub<#12 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL33RKSNLOCENOF7FFV2ESLYRFUTFAVCNFSM6AAAAAA5LKVOAGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGMJRHAYDI>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>