Birth And Fetal Death (BFDR) - STU2-ballot
2.0.0-Preview1 - trial-use United States of America flag

Birth And Fetal Death (BFDR) - STU2-ballot, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 2.0.0-Preview1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-bfdr/ and changes regularly. See the Directory of published versions

ValueSet: Birth Attendants Titles

Official URL: http://hl7.org/fhir/us/bfdr/ValueSet/ValueSet-birth-attendant-titles Version: 2.0.0-Preview1
Active as of 2024-07-11 Computable Name: BirthAttendantTitlesVS
Other Identifiers: OID:2.16.840.1.113883.4.642.40.13.48.3

Copyright/Legal: This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement

This valueset contains codes to represent the type of birth attendant titles.

Mapping to IJE codes here.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

Generated Narrative: ValueSet ValueSet-birth-attendant-titles

This value set includes codes based on the following rules:

  • Include these codes as defined in http://snomed.info/sct
    CodeDisplay
    112247003Medical Doctor
    76231001Osteopath
    445521000124102Advanced Practice Midwife
    445531000124104Lay Midwife
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor
    CodeDisplayDefinition
    OTH 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.
    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

Generated Narrative: ValueSet

Expansion based on:

This value set contains 6 concepts

CodeSystemDisplayInactiveDefinition
  112247003http://snomed.info/sctMedical Doctorinactive
  76231001http://snomed.info/sctOsteopath
  445521000124102http://snomed.info/sctAdvanced practice midwife (occupation)
  445531000124104http://snomed.info/sctLay midwife (occupation)
  OTHhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorOther

**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.

  UNKhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorUnknown

**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.)

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