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.
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
Gender identity defined in USCDI v2 does not represent all different gender identities expressed by the community as a whole. There are additional gender identities that could not be categorized in any of the values existing in the current version. For example – there are community members identifying themselves as ‘Transgender’ rather than either ‘Male Transgender’ or ‘Female Transgender’. Similarly, there are additional categories that are presently represented by ‘other’ which accurately represents additional gender identities, as follows:
MedMorph supports the addition of the Gender Identity element and believes it should be promoted to V2. Gender Identity is important for measuring the impact of disease and outcomes across populations. It is also beneficial in the Healthcare Survey domain since it is used to guide the provider and staff about how to interact with the patient. Also, HL7 has just completed an informative ballot: "Gender Harmony - Modeling Sex and Gender Representation, Release 1".
While I have some concerns with the sentiments noted in the "Rationale for Separate Consideration" I absolutely agree with the summary consideration that Gender Identity is a critical piece of information about people in the course of clinical care. It is distinct from other representations of sex-oriented identities, such as whatever administrative sex might be. It should be noted that Gender Identity is something that is expressed by an individual, is not assigned by any other entity (such as a parent.) Gender Identity is not something that should be used as a surrogate for physiologic sex-oriented clinical observations; instead I would like to see a separate data element that we like to call Sex For Clinical Use (SFCU). Please note that Gender Identity is NOT the element to capture information indicating if a person has gone through a transgender process, which would be best captured via clinical observations (that could properly be masked if needed.) Many transgender individuals will properly indicate Male or Female as their gender identity.
We've reviewed and submitted feedback on the submission we've put forward for Patient Gender Identity, and we believe the information provided differs from the submission here, which has been referenced when told we submitted a duplicate. We believe our submission should be revisited as it differs in some areas to the submission seen here.
This is the data element description from the submission we've put forth:
The gender the patient identifies with. The Patient's gender identity is used as guidance (e.g. for staff) about how to interact with the patient.
The NY eHealth Collaborative (NYeC) supports including Gender Identity in the USCDI v2 due to its widespread use and clinical value for LGBTQIA individuals. We suggest revising the element description to reference the Human Rights Campaign (HRC) definition: "One's innermost concept of self as male, female, a blend of both or neither – how individuals perceive themselves and what they call themselves. One's gender identity can be the same or different from their sex assigned at birth."
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 Unified Comment