-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What value should be used to populate gender_concept_id? #94
Comments
So the title is even misleading since this really is about how to store the biological sex :) |
Yeah that is a good point, I will update the title. I am going back and forth on the gender fields because they are meant to capture sex but really most of the time we get a sex value for a person and we don't know if it is biological sex or gender identity |
@askanter I am going to open a second one specifically about gender identity |
Issue # and locationForum Format as follows: Issue summaryhe term "gender_concept_id" is outdated and really should be "sex_concept_id". Since changing gender_concept_id is a huge lift for developers and package maintainers, this change will be implemented at the next major release. In the meantime, what value should be used to populate gender_concept_id? Convention typeTable CDM tablePerson CDM fieldgender_concept_id Links to issue discussionLinks to location of discussion on forums, CDM GitHub, Themis GitHub, etc. Format as follows: Provenance of dataAll data The ratified conventionPERSON.Gender_concept_id should hold the standard concept representing the patient's assigned sex at birth Date of ratification/publishedNA Downstream implicationsNo Link to DQD checkisRequired Related conventions/further informationIf the source data captures gender identity it should be stored in the OBSERVATION table. #Tags |
opened PR #114 |
What value should be used to populate gender_concept_id?
CDM or THEMIS convention?
THEMIS
Is this a general convention?
No
Summary of issues
Summary of answer
Related links
Other comments/notes
The text was updated successfully, but these errors were encountered: