HL7 Terminology (THO)
7.1.0 - Publication International flag

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

ValueSet: Yes No Unknown NotApplicable

Official URL: http://terminology.hl7.org/ValueSet/yes-no-unknown-not-applicable Version: 1.0.0
Responsible: Health Level Seven International Computable Name: YesNoUnknownNotApplicable

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

This valueset contains the set of codes used to respond to any question that can be answered Yes, No, Unknown, or Not Applicable.

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)

Language: en

This value set includes codes based on the following rules:

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v2-0532 version 📦3.0.0
    CodeDisplayDefinition
    YYesYes
    NNoNo
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor version 📦4.0.0
    CodeDisplayDefinition
    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.)
    NA not applicable Known to have no proper value (e.g., last menstrual period for a male).

 

Expansion

This value set contains 4 concepts

SystemCodeDisplay (en)DefinitionJSONXML
http://terminology.hl7.org/CodeSystem/v2-0532  YYesYes
http://terminology.hl7.org/CodeSystem/v2-0532  NNoNo
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.)
http://terminology.hl7.org/CodeSystem/v3-NullFlavor  NAnot applicable

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

Description of the above table(s).

History

DateActionCustodianAuthorComment
2025-04-26createTIJessica BotaCreate a THO Valueset for Y/N/NA/UNK; up-642