Vital Records Death Reporting FHIR Implementation Guide - Local Development build (v1.1.0). See the Directory of published versions
Official URL: http://hl7.org/fhir/us/vrdr/ValueSet/YesNoUnknownNotApplicable | Version: 1.1.0 | |||
Draft as of 2022-04-04 | Computable Name: YesNoUnknownNotApplicable |
A set of codes used to express an affirmative response (Yes), negative response (No), or indicate that a response is not applicable (NA) or unknown (UNK) with regard to the question posed.
Inter-jurisdictional Exchange (IJE) concept mapping
VRDR IG Code | VRDR IG Display Name | IJE Code | IJE Display Name |
---|---|---|---|
N | No | Y | Yes |
Y | Yes | N | No |
UNK | unknown | U | Unknown |
NA | not applicable | X | Not Applicable: Computer generated |
References
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v2-0136
Code | Display |
Y | Yes |
N | No |
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
Code | Display | Definition |
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). |
This value set contains 4 concepts
Expansion based on:
Code | System | Display | Definition |
Y | http://terminology.hl7.org/CodeSystem/v2-0136 | Yes | |
N | http://terminology.hl7.org/CodeSystem/v2-0136 | No | |
UNK | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | 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 | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | not 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 |