Vital Records Death Reporting (VRDR) FHIR Implementation Guide
3.0.0 - STU3 US

Vital Records Death Reporting (VRDR) FHIR Implementation Guide, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/vrdr/ and changes regularly. See the Directory of published versions

ValueSet: Spouse Alive ValueSet

Official URL: http://hl7.org/fhir/us/vrdr/ValueSet/vrdr-spouse-alive-vs Version: 3.0.0
Standards status: Draft Computable Name: SpouseAliveVS
Other Identifiers: OID:2.16.840.1.113883.4.642.40.10.48.21

The set of codes used to indicate whether the decedent's spouse is alive.

Mapping to IJE codes here.

References

Changes since version true:

  • New Content

    • Logical Definition (CLD)

    This value set includes codes based on the following rules:

    • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v2-0136 version 📦2.9
      CodeDisplay
      YYes
      NNo
    • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor version 📍2018-08-12
      CodeDisplay
      UNK unknown
      NA not applicable

     

    Expansion

    Expansion from tx.fhir.org based on:

    This value set contains 4 concepts

    SystemCodeDisplay (en)DefinitionJSONXML
    http://terminology.hl7.org/CodeSystem/v2-0136  YYes
    http://terminology.hl7.org/CodeSystem/v2-0136  NNo
    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:

                    
                       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.)
    http://terminology.hl7.org/CodeSystem/v3-NullFlavor  NAnot applicable

    Known to have no proper value (e.g., last menstrual period for a male).

    Description of the above table(s).