Vital Records Death Reporting (VRDR) FHIR Implementation Guide
3.0.0-ballot - ballot United States of America flag

This page is part of the Vital Records Death Reporting FHIR Implementation Guide (v3.0.0-ballot: STU 3 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 2.2.0. For a full list of available versions, 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-ballot
Draft as of 2024-04-05 Computable Name: SpouseAliveVS
Other Identifiers: OID:2.16.840.1.113883.4.642.40.10.48.24

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

Mapping to IJE codes here.

References

Changes since version true:

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
    CodeDisplay
    YYes
    NNo
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor
    CodeDisplayDefinition
    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.)
    NA not applicable Known to have no proper value (e.g., last menstrual period for a male).

 

Expansion

This value set contains 4 concepts.

CodeSystemDisplayDefinition
  Yhttp://terminology.hl7.org/CodeSystem/v2-0136Yes
  Nhttp://terminology.hl7.org/CodeSystem/v2-0136No
  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.)
  NAhttp://terminology.hl7.org/CodeSystem/v3-NullFlavornot applicable

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

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