Argonaut Data Query Implementation Guide Version 1.0.0

This page is part of the Argonaut Data Query Implementation Guide (v1.0.0: Release) based on FHIR R2. This is the current published version. For a full list of available versions, see the Directory of published versions

USRealm Birth Sex Value Set

Defining URL:http://fhir.org/guides/argonaut/ValueSet/usrealm-birthsex
Name:USRealm Birth Sex Value Set
Definition:

Codes for assigning sex at birth as specified by the Office of the National Coordinator for Health IT (ONC)

Publisher:Argonaut Project
Source ResourceXML / JSON / Turtle
This ValueSet is used by:

USRealm Birth Sex Value Set

Codes for assigning sex at birth as specified by the Office of the National Coordinator for Health IT (ONC)

This value set includes codes from the following code systems:

  • Include these codes as defined in http://hl7.org/fhir/v3/AdministrativeGender
    CodeDisplay
    FFemaleFemale
    MMaleMale
  • Include these codes as defined in http://hl7.org/fhir/v3/NullFlavor
    CodeDisplay
    UNKUnknownDescription: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: Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 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

CodeSystemDisplayDefinition
Fhttp://hl7.org/fhir/v3/AdministrativeGenderFemaleFemale
Mhttp://hl7.org/fhir/v3/AdministrativeGenderMaleMale
UNKhttp://hl7.org/fhir/v3/NullFlavorUnknownDescription: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: Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 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.)