HRSA 2023 Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+) FHIR IG
1.1.0 - STU1 Release 1.1 - Standard for Trial-Use
HRSA 2023 Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+) FHIR IG
1.1.0 - STU1 Release 1.1 - Standard for Trial-Use
This page is part of the HRSA Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+ or uds-plus) FHIR IG (v1.1.0: STU1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
| Official URL: http://fhir.org/guides/hrsa/uds-plus/ValueSet/uds-plus-gender-identity-codes | Version: 1.1.0 | |||
| Standards status: Trial-use | Maturity Level: 2 | Computable Name: UdsPlusGenderIdentityCodes | ||
The Uds Plus Gender Identity Codes is a 'starter set' of codes for identifying the gender identity of Patients.
References
Generated Narrative: ValueSet uds-plus-gender-identity-codes
version: 1; Last updated: 2022-08-04 15:52:33+0000;
Information Source: #3Te0anOrvocKgcow
Profile: Shareable ValueSet
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
| Code | Display | Definition |
| NASK | Not Asked | This information has not been sought (e.g., patient was not asked) |
Generated Narrative: ValueSet
version: 1; Last updated: 2022-08-04 15:52:33+0000;
Information Source: #3Te0anOrvocKgcow
Profile: Shareable ValueSet
Expansion based on:
This value set contains 8 concepts
| Code | System | Display | Definition |
| ASKU | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | asked but unknown | Information was sought but not found (e.g., patient was asked but didn't know) |
| OTH | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | other | **Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE. |
| 407376001 | http://snomed.info/sct | Male-to-female transsexual (finding) | |
| 407377005 | http://snomed.info/sct | Female-to-male transsexual (finding) | |
| 446131000124102 | http://snomed.info/sct | Identifies as non-conforming gender (finding) | |
| 446141000124107 | http://snomed.info/sct | Identifies as female gender (finding) | |
| 446151000124109 | http://snomed.info/sct | Identifies as male gender (finding) | |
| NASK | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | Not Asked | This information has not been sought (e.g., patient was not asked) |
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 |