eHealth Infrastructure
10.0.0 - release Denmark flag

eHealth Infrastructure, published by Den telemedicinske infrastruktur (eHealth Infrastructure). This guide is not an authorized publication; it is the continuous build for version 10.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/fut-infrastructure/implementation-guide/ and changes regularly. See the Directory of published versions

Resource Profile: ehealth-consent

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-consent Version: 10.0.0
Active as of 2026-08-06 Computable Name: ehealth-consent

Introduction

A Consent resource is a record of a healthcare consumer’s policy choices, which permits or denies identified actors(s) or identified role(s) to perform one or more actions within a given policy context, for specific purpose(s) and period of time.

Scope and Usage

In the eHealth infrastructure a Consent resource is used

  1. as a record of the fact that a Patient has given a Consent and
  2. to enforce data policies that require Consent to be given and recorded for a Patient.

The eHealth profile of Consent has the following extensions:

  • ehealth-consent-affiliation which specifies the care context level to which the consent applies—either EpisodeOfCare level (mandatory reference) or CarePlan level (optional reference). See section on Affiliation below.

When a Patient gives a consent, this consent must be recorded as a Consent resource. This resource can be created by the Patient herself or by a Practitioner as a result of conversations or correspondence with the Patient.

eHealth operates with three categories of consents:

  1. Category PITEOC: Consent given by a Patient to be enrolled into a telemedical EpisodeOfCare. This Consent is interpretated to also apply to all CarePlan instances related to the consented EpisodeOfCare.

  2. Category SSLPCI: Consent given by a Patient to have his/her contact information (physical address and telecommunication endpoints) being disclosed to a specified actor supplying device(s) and service(s) to the Patient as part of an EpisodeOfCare and related CarePlan(s).

  3. Category behavior-by-policy: A policy-driven behaviour marker that records whether an actor is permitted or denied a behaviour, where the concrete behaviour is identified by the Consent.policy.uri. Unlike PITEOC and SSLPCI, a behavior-by-policy Consent is not necessarily a consent given by the Patient — it is typically recorded by a Practitioner. The behaviour can be scoped to a care pathway (EpisodeOfCare) and/or a citizen-specific plan (CarePlan) by means of the ehealth-consent-affiliation extension. The policies that can be expressed are defined in the ValueSet ehealth-consent-policy. At present, the only defined policy controls whether triage results may be displayed to the Patient; additional policies may be added in the future. See Controlling display of triage results to the Patient and Affiliation below for details of that policy.

Consents of category PITEOC are expressed by creating a Consent resource with:

  • Consent.category.coding.system = "http://ehealth.sundhed.dk/cs/consent-category"
  • Consent.category.coding.code = "PITEOC".

Consents of category SSLPCI are expressed by creating a Consent resource with:

  • Consent.category.coding.system = "http://ehealth.sundhed.dk/cs/consent-category"
  • Consent.category.coding.code = "SSLPCI".

Consents of category behavior-by-policy are expressed by creating a Consent resource with:

  • Consent.category.coding.system = "http://ehealth.sundhed.dk/cs/consent-category"
  • Consent.category.coding.code = "behavior-by-policy"
  • Consent.policy.uri set to the policy that defines the behaviour being decided. The policy must be one of those in the ValueSet ehealth-consent-policy - it is the policy that gives the Consent its concrete meaning.

The remaining elements to set depend on the specific policy. For the currently defined policy, see Controlling display of triage results to the Patient below.

Controlling display of triage results to the Patient

A Consent of category behavior-by-policy with Consent.policy.uri = "http://ehealth.sundhed.dk/policy/ehealth/display-triage-result" is used to record the decision of whether triage results may be displayed to the Patient. The decision can be recorded at the EpisodeOfCare level and/or at the CarePlan level by use of the ehealth-consent-affiliation extension.

The eHealth infrastructure only stores this decision. It does not act on it, does not enforce it, and does not define any precedence between levels or any default behaviour. It is the responsibility of the consuming Telemedicine Solutions to read the Consent(s), to decide which level takes precedence when decisions exist at both the EpisodeOfCare and CarePlan level, and to decide how to behave when no applicable Consent exists. The infrastructure carries no opinion on these matters.

A Consent recording this decision is expressed with the following elements:

Element Value Description
Consent.category http://ehealth.sundhed.dk/cs/consent-category#behavior-by-policy Marks this Consent as expressing a behavior governed by a policy.
Consent.scope http://ehealth.sundhed.dk/cs/ehealth-consent-scope#behavior The scope of the Consent.
Consent.policy.uri http://ehealth.sundhed.dk/policy/ehealth/display-triage-result The policy being decided on, i.e. display of triage results.
Consent.extension[ehealth-consent-affiliation] Reference to EpisodeOfCare, and optionally also CarePlan The care context level(s) the decision applies to. See Affiliation.
Consent.patient Reference to the Patient The Patient who is the subject of this Consent.
Consent.provision.type permit Records that triage results may be displayed to the Patient.
Consent.provision.class http://hl7.org/fhir/resource-types#ClinicalImpression The type of data the decision is about.
Consent.provision.code http://ehealth.sundhed.dk/cs/clinicalimpression-codes#TriagingResult The specific kind of data the decision is about.
Consent.provision.period A (possibly open-ended) period The validity period of the decision. As with the decision itself, the infrastructure stores this period but does not act on or enforce it.
Consent.status active The infrastructure does not act on the status for this category, so deciding which statuses to treat as a current decision (e.g. only active) is the responsibility of the consuming Telemedicine Solution.

The elements above are those that give this policy its meaning; the list is not exhaustive. As for any Consent, additional elements should be set as appropriate. In particular, it is recommended to also set Consent.performer (the actor recording/agreeing the decision) and Consent.organization (the custodian Organization responsible for the Consent). These have been omitted from the above for brevity.

When the affiliation extension is used, the infrastructure validates the following on create and update — if any check fails, the Consent is rejected:

  • The Consent must carry the http://ehealth.sundhed.dk/policy/ehealth/display-triage-result policy.
  • Exactly one EpisodeOfCare affiliation must be present, and it must match the EpisodeOfCare in the creating Practitioner's security context.
  • Any CarePlan affiliation must reference a CarePlan whose CarePlan.episodeOfCare equals the affiliated EpisodeOfCare.

Accordingly, the affiliation level expresses where the decision applies:

  • An affiliation to only an EpisodeOfCare expresses a decision at the care pathway (EpisodeOfCare) level.
  • An affiliation to both an EpisodeOfCare and a CarePlan expresses a decision at the citizen-specific plan (CarePlan) level.

See Affiliation for the extension definition.

See Consent/23 for an example of a Consent that records the triage-result display decision.

Note that, unlike the policy-enforcing categories PITEOC and SSLPCI (see Enforcement of Consent below), a behavior-by-policy Consent does not use Consent.provision.data.reference to bind the Consent to an EpisodeOfCare/CarePlan. Using Consent.provision.data.reference would change the meaning of the Consent (it would state which data the consent is about); the care context level is instead expressed through the ehealth-consent-affiliation extension.

Access control

A Patient (citizen) is not allowed to create or update a Consent with policy http://ehealth.sundhed.dk/policy/ehealth/display-triage-result — the decision of whether triage results may be displayed to the Patient is controlled by a Practitioner. See Remarks on operations below.

Business rules are built into eHealth infrastructure to ensure that data can only be processed or forwarded to other systems and actors when the proper Consent is given.

This means, that:

  1. An EpisodeOfCare can only change status to active if a Consent with category PITEOC has been given.
  2. An SSL Order can only change status to submitted if a Consent with category SSLPCI has been given.

In addition to the Consent.category element, the following elements must be set on a Consent resource for the policy enforcing business logic to take effect:

  • Consent.patient - the patient who is the subject of this consent (must coincide with the EpisodeOfCare.patient referenced by Consent.data.reference)
  • Consent.provision.data.reference - the EpisodeOfCare for which this Consent is in force.
  • Consent.provision.actor - the actor (Organization, CareTeam, Practitioner) whose behaviour is controlled by this consent.
  • Consent.status - the status of this consent (only active consents are considered to be in force)
  • Consent.provision.period - the (possibly open-ended) period for which this consent is in force.

For more information see the element descriptions in the snapshot table on this page and also see the example Consent resources on the Examples tab.

Affiliation

Specifies the care context level to which the consent applies—either EpisodeOfCare level (mandatory reference) or CarePlan level (optional reference). This enables precise scoping of consent in telemedicine solutions, such as controlling patient access to triage results for specific CarePlan or broader EpisodeOfCare. The Consent.provision.data element is for data controlled by the consent, while ehealth-consent-affiliation indicates the care level to which the consent applies. See Consent/23 for an example of how to use the affiliation extension.

Remarks on operations

  • As patient user
    • Search parameter patient is mandatory and must match the patient in the user context.
  • As practitioner user
    • Search parameters most contain either data or affiliation that matches the episodeOfCare in the user context.
    • Parameter affiliation:
      • If searching by affiliation for multiple CarePlans, the affiliation parameter must be specified two times ?affiliation=episodeOfCareRef&affiliation=careplanRef1,careplanRef2. A single OR search containing both episodeOfCareRef and CarePlanRefs is not allowed, as there is no guarantee the CarePlan is referencing the specified episodeOfCare.

Create

  • As patient user
    • Not allowed to create Consent with policy http://ehealth.sundhed.dk/policy/ehealth/display-triage-result.

Update

  • As patient user
    • Not allowed to update Consent with policy http://ehealth.sundhed.dk/policy/ehealth/display-triage-result.

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

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

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Consent C 0..* Consent A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
Constraints: ppc-1, ppc-2, ppc-3, ppc-4, ppc-5
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:affiliation 0..* Reference(ehealth-episodeofcare | ehealth-careplan) {r} Affiliation to EpisodeOfCare and optionally CarePlan
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-consent-affiliation
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... scope ?!Σ 1..1 CodeableConcept Specific scope covered by this consent
Binding: Consent Scope (required)
... category Σ 1..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Binding: Consent Category (required)
... patient Σ 1..1 Reference(ehealth-patient) {r} Who the consent applies to
... organization Σ 0..* Reference(ehealth-organization) {r} Custodian of the consent
... Slices for source[x] Σ 0..1 Source from which this consent is taken
Slice: Unordered, Open by type:$this
.... sourceAttachment Attachment
.... sourceReference Reference(Consent | DocumentReference | Contract | QuestionnaireResponse)
.... source[x]:sourceReference Σ 0..1 Reference(ehealth-consent | ehealth-documentreference | Contract | ehealth-questionnaireresponse) Source from which this consent is taken

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Consent.status Base required ConsentState 📍4.0.1 FHIR Std.
Consent.scope Base required Consent Scope 📦10.0.0 This IG
Consent.category Base required Consent Category 📦10.0.0 This IG

Constraints

Id Grade Path(s) Description Expression

This structure is derived from Consent

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. 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
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:affiliation 0..* Reference(ehealth-episodeofcare | ehealth-careplan) {r} Affiliation to EpisodeOfCare and optionally CarePlan
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-consent-affiliation
... scope 1..1 CodeableConcept Specific scope covered by this consent
Binding: Consent Scope (required)
... category 1..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Binding: Consent Category (required)
... organization 0..* Reference(ehealth-organization) {r} Custodian of the consent
... Slices for source[x] 0..1 Attachment, Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Source from which this consent is taken
Slice: Unordered, Open by type:$this
.... source[x]:sourceReference 0..1 Reference(ehealth-consent | ehealth-documentreference | Contract | ehealth-questionnaireresponse) Source from which this consent is taken
... policy
.... uri 0..1 uri Specific policy covered by this consent
Binding: Consent Policy (required)
... provision
.... class 0..* Coding Specific class covered by this consent
Binding: Consent Provision Class (required)
.... code 0..* CodeableConcept Specific code covered by this consent
Binding: Consent Provision Code (required)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Consent.scope Base required Consent Scope 📦10.0.0 This IG
Consent.category Base required Consent Category 📦10.0.0 This IG
Consent.policy.uri Base required Consent Policy 📦10.0.0 This IG
Consent.provision.class Base required Consent Provision Class 📦10.0.0 This IG
Consent.provision.code Base required Consent Provision Code 📦10.0.0 This IG
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Consent C 0..* Consent A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
Constraints: ppc-1, ppc-2, ppc-3, ppc-4, ppc-5
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:affiliation 0..* Reference(ehealth-episodeofcare | ehealth-careplan) {r} Affiliation to EpisodeOfCare and optionally CarePlan
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-consent-affiliation
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier Σ 0..* Identifier Identifier for this record (external references)

Example General: {"system":"http://acme.org/identifier/local/eCMS","value":"Local eCMS identifier"}
... status ?!Σ 1..1 code draft | proposed | active | rejected | inactive | entered-in-error
Binding: ConsentState (required): Indicates the state of the consent.
... scope ?!Σ 1..1 CodeableConcept Specific scope covered by this consent
Binding: Consent Scope (required)
... category Σ 1..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Binding: Consent Category (required)
... patient Σ 1..1 Reference(ehealth-patient) {r} Who the consent applies to
... dateTime Σ 0..1 dateTime When this Consent was created or indexed
... performer Σ 0..* Reference(Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Who is agreeing to the policy and rules
... organization Σ 0..* Reference(ehealth-organization) {r} Custodian of the consent
... Slices for source[x] Σ 0..1 Source from which this consent is taken
Slice: Unordered, Open by type:$this
.... sourceAttachment Attachment
.... sourceReference Reference(Consent | DocumentReference | Contract | QuestionnaireResponse)
.... source[x]:sourceReference Σ 0..1 Reference(ehealth-consent | ehealth-documentreference | Contract | ehealth-questionnaireresponse) Source from which this consent is taken
... policy 0..* BackboneElement Policies covered by this consent
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... authority C 0..1 uri Enforcement source for policy
.... uri C 0..1 uri Specific policy covered by this consent
Binding: Consent Policy (required)
... policyRule ΣC 0..1 CodeableConcept Regulation that this consents to
Binding: ConsentPolicyRuleCodes (extensible): Regulatory policy examples.
... verification Σ 0..* BackboneElement Consent Verified by patient or family
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... verified Σ 1..1 boolean Has been verified
.... verifiedWith 0..1 Reference(Patient | RelatedPerson) Person who verified
.... verificationDate 0..1 dateTime When consent verified
... provision Σ 0..1 BackboneElement Constraints to the base Consent.policyRule
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... type Σ 0..1 code deny | permit
Binding: ConsentProvisionType (required): How a rule statement is applied, such as adding additional consent or removing consent.
.... period Σ 0..1 Period Timeframe for this rule
.... actor 0..* BackboneElement Who|what controlled by this rule (or group, by role)
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... role 1..1 CodeableConcept How the actor is involved
Binding: SecurityRoleType (extensible): How an actor is involved in the consent considerations.
..... reference 1..1 Reference(Device | Group | CareTeam | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Resource for the actor (or group, by role)
.... action Σ 0..* CodeableConcept Actions controlled by this rule
Binding: ConsentActionCodes (example): Detailed codes for the consent action.
.... securityLabel Σ 0..* Coding Security Labels that define affected resources
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
.... purpose Σ 0..* Coding Context of activities covered by this rule
Binding: PurposeOfUse (extensible): What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels.
.... class Σ 0..* Coding Specific class covered by this consent
Binding: Consent Provision Class (required)
.... code Σ 0..* CodeableConcept Specific code covered by this consent
Binding: Consent Provision Code (required)
.... dataPeriod Σ 0..1 Period Timeframe for data controlled by this rule
.... data Σ 0..* BackboneElement Data controlled by this rule
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... meaning Σ 1..1 code instance | related | dependents | authoredby
Binding: ConsentDataMeaning (required): How a resource reference is interpreted when testing consent restrictions.
..... reference Σ 1..1 Reference(Resource) The actual data reference
.... provision 0..* See provision (Consent) Nested Exception Rules

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Consent.language Base preferred Common Languages 📍4.0.1 FHIR Std.
Consent.status Base required ConsentState 📍4.0.1 FHIR Std.
Consent.scope Base required Consent Scope 📦10.0.0 This IG
Consent.category Base required Consent Category 📦10.0.0 This IG
Consent.policy.uri Base required Consent Policy 📦10.0.0 This IG
Consent.policyRule Base extensible Consent PolicyRule Codes 📍4.0.1 FHIR Std.
Consent.provision.type Base required ConsentProvisionType 📍4.0.1 FHIR Std.
Consent.provision.actor.​role Base extensible SecurityRoleType 📍4.0.1 FHIR Std.
Consent.provision.action Base example Consent Action Codes 📍4.0.1 FHIR Std.
Consent.provision.securityLabel Base extensible SecurityLabels 📍4.0.1 FHIR Std.
Consent.provision.purpose Base extensible PurposeOfUse 📦3.1.0 THO v7.3
Consent.provision.class Base required Consent Provision Class 📦10.0.0 This IG
Consent.provision.code Base required Consent Provision Code 📦10.0.0 This IG
Consent.provision.data.​meaning Base required ConsentDataMeaning 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Consent C 0..* Consent A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
Constraints: ppc-1, ppc-2, ppc-3, ppc-4, ppc-5
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:affiliation 0..* Reference(ehealth-episodeofcare | ehealth-careplan) {r} Affiliation to EpisodeOfCare and optionally CarePlan
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-consent-affiliation
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... scope ?!Σ 1..1 CodeableConcept Specific scope covered by this consent
Binding: Consent Scope (required)
... category Σ 1..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Binding: Consent Category (required)
... patient Σ 1..1 Reference(ehealth-patient) {r} Who the consent applies to
... organization Σ 0..* Reference(ehealth-organization) {r} Custodian of the consent
... Slices for source[x] Σ 0..1 Source from which this consent is taken
Slice: Unordered, Open by type:$this
.... sourceAttachment Attachment
.... sourceReference Reference(Consent | DocumentReference | Contract | QuestionnaireResponse)
.... source[x]:sourceReference Σ 0..1 Reference(ehealth-consent | ehealth-documentreference | Contract | ehealth-questionnaireresponse) Source from which this consent is taken

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Consent.status Base required ConsentState 📍4.0.1 FHIR Std.
Consent.scope Base required Consent Scope 📦10.0.0 This IG
Consent.category Base required Consent Category 📦10.0.0 This IG

Constraints

Id Grade Path(s) Description Expression

Differential View

This structure is derived from Consent

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. 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
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:affiliation 0..* Reference(ehealth-episodeofcare | ehealth-careplan) {r} Affiliation to EpisodeOfCare and optionally CarePlan
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-consent-affiliation
... scope 1..1 CodeableConcept Specific scope covered by this consent
Binding: Consent Scope (required)
... category 1..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Binding: Consent Category (required)
... organization 0..* Reference(ehealth-organization) {r} Custodian of the consent
... Slices for source[x] 0..1 Attachment, Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Source from which this consent is taken
Slice: Unordered, Open by type:$this
.... source[x]:sourceReference 0..1 Reference(ehealth-consent | ehealth-documentreference | Contract | ehealth-questionnaireresponse) Source from which this consent is taken
... policy
.... uri 0..1 uri Specific policy covered by this consent
Binding: Consent Policy (required)
... provision
.... class 0..* Coding Specific class covered by this consent
Binding: Consent Provision Class (required)
.... code 0..* CodeableConcept Specific code covered by this consent
Binding: Consent Provision Code (required)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Consent.scope Base required Consent Scope 📦10.0.0 This IG
Consent.category Base required Consent Category 📦10.0.0 This IG
Consent.policy.uri Base required Consent Policy 📦10.0.0 This IG
Consent.provision.class Base required Consent Provision Class 📦10.0.0 This IG
Consent.provision.code Base required Consent Provision Code 📦10.0.0 This IG

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Consent C 0..* Consent A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
Constraints: ppc-1, ppc-2, ppc-3, ppc-4, ppc-5
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:affiliation 0..* Reference(ehealth-episodeofcare | ehealth-careplan) {r} Affiliation to EpisodeOfCare and optionally CarePlan
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-consent-affiliation
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier Σ 0..* Identifier Identifier for this record (external references)

Example General: {"system":"http://acme.org/identifier/local/eCMS","value":"Local eCMS identifier"}
... status ?!Σ 1..1 code draft | proposed | active | rejected | inactive | entered-in-error
Binding: ConsentState (required): Indicates the state of the consent.
... scope ?!Σ 1..1 CodeableConcept Specific scope covered by this consent
Binding: Consent Scope (required)
... category Σ 1..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Binding: Consent Category (required)
... patient Σ 1..1 Reference(ehealth-patient) {r} Who the consent applies to
... dateTime Σ 0..1 dateTime When this Consent was created or indexed
... performer Σ 0..* Reference(Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Who is agreeing to the policy and rules
... organization Σ 0..* Reference(ehealth-organization) {r} Custodian of the consent
... Slices for source[x] Σ 0..1 Source from which this consent is taken
Slice: Unordered, Open by type:$this
.... sourceAttachment Attachment
.... sourceReference Reference(Consent | DocumentReference | Contract | QuestionnaireResponse)
.... source[x]:sourceReference Σ 0..1 Reference(ehealth-consent | ehealth-documentreference | Contract | ehealth-questionnaireresponse) Source from which this consent is taken
... policy 0..* BackboneElement Policies covered by this consent
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... authority C 0..1 uri Enforcement source for policy
.... uri C 0..1 uri Specific policy covered by this consent
Binding: Consent Policy (required)
... policyRule ΣC 0..1 CodeableConcept Regulation that this consents to
Binding: ConsentPolicyRuleCodes (extensible): Regulatory policy examples.
... verification Σ 0..* BackboneElement Consent Verified by patient or family
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... verified Σ 1..1 boolean Has been verified
.... verifiedWith 0..1 Reference(Patient | RelatedPerson) Person who verified
.... verificationDate 0..1 dateTime When consent verified
... provision Σ 0..1 BackboneElement Constraints to the base Consent.policyRule
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... type Σ 0..1 code deny | permit
Binding: ConsentProvisionType (required): How a rule statement is applied, such as adding additional consent or removing consent.
.... period Σ 0..1 Period Timeframe for this rule
.... actor 0..* BackboneElement Who|what controlled by this rule (or group, by role)
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... role 1..1 CodeableConcept How the actor is involved
Binding: SecurityRoleType (extensible): How an actor is involved in the consent considerations.
..... reference 1..1 Reference(Device | Group | CareTeam | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Resource for the actor (or group, by role)
.... action Σ 0..* CodeableConcept Actions controlled by this rule
Binding: ConsentActionCodes (example): Detailed codes for the consent action.
.... securityLabel Σ 0..* Coding Security Labels that define affected resources
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
.... purpose Σ 0..* Coding Context of activities covered by this rule
Binding: PurposeOfUse (extensible): What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels.
.... class Σ 0..* Coding Specific class covered by this consent
Binding: Consent Provision Class (required)
.... code Σ 0..* CodeableConcept Specific code covered by this consent
Binding: Consent Provision Code (required)
.... dataPeriod Σ 0..1 Period Timeframe for data controlled by this rule
.... data Σ 0..* BackboneElement Data controlled by this rule
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... meaning Σ 1..1 code instance | related | dependents | authoredby
Binding: ConsentDataMeaning (required): How a resource reference is interpreted when testing consent restrictions.
..... reference Σ 1..1 Reference(Resource) The actual data reference
.... provision 0..* See provision (Consent) Nested Exception Rules

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Consent.language Base preferred Common Languages 📍4.0.1 FHIR Std.
Consent.status Base required ConsentState 📍4.0.1 FHIR Std.
Consent.scope Base required Consent Scope 📦10.0.0 This IG
Consent.category Base required Consent Category 📦10.0.0 This IG
Consent.policy.uri Base required Consent Policy 📦10.0.0 This IG
Consent.policyRule Base extensible Consent PolicyRule Codes 📍4.0.1 FHIR Std.
Consent.provision.type Base required ConsentProvisionType 📍4.0.1 FHIR Std.
Consent.provision.actor.​role Base extensible SecurityRoleType 📍4.0.1 FHIR Std.
Consent.provision.action Base example Consent Action Codes 📍4.0.1 FHIR Std.
Consent.provision.securityLabel Base extensible SecurityLabels 📍4.0.1 FHIR Std.
Consent.provision.purpose Base extensible PurposeOfUse 📦3.1.0 THO v7.3
Consent.provision.class Base required Consent Provision Class 📦10.0.0 This IG
Consent.provision.code Base required Consent Provision Code 📦10.0.0 This IG
Consent.provision.data.​meaning Base required ConsentDataMeaning 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

 

Other representations of profile: CSV, Excel, Schematron