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
| Official URL: https://profiles.ihe.net/ITI/PCF/CapabilityStatement/IHE.PCF.consentRecorder | Version: 1.1.1-current | |||
| Active as of 2023-02-14 | Computable Name: IHE_PCF_consentRecorder | |||
CapabilityStatement for the Consent Recorder Actor
Explain
Raw OpenAPI-Swagger Definition file | Download
application/fhir+xml, application/fhir+jsonNote 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.
clientPCF Consent Recorder provides capability to record a Privacy Consent.
Recommend ATNA, encouraged IHE-IUA or SMART-app-launch
search-systeminteraction.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 |
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 |