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

Resource Profile: IHE PCF Explicit Basic Consent

Official URL: https://profiles.ihe.net/ITI/PCF/StructureDefinition/IHE.PCF.consentBasic Version: 1.1.1-current
Active as of 2024-10-21 Computable Name: BasicConsent

Explicit Basic Consent

  • status 1..1 - would indicate active
  • scope 1..1 - #patient-privacy
  • category 1..1 - would indicate patient consent, specifically a delegation of authority
  • identifier 0..1 - no defined use in PCF. This could carry business identifiers assigned to the consent instance
  • patient 1..1 - would indicate the Patient resource reference for the given patient
  • dateTime 1..1 - would indicate when the privacy policy was presented
  • performer 1.. - would indicate the Patient resource if the patient was presented, a RelatedPerson for parent or guardian
  • organization 1.. - would indicate the Organization that presented the privacy policy, and that is going to enforce that privacy policy
  • source 1..1 - would point at the specific signed consent by the patient
  • policy.uri 1..1 - would indicate the privacy policy that was presented. Usually, the url to the version-specific policy
  • provision.type 1..1 - permit indicates agreement with the policy, deny would indicate rejection.
  • provision.actor 0..* - would indicate those being granted permit / denied access, if empty then all in the community
  • provision.actor.role - fixed value IRCP to indicate information recipient.
  • provision.purpose - would indicate some set of authorized purposeOfUse
  • provision.period MS - would indicate a sunset for the consent if applicable, empty means no expiration
  • provision.provisions are allowed

Not defined in PCF, but allowed

  • policy.authority - not used in PCF
  • policyRule - not used in PCF

Not allowed in PCF

  • provision.provision.provisions - NOT allowed, no clear use-case need and would add complexity
  • verification - not used in PCF, unclear the use-case need
  • provision.action - not used in PCF. The purpose is sufficient.
  • provision.class - not used in PCF, unclear the use-case need
  • provision.code - not used in PCF, unclear the use-case need

Specifics of Basic:

  • provision.purpose - would indicate some set of authorized purposeOfUse only Treatment, Payment, or Operations, see Intermediate
  • provision.securityLabel is not allowed, see Intermediate
  • provision.dataPeriod is not allowed, see Intermediate
  • provision.data is nto allowed, see Intermediate
  • provision.provision are NOT allowed, see Intermediate

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Consent

NameFlagsCard.TypeDescription & Constraintsdoco
.. Consent 0..* Consent A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
... scope 1..1 CodeableConcept Which of the four areas this resource covers (extensible)
Required Pattern: At least the following
.... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
..... system 1..1 uri Identity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/consentscope
..... code 1..1 code Symbol in syntax defined by the system
Fixed Value: patient-privacy
... patient 1..1 Reference(Patient) Who the consent applies to
... dateTime 1..1 dateTime When this Consent was created or indexed
... performer 1..* Reference(Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Who is agreeing to the policy and rules
... organization 1..* Reference(Organization) Custodian of the consent
... source[x] 1..1 Attachment, Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Source from which this consent is taken
... policy
.... uri 1..1 uri Specific policy covered by this consent
... verification 0..0
... provision S 1..1 BackboneElement Constraints to the base Consent.policyRule
.... type 1..1 code deny | permit
.... period S 0..1 Period Timeframe for this rule
.... actor S 0..* BackboneElement Who|what controlled by this rule (or group, by role)
..... role 1..1 CodeableConcept How the actor is involved
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: IRCP
.... action 0..0
.... securityLabel 0..0
.... purpose S 0..* Coding Context of activities covered by this rule
Binding: Basic Purpose ValueSet (extensible)
.... class 0..0
.... code 0..0
.... dataPeriod 0..0
.... data 0..0
.... provision 0..0

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Consent.provision.purposeextensibleBasicPurposeVS
https://profiles.ihe.net/ITI/PCF/ValueSet/BasicPurposeVS
from this IG

 

Other representations of profile: CSV, Excel, Schematron