This page is part of the US Core (v3.1.1: STU3) based on FHIR R4. The current version which supercedes this version is 5.0.1. For a full list of available versions, see the Directory of published versions 
| Defining URL: | http://hl7.org/fhir/us/core/ValueSet/birthsex |
| Version: | 3.1.1 |
| Name: | BirthSex |
| Status: | Active |
| Title: | Birth Sex |
| Definition: | Codes for assigning sex at birth as specified by the Office of the National Coordinator for Health IT (ONC) |
| Publisher: | HL7 US Realm Steering Committee |
| OID: | 2.16.840.1.113762.1.4.1021.24 (for OID based terminology systems) |
| Source Resource: | XML / JSON / Turtle |
Logical Definition (CLD)
This value set includes codes based on the following rules:
- Include these codes as defined in
http://terminology.hl7.org/CodeSystem/v3-AdministrativeGenderCode Display F Female Female M Male Male - Include these codes as defined in
http://terminology.hl7.org/CodeSystem/v3-NullFlavorCode Display 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.)
Expansion
This value set contains 3 concepts
Expansion based on:
| Code | System | Display | Definition |
| F | http://terminology.hl7.org/CodeSystem/v3-AdministrativeGender | Female | Female |
| M | http://terminology.hl7.org/CodeSystem/v3-AdministrativeGender | Male | Male |
| 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: 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.) |
