Vital Records Common Library (VRCL) STU2-ballot
2.0.0 - trial-use United States of America flag

Vital Records Common Library (VRCL) STU2-ballot, 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: 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 2024-03-21 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
    CodeDisplayDefinition
    PREFUSpatient refuse**Description:**The patient refused to take the product.
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor
    CodeDisplayDefinition
    ASKUasked but unknownInformation was sought but not found (e.g., patient was asked but didn't know)
    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.)

 

Expansion

This value set contains 3 concepts.

CodeSystemDisplayDefinition
  PREFUShttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient refuse

**Description:**The patient refused to take the product.

  ASKUhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorasked but unknown

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

  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