DSTU2

This page is part of the FHIR Specification (v0.0.82: (v1.0.2: DSTU 1). 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: R5 R4B R4 R3 R2

1.14.2.1.90 1.25.2.1.176 Value Set http://hl7.org/fhir/vs/list-empty-reason http://hl7.org/fhir/ValueSet/list-empty-reason

This is a value set defined by the FHIR project.

If a list is empty, why it is empty Formal definitions: XML or JSON . Summary

1.14.2.1.90.1
Defining URL: http://hl7.org/fhir/ValueSet/list-empty-reason
Name: 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) list).
OID: 2.16.840.1.113883.4.642.2.176 (for OID based terminology systems)
System URL: http://hl7.org/fhir/list-empty-reason
System OID: 2.16.840.1.113883.4.642.1.176
Source Resource XML / JSON

This value set defines its own terms is used in the following places:

1.25.2.1.176.1 Content Logical Definition

This value set has an inline code system http://hl7.org/fhir/list-empty-reason http://hl7.org/fhir/list-empty-reason, which defines the following codes:

Comments Other language is sometimes used for this concept, such as 'no significant [x] known'. SNOMED CT includes many codes for this general concept, but no single generalisation. If using SNOMED CT, use this code and the appropriate specific SNOMED CT code
Code Display Definition
nilknown Nil Known Clinical judgement 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 The investigation to find out whether there are items for this list has not occurred occurred.
withheld Information Withheld Information 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 it's its contents - it can also be a policy decision decision.
In spite of the definition, unavailable Unavailable Information to populate this code should list cannot be used carefully as it represents potential information leakage or the perception thereof obtained; e.g. unconscious patient.
notstarted Not Started The work to populate this list has not yet begun begun.
closed Closed This list has now closed or has ceased to be relevant or useful useful.

These codes are used in the following places: List.emptyReason ( Incomplete ) The OID for the value set is 2.16.840.1.113883.4.642.2.90 (OIDs are not used in FHIR, but may be used in v3, or OID based terminology systems).  

See the full registry of value sets 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
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)
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
var disqus_shortname = 'fhirdstu';(function() {var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq); })(); Please enable JavaScript to view the comments powered by Disqus. comments powered by Disqus