HL7 Terminology (THO)
6.1.0 - Continuous Process Integration (ci build)
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/gender-identity | Version: 2.0.0 | |||
Active as of 2024-12-21 | Maturity Level: 1 | Responsible: Health Level Seven International | Computable Name: GenderIdentity | |
Other Identifiers: OID:2.16.840.1.113883.4.642.3.3291 | ||||
Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
Codes that indicate a individual's gender identity. This value set is a minimum set of commonly used values. It is expected and encouraged that specific jurisdictions or communities will use additional gender identity concepts that are relevant within their community.
References
Generated Narrative: ValueSet gender-identity
This value set includes codes based on the following rules:
http://snomed.info/sct
Code | Display |
446141000124107 | Female gender identity |
446151000124109 | Male gender identity |
33791000087105 | Non-binary gender identity |
http://terminology.hl7.org/CodeSystem/data-absent-reason
Code | Display | Definition |
asked-declined | Asked But Declined | The source was asked but declined to answer. |
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
Code | Display | Definition |
UNK | Unknown | **Description:**A proper value is applicable, but not known. **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: 1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.) |
Generated Narrative: ValueSet
Expansion based on:
This value set contains 5 concepts
Code | System | Display | Definition |
446141000124107 | http://snomed.info/sct | Identifies as female gender (finding) | |
446151000124109 | http://snomed.info/sct | Identifies as male gender (finding) | |
33791000087105 | http://snomed.info/sct | Identifies as gender nonbinary | |
asked-declined | http://terminology.hl7.org/CodeSystem/data-absent-reason | Asked But Declined | The source was asked but declined to answer. |
UNK | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | Unknown | **Description:**A proper value is applicable, but not known. Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:
|
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |
History
Date | Action | Custodian | Author | Comment |
2023-11-14 | revise | TSMG | Marc Duteau | Add standard copyright and contact to internal content; up-476 |
2023-06-20 | create | TSMG | Marc Duteau | Moving gender harmony terminology from extension IG into THO; up-432 |