StructureDefinition-IHE.PCF.consentBasic

Source

ihe.iti.pcf#current:Privacy Consent on FHIR (PCF) (v4.3.0)

resourceType

StructureDefinition

IHE.PCF.consentBasic

canonical

https://profiles.ihe.net/ITI/PCF/StructureDefinition/IHE.PCF.consentBasic

version

1.0.0

status

active

publisher

IHE IT Infrastructure Technical Committee

name

BasicConsent

title

IHE PCF Explicit Basic Consent

date

2023-08-05T12:10:13+00:00

description

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

jurisdictions

fhirVersion

4.3.0

kind

resource

abstract

false

sdTtype

Consent

derivation

constraint

base

http://hl7.org/fhir/StructureDefinition/Consent

Usages

(none)

Name	Flags	Card.	Type	Description & Constraints
Consent			Consent
scope				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..
dateTime		1..
performer		1..
organization		1..
source[x]		1..
policy
uri		1..
verification		.. 0
provision	S	1..
type		1..
period	S
actor	S
role				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
securityLabel		.. 0
purpose	S			Binding: Basic Purpose ValueSet ( extensible )
class		.. 0
code		.. 0
dataPeriod		.. 0
data		.. 0
provision		.. 0
Documentation for this format

Produced 08 Sep 2023