HL7 Terminology
2.1.11 - Continuous Process Integration (ci build)

HL7 Terminology, published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 2.1.11). This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: Unknown


Defining URL:http://terminology.hl7.org/ValueSet/v3-Unknown
Status:Active as of 2014-03-26

A proper value is applicable, but not known.

OID:2.16.840.1.113883.1.11.10612 (for OID based terminology systems)
Source Resource:XML / JSON / Turtle


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)



This value set contains 7 concepts

Expansion based on NullFlavor v2.0.0 (CodeSystem)

All codes from system 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: 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.)
ASKUasked but unknownInformation was sought but not found (e.g., patient was asked but didn't know)
NAVtemporarily unavailableInformation is not available at this time but it is expected that it will be available later.
NASKnot askedThis information has not been sought (e.g., patient was not asked)
NAVUNot availableInformation is not available at this time (with no expectation regarding whether it will or will not be available in the future).
QSSufficient Quantity**Description:**The specific quantity is not known, but is known to be non-zero and is not specified because it makes up the bulk of the material. e.g. 'Add 10mg of ingredient X, 50mg of ingredient Y, and sufficient quantity of water to 100mL.' The null flavor would be used to express the quantity of water.
TRCtraceThe content is greater than zero, but too small to be quantified.

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
Source 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


2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26