PACIO Advance Healthcare Directive Interoperability Implementation Guide
2.0.0-ballot - STU 2 – Ballot

PACIO Advance Healthcare 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.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/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.0.0-ballot
Standards status: Trial-use | Maturity Level: 2 | Computable Name: ADINoHealthcareAgentIncludedReasonVS

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

References

- ADI PtAuthored Composition

### Logical Definition (CLD)

- Include these codes as defined in `http://terminology.hl7.org/CodeSystem/data-absent-reason`

  Code | Display | Definition
  unknown | Unknown | The value is expected to exist but is not known.
  asked-unknown | Asked But Unknown | The source was asked but does not know the value.
  temp-unknown | Temporarily Unknown | There is reason to expect (from the workflow) that the value may become known.
  not-asked | Not Asked | The workflow didn't lead to this value being known.
  asked-declined | Asked But Declined | The source was asked but declined to answer.
  not-applicable | Not Applicable | There is no proper value for this element (e.g. last menstrual period for a male).
  unsupported | Unsupported | The source system wasn't capable of supporting this element.

### Expansion

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

This value set contains 7 concepts

Code | System | Display (en-US) | Definition
unknown | http://terminology.hl7.org/CodeSystem/data-absent-reason | Unknown | The value is expected to exist but is not known.
asked-unknown | http://terminology.hl7.org/CodeSystem/data-absent-reason | Asked But Unknown | The source was asked but does not know the value.
temp-unknown | http://terminology.hl7.org/CodeSystem/data-absent-reason | Temporarily Unknown | There is reason to expect (from the workflow) that the value may become known.
not-asked | http://terminology.hl7.org/CodeSystem/data-absent-reason | Not Asked | The workflow didn't lead to this value being known.
asked-declined | http://terminology.hl7.org/CodeSystem/data-absent-reason | Asked But Declined | The source was asked but declined to answer.
not-applicable | http://terminology.hl7.org/CodeSystem/data-absent-reason | Not Applicable | There is no proper value for this element (e.g. last menstrual period for a male).
unsupported | http://terminology.hl7.org/CodeSystem/data-absent-reason | Unsupported | 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