Privacy Consent on FHIR (PCF)
1.1.1-current - ci-build

Privacy Consent on FHIR (PCF), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.1.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.PCF/ and changes regularly. See the Directory of published versions

## CapabilityStatement: PCF Consent Registry Actor

Official URL: https://profiles.ihe.net/ITI/PCF/CapabilityStatement/IHE.PCF.consentRegistry | Version: 1.1.1-current
Active as of 2023-02-14 | Computable Name: IHE_PCF_consentRegistry

CapabilityStatement for Consent Registry Actor.

Explain

- provides Access Consent [ITI-108] to store and support access to Privacy Consent Resources

Raw OpenAPI-Swagger Definition file | Download

## IHE PCF Consent Registry

- Implementation Guide Version: 1.1.1-current
- FHIR Version: 4.0.1
- Supported Formats: `application/fhir+xml`, `application/fhir+json`
- Published on: 2023-02-14
- Published by: IHE IT Infrastructure Technical Committee

> Note to Implementers: FHIR Capabilities

> Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

## FHIR RESTful Capabilities

### Mode: `server`

PCF Consent Registry actor provides capability to record, search, and manage Consents.

Security

> Recommend ATNA, encouraged IHE-IUA or SMART-app-launch

Summary of System-wide Interactions

- Supports the `search-system`interaction.

### Capabilities by Resource/Profile

#### Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

- The relevant profiles (if any)
- The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
- The required, recommended, and some optional search parameters (if any).
- The linked resources enabled for `_include`
- The other resources enabled for `_revinclude`
- The operations on the resource (if any)

Resource Type | Profile | R | S | U | C | D | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Consent |  | y | y | y | y | y | _lastUpdated, _id, status, patient, patient.identifier, actor |  |  |

#### Resource Conformance: supported Consent

Core FHIR Resource
Consent
Reference Policy
Interaction summary

- Supports `create`, `read`, `update`, `delete`, `search-type`.

Documentation

> PCF transaction Access Consent [ITI-108]

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | _lastUpdated | `date` | When the resource version last changed
SHALL | _id | `token` | Logical id of this artifact
SHALL | status | `token` | Whether the Consent record is active
SHALL | patient | `reference` | The Patient
SHALL | patient.identifier | `token` |
SHALL | actor | `token` |