PACIO Advance Directive Interoperability Implementation Guide
2.1.0 - STU 2 United States of America flag

PACIO Advance Directive Interoperability Implementation Guide, published by HL7 International / Patient Empowerment. This guide is not an authorized publication; it is the continuous build for version 2.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-pacio-adi/ and changes regularly. See the Directory of published versions

ValueSet: No Healthcare Agent Included Reason

Official URL: http://hl7.org/fhir/us/pacio-adi/ValueSet/ADINoHealthcareAgentIncludedReasonVS Version: 2.1.0
Active as of 2025-04-01 Computable Name: ADINoHealthcareAgentIncludedReasonVS

Includes data absent reason concepts to express why a Healthcare Agent is not included.

References

Logical Definition (CLD)

Generated Narrative: ValueSet ADINoHealthcareAgentIncludedReasonVS

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/data-absent-reason
    CodeDisplayDefinition
    unknownUnknownThe value is expected to exist but is not known.
    asked-unknownAsked But UnknownThe source was asked but does not know the value.
    temp-unknownTemporarily UnknownThere is reason to expect (from the workflow) that the value may become known.
    not-askedNot AskedThe workflow didn't lead to this value being known.
    asked-declinedAsked But DeclinedThe source was asked but declined to answer.
    not-applicableNot ApplicableThere is no proper value for this element (e.g. last menstrual period for a male).
    unsupportedUnsupportedThe source system wasn't capable of supporting this element.

 

Expansion

ValueSet

Expansion performed internally based on codesystem DataAbsentReason v1.0.0 (CodeSystem)

This value set contains 7 concepts

CodeSystemDisplay (en-US)Definition
  unknownhttp://terminology.hl7.org/CodeSystem/data-absent-reason

The value is expected to exist but is not known.

  asked-unknownhttp://terminology.hl7.org/CodeSystem/data-absent-reason

The source was asked but does not know the value.

  temp-unknownhttp://terminology.hl7.org/CodeSystem/data-absent-reason

There is reason to expect (from the workflow) that the value may become known.

  not-askedhttp://terminology.hl7.org/CodeSystem/data-absent-reason

The workflow didn't lead to this value being known.

  asked-declinedhttp://terminology.hl7.org/CodeSystem/data-absent-reason

The source was asked but declined to answer.

  not-applicablehttp://terminology.hl7.org/CodeSystem/data-absent-reason

There is no proper value for this element (e.g. last menstrual period for a male).

  unsupportedhttp://terminology.hl7.org/CodeSystem/data-absent-reason

The source system wasn't capable of supporting this element.

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