HL7 Terminology (THO)
5.5.0 - Publication International flag

This page is part of the HL7 Terminology (v5.5.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

ValueSet: ClassNullFlavor

Official URL: http://terminology.hl7.org/ValueSet/v3-ClassNullFlavor Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: ClassNullFlavor
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn:oid:2.16.840.1.113883.1.11.20352

Copyright/Legal: 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

Description: Subset of null flavors, used for associations as needed for the ITS, and used in InfrastructureRoot.

References

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)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor
    CodeDisplayDefinition
    ASKUasked but unknownInformation was sought but not found (e.g., patient was asked but didn't know)
    MSKmaskedThere 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.
    NAnot applicableKnown to have no proper value (e.g., last menstrual period for a male).
    NASKnot askedThis information has not been sought (e.g., patient was not asked)
    NAVtemporarily unavailableInformation is not available at this time but it is expected that it will be available later.
    NINoInformation**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.
    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.)

 

Expansion

Expansion based on codesystem NullFlavor v3.0.0 (CodeSystem)

This value set contains 7 concepts.

CodeSystemDisplayDefinition
  ASKUhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorasked but unknown

Information was sought but not found (e.g., patient was asked but didn't know)

  MSKhttp://terminology.hl7.org/CodeSystem/v3-NullFlavormasked

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.

  NAhttp://terminology.hl7.org/CodeSystem/v3-NullFlavornot applicable

Known to have no proper value (e.g., last menstrual period for a male).

  NASKhttp://terminology.hl7.org/CodeSystem/v3-NullFlavornot asked

This information has not been sought (e.g., patient was not asked)

  NAVhttp://terminology.hl7.org/CodeSystem/v3-NullFlavortemporarily unavailable

Information is not available at this time but it is expected that it will be available later.

  NIhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorNoInformation

**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.

  UNKhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorunknown

**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.)

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

History

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
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