PACIO Advance Directive Interoperability Implementation Guide, published by HL7 Patient Empowerment Working Group. This is not an authorized publication; it is the continuous build for version 0.1.0). This version is based on the current content of https://github.com/HL7/pacio-adi/ and changes regularly. See the Directory of published versions

Home

The Advance Directive Interoperability (ADI) FHIR implementation guide (IG) explains how to represent, exchange, and verify a person’s goals, preferences and priorities for treatments and interventions regarding future medical care.

Introduction

This ADI implementation guide (IG) describes how to use existing HL7 FHIR® standards to create, update, share, verify, and exchange information about an individual's advance medical goals, preferences, and priorities for care in the event the individual is unable to communicate this information to medical teams for himself or herself. Advance directives in this IG includes person-authored advance directives and personal advance care plans, and patient consent information attesting to a patient authorizing a person or persons to serve as a healthcare agent or attesting to permission granted to share advance directive information with others. It also includes practitioner-authored patient instructions (obligation and prohibitions), and practitioner-authored portable medical orders for life sustaining treatments.

Advance directives can be categorized into three types of information. The current version of this guide addresses Type I: Person-Authored Advance Directive Information. Subsequent versions of this guide will address the other two types; Encounter-Centric Instructions and Portable Medical Order for Life-Sustaining Treatment.

Background

Advance directive interoperability is a complex area that involves many stakeholders. The HL7 workgroup sponsor for this FHIR IG is Patient Empowerment. HL7 co-sponsor workgroups include Patient Care, Community Based Care and Privacy, and Orders & Observations. As part of PACIO’s main goal in improving care transitions, the Post-Acute Care Interoperability (PACIO) Community has adopted this project as a critical use case. The PACIO Community has a strong interest in the topic of advance directive interoperability with FHIR and will support the community engagement and technical FHIR IG development needed for advance directives interoperability. PACIO is supported by MITRE, CMS, ONC and many other stakeholders (clinical, technical, and industry associations).

FHIR profiles have been developed for several existing FHIR resources to represent advance directive content such as: living will, durable medical power of attorney, personal health goals at end of life, care experience preferences, end-of-life and emergency intervention preferences under certain circumstances, patient instructions (obligation, prohibitions, and consent), and portable medical orders for life sustaining treatments.

Content Types

There is a very important distinction for the three types of information that will be covered in this IG. Below is a description of each type of content that will be covered by the IG.

 

	Type I: Person-Authored Advance Directive Information
		Patient-authored information Used as a tool for sharing an individual’s (patient’s) medical treatment and intervention goals, preferences, and priorities (GPP) Provides guidance that a patient would want known to inform care planning during a potential future medical emergency, in the case where the patient is unable to communicate with caregivers and medical personnel There is NO “contract” between the author (patient) and any other party involved in the future medical emergency that the GPP is required to be followed (i.e., no offer or acceptance, no consideration, no consequences for failure to follow the patient’s directives)
	Type II: Encounter-Centric Instructions
		Practitioner-authored Instructions are related to a current, immediate episode of care The patient, or healthcare agent, provides direct input in the creation of the instructions which document decisions that have been made about treatments that may be utilized during a medical emergency occurring within the current episode of care.
	Type III: Portable Medical Orders for Life-Sustaining Treatments
		Practitioner-authored A set of medical orders intended to follow a patient and be available across the continuum of care The patient, or healthcare agent, provides direct input in the creation of the instructions. These orders are used to document a provider’s order for or prohibition of treatments that are to be utilized during a future medical emergency that would necessitate this type of treatment be necessitated and are based on a patient’s wishes for or against the treatments.

The current version of this FHIR IG covers the use of RESTful API interactions for creation, sharing, query/access, and verification of advance directive documentation between systems. It is intended to address advance directive interoperability needs for Content Type 1, where the author is the individual that is making medical intervention goals, preferences, priorities known in advance. This IG is not intended to cover medical intervention goals, preferences, priorities for individuals who are not able to make their own wishes known.

Future versions of this FHIR IG will address encounter-centric patient instructions, Content Type 2, and portable medical orders for life-sustaining treatment, Content Type 3.

 

About PACIO

The PACIO Project is a collaborative effort to advance interoperable health data exchange between post-acute care (PAC) and other providers, patients, and key stakeholders across health care and to promote health data exchange in collaboration with policy makers, standards organizations, and industry through a consensus-based approach.

The primary goal of the PACIO Project is to establish a framework for the development of Fast Healthcare Interoperability Resources (FHIR) technical implementation guides and reference implementations that will facilitate health data exchange through standards-based use case-driven application programming interfaces (APIs).

Project Need

Systems used to create and update patient-generated advance care plans through a patient-directed process need a way for individuals to communicate information about their advance medical care goals, preferences, and priorities. Individuals need a way to generate and update information related to their advance directives so that their current wishes can inform provider-generated care plans. Interoperable exchange of the advance directive documentation supports more effective sharing of this information across transitions of care and enables practitioners to create person-centered care plans that align with a patient’s values, goals of care, treatment preferences, and quality of life priorities when a patient can no longer communicate for themselves.

External drivers

The aging population receiving healthcare in skilled nursing facilities and assisted living communities have been under forced isolation to reduce the risk of contracting COVID-19. Additionally, due to the pandemic, those requiring medical care have experienced transitions of care without family or a personal advocate to accompany them in order to influence medical care or be at their side; concerns about the viral transmission potential associated with paper advance directive documents further complicate transitions of care. The impact is a sense of disempowerment, isolation, and a disconnection with the world they can no longer safely interact freely with.

Never before has the availability of verifiable digital advance directive documents been so essential to delivering care.

Providers understand that a person’s goals, preferences, and priorities for care are a critical element in a person-centered healthcare system.

The role of technology and expanded adoption by the aging population, providers, and care teams has brought to the forefront the expectation of seamless accessibility of advance directive information.

Audience/Expected Users

The audience for this IG includes architects and developers of healthcare information technology (HIT) systems in the US Realm that exchange clinical and non-clinical data. Business analysts and policy managers can also benefit from a basic understanding of the use of FHIR profiles across multiple implementation use cases. Finally, Quality Reporting Agencies, Standards Development Organizations (SDOs), Payors, Providers and Patients will benefit from this IG.

How to read this Guide

This Guide is divided into several pages which are listed at the top of each page in the menu bar.

• Home: The home page provides the introduction and background information to set context for the use of the HL7 FHIR® ADI Implementation Guide.
• Guidance: These pages provide overall guidance in using the profiles and transactions defined in this guide by detailing the patient stories and personas and use cases.
  • Patient Stories and Personas: Patient stories and personas give context to the data exchange standards detailed in the technical areas of the IG. They allow the non-technical reader to envision situations in which the IGs provisions would apply, and ensure that the IG meets the intended needs for exchange of this type of information.
  • Use Cases: A use case is a list of technical actions or event steps typically defining the interactions between a role and a system to achieve a goal. The actor can be a human or other external system. Technical scenarios that describe systems interactions between technical actors to implement the use case.
  • General Guidance: Information about conformance to the guide including Must Support requirements, document signatures, and document workflow.
  • Security: General security requirements and recommendations for HL7 FHIR® ADI Implementation Guide actors, including authentication, authorization, and logging requirements and guidance.
• FHIR Artifacts: These sections provide detailed descriptions and formal definitions for all the FHIR artifacts defined in this guide.
  • Profiles: This section lists the set of Profiles that are defined in this guide to exchange advance directive information. Each linked Profile page includes a narrative introduction and a formal definition.
  • Extensions: This section lists the set of Extensions that are defined in this guide that are used by the IG defined profiles. Each linked Extension page includes a formal definition.
  • Search Parameters and Operations: This section lists the HL7 FHIR® ADI Implementation Guide defined Operations and Search Parameters that are used in ADI transactions.
  • Terminology: This section lists the value sets and code system defined for HL7 FHIR® ADI Implementation Guide profiles.
  • Capability Statement: The following artifacts define the specific capabilities that different types of systems need to support to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the included capability statements.
  • Examples: The section that contains examples of advance directive information that is conformant to the profiles of this guide.
• Downloads: This page provides links to downloadable artifacts.

Key Terms and Acronyms

Term	Definition
Patient story	Patient stories are fictitious illustrative personal stories that are included to show the personal nature of the information being shared and demonstrate the value of having and sharing personal advance care plan information or, alternatively, the negative outcomes that arise when this information is not available in a high-quality, standardized, sharable digital format. Personas are used to model, summarize and communicate research about people who have been observed or researched in some way. A persona is depicted as a specific person but is not a real individual; rather, it is synthesized from observations of many people.
Use case	A use case is a list of technical actions or event steps typically defining the interactions between a role and a system to achieve a goal. The actor can be a human or other external system. Technical scenarios that describe systems interactions between technical actors to implement the use case.
Advance directives	A general term that encompasses all of the following: Living will (what you want), medical power of attorney (who speaks), combined living will and medical power of attorney. These documents have several names depending on where you are. “Advance directives” is the general term that people use to refer to all of these documents as a concept.
ADI	Advance Directive Interoperability

Dependencies

This implementation guide relies on the following other specifications:

• FHIR R4 - The version of FHIR used as the base for this implementation guide.
• US Core STU4.0.0 - The version of US Core based on FHIR R4.

ADI Profiles

Table: ADI Profiles

CONTENT TYPE I: Advance Directive Information (in STU1 scope)
Name of Profile to be developed		Short description	Based On
1	ADI Document Reference	This profile defines constraints that represent the information needed to register an advance directive information document on a FHIR server.	US Core DocumentReference
2	ADI Header	This profile defines constraints that represent common administrative and demographic concepts for advance directives information used in US Realm clinical documents.	ClinicalDocument
3	ADI Personal Advance Care Plan Composition	This profile encompasses information that makes up the author’s advance care information plan.	ADI Header
4	ADI Participant	This profile represents a person participating in a persons advance directives in some capacity such as healthcare agent or healthcare agent advisor.	RelatedPerson
5	ADI Participant Consent	This profile is used to represent a consent for an advance directive participant such as a healthcare agent or advisor and power or limitation granted to such persons.	Consent
6	ADI Documentation Observation	This profile is used to indicate if additional advance directive documents, such as physician order for life sustaining treatment (MOLST or POLST) or Do Not Resuscitate Order (DNR) exist and a reference to the document.	Observation
7	ADI Goal	This profile defines the base requirements for all ADI Goals.	US Core Goal
8	ADI Personal Intervention Preference	This profile is used to represent a personal preference for a type of medical intervention (treatment).	ADI Goal
9	ADI Care Experience Preference	This profile is a clinical statement that presents the author's personal thoughts about something he or she feels is relevant to his or her care experience and may be pertinent when planning his or her care.	ADI Goal
10	ADI Personal Goal	This profile is a statement that presents the author's personal health and treatment goals that are pertinent when planning his or her care.	ADI Goal
11	ADI Personal Priorities Organizer	This profile is used to represent a set of personal goals, preferences or care experiences in a preferred ranked order.	List
12	ADI Organ Donation Observation	This profile is used to represent the author's thoughts about organ donation.	Observation
13	ADI Autopsy Observation	This profile is used to represent the author's thoughts about autopsy.	Observation
14	ADI Provenance	Advance Directive Interoperability Provenance based on US Core to capture, search and fetch provenance information associated with advance directive interoperability data.	US Core Provenance
CONTENT TYPE II: Encounter-Centric Patient Instructions (after STU1)
Name of Profile to be developed		Short description	Based On
15	ADI Obligation Instruction	This profile always expresses activities that care providers have been instructed to perform.	Consent
16	ADI Prohibition Instruction	This profile always expresses activities that care providers have been instructed not to perform.	Consent
17	Advance Directives Organizer	This profile groups a set of advance directive observations documented together at a single point in time, and relevant during the episode of care being documented.	List
18	ADI Advance Directives Observation	This profile is used to record information about a document authored by the person and containing goals, preferences, and priorities for care.	Observation
19	ADI Advance Care Planning Intervention	This profile is used to record a planned intervention that will involve reviewing and verifying a person’s directives, or will involve educating and supporting a person on establishing or modifying his or her advance directives.	US Core Procedure
CONTENT Type III: P/MOLST (after STU1)
Name of Profile to be developed		Short description	Based On
20	ADI Consent for Portable Medical Orders	This profile is used to express the patient’s or healthcare agent consent that is not bound by an encounter.	Consent
21	ADI Consent for DNR Orders	This profile is used to express the patient’s or healthcare agent consent that is not bound by an encounter.	Consent
Sharing Documents
Name of Profile to be developed		Short description	Based On
22	ADI Consent to Share	This profile is used to expresses the patient’s or healthcare agent consent to share Advance Directive information with others	Consent