DataStandardsWales-Consent
The Consent profile is to be used to express a Consent regarding Healthcare. There are four anticipated uses for the Consent Resource, all of which are written or verbal agreements by a healthcare consumer (grantor) or a personal representative, made to an authorised entity (grantee) concerning authorised or restricted actions with any limitations on purpose of use, and handling instructions to which the authorised entity SHALL comply:
- 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).
The DataStandardsWales-Consent profile is derived from the HL7 R4 Consent. It defines additional rules for use within health and care organisations in Wales.
A direct link to the Data Standards Wales asset can be accessed here - Data Standards Wales Consent
Formal Views of Profile Content
- Snapshot View
- Differential View
- Hybrid View
- Examples
| DataStandardsWalesConsent (Consent) | C | Consent | There are no (further) constraints on this element Element idConsentShort description A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time DefinitionA 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.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idConsent.idShort description Logical id of this artifact DefinitionThe 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. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idConsent.metaShort description Metadata about the resource DefinitionThe 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.
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idConsent.implicitRulesShort description A set of rules under which this content was created DefinitionA 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.
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idConsent.languageShort description Language of the resource content DefinitionThe 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). A human language.
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idConsent.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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.
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idConsent.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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.
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 is allowed to 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). 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. 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.
| ||
| identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idConsent.identifierShort description Identifier for this record (external references) DefinitionUnique 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.
General {
"system": "urn:ietf:rfc:3986",
"value": "Local eCMS identifier"
}Mappings
| ||
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idConsent.statusShort description draft | proposed | active | rejected | inactive | entered-in-error DefinitionIndicates the current state of this consent. The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive. 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. Indicates the state of the consent.
| ||
| scope | Σ ?! | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.scopeShort description Which of the four areas this resource covers (extensible) DefinitionA 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. ConsentScopeCodes (extensible) Constraints
| ||
| category | Σ | 1..* | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.categoryShort description Classification of the consent statement - for indexing/retrieval DefinitionA 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. ConsentCategoryCodes (extensible) Constraints
| ||
| patient | Σ | 0..1 | Reference(DataStandardsWalesPatient) | Element idConsent.patientShort description Who the consent applies to DefinitionThe 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. Reference(DataStandardsWalesPatient) Constraints
| ||
| dateTime | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idConsent.dateTimeShort description When this Consent was created or indexed DefinitionWhen 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.
| ||
| performer | Σ | 0..* | Reference(DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) | Element idConsent.performerShort description Who is agreeing to the policy and rules Alternate namesconsentor DefinitionEither 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. Reference(DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) Constraints
| ||
| organization | Σ | 0..* | Reference(DataStandardsWalesOrganization) | Element idConsent.organizationShort description Custodian of the consent Alternate namescustodian DefinitionThe organization that manages the consent, and the framework within which it is executed. Reference(DataStandardsWalesOrganization) Constraints
| ||
| source[x] | Σ | 0..1 | There are no (further) constraints on this element Element idConsent.source[x]Short description Source from which this consent is taken DefinitionThe 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.
| |||
| sourceAttachment | Attachment | Data type | ||||
| sourceReference | Reference(DocumentReference | Contract | DataStandardsWalesConsent | DataStandardsWalesQuestionnaireResponse) | Data type Reference(DocumentReference | Contract | DataStandardsWalesConsent | DataStandardsWalesQuestionnaireResponse) | ||||
| policy | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.policyShort description Policies covered by this consent DefinitionThe references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.policy.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.policy.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.policy.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| authority | C | 0..1 | uri | There are no (further) constraints on this element Element idConsent.policy.authorityShort description Enforcement source for policy DefinitionEntity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives. The cardinality or value of this element may be affected by these constraints: ppc-1 Constraints
| ||
| uri | C | 0..1 | uri | There are no (further) constraints on this element Element idConsent.policy.uriShort description Specific policy covered by this consent DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ppc-1 Constraints
| ||
| policyRule | Σ C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.policyRuleShort description Regulation that this consents to DefinitionA reference to the specific base computable regulation or policy. Might be a unique identifier of a policy set in XACML, or other rules engine. If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource. Regulatory policy examples. ConsentPolicyRuleCodes (extensible) ConditionsThe cardinality or value of this element may be affected by these constraints: ppc-1 Constraints
| ||
| verification | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.verificationShort description Consent Verified by patient or family DefinitionWhether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.verification.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.verification.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.verification.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| verified | Σ | 1..1 | boolean | There are no (further) constraints on this element Element idConsent.verification.verifiedShort description Has been verified DefinitionHas the instruction been verified.
| ||
| verifiedWith | 0..1 | Reference(DataStandardsWalesPatient | DataStandardsWalesRelatedPerson) | Element idConsent.verification.verifiedWithShort description Person who verified DefinitionWho verified the instruction (Patient, Relative or other Authorized Person). Reference(DataStandardsWalesPatient | DataStandardsWalesRelatedPerson) Constraints
| |||
| verificationDate | 0..1 | dateTime | There are no (further) constraints on this element Element idConsent.verification.verificationDateShort description When consent verified DefinitionDate verification was collected.
| |||
| provision | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idConsent.provisionShort description Constraints to the base Consent.policyRule DefinitionAn exception to the base policy of this consent. An exception can be an addition or removal of access permissions.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.provision.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| type | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idConsent.provision.typeShort description deny | permit DefinitionAction 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. ConsentProvisionType (required) Constraints
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idConsent.provision.periodShort description Timeframe for this rule DefinitionThe timeframe in this rule is valid.
| ||
| actor | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.provision.actorShort description Who|what controlled by this rule (or group, by role) DefinitionWho or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers'). There is no specific actor associated with the exception
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.provision.actor.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.actor.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.actor.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| role | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.provision.actor.roleShort description How the actor is involved DefinitionHow the individual is involved in the resources content that is described in the exception. How an actor is involved in the consent considerations.
| |||
| reference | 1..1 | Reference(Group | CareTeam | DataStandardsWalesDevice | DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) | Element idConsent.provision.actor.referenceShort description Resource for the actor (or group, by role) DefinitionThe 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'). Reference(Group | CareTeam | DataStandardsWalesDevice | DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) Constraints
| |||
| action | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idConsent.provision.actionShort description Actions controlled by this rule DefinitionActions 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'. all actions Detailed codes for the consent action.
| ||
| securityLabel | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idConsent.provision.securityLabelShort description Security Labels that define affected resources DefinitionA 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. All Security Labels (extensible) Constraints
| ||
| purpose | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idConsent.provision.purposeShort description Context of activities covered by this rule DefinitionThe 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.
| ||
| class | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idConsent.provision.classShort description e.g. Resource Type, Profile, CDA, etc. DefinitionThe 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. ConsentContentClass (extensible) Constraints
| ||
| code | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idConsent.provision.codeShort description e.g. LOINC or SNOMED CT code, etc. in the content DefinitionIf 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.
| ||
| dataPeriod | Σ | 0..1 | Period | There are no (further) constraints on this element Element idConsent.provision.dataPeriodShort description Timeframe for data controlled by this rule DefinitionClinical 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.
| ||
| data | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.provision.dataShort description Data controlled by this rule DefinitionThe resources controlled by this rule if specific resources are referenced. all data
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.provision.data.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.data.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.data.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| meaning | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idConsent.provision.data.meaningShort description instance | related | dependents | authoredby DefinitionHow the resource reference is interpreted when testing consent restrictions. How a resource reference is interpreted when testing consent restrictions.
| ||
| reference | Σ | 1..1 | Reference(Resource) | There are no (further) constraints on this element Element idConsent.provision.data.referenceShort description The actual data reference DefinitionA reference to a specific resource that defines which resources are covered by this consent.
| ||
| provision | 0..* | see (provision) | There are no (further) constraints on this element Element idConsent.provision.provisionShort description Nested Exception Rules DefinitionRules which provide exceptions to the base rule or subrules.
|
| DataStandardsWalesConsent (Consent) | C | Consent | There are no (further) constraints on this element Element idConsentShort description A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time DefinitionA 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.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idConsent.idShort description Logical id of this artifact DefinitionThe 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. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idConsent.metaShort description Metadata about the resource DefinitionThe 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.
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idConsent.implicitRulesShort description A set of rules under which this content was created DefinitionA 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.
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idConsent.languageShort description Language of the resource content DefinitionThe 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). A human language.
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idConsent.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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.
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idConsent.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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.
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 is allowed to 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). 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. 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.
| ||
| identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idConsent.identifierShort description Identifier for this record (external references) DefinitionUnique 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.
General {
"system": "urn:ietf:rfc:3986",
"value": "Local eCMS identifier"
}Mappings
| ||
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idConsent.statusShort description draft | proposed | active | rejected | inactive | entered-in-error DefinitionIndicates the current state of this consent. The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive. 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. Indicates the state of the consent.
| ||
| scope | Σ ?! | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.scopeShort description Which of the four areas this resource covers (extensible) DefinitionA 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. ConsentScopeCodes (extensible) Constraints
| ||
| category | Σ | 1..* | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.categoryShort description Classification of the consent statement - for indexing/retrieval DefinitionA 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. ConsentCategoryCodes (extensible) Constraints
| ||
| patient | Σ | 0..1 | Reference(DataStandardsWalesPatient) | Element idConsent.patientShort description Who the consent applies to DefinitionThe 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. Reference(DataStandardsWalesPatient) Constraints
| ||
| dateTime | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idConsent.dateTimeShort description When this Consent was created or indexed DefinitionWhen 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.
| ||
| performer | Σ | 0..* | Reference(DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) | Element idConsent.performerShort description Who is agreeing to the policy and rules Alternate namesconsentor DefinitionEither 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. Reference(DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) Constraints
| ||
| organization | Σ | 0..* | Reference(DataStandardsWalesOrganization) | Element idConsent.organizationShort description Custodian of the consent Alternate namescustodian DefinitionThe organization that manages the consent, and the framework within which it is executed. Reference(DataStandardsWalesOrganization) Constraints
| ||
| source[x] | Σ | 0..1 | There are no (further) constraints on this element Element idConsent.source[x]Short description Source from which this consent is taken DefinitionThe 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.
| |||
| sourceAttachment | Attachment | Data type | ||||
| sourceReference | Reference(DocumentReference | Contract | DataStandardsWalesConsent | DataStandardsWalesQuestionnaireResponse) | Data type Reference(DocumentReference | Contract | DataStandardsWalesConsent | DataStandardsWalesQuestionnaireResponse) | ||||
| policy | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.policyShort description Policies covered by this consent DefinitionThe references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.policy.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.policy.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.policy.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| authority | C | 0..1 | uri | There are no (further) constraints on this element Element idConsent.policy.authorityShort description Enforcement source for policy DefinitionEntity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives. The cardinality or value of this element may be affected by these constraints: ppc-1 Constraints
| ||
| uri | C | 0..1 | uri | There are no (further) constraints on this element Element idConsent.policy.uriShort description Specific policy covered by this consent DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ppc-1 Constraints
| ||
| policyRule | Σ C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.policyRuleShort description Regulation that this consents to DefinitionA reference to the specific base computable regulation or policy. Might be a unique identifier of a policy set in XACML, or other rules engine. If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource. Regulatory policy examples. ConsentPolicyRuleCodes (extensible) ConditionsThe cardinality or value of this element may be affected by these constraints: ppc-1 Constraints
| ||
| verification | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.verificationShort description Consent Verified by patient or family DefinitionWhether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.verification.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.verification.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.verification.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| verified | Σ | 1..1 | boolean | There are no (further) constraints on this element Element idConsent.verification.verifiedShort description Has been verified DefinitionHas the instruction been verified.
| ||
| verifiedWith | 0..1 | Reference(DataStandardsWalesPatient | DataStandardsWalesRelatedPerson) | Element idConsent.verification.verifiedWithShort description Person who verified DefinitionWho verified the instruction (Patient, Relative or other Authorized Person). Reference(DataStandardsWalesPatient | DataStandardsWalesRelatedPerson) Constraints
| |||
| verificationDate | 0..1 | dateTime | There are no (further) constraints on this element Element idConsent.verification.verificationDateShort description When consent verified DefinitionDate verification was collected.
| |||
| provision | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idConsent.provisionShort description Constraints to the base Consent.policyRule DefinitionAn exception to the base policy of this consent. An exception can be an addition or removal of access permissions.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.provision.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| type | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idConsent.provision.typeShort description deny | permit DefinitionAction 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. ConsentProvisionType (required) Constraints
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idConsent.provision.periodShort description Timeframe for this rule DefinitionThe timeframe in this rule is valid.
| ||
| actor | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.provision.actorShort description Who|what controlled by this rule (or group, by role) DefinitionWho or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers'). There is no specific actor associated with the exception
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.provision.actor.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.actor.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.actor.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| role | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.provision.actor.roleShort description How the actor is involved DefinitionHow the individual is involved in the resources content that is described in the exception. How an actor is involved in the consent considerations.
| |||
| reference | 1..1 | Reference(Group | CareTeam | DataStandardsWalesDevice | DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) | Element idConsent.provision.actor.referenceShort description Resource for the actor (or group, by role) DefinitionThe 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'). Reference(Group | CareTeam | DataStandardsWalesDevice | DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) Constraints
| |||
| action | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idConsent.provision.actionShort description Actions controlled by this rule DefinitionActions 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'. all actions Detailed codes for the consent action.
| ||
| securityLabel | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idConsent.provision.securityLabelShort description Security Labels that define affected resources DefinitionA 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. All Security Labels (extensible) Constraints
| ||
| purpose | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idConsent.provision.purposeShort description Context of activities covered by this rule DefinitionThe 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.
| ||
| class | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idConsent.provision.classShort description e.g. Resource Type, Profile, CDA, etc. DefinitionThe 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. ConsentContentClass (extensible) Constraints
| ||
| code | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idConsent.provision.codeShort description e.g. LOINC or SNOMED CT code, etc. in the content DefinitionIf 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.
| ||
| dataPeriod | Σ | 0..1 | Period | There are no (further) constraints on this element Element idConsent.provision.dataPeriodShort description Timeframe for data controlled by this rule DefinitionClinical 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.
| ||
| data | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.provision.dataShort description Data controlled by this rule DefinitionThe resources controlled by this rule if specific resources are referenced. all data
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.provision.data.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.data.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.data.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| meaning | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idConsent.provision.data.meaningShort description instance | related | dependents | authoredby DefinitionHow the resource reference is interpreted when testing consent restrictions. How a resource reference is interpreted when testing consent restrictions.
| ||
| reference | Σ | 1..1 | Reference(Resource) | There are no (further) constraints on this element Element idConsent.provision.data.referenceShort description The actual data reference DefinitionA reference to a specific resource that defines which resources are covered by this consent.
| ||
| provision | 0..* | see (provision) | There are no (further) constraints on this element Element idConsent.provision.provisionShort description Nested Exception Rules DefinitionRules which provide exceptions to the base rule or subrules.
|
| DataStandardsWalesConsent (Consent) | C | Consent | There are no (further) constraints on this element Element idConsentShort description A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time DefinitionA 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.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idConsent.idShort description Logical id of this artifact DefinitionThe 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. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idConsent.metaShort description Metadata about the resource DefinitionThe 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.
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idConsent.implicitRulesShort description A set of rules under which this content was created DefinitionA 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.
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idConsent.languageShort description Language of the resource content DefinitionThe 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). A human language.
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idConsent.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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.
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idConsent.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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.
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 is allowed to 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). 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. 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.
| ||
| identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idConsent.identifierShort description Identifier for this record (external references) DefinitionUnique 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.
General {
"system": "urn:ietf:rfc:3986",
"value": "Local eCMS identifier"
}Mappings
| ||
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idConsent.statusShort description draft | proposed | active | rejected | inactive | entered-in-error DefinitionIndicates the current state of this consent. The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive. 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. Indicates the state of the consent.
| ||
| scope | Σ ?! | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.scopeShort description Which of the four areas this resource covers (extensible) DefinitionA 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. ConsentScopeCodes (extensible) Constraints
| ||
| category | Σ | 1..* | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.categoryShort description Classification of the consent statement - for indexing/retrieval DefinitionA 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. ConsentCategoryCodes (extensible) Constraints
| ||
| patient | Σ | 0..1 | Reference(DataStandardsWalesPatient) | Element idConsent.patientShort description Who the consent applies to DefinitionThe 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. Reference(DataStandardsWalesPatient) Constraints
| ||
| dateTime | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idConsent.dateTimeShort description When this Consent was created or indexed DefinitionWhen 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.
| ||
| performer | Σ | 0..* | Reference(DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) | Element idConsent.performerShort description Who is agreeing to the policy and rules Alternate namesconsentor DefinitionEither 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. Reference(DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) Constraints
| ||
| organization | Σ | 0..* | Reference(DataStandardsWalesOrganization) | Element idConsent.organizationShort description Custodian of the consent Alternate namescustodian DefinitionThe organization that manages the consent, and the framework within which it is executed. Reference(DataStandardsWalesOrganization) Constraints
| ||
| source[x] | Σ | 0..1 | There are no (further) constraints on this element Element idConsent.source[x]Short description Source from which this consent is taken DefinitionThe 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.
| |||
| sourceAttachment | Attachment | Data type | ||||
| sourceReference | Reference(DocumentReference | Contract | DataStandardsWalesConsent | DataStandardsWalesQuestionnaireResponse) | Data type Reference(DocumentReference | Contract | DataStandardsWalesConsent | DataStandardsWalesQuestionnaireResponse) | ||||
| policy | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.policyShort description Policies covered by this consent DefinitionThe references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.policy.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.policy.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.policy.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| authority | C | 0..1 | uri | There are no (further) constraints on this element Element idConsent.policy.authorityShort description Enforcement source for policy DefinitionEntity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives. The cardinality or value of this element may be affected by these constraints: ppc-1 Constraints
| ||
| uri | C | 0..1 | uri | There are no (further) constraints on this element Element idConsent.policy.uriShort description Specific policy covered by this consent DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ppc-1 Constraints
| ||
| policyRule | Σ C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.policyRuleShort description Regulation that this consents to DefinitionA reference to the specific base computable regulation or policy. Might be a unique identifier of a policy set in XACML, or other rules engine. If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource. Regulatory policy examples. ConsentPolicyRuleCodes (extensible) ConditionsThe cardinality or value of this element may be affected by these constraints: ppc-1 Constraints
| ||
| verification | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.verificationShort description Consent Verified by patient or family DefinitionWhether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.verification.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.verification.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.verification.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| verified | Σ | 1..1 | boolean | There are no (further) constraints on this element Element idConsent.verification.verifiedShort description Has been verified DefinitionHas the instruction been verified.
| ||
| verifiedWith | 0..1 | Reference(DataStandardsWalesPatient | DataStandardsWalesRelatedPerson) | Element idConsent.verification.verifiedWithShort description Person who verified DefinitionWho verified the instruction (Patient, Relative or other Authorized Person). Reference(DataStandardsWalesPatient | DataStandardsWalesRelatedPerson) Constraints
| |||
| verificationDate | 0..1 | dateTime | There are no (further) constraints on this element Element idConsent.verification.verificationDateShort description When consent verified DefinitionDate verification was collected.
| |||
| provision | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idConsent.provisionShort description Constraints to the base Consent.policyRule DefinitionAn exception to the base policy of this consent. An exception can be an addition or removal of access permissions.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.provision.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| type | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idConsent.provision.typeShort description deny | permit DefinitionAction 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. ConsentProvisionType (required) Constraints
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idConsent.provision.periodShort description Timeframe for this rule DefinitionThe timeframe in this rule is valid.
| ||
| actor | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.provision.actorShort description Who|what controlled by this rule (or group, by role) DefinitionWho or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers'). There is no specific actor associated with the exception
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.provision.actor.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.actor.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.actor.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| role | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idConsent.provision.actor.roleShort description How the actor is involved DefinitionHow the individual is involved in the resources content that is described in the exception. How an actor is involved in the consent considerations.
| |||
| reference | 1..1 | Reference(Group | CareTeam | DataStandardsWalesDevice | DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) | Element idConsent.provision.actor.referenceShort description Resource for the actor (or group, by role) DefinitionThe 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'). Reference(Group | CareTeam | DataStandardsWalesDevice | DataStandardsWalesOrganization | DataStandardsWalesPatient | DataStandardsWalesPractitioner | DataStandardsWalesRelatedPerson | DataStandardsWalesPractitionerRole) Constraints
| |||
| action | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idConsent.provision.actionShort description Actions controlled by this rule DefinitionActions 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'. all actions Detailed codes for the consent action.
| ||
| securityLabel | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idConsent.provision.securityLabelShort description Security Labels that define affected resources DefinitionA 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. All Security Labels (extensible) Constraints
| ||
| purpose | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idConsent.provision.purposeShort description Context of activities covered by this rule DefinitionThe 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.
| ||
| class | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idConsent.provision.classShort description e.g. Resource Type, Profile, CDA, etc. DefinitionThe 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. ConsentContentClass (extensible) Constraints
| ||
| code | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idConsent.provision.codeShort description e.g. LOINC or SNOMED CT code, etc. in the content DefinitionIf 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.
| ||
| dataPeriod | Σ | 0..1 | Period | There are no (further) constraints on this element Element idConsent.provision.dataPeriodShort description Timeframe for data controlled by this rule DefinitionClinical 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.
| ||
| data | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idConsent.provision.dataShort description Data controlled by this rule DefinitionThe resources controlled by this rule if specific resources are referenced. all data
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idConsent.provision.data.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.data.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idConsent.provision.data.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
| ||
| meaning | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idConsent.provision.data.meaningShort description instance | related | dependents | authoredby DefinitionHow the resource reference is interpreted when testing consent restrictions. How a resource reference is interpreted when testing consent restrictions.
| ||
| reference | Σ | 1..1 | Reference(Resource) | There are no (further) constraints on this element Element idConsent.provision.data.referenceShort description The actual data reference DefinitionA reference to a specific resource that defines which resources are covered by this consent.
| ||
| provision | 0..* | see (provision) | There are no (further) constraints on this element Element idConsent.provision.provisionShort description Nested Exception Rules DefinitionRules which provide exceptions to the base rule or subrules.
|