Privacy Consent on FHIR (PCF)
1.1.0 - Trial-Implementation
This page is part of the Privacy Consent on FHIR (PCF) (v1.1.0: Publication) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Official URL: https://profiles.ihe.net/ITI/PCF/CapabilityStatement/IHE.PCF.consentRegistry | Version: 1.1.0 | |||
Active as of 2023-02-14 | Computable Name: IHE_PCF_consentRegistry |
CapabilityStatement for Consent Registry Actor.
Explain
Raw OpenAPI-Swagger Definition file | Download
application/fhir+xml
, application/fhir+json
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.
server
PCF Consent Registry actor provides capability to record, search, and manage Consents.
Recommend ATNA, encouraged IHE-IUA or SMART-app-launch
search-system
interaction.The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include
_revinclude
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 |
create
, read
, update
, delete
, search-type
.PCF transaction Access Consent [ITI-108]
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 |