FHIR Release 3 (STU) Current Build
This page is part of FHIR STU 3 (v3.0.1) in it's permanent home (it will always be available at this URL). It has been superceded by R4 . For a full list of available versions, see the Directory of published versions .

4.2.12.314 4.3.14.392 Code System http://hl7.org/fhir/list-empty-reason http://terminology.hl7.org/CodeSystem/list-empty-reason

Vocabulary Structured Documents Work Group   Maturity Level : 2 0 Informative Use Context : Not Intended for Production use Any

This is a code system defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/list-empty-reason http://terminology.hl7.org/CodeSystem/list-empty-reason
Version: 4.1.0
Name: ListEmptyReasons
Title: List Empty Reasons
Definition:

General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).

Committee: FHIR Infrastructure Structured Documents Work Group
OID: 2.16.840.1.113883.4.642.1.314 2.16.840.1.113883.4.642.1.1106 (for OID based terminology systems)
Source Resource XML / JSON

This Code system is used in the following value sets:

  • ValueSet: List Empty Reasons (General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).)
  • ValueSet: List Empty Reasons (General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).)

General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).

This code system http://hl7.org/fhir/list-empty-reason http://terminology.hl7.org/CodeSystem/list-empty-reason defines the following codes:
Code Display Definition
nilknown Nil Known Clinical judgment that there are no known items for this list after reasonable investigation. Note that this a positive statement by a clinical user, and not a default position asserted by a computer system in the lack of other information. Example uses: * For allergies: the patient or patient's agent/guardian has asserted that he/she is not aware of any allergies (NKA - nil known allergies) * For medications: the patient or patient's agent/guardian has asserted that the patient is known to be taking no medications * For diagnoses, problems and procedures: the patient or patient's agent/guardian has asserted that there is no known event to record.
notasked Not Asked The investigation to find out whether there are items for this list has not occurred.
withheld Information Withheld The content of the list was not provided due to privacy or confidentiality concerns. Note that it should not be assumed that this means that the particular information in question was withheld due to its contents - it can also be a policy decision.
unavailable Unavailable Information to populate this list cannot be obtained; e.g. unconscious patient.
notstarted Not Started The work to populate this list has not yet begun.
closed Closed This list has now closed or has ceased to be relevant or useful.

 

See the full registry of value sets code systems defined as part of FHIR.


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 See Code System for further information.
Source 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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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