MyHealth@Eu MVC package
9.1.0 - trial-use

MyHealth@Eu MVC package - Downloaded Version 9.1.0 See the Directory of published versions

## ValueSet: eHDSI Null Flavor

Official URL: http://terminology.ehdsi.eu/ValueSet/eHDSINullFlavor | Version: 9.1.0
Active as of 2026-05-08 | Computable Name: EHDSINullFlavor
Other Identifiers: OID:1.3.6.1.4.1.12559.11.10.1.3.1.42.37

The Value Set is used to specify why a valid value is not present.

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` version 📍4.0.0

  Code | Display | Definition
  ASKU | asked but unknown | Information was sought but not found (e.g., patient was asked but didn't know)
  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.
  NA | not applicable | Known to have no proper value (e.g., last menstrual period for a male).
  NASK | not asked | This information has not been sought (e.g., patient was not asked)
  NAV | temporarily unavailable | Information is not available at this time but it is expected that it will be available later.
  NI | 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.
  NINF | negative infinity | Negative infinity of numbers.
  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.
  PINF | positive infinity | Positive infinity of numbers.
  TRC | trace | The content is greater than zero, but too small to be quantified.
  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.)

### Expansion

Expansion performed internally based on codesystem NullFlavor v4.0.0 (CodeSystem)

This value set contains 11 concepts

System | Code | Display (en) | Definition | JSON | XML
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | ASKU | asked but unknown | Information was sought but not found (e.g., patient was asked but didn't know) |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | 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. |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | NA | not applicable | Known to have no proper value (e.g., last menstrual period for a male). |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | NASK | not asked | This information has not been sought (e.g., patient was not asked) |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | NAV | temporarily unavailable | Information is not available at this time but it is expected that it will be available later. |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | NI | 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. |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | NINF | negative infinity | Negative infinity of numbers. |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | 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. |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | PINF | positive infinity | Positive infinity of numbers. |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | TRC | trace | The content is greater than zero, but too small to be quantified. |  |
`http://terminology.hl7.org/CodeSystem/v3-NullFlavor` | 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.) |  |

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