Consent (10)

#NameSourceVerDescription
1Consent to allow use for treatmentjohnmoehrke.consentwithsegmentation#currentR5Some useful
2Consent-IEHRfhir.uv.crossborderdataexchange#currentR4
3IHE PCF Explicit Advanced Consentihe.iti.pcf#currentR4BExplicit Advanced Consent - all elements allowed by Basic and Intermediate are allowed here, plus the following - `securityLabel` indicates sensitivity or confidentiality tags on data - Only codes from [Avanced Security Tag ValueSet](ValueSet-AdvancedSecurityTagVS.html)
4IHE PCF Explicit Basic Consentihe.iti.pcf#currentR4BExplicit 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
5IHE PCF Explicit Intermediate Consentihe.iti.pcf#currentR4BExplicit 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
6Most Simple Patient Consentjohnmoehrke.testConsent.example#currentR4BConsent constrained to just be a patient consent.
7Simple Consent Privacy with no provisionjohnmoehrke.testConsent.example#currentR4BConsent constrained minimally to be a patient privacy consent, forbidding any provisions.
8Simple Consent Privacy with root provision but nothing morejohnmoehrke.testConsent.example#currentR4BConsent constrained minimally to be a patient privacy consent, with restriction on one level deep.
9Simple Consent Privacy with two provisions deepjohnmoehrke.testConsent.example#currentR4BConsent constrained minimally to be a patient privacy consent, with restriction of provisions only two levels deep.
10VhDir Restrictionhl7.fhir.uv.vhdir#currentR4Restriction on use/release of exchanged information
1 2 3 4 5 6 7 8 9 10
Consent
Consent.policyRule C
Consent.policy
Consent.policy.authority C
Consent.source[x] C C C C
Consent.organization C C C C C C C
Consent.patient C C C C C C C C
Consent.scope F F F F F F B M
Consent.performer C C C C C C C C
Consent.dateTime C C C C C C C C D
Consent.meta
Consent.implicitRules
Consent.language
Consent.text C
Consent.contained
Consent.extension S C (2)
Consent.modifierExtension
Consent.identifier C
Consent.status F C F F F D
Consent.category S C F (2) C D
Consent.subject C
Consent.date
Consent.period
Consent.grantor
Consent.grantee
Consent.manager
Consent.controller
Consent.sourceAttachment
Consent.sourceReference
Consent.regulatoryBasis
Consent.policyBasis
Consent.policyBasis.extension
Consent.policyBasis.modifierExtension
Consent.policyBasis.reference
Consent.policyBasis.url
Consent.policyText
Consent.verification C C C C
Consent.verification.extension
Consent.verification.modifierExtension
Consent.verification.verified
Consent.verification.verificationType
Consent.verification.verifiedBy
Consent.verification.verifiedWith
Consent.verification.verificationDate
Consent.decision
Consent.provision C C C C C
Consent.provision.class C C C C
Consent.provision.type C C C F
Consent.provision.extension
Consent.provision.modifierExtension
Consent.provision.period C
Consent.provision.actor C
Consent.provision.actor.extension
Consent.provision.actor.modifierExtension
Consent.provision.actor.role F F F
Consent.provision.actor.reference
Consent.provision.action C C C C D
Consent.provision.securityLabel B M C C
Consent.provision.purpose B M D
Consent.provision.documentType
Consent.provision.resourceType
Consent.provision.code C C C C
Consent.provision.dataPeriod C C
Consent.provision.data C S C (4) C
Consent.provision.data.extension
Consent.provision.data.modifierExtension
Consent.provision.data.meaning F (3)
Consent.provision.data.reference (2)
Consent.provision.expression
Consent.provision.provision C C C
Consent.provision.provision.data S C (4)
Consent.provision.provision.data.reference (2)
Consent.provision.provision.data.meaning F (3)
Consent.provision.provision.dataPeriod
Consent.provision.provision.purpose
Consent.provision.provision.provision C C C C
Consent.provision.provision.securityLabel B M
Consent.policy.uri C C C
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023