UK Core Implementation Guide Assets in Development

Please note:

This is an Implementation Guide for UK Core FHIR Assets in Development.
There will be disruption as the content will be updated on an ad-hoc basis and with links not working.
Therefore this Implementation Guide must not be implemented.
Please follow the guidance on the "Contact Us" page if you need any assistance.

Command 'tree' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Consent'

Detailed Descriptions

Command 'dict' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Consent'

Table View

Command 'table' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Consent'

XML View

Command 'xml' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Consent'

JSON View

Command 'json' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Consent'

Usage

This Profile has the following derived profiles:

This Profile is referenced in the following Extensions:

This Profile is referenced in the following Profiles:

Feedback

Click here to:

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Examples

For Information Access - An example to illustrate a patient giving consent for information access.
Example UKCore-Consent-ForInformationAccess

Example Usage Scenarios

The following are example usage scenarios for the UK Core Consent profile:

Privacy Consent Directive: Agreement to collect, access, use or disclose (share) information.
Medical Treatment Consent Directive: Consent to undergo a specific treatment (or record of refusal to consent).
Research Consent Directive: Consent to participate in research protocol and information sharing required.
Advance Care Directives: Consent to instructions for potentially needed medical treatment (e.g. DNR).

Profile Specific Implementation Guidance:

Minimum Viable Content

A minimum viable content that all provider and consumer systems SHALL support are the following elements.

Element	Reason
`Consent.status`	Indicates the current state of this consent.
`Consent.scope`	A selector of the type of consent being presented: ADR, Privacy, Treatment, Research.
`Consent.category`	The classification of the consent statement - for indexing/retrieval
`Consent.patient`	The patient/healthcare consumer to whom this consent applies.
`Consent.dateTime`	When this consent was issued / created / indexed.
`Consent.performer`	Who is agreeing to the policy and rules
`Consent.organization`	The custodian of the consent
`Consent.source[x]`	The source from which this consent is taken

Bindings (differential)

More information about the bindings to UK Core ValueSets can be found below.

Context	Strength	Link
Consent.provision.code	Preferred	ValueSet UKCore-ConsentException

`patient`

The resource being referenced SHALL conform to the following Profile UKCore-Patient.

`performer`

The resource being referenced SHALL conform to one of the following:

`organization`

The resource being referenced SHALL conform to the following Profile UKCore-Organization.

`source[x]`

The source on which this consent statement is based, either as an inline Attachment, or as a reference. The resource being referenced SHALL conform to one of the following:

`verification`

verification.verifiedWith

The resource being referenced SHALL conform to one of the following:

`provision`

provision.actor.reference

The resource being referenced SHOULD conform to one of the following:

provision.data.reference

Where a UK Core profile exists the resource being referenced SHOULD conform to the profile.

provision.code

This element has a binding to ValueSet UKCore-ConsentException.

StructureDefinition-UKCore-Consent