R4 Ballot #1 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.3.0: R4 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.3.2.1008 HL7 v3 Code System NullFlavor

Vocabulary Work Group Maturity Level: N/AExternal Use Context: Any

This code system (http://hl7.org/fhir/v3/NullFlavor) is defined as part of HL7 v3.

Summary

Defining URL:http://hl7.org/fhir/v3/NullFlavor
Name:v3 Code System NullFlavor
Definition:

A collection of codes specifying why a valid value is not present.

OID:2.16.840.1.113883.5.1008 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • HumanNameAssemblyOrder (A code that represents the preferred display order of the components of a human name)
  • Marital Status Codes (This value set defines the set of codes that can be used to indicate the marital status of a person.)
  • v2 Expanded Yes/no Indicator (FHIR Value set/code system definition for HL7 v2 table 0532 ( Expanded Yes/no Indicator))
  • SpecialCourtesy (This value set defines a set of codes that can be used to indicate special courtesies provided to the patient.)
  • v2 CWE statuses (FHIR Value set/code system definition for HL7 v2 table 0353 ( CWE statuses))
  • v3 Code System NullFlavor ( A collection of codes specifying why a valid value is not present.)

4.3.2.1008.1 Code System Content

Release Date: 2018-04-01

LevelCodeDisplayDefinition
1NI NoInformation Description:The value is exceptional (missing, omitted, incomplete, improper). No information as to the reason for being an exceptional value is provided. This is the most general exceptional value. It is also the default exceptional value.
2  INV invalid Description:The value as represented in the instance is not a member of the set of permitted data values in the constrained value domain of a variable.
3    DER derived Description:An actual value may exist, but it must be derived from the provided information (usually an EXPR generic data type extension will be used to convey the derivation expressionexpression .
3    OTH other Description:The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system).
Usage Notes: 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.
4      NINF negative infinity Negative infinity of numbers.
4      PINF positive infinity Positive infinity of numbers.
3    UNC un-encoded Description: The actual value has not yet been encoded within the approved value domain.
Example: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system. Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM.
Usage Notes: 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.
2  MSK masked There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons. There may be an alternate mechanism for gaining access to this information.
Note: using this null flavor does provide information that may be a breach of confidentiality, even though no detail data is provided. Its primary purpose is for those circumstances where it is necessary to inform the receiver that the information does exist without providing any detail.
2  NA not applicable Known to have no proper value (e.g., last menstrual period for a male).
2  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:
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.)
3    ASKU asked but unknown Information was sought but not found (e.g., patient was asked but didn't know)
4      NAV temporarily unavailable Information is not available at this time but it is expected that it will be available later.
3    NASK not asked This information has not been sought (e.g., patient was not asked)
3    NAVU Not available Information is not available at this time (with no expectation regarding whether it will or will not be available in the future).
4      NAV
3    QS Sufficient 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.
3    TRC trace The content is greater than zero, but too small to be quantified.
1NP not present Value is not present in a message. This is only defined in messages, never in application data! All values not present in the message must be replaced by the applicable default, or no-information (NI) as the default of all defaults.