Birth And Fetal Death (BFDR) FHIR Implementation Guide
2.0.0 - STU2 - CIBuild United States of America flag

Birth And Fetal Death (BFDR) FHIR Implementation Guide, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 2.0.0 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: Fetal Presentations

Official URL: http://hl7.org/fhir/us/bfdr/ValueSet/ValueSet-fetal-presentations Version: 2.0.0
Standards status: Draft Computable Name: FetalPresentationsVS
Other Identifiers: OID:2.16.840.1.113883.4.642.40.13.48.12

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 fetal presentations. Only these codes are supported for exchange with NCHS.

Mapping to IJE codes here.

References

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Include these codes as defined in http://snomed.info/sct version Not Stated (use latest from terminology server)
    CodeDisplay
    70028003Vertex presentation (finding)
    6096002Breech presentation (finding)
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor version 📍4.0.0
    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

Expansion from tx.fhir.org based on:

This value set contains 4 concepts

SystemCodeDisplay (en)DefinitionJSONXML
http://snomed.info/sct  70028003Vertex presentation
http://snomed.info/sct  6096002Breech presentation
http://terminology.hl7.org/CodeSystem/v3-NullFlavor  OTHOther

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

http://terminology.hl7.org/CodeSystem/v3-NullFlavor  UNKunknown

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

Description of the above table(s).