Skip to content
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

Closed
clairblacketer opened this issue Apr 1, 2024 · 5 comments
Closed

What value should be used to populate gender_concept_id? #94

clairblacketer opened this issue Apr 1, 2024 · 5 comments

Comments

@clairblacketer
Copy link
Collaborator

clairblacketer commented Apr 1, 2024

What value should be used to populate gender_concept_id?

CDM or THEMIS convention?

THEMIS

Is this a general convention?

No

Summary of issues

  • 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?

Summary of answer

  • Gender_concept_id should hold the standard concept representing the patient's assigned sex at birth

Related links

Other comments/notes

  • This is challenging because of different cultural understanding of sex at birth, legal sex, genetic sex, and gender identity. Most sources will just have one value for a patient's sex so that can be used as the gender_concept_id with the understanding that it may not be assigned sex at birth.
@clairblacketer clairblacketer self-assigned this Apr 1, 2024
@askanter
Copy link

askanter commented Apr 4, 2024

So the title is even misleading since this really is about how to store the biological sex :)

@clairblacketer
Copy link
Collaborator Author

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

@clairblacketer clairblacketer changed the title How to store gender identity What value should be used to populate gender_concept_id? Apr 4, 2024
@clairblacketer
Copy link
Collaborator Author

@askanter I am going to open a second one specifically about gender identity

@MelaniePhilofsky
Copy link
Collaborator

MelaniePhilofsky commented Apr 5, 2024

Issue # and location

Forum

Format as follows:

Issue summary

he 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

Links to location of discussion on forums, CDM GitHub, Themis GitHub, etc.

Format as follows:

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

No

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.

#Tags
Sex, gender, gender identity

@clairblacketer clairblacketer removed their assignment Apr 9, 2024
clairblacketer added a commit that referenced this issue Apr 10, 2024
@clairblacketer
Copy link
Collaborator Author

opened PR #114

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants