Issue # and location
Issue summary
The 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 type
Table
CDM table
PERSON
CDM field
gender_concept_id
Links to issue discussion
Provenance of data
All data
The ratified convention
PERSON.gender_concept_id should hold the standard concept representing the patient’s assigned sex at birth
Date of ratification/published
NA
Downstream implications
NA
Link to DQD check
isRequired cdmDatatype isForeignKey fkDomain isStandardValidConcept standardRecordConceptCompleteness
Related conventions/further information
If the source data captures gender identity it should be stored in the OBSERVATION table. See the gender identity convention for more information.