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 - Race Missing Value Reason Vital Records

Official URL: http://hl7.org/fhir/us/vr-common-library/ValueSet/ValueSet-race-missing-value-reason-vr Version: 2.0.0
Active as of 2026-06-01 Computable Name: ValueSetRaceMissingValueReasonVitalRecords

This valueset contains the set of codes used to indicate the reason decedent race data is absent.

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://terminology.hl7.org/CodeSystem/v3-ActReason version 📍2018-08-12
    CodeDisplay
    PREFUSpatient refuse
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor version 📍2018-08-12
    CodeDisplay
    ASKU asked but unknown
    UNK unknown

 

Expansion

Expansion from tx.fhir.org based on:

  • codesystem v3 Code System ActReason version 2018-08-12
  • codesystem v3 Code System NullFlavor version 2018-08-12

This value set contains 3 concepts

SystemCodeDisplay (en)DefinitionJSONXML
http://terminology.hl7.org/CodeSystem/v3-ActReason  PREFUSpatient refuse

Description:The patient refused to take the product.

http://terminology.hl7.org/CodeSystem/v3-NullFlavor  ASKUasked but unknown

Information was sought but not found (e.g., patient was asked but didn't know)

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

Description of the above table(s).