Vital Records Common Library (VRCL) FHIR Implementation Guide
2.0.0 - STU2 United States of America flag

Vital Records Common Library (VRCL) 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/vr-common-library/ and changes regularly. See the Directory of published versions

ValueSet: Value Set - Marital Status Vital Records

Official URL: http://hl7.org/fhir/us/vr-common-library/ValueSet/ValueSet-marital-status-vr Version: 2.0.0
Active as of 2024-10-11 Computable Name: ValueSetMaritalStatusVitalRecords

The set of codes used to indicate the marital status of the decedent

Note: 'Domestic Partnership' is not supported by NCHS and will be mapped to 'U' unknown

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-marital-status-vr

This value set includes codes based on the following rules:

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-MaritalStatus
    CodeDisplayDefinition
    DDivorcedMarriage contract has been declared dissolved and inactive
    LLegally Separated
    MMarriedA current marriage contract is active
    SNever MarriedNo marriage contract has ever been entered
    WWidowedThe spouse has died
    TDomestic PartnerPerson declares that a domestic partner relationship exists.
  • 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.)

 

Expansion

Generated Narrative: ValueSet

This value set contains 7 concepts

CodeSystemDisplayDefinition
  Dhttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusDivorced

Marriage contract has been declared dissolved and inactive

  Lhttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusLegally Separated
  Mhttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusMarried

A current marriage contract is active

  Shttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusNever Married

No marriage contract has ever been entered

  Whttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusWidowed

The spouse has died

  Thttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusDomestic Partner

Person declares that a domestic partner relationship exists.

  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