A person’s internal sense of being a man, woman, both, or neither.
Applicable Vocabulary Standard(s)
Applicable Standards
Gender Identify must be coded in accordance with SNOMED CT® and HL7 Version 3 Standard, Value Sets for AdministrativeGender and NullFlavor, attributed as follows:
Genderqueer, neither exclusively male nor female. 446131000124102
Additional gender category or other, please specify. nullFlavor OTH
Choose not to disclose. nullFlavor ASKU
Adopted at 45 CFR 170.207(o)(2)
Submitted By: A. Taylor
/ ONC
Data Element Information
Data Element Description
A coded representation of a patient's stated gender identity
Rationale for Separate Consideration
It is important for healthcare providers and staff to record patients’ administrative sex and gender identity separately and accurately. Although administrative sex may affect gender-specific care (e.g., mammograms), a patient's gender identity may also affect care and health outcomes. For example, transgender patients are known to face health disparities, and lack of adherence to preferred names and pronouns can lead to embarrassment and even discrimination in healthcare.
Use Case Description(s)
Use Case Description
Technical outcome – A user can record a patient’s gender identity according to HL7® FHIR R4, HL7® version 3, SNOMED CT®, and LOINC codes specified in the “standard(s) referenced” column. The user must be able to record whether the patient declined to specify gender identity. Note that while gender identity was included in the 2015 Edition “demographics” certification criterion and the 2015 Edition Base EHR definition, it was not included in the Common Clinical Data Set definition. This means that gender identity is not required to be exchanged using certain standards, only that systems enable a user to record, change, and access gender identity. [see also 80 FR 62619].
Estimate the breadth of applicability of the use case(s) for this data element
Users of the 572 certified health IT products, out of 901 total products certified to ONC's 2015 Edition, that successfully tested to the 170.315(a)(5) demographics certification criterion has the ability to record, change, and access gender identity data within these products.
This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders
Extent of exchange
N/A
Potential Challenges
Restrictions on Standardization (e.g. proprietary code)
While it is required under the 2015 Edition 170.315(a)(5) demographics certification criterion to be able to record, change, and access gender identity data, it is not required for exchange. One restriction may be the ability to restrict exchange based on patient consent by element.
Restrictions on Use (e.g. licensing, user fees)
None known
Privacy and Security Concerns
Potential concern due to limited capacity to capture and enforce patient consent by element across the industry at this time.
Estimate of Overall Burden
Already implemented for record, change, and access, but not for exchange.
Addressing health equity tasks through the USCDI in a scope of the SOGI, the USCDI should contain 5 data elements (Gender Identity, Sex assigned at birth, Sexual Orientation, Sex for Clinical Use Note and Patient Pronoun). The last two mentioned data elements were not included into the v.3. We recommend including the Sex for Clinical Use Note (within the Clinical Notes data class) and Patient Pronoun (within the Patient Demographic) into the next, the USCDI v.4 version.
We propose adding the LOINC code 76691-5, Gender Identity, for the Gender Identity question (it was missed in the current v.3)
We suggest updating the value set for Gender Identity responses that has been already included into the Gender Identity data elements by ONC in v.3. Specifically, we suggest adding two more values: Non-Binary (SNOMED 772004004) and Two-Spirit that refers to a person who identifies as having both a masculine and a feminine spirit and is used by some Indigenous people to describe their sexual, gender and/or spiritual identity.
CSTE Comment:
While more work is needed to develop public health community consensus on the best way to collect and exchange data on gender identity, and there is variability in how these data are currently collected by health care as well as by health departments, CSTE supports the use of multiple questions to describe gender identity and sex, specifically Gender Identity and Sex for Clinical Use (a category that is based upon clinical observations typically associated with the designation of male and female). This is the recommendation of the HL7 Gender Harmony project (http://www.hl7.org/implement/standards/product_brief.cfm?product_id=564 http://www.hl7.org/documentcenter/private/standards/HL7_GENDER_R1_INFORM_2021AUG.pdf ). Sex assigned at birth as a term is controversial among members of the LGBTQ community and some individuals opt to correct or revise their sex on a birth certificate.
Values for gender identity should include male, female, nonbinary, exploring or questioning, another not listed (specify), choose not to disclose, and unknown. CSTE recommends that the terms transgender, female to male and transgender male to female be deprecated.
Values for sex for clinical use should include female, male, unknown, and something not listed (specify)
The HL7 Gender Harmony (GH) project today voted to make the following concepts the MINIMUM set of concepts that all GH-conformant systems SHALL support when representing Gender Identity:
From SNOMED CT (International edition in May release, currently in US and Canadian editions):
We want to stress that these concepts are rarely expected to be the only allowed values for systems capturing and representing gender identity. For example the codes currently in the USCDI proposed set can be added to this list. It should be noted that it is our recommendation that systems should not "roll up" concepts they may collect or receive into these minimum values. Each gender identity should be considered unique and independent in meaning. We also expect that addition Null-type codes will be of value in specific systems and requirements, such as USCDI. The GH project will be creating a value set with this minimum set in the near future.
Recommend adding Non-Binary (NCPDP Definition: An umbrella term for people with gender identities that fall somewhere outside of the traditional conceptions of strictly either female or male) as a valid value for Gender Identity to align with the values defined by NCPDP. NCPDP also recommends adding Pronouns (NCPDP Definition: A set of pronouns an individual would like others to use when talking to or about that individual) using the LOINC codes to align with NCPDP identifiers defined.
The options here should be in-line with those discussed by clinicians and researchers here: https://doi.org/10.1093/jamia/ocab136.
Additionally, culturally-specific gender identities such as Two-Spirit, Palao'ana, and Māhū should be included given their specific usage in the United States.
Doing this is in-line with best practices and with the HL7 Gender Harmony Project.
The terms Female-to-Male and Male-to-Female listed here are obsolete and inappropriate. The terms transgender woman, trans woman, transgender man, and trans man are accurate descriptors of medical history but not of gender directly. Binary trans women and men may be correctly identified simply as women and men, without separate categories, and nonbinary trans people as nonbinary. It is widely recognized that listing trans women and trans men as separate categories from women and men results in a harmful and incorrect understanding that binary trans people are not "real" women and men.
The "female to male" and "male to female" terms listed here are obsolete and reflect a transphobic attitude toward trans people. Trans men are men; trans women are women. Their gender identities may be distinct from their status as being trans. It is widely recognized that listing trans women and trans men as separate categories from women and men results in a harmful and incorrect understanding that binary trans people are not "real" women and men.
I would also advocate for inclusion of further categories beyond "Genderqueer". I am nonbinary and agender, and my gender identity is categorically different from that of many other people who could also fall under the umbrella term "genderqueer". Without ways to accurately represent people with diverse gender identities, we lose important information about who Americans are, and what outcomes and experiences people with different genders face. The list of options presented should capture the most information possible while still being accurate, respectful and inclusive.
This question currently does not but should follow the best practices developed in the literature (e.g. https://academic.oup.com/jamia/article/29/2/271/6364772). As a trans person myself, I would select female over the “MTF/transgender female/trangender woman” and I think many people feel the same, so why then is it an option? This way of asking the question implies that transgender women are not “female.” Instead, just ask gender identity (e.g. male, female, non-binary/genderqueer, other, prefer not to reply) and gender assigned at birth (e.g. Male, female, X, prefer not to say) as two separate questions, and then transness can be inferred. Additionally, explicitly including "non-binary" as opposed to just having "genderqueer, neither exclusively ..." as a category would be in line with the best practices as laid out in the literature.
The terms Female-to-Male and Male-to-Female listed here are obsolete and inappropriate. The terms transgender woman, trans woman, transgender man, and trans man are accurate descriptors of medical history but not of gender directly. Binary trans women and men may be correctly identified simply as women and men, without separate categories, and nonbinary trans people as nonbinary. It is widely recognized that listing trans women and trans men as separate categories from women and men results in a harmful and incorrect understanding that binary trans people are not "real" women and men. Please see https://academic.oup.com/jamia/article/29/2/271/6364772 for further discussion.
FTM and MTF are outdated and unnecessary terms, as man/male and woman/female convey the gender of the individual. Additionally, as cis and trans individuals often have the same gender (man or woman), it is redundant and will lead to underestimates of trans individuals who select terms like male/female rather than transgender male/transgender female. This publication can be referenced https://academic.oup.com/jamia/article/29/2/271/6364772. One improvement would be to utilize a two-step question process integrated with assigned sex to determine gender, sex, and gender modality (transgender or cisgender). Another option would be to have multiple selections available, so that an individual can choose a gender and gender modality from the same question's answer choices. This would also accommodate individuals with genders encompassing multiple terms, such as bigender/two-spirit respondents who may want to select multiple gender options.
Revise the data element definition as the following:
Gender identity is an individual's personal sense of being a man, woman, or other gender, regardless of the sex that person was assigned at birth. It should be noted that Gender Identity is something that is expressed by an individual, is not assigned by any other entity (i.e., parent) or clinician.
Revise applicable to the Data Element vocabulary standards as the following:
Gender identity (question). LOINC® code: 76691-5.
List of answers: Findings related to development of sexuality (finding), SNOMED CT ® Code 285116001:
My sense of personal identity and gender corresponds with my birth sex (cisgender), PHIN VADS PHC1490
Identifies as female-to-male transgender (finding) SNOMED CT ® 407377005
Identifies as male-to-female transgender (finding), SNOMED CT ® 407376001
Identifies as non-conforming gender (SNOMED CT (US) synonyms include: Genderqueer;
Identifies as neither exclusively male nor female, Non-binary gender) SNOMED CT® code: 446131000124102
Identifies as Other, HL7 version 3 Null Flavor code OTH or SNOMED CT ® 74964007, Other (qualifier value)
Choose not to disclose, HL7 version 3 Null Flavor code ASKU, Asked but unknown
The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.
If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.
If you are only commenting on a single data class or element, you may leave this field blank.
2. Select the Data Class
To specify which data class your comment addresses:
In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
Note that the Data Class field will automatically populate based on your current location in the platform:
If you are on a data class page, the field will be set to that specific data class
If you are on a data element page, the corresponding data class will be pre-selected
3. Select the Data Element
To specify which data element your comment addresses:
In the "Data Element" drop-down menu, select the specific data element you want to comment on.
The drop-down menu will display only the elements available under the data class you selected in the previous step.
You can use the search function within the drop-down to quickly locate a specific data element.
If you are commenting on the data class itself rather than a specific element, you may leave this field blank.
Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.
4. Optional: Propose New Data Class or Element
If you cannot find the appropriate data class or element for your comment:
Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.
5. Complete the Comment Form
Fill out the required fields in the comment form:
Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.
Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.
6. Optional: Add Additional Comments
If you need to comment on multiple data classes or elements:
After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
A new comment section will appear, allowing you to enter details for your additional comment.
For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
Complete the Subject and Comment fields for your additional comment.
Repeat this process for each additional comment you wish to submit.
Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.
7. Optional: Upload Supporting Files
The platform allows you to upload supporting documentation to enhance your comment:
Locate the "File Upload" section at the bottom of the comment form.
Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.
Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.
Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.
8. Optional: Save and Exit
If you need to pause your work and return to complete your comment later:
Click the "Save and Exit" button at the bottom of the form.
Your comment will be saved as a draft that you can access and complete later.
When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
Click this button to continue working on your draft.
You will be taken to a review page where you can:
Select "Submit Comment" to officially submit your feedback.
Click "Edit" to return to the comment form and make changes
Select "Discard Draft" to delete the saved draft and start fresh
Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.
9. Review and Submit
Once you have completed your comment:
Click the "Review and Submit" button at the bottom of the form.
This will take you to a review screen displaying your comment(s) in full.
Review all information for accuracy and completeness.
On this review screen, you have three options:
Click "Submit Comment" to officially submit your feedback
Click "Edit" to return to the comment form and make changes
Click "Discard Draft" to delete the comment and start fresh
The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records.
If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.
Submitted by nedragarrett_CDC on
CDC's Consolidated Comment
Gender Identity
CSTE Comment: