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 Intermediate Consent

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

Explicit Intermediate Consent

  • all elements allowed by Basic are allowed here, plus the following
  • restriction at the root .provision apply to the whole Consent
    • restrictions at the .provision.provision are exceptions to the base consent
    • no .provision.provision.provisions are allowed
  • data authored in a timeframe is specified in the .dataPeriod element
  • explicit data objects are indicated in the .data element with .meaning of #instance
  • data with relationship to an object are indicated in a .data element with .meaning of #related
  • data authored by a given actor is indicated in the .data element with .meaning of #authoredby
  • purposes of use activities are indicated in the .purpose element
  • securityLabel is not allowed, see Advanced

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
.... class 0..0
.... code 0..0
.... dataPeriod S 0..1 Period Timeframe for data controlled by this rule
.... Slices for data S 0..* BackboneElement Data controlled by this rule
Slice: Unordered, Closed by value:meaning
..... data:iData 0..* BackboneElement Data controlled by this rule
...... meaning 1..1 code instance | related | dependents | authoredby
Required Pattern: instance
..... data:rData 0..* BackboneElement Data controlled by this rule
...... meaning 1..1 code instance | related | dependents | authoredby
Required Pattern: related
...... reference 1..1 Reference(Encounter | CarePlan | EpisodeOfCare) The actual data reference
..... data:aData 0..* BackboneElement Data controlled by this rule
...... meaning 1..1 code instance | related | dependents | authoredby
Required Pattern: authoredby
...... reference 1..1 Reference(Practitioner | PractitionerRole | Organization | Device | Group | CareTeam | Patient | RelatedPerson) The actual data reference
.... provision S 0..* BackboneElement Nested Exception Rules
..... purpose S 0..* Coding Context of activities covered by this rule
..... dataPeriod S 0..1 Period Timeframe for data controlled by this rule
..... Slices for data S 0..* BackboneElement Data controlled by this rule
Slice: Unordered, Closed by value:meaning
...... data:iDataP 0..1 BackboneElement Data controlled by this rule
....... meaning 1..1 code instance | related | dependents | authoredby
Required Pattern: instance
...... data:rDataP 0..1 BackboneElement Data controlled by this rule
....... meaning 1..1 code instance | related | dependents | authoredby
Required Pattern: related
....... reference 1..1 Reference(Encounter | CarePlan | EpisodeOfCare) The actual data reference
...... data:aDataP 0..1 BackboneElement Data controlled by this rule
....... meaning 1..1 code instance | related | dependents | authoredby
Required Pattern: authoredby
....... reference 1..1 Reference(Practitioner | PractitionerRole | Organization | Device | Group | CareTeam | Patient | RelatedPerson) The actual data reference
..... provision 0..0

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron