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

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 Authorization Server Actor

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

CapabilityStatement for the Consent Authorization Server Actor

Explain

  • is a Client that uses Access Consent [ITI-108] to retrieve current Privacy Consent and make access control decisions based upon them

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement IHE.PCF.consentAuthorizationServer

IHE PCF Consent Authorization Server

  • Implementation Guide Version: 1.1.1-current
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+xml, application/fhir+json
  • Supported Patch Formats:
  • 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: client

PCF Consent Authorization Server makes authorization decisions based on the existing Privacy Consent.

Security

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

Summary of System-wide Interactions
  • Supports the search-systeminteraction.

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 TypeProfileRSUCSearches_include_revincludeOperations
Consent yy_lastUpdated, _id, status, patient, patient.identifier, actor
Core FHIR Resource
Consent
Reference Policy
Interaction summary
  • Supports read, search-type.

Documentation

PCF transaction Access Consent [ITI-108]

Search Parameters
ConformanceParameterTypeDocumentation
SHALL_lastUpdateddate

When the resource version last changed

SHALL_idtoken

Logical id of this artifact

SHALLstatustoken

Whether the Consent record is active

SHALLpatientreference

The Patient

SHALLpatient.identifiertoken
SHALLactortoken