CodeSystem Comparison between http://terminology.hl7.org/CodeSystem/v3-NullFlavor vs http://terminology.hl7.org/CodeSystem/v3-NullFlavor

Messages

Metadata

Name	Value		Comments
caseSensitive	true
compositional
content	complete
copyright	This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license
date	2019-03-20
description	A collection of codes specifying why a valid value is not present.
experimental	false
hierarchyMeaning	is-a
jurisdiction
name	NullFlavor
publisher	Health Level Seven International
purpose
status	active
title	NullFlavor
url	http://terminology.hl7.org/CodeSystem/v3-NullFlavor
version	3.0.0
versionNeeded

Concepts

Code	Display		Specializes		Generalizes		internalId		status		HL7usageNotes		subsumedBy		Specializes		Generalizes		internalId		status		HL7usageNotes		subsumedBy		Comments
NI	NoInformation						10610	10610	active	active									10610	10610	active	active
NP	not present						10619	10619	retired	retired									10619	10619	retired	retired
NAV	temporarily unavailable						10615	10615	active	active			NAVU	NAVU					10615	10615	active	active			NAVU	NAVU
DER	derived						22657	22657	active	active			INV	INV					22657	22657	active	active			INV	INV
OTH	other						10616	10616	active	active	This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.	This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.	INV	INV					10616	10616	active	active	This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.	This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.	INV	INV
UNC	un-encoded						22185	22185	active	active	If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted. Data type properties such as original text and translations may be present when this null flavor is included.	If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted. Data type properties such as original text and translations may be present when this null flavor is included.	INV	INV					22185	22185	active	active	If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted. Data type properties such as original text and translations may be present when this null flavor is included.	If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted. Data type properties such as original text and translations may be present when this null flavor is included.	INV	INV
INV	invalid						22656	22656	active	active			NI	NI					22656	22656	active	active			NI	NI
MSK	masked						17932	17932	active	active			NI	NI					17932	17932	active	active			NI	NI
NA	not applicable						10611	10611	active	active			NI	NI					10611	10611	active	active			NI	NI
UNK	unknown						10612	10612	active	active	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.)	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.)	NI	NI					10612	10612	active	active	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.)	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.)	NI	NI
NINF	negative infinity						10618	10618	active	active			OTH	OTH					10618	10618	active	active			OTH	OTH
PINF	positive infinity						10617	10617	active	active			OTH	OTH					10617	10617	active	active			OTH	OTH
ASKU	asked but unknown						10614	10614	active	active			UNK	UNK					10614	10614	active	active			UNK	UNK
NASK	not asked						10613	10613	active	active			UNK	UNK					10613	10613	active	active			UNK	UNK
NAVU	Not available						23731	23731	active	active			UNK	UNK					23731	23731	active	active			UNK	UNK
QS	Sufficient Quantity						21436	21436	active	active			UNK	UNK					21436	21436	active	active			UNK	UNK
TRC	trace						21386	21386	active	active			UNK	UNK					21386	21386	active	active			UNK	UNK