This page is part of the Vital Records Common Profile Library (v2.0.0: STU2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/us/vr-common-library/ValueSet/ValueSet-yes-no-unknown-vr | Version: 2.0.0 | |||
Active as of 2024-10-11 | Computable Name: ValueSetYesNoUnknownVitalRecords |
This valueset contains the set of codes used to respond to any question that can be answered Yes, No, or Unknown.
Mapping to IJE codes here.
References
Generated Narrative: ValueSet ValueSet-yes-no-unknown-vr
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v2-0136
Code | Display |
N | No |
Y | Yes |
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.) |
Generated Narrative: ValueSet
Expansion based on:
This value set contains 3 concepts
Code | System | Display | Definition |
N | http://terminology.hl7.org/CodeSystem/v2-0136 | No | |
Y | http://terminology.hl7.org/CodeSystem/v2-0136 | Yes | |
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:
|
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 |