×

To enhance security, Multi-Factor Authentication (MFA) is mandatory for all HL7 users. More information

 

FAST Consent Management FHIR IG (Jira PSS-2354)

Basics

FAST Consent Management FHIR IG (Jira PSS-2354)

1878
Ballot - STU


FHIR Implementation Guide

Implementation Guide

Details

Patient Consent management is the central component in a consent ecosystem and at the core of a scalable consent architecture. This project is about answering the question "is it possible to determine if payer/provider X have authority to view healthcare data Y about patient Z?". This FAST project will be dealing with how to handle the use cases across a set of consent management repositories in a scaleable fashion.

Our initial set of potential use cases are:

1. Provider-Initiated Request to Consent

2. Patient-Initiated Consent

3. Review Consent

4. File/Sign Consent

5. Delegate Consent

6. Revoke Consent

7. Propogation of Revocation

8. Disclosure Audit

9. Query Consent Decision

10. Enforce Consent Decision

NOTE: The actual authentication (is the consumer who they say they are) and data authorization (does the consumer have access to patient health data) is not in scope of this IG. We will provide the operations to gather and request consent and answer the question on whether a consumer has been granted consent to a patient's specific set healthcare data. The question of whether the consumer can actually access a patient's health data based on legal, corporate, and other policies and the granted consent is not in scope.

This project intends to create a FHIR Implementation Guide that details the consent management use cases as well as the required custom FHIR operations and profiles to exchange the required consent data elements both between the user and the consent mangement repository as well as between repositories.


There is currently some support for some basic consent management use cases in the existing specifications, including FHIR Core and the IHE.ITI Privacy Consent on FHIR (PCF), mostly at the basic operations for creating, reading, and updating consent resources. Consent management, however, needs more implementation guidance and standardized specifications that are still missing. This includes the interactions between patients and the consent management system in the process of soliciting, navigating, and executing consents, which is sometimes referred to as consent ceremony, as well as a high-level API (e.g., defining custom FHIR operations) to cover use cases for consent management.



FHIR IG R1 - STU Ballot - Target: 2025 Jan Ballot Cycle


https://github.com/HL7/fhir-consent-management PSS: https://jira.hl7.org/browse/PSS-2354



Other (specify in Misc. Notes below),N/A

Edifecs HCSC




N/A

N/A

No

Stakeholders: Consultant, Healthcare IT Vendors, Healthcare Provider/user, Patients, Payer/Third Party Administrator, Providers, Vendor/Manufacturer
Organization & Realm

Universal

People

Jean Duteau



Community-Based Care and Privacy (CBCP) Work Group


Status & Dates

Active

Active Project (Resources assigned to pjt)

02/29/2024

01/15/2028

2028 Jan WGM/Ballot

01/15/2027

2027 Jan WGM/Ballot

2026 Jan Cycle; STU ballot. Met basic vote requirements with 27 negatives to reconcile. Ballot name: HL7 FHIR® Implementation Guide: Consent Management, Edition 1- US Realm
Approvals

04/02/2024


Not Needed


All Received




FHIR Management Group -- Agreed -- (PSS-2364)
US Realm -- Agreed -- (PSS-2370)
System Info

229276

PSS-2354



04/09/2026

Anne Wizauer