A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.

Broadly, there are 3 key areas of consent for patients: Consent around sharing information (aka Privacy Consent Directive - Authorization to Collect, Use, or Disclose information), consent for specific treatment, or kinds of treatment, and general advance care directives.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

An Extension

R5: Consent.period (new:Period)

Element Consent.period has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.period has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.grantor (new:Reference(CareTeam,HealthcareService,Organization,Patient,Practitioner,RelatedPerson,PractitionerRole))

Element Consent.grantor has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.grantor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.manager (new:Reference(HealthcareService,Organization,Patient,Practitioner))

Element Consent.manager has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.manager has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.controller (new:Reference(HealthcareService,Organization,Patient,Practitioner))

Element Consent.controller has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.controller has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.policyText (new:Reference(DocumentReference))

Element Consent.policyText has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.policyText has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

An Extension

R5: Consent.decision (new:code)

Element Consent.decision has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.decision has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Indicates the current state of this consent.

This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.

The codes SHALL be taken from ConsentState http://hl7.org/fhir/ValueSet/consent-state-codes|4.0.1
(required to http://hl7.org/fhir/ValueSet/consent-state-codes|4.0.1)

Indicates the state of the consent.

The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive.

An Extension

R5: Consent.status

Element Consent.status is mapped to FHIR R4 element Consent.status as SourceIsBroaderThanTarget. The target context Consent.status is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.

A selector of the type of consent being presented: ADR, Privacy, Treatment, Research. This list is now extensible.

The four anticipated uses for the Consent Resource.

A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements.

A classification of the type of consents found in a consent statement.

R5: Consent.period (new:Period)

Element Consent.period has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.period has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.grantor (new:Reference(CareTeam,HealthcareService,Organization,Patient,Practitioner,RelatedPerson,PractitionerRole))

Element Consent.grantor has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.grantor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.manager (new:Reference(HealthcareService,Organization,Patient,Practitioner))

Element Consent.manager has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.manager has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.controller (new:Reference(HealthcareService,Organization,Patient,Practitioner))

Element Consent.controller has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.controller has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.policyText (new:Reference(DocumentReference))

Element Consent.policyText has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.policyText has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.decision (new:code)

Element Consent.decision has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.decision has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.status

Element Consent.status is mapped to FHIR R4 element Consent.status as SourceIsBroaderThanTarget. The target context Consent.status is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.

R5: Consent.subject

Element Consent.subject is mapped to FHIR R4 element Consent.patient as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Consent.subject with unmapped reference targets: Group, Practitioner.

R5: Consent.grantee

Element Consent.grantee is mapped to FHIR R4 element Consent.performer as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Consent.grantee with unmapped reference targets: CareTeam, HealthcareService. In a fully computable consent, both grantee and grantor will be listed as actors within the consent. The Grantee and Grantor elements are for ease of search only.

R5: Consent.sourceReference

Element Consent.sourceReference is mapped to FHIR R4 element Consent.source[x] as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Consent.sourceReference with unmapped reference targets: DocumentReference. Source element Consent.sourceReference has unmapped reference types. While the target element Consent.source[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it. The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.

R5: Consent.verification.verificationType (new:CodeableConcept)

Element Consent.verification.verificationType has a context of Consent.verification based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verificationType has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This allows the verification element to hold multiple use cases including RelatedPerson verification of the Grantee decision and periodic re-validation of the consent.

R5: Consent.verification.verifiedBy (new:Reference(Organization,Practitioner,PractitionerRole))

Element Consent.verification.verifiedBy has a context of Consent.verification based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verifiedBy has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.provision.expression (new:Expression)

Element Consent.provision.expression has a context of Consent.provision based on following the parent source element upwards and mapping to Consent. Element Consent.provision.expression has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Constraining the expression type for a specific implementation via profile is recommended

A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.

Broadly, there are 3 key areas of consent for patients: Consent around sharing information (aka Privacy Consent Directive - Authorization to Collect, Use, or Disclose information), consent for specific treatment, or kinds of treatment, and general advance care directives.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

The codes SHOULD be taken from CommonLanguages
(preferred to http://hl7.org/fhir/ValueSet/languages|4.0.1)

A human language.

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

An Extension

R5: Consent.period (new:Period)

Element Consent.period has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.period has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.grantor (new:Reference(CareTeam,HealthcareService,Organization,Patient,Practitioner,RelatedPerson,PractitionerRole))

Element Consent.grantor has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.grantor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.manager (new:Reference(HealthcareService,Organization,Patient,Practitioner))

Element Consent.manager has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.manager has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.controller (new:Reference(HealthcareService,Organization,Patient,Practitioner))

Element Consent.controller has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.controller has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Consent.policyText (new:Reference(DocumentReference))

Element Consent.policyText has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.policyText has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

An Extension

R5: Consent.decision (new:code)

Element Consent.decision has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.decision has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Unique identifier for this copy of the Consent Statement.

This identifier identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same.

Indicates the current state of this consent.

This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.

The codes SHALL be taken from ConsentState
(required to http://hl7.org/fhir/ValueSet/consent-state-codes|4.0.1)

Indicates the state of the consent.

The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive.

unique id for the element within a resource (for internal references)

An Extension

R5: Consent.status

Element Consent.status is mapped to FHIR R4 element Consent.status as SourceIsBroaderThanTarget. The target context Consent.status is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.

Primitive value for code

A selector of the type of consent being presented: ADR, Privacy, Treatment, Research. This list is now extensible.

The four anticipated uses for the Consent Resource.

A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements.

A classification of the type of consents found in a consent statement.

The patient/healthcare consumer to whom this consent applies.

Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Consent.subject

Element Consent.subject is mapped to FHIR R4 element Consent.patient as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Consent.subject with unmapped reference targets: Group, Practitioner.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|4.0.1)

Aa resource (or, for logical models, the URI of the logical model).

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

When this Consent was issued / created / indexed.

This is not the time of the original consent, but the time that this statement was made or derived.

Either the Grantor, which is the entity responsible for granting the rights listed in a Consent Directive or the Grantee, which is the entity responsible for complying with the Consent Directive, including any obligations or limitations on authorizations and enforcement of prohibitions.

Commonly, the patient the consent pertains to is the consentor, but particularly for young and old people, it may be some other person - e.g. a legal guardian.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Consent.grantee

Element Consent.grantee is mapped to FHIR R4 element Consent.performer as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Consent.grantee with unmapped reference targets: CareTeam, HealthcareService. In a fully computable consent, both grantee and grantor will be listed as actors within the consent. The Grantee and Grantor elements are for ease of search only.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|4.0.1)

Aa resource (or, for logical models, the URI of the logical model).

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The organization that manages the consent, and the framework within which it is executed.

The source on which this consent statement is based. The source might be a scanned original paper form, or a reference to a consent that links back to such a source, a reference to a document repository (e.g. XDS) that stores the original consent document.

The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Consent.sourceReference

Element Consent.sourceReference is mapped to FHIR R4 element Consent.source[x] as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Consent.sourceReference with unmapped reference targets: DocumentReference. Source element Consent.sourceReference has unmapped reference types. While the target element Consent.source[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it. The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.

The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives.

The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.

This element is for discoverability / documentation and does not modify or qualify the policy rules.

A reference to the specific base computable regulation or policy.

If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource.

Regulatory policy examples.

Might be a unique identifier of a policy set in XACML, or other rules engine.

Whether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Consent.verification.verificationType (new:CodeableConcept)

Element Consent.verification.verificationType has a context of Consent.verification based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verificationType has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This allows the verification element to hold multiple use cases including RelatedPerson verification of the Grantee decision and periodic re-validation of the consent.

R5: Consent.verification.verifiedBy (new:Reference(Organization,Practitioner,PractitionerRole))

Element Consent.verification.verifiedBy has a context of Consent.verification based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verifiedBy has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Has the instruction been verified.

Who verified the instruction (Patient, Relative or other Authorized Person).

Date verification was collected.

An exception to the base policy of this consent. An exception can be an addition or removal of access permissions.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Consent.provision.expression (new:Expression)

Element Consent.provision.expression has a context of Consent.provision based on following the parent source element upwards and mapping to Consent. Element Consent.provision.expression has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Constraining the expression type for a specific implementation via profile is recommended

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Action to take - permit or deny - when the rule conditions are met. Not permitted in root rule, required in all nested rules.

How a rule statement is applied, such as adding additional consent or removing consent.

The timeframe in this rule is valid.

Who or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers').

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

How the individual is involved in the resources content that is described in the exception.

How an actor is involved in the consent considerations.

The resource that identifies the actor. To identify actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers').

Actions controlled by this Rule.

Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.

Detailed codes for the consent action.

A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception.

If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict.

Security Labels from the Healthcare Privacy and Security Classification System.

The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule.

When the purpose of use tag is on the data, access request purpose of use shall not conflict.

What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels.

The class of information covered by this rule. The type can be a FHIR resource type, a profile on a type, or a CDA document, or some other type that indicates what sort of information the consent relates to.

Multiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.

The class (type) of information a consent rule covers.

If this code is found in an instance, then the rule applies.

Typical use of this is a Document code with class = CDA.

If this code is found in an instance, then the exception applies.

Clinical or Operational Relevant period of time that bounds the data controlled by this rule.

This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.

The resources controlled by this rule if specific resources are referenced.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

How the resource reference is interpreted when testing consent restrictions.

How a resource reference is interpreted when testing consent restrictions.

A reference to a specific resource that defines which resources are covered by this consent.

Rules which provide exceptions to the base rule or subrules.