Advance Healthcare Directive Interoperability (cda-adi)
0.1.0 - ci-build

Advance Healthcare Directive Interoperability (cda-adi), published by Health Level Seven. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cda-adi/ and changes regularly. See the Directory of published versions

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

ADI Healthcare Agent Consent Entry

This entry includes the person's consent to appoint a Healthcare Agent. It may include powers granted or denied.

ADI Source Form Entry

This entry includes the Source Form document and info about the jurisdiction for the form. If the form is copyrighted by an organization, the organization's name may be included in an author participation.

Additional Documentation Section

This section contains information about additional relevant advance healthcare directive documents.

Additional Order Entry

This entry is an act in moodCode RQO. In FHIR this expresses a ServiceRequest with an intent of a directive. Each entry includes only a single procedures (with moodCode RQO) for the person as a portable medical order. If the order is to NOT perform the procedure, then negationInd will be true for the procedure. In FHIR this aligns with use of the doNotPerform element.

Additional Order Procedure Information

This entry is a procedure in moodCode RQO. In FHIR this expresses the ServiceRequest.code. If the order is to NOT perform the procedure, then negationInd will be true for the procedure. In FHIR this aligns with use of the doNotPerform element.

Administrative Information Section

This section contains information about additional administrative data.

Agent Appointment Part of the ADI Healthcare Agent Consent Entry

Sub-part of the ADI Healthcare Agent Consent Entry. This entry part includes the info about who was apointed a healthcare agent and their ordinal role. This entry is not intended to be used as a complete clinical statement entry on its own.

CPR Order Detail

This entry is an act in moodCode RQO. In FHIR this expresses the ServiceRequest.orderDetail. For a CPR order, there can be only one order detail.

CPR Procedure Information

This entry is an procedure in moodCode RQO. In FHIR this expresses the ServiceRequest.code. If the order is to NOT perform the procedure, then negationInd will be true for the procedure. In FHIR this aligns with use of the doNotPerform element.

Cardiopulmonary Resuscitation Order Entry

This entry is an act in moodCode RQO. In FHIR this expresses a ServiceRequest with an intent of a directive. It includes a CPR procedure (in moodCode RQO) for the person as a portable medical order. If the order is to NOT perform the procedure, then negationInd will be true for the procedure. In FHIR this aligns with use of the doNotPerform element.

Care Experience Preferences Section

This section contains information about the person's expressed care experience preferences.

Coded Powers Granted Part of the ADI Healthcare Agent Consent Entry

Sub-part of the ADI Healthcare Agent Consent Entry. This entry part includes powers granted which are specific coded concepts. This entry is not intended to be used as a complete clinical statement entry on its own.

Completion Information Section

This section contains information about requirements to complete the document as a valid form.

Form Title Part of the ADI Source Form Entry

Sub-part of the ADI Source Form Entry. This entry part includes the form title. This entry is not intended to be used as a complete clinical statement entry on its own.

Healthcare Agent Appointment Section

This section contains the consent to appoint one or more healthcare agents and additional information about the agents' powers or limitations.

Initial Treatment Order Detail

This entry is an act in moodCode RQO. In FHIR this expresses the ServiceRequest.orderDetail. For a CPR order, there can be only one order detail.

Initial Treatment Order Entry

This entry is an act in moodCode RQO. In FHIR this expresses a ServiceRequest with an intent of a directive. Each entry includes only a single procedures (with moodCode RQO) for the person as a portable medical order. If the order is to NOT perform the procedure, then negationInd will be true for the procedure. In FHIR this aligns with use of the doNotPerform element.

Initial Treatment Procedure Information

This entry is an procedure in moodCode RQO. In FHIR this expresses the ServiceRequest.code. If the order is to NOT perform the procedure, then negationInd will be true for the procedure. In FHIR this aligns with use of the doNotPerform element.

Jurisdiction Part of the ADI Source Form Entry

Sub-part of the ADI Source Form Entry. This entry part includes the info about the jurisdiction for the form. This entry is not intended to be used as a complete clinical statement entry on its own.

Medically Assisted Nutrition Order Detail

This entry is an act in moodCode RQO. In FHIR this expresses the ServiceRequest.orderDetail. For a CPR order, there can be only one order detail.

Medically Assisted Nutrition Order Entry

This entry is an act in moodCode RQO. In FHIR this expresses a ServiceRequest with an intent of a directive. Each entry includes only a single procedures (with moodCode RQO) for the person as a portable medical order. If the order is to NOT perform the procedure, then negationInd will be true for the procedure. In FHIR this aligns with use of the doNotPerform element.

Medically Assisted Nutrition Procedure Information

This entry is an procedure in moodCode RQO. In FHIR this expresses the ServiceRequest.code. If the order is to NOT perform the procedure, then negationInd will be true for the procedure. In FHIR this aligns with use of the doNotPerform element.

Personal Advance Care Plan

This profile defines the requirements for communicating a Personal Advance Care Plan (ACP) document using a Composition Resource.

Depending on the range of content included, this type of document is known by different names:

  • Durable Medical Power of Attorney - healthcare agent appointment only
  • Living Will - treatment preferences only
  • Living Will and Durable Medical Power of Attorney
  • Advance Care Plan - a combined Living Will and Durable Medical Power of Attorney plus additional content regarding relevant care experience preferences

It is a person-generated document, authored by the subject of the document. If care professionals are involved in the creation of the document, their supporting role in the advance care planning process can be represented in the service event associated with the document. If data entry assistance is provided, the person performing the data entry can be represented in the role of a data enterer.

Additionally, the system used to assemble the document can be represented as a participant of the document in the role of Assembler. The Custodian organization responsible for maintaining the source copy of the document must be included.

For a person authored document, the person's signature is required. Notarization or witnessing of the document also should be represented because person-authored documents typically are not considered complete without validation for the person's identity and signature.

The document includes a mandatory source form section to hold a pdf of the original “source form” completed by the person. It also includes a healthcare agent appointment section which is mandatory in all types of PACP documents with the exception of a Living Will. If the person elects not to appoint a healthcare agent, the section includes information about the reason why. This section includes machine processable representations of the healthcare agent information and their powers and limitations to facilitate data resusability as the document is shared between systems.

A Personal ACP document may contain additional textual information from the source form that does not have corresponding encoded entries. In this case, the section.text element is populated without corresponding section.entry elements. For minimum required information, the information in the section.text element will include corresponding section.entry elements and will be linked using the test linking mechanism.

Optionally, the document may contain sections for treatment intervention preferences, care experience preferences, additional documentation, administrative information which includes record of the person's signature, and notary or witness information.

Planned Procedure PMO Section

This section contains portable medical orders for the patient.

Portable Medical Order

This profile defines the requirements for communicating a practitioner-authored portable medical order (PMO) advance healthcare directive document using a Composition Resource. Different states may call this type of document by a number of different names:

  • MOLST (Medical Orders for Life Sustaining Treatment)
  • POLST (Physician Orders for Life Sustaining Treatment)
  • MOST (Medical Orders for Scope of Treatment)
  • POST (Physician Orders for Scope of Treatment)
  • TPOPP (Transportable Physician Orders for Patient Preferences)
  • Out-of-hospital Do Not Resuscitate (DNR) Orders
  • DNAR (Do Not Attempt Resuscitation) or AND (Allow Natural Death) Orders

It is a practitioner-generated document, authored by a practitioner with necessary credentials established for the document within its jurisdiction of use. If other care professionals are involved in the creation of the document, their supporting role in the advance care planning process can be represented in the service event associated with the document. If data entry assistance is provided, the person performing the data entry can be represented in the role of a data enterer. However, only the authoring practitioner signs the document as the legal authenticator. The signature of the person/patient who is the subject of the document also is required. If the subject is unable to sign the document, a person who is permitted to sign on their behalf may sign in place of the subject.

Additionally, the system used to assemble the document can be represented as a participant of the document in the role of Assembler. The Custodian organization responsible for maintaining the source copy of the document must be included.

The document includes a mandatory source form section to hold a pdf of the original “source form” showing the PMO completed by the practitioner and patient. It also includes a mandatory Medical Orders section. This section includes machine processable representations of–at a minimum- the directive regarding cardiopulmonary resuscitation. Other directives such as initial treatment and other types of orders may also be included to facilitate data resusability as the document is shared between systems. However, the source form remains the “source of truth” providing the full range of relevant orders.

A PMO document may contain additional textual information from the source form that does not have corresponding encoded entries. In this case, the section.text element is populated without corresponding section.entry elements. For minimum required information, the information in the section.text element will include corresponding section.entry elements and will be linked using the test linking mechanism.

Optionally, the document may contain sections for form completion information which includes the necessary signature information, administrative information, additional documentation, upon death information, healthcare agent appointment, and notary and witness information.

Powers Denied Part of the ADI Healthcare Agent Consent Entry

Sub-part of the ADI Healthcare Agent Consent Entry. This entry part includes powers denied. This entry is not intended to be used as a complete clinical statement entry on its own.

Powers Granted Part of the ADI Healthcare Agent Consent Entry

Sub-part of the ADI Healthcare Agent Consent Entry. This entry part includes powers granted. This entry is not intended to be used as a complete clinical statement entry on its own.

Source Form Section

This section shall contain the binary object used to render the source form in it's original format with completion signatures, etc.

Treatment Intervention Preferences Section

This section contains treatment intervention preferences under potential future health scenarios expressed by the person.

Upon Death Preferences Section

This section contains care experience preferences expressed by the person which address what they want to have happen after their death.

Witness And Notary Section

This section contains the person's signature information with Witness and Notary information.