Consent
The FHIR resource Consent is for Immunization Consent for antigens.
Consent | I | Consent | |
id | Σ | 1..1 | string |
meta | Σ | 0..1 | Meta |
id | 0..1 | string | |
extension | I | 0..* | Extension |
versionId | Σ | 0..1 | id |
lastUpdated | Σ | 0..1 | instant |
source | Σ | 0..1 | uri |
profile | Σ | 1..1 | canonical(StructureDefinition) |
security | Σ | 0..1 | CodingBinding |
tag | Σ | 0..1 | Coding |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | 0..1 | Narrative | |
contained | 1..* | RelatedPerson, PractitionerConsentGivenTo | |
extension | I | 0..* | Extension |
consentExtension | I | 0..* | Extension(Complex) |
modifierExtension | ?! I | 0..* | Extension |
identifier | Σ | 1..1 | Identifier |
id | 0..1 | string | |
extension | I | 0..* | Extension |
use | Σ ?! | 0..1 | codeBinding |
type | Σ | 1..1 | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..1 | Coding |
text | Σ | 1..1 | string |
system | Σ | 1..1 | uri |
value | Σ | 1..1 | string |
period | Σ | 0..1 | Period |
assigner | Σ | 0..1 | Reference(Organization) |
status | Σ ?! | 1..1 | codeBinding |
scope | Σ ?! | 1..1 | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 1..* | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | Σ | 1..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
category | Σ | 1..* | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | Σ | 1..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
patient | Σ | 0..1 | Reference(Patient) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 1..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..1 | Identifier |
display | Σ | 0..1 | string |
dateTime | Σ | 0..1 | dateTime |
performer | Σ | 0..1 | Reference(Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 1..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..1 | Identifier |
display | Σ | 0..1 | string |
organization | Σ | 0..1 | Reference(Organization) |
source[x] | Σ | 0..1 | |
sourceAttachment | Attachment | ||
sourceReference | Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) | ||
policy | 0..1 | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
authority | I | 0..1 | uri |
uri | I | 0..1 | uri |
policyRule | Σ I | 1..1 | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 1..* | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | Σ | 1..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
verification | Σ | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
verified | Σ | 1..1 | boolean |
verifiedWith | 0..1 | Reference(Patient | RelatedPerson) | |
verificationDate | 0..1 | dateTime | |
provision | Σ | 1..1 | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
type | Σ | 0..1 | codeBinding |
period | Σ | 1..1 | Period |
id | 0..1 | string | |
extension | I | 0..* | Extension |
start | Σ I | 1..1 | dateTime |
end | Σ I | 0..1 | dateTime |
actor | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
role | 1..1 | CodeableConceptBinding | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 1..* | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | Σ | 1..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
reference | 1..1 | Reference(Device | Group | CareTeam | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 1..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..1 | Identifier |
display | Σ | 0..1 | string |
action | Σ | 1..1 | CodeableConcept |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 1..* | Coding |
sliceConsentInstruction | Σ | 1..1 | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | Σ | 1..1 | code |
display | Σ | 1..1 | string |
userSelected | Σ | 0..1 | boolean |
sliceConsentRefusalReaason | Σ | 1..1 | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | Σ | 1..1 | code |
display | Σ | 1..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
securityLabel | Σ | 0..1 | CodingBinding |
purpose | Σ | 0..1 | CodingBinding |
class | Σ | 0..1 | CodingBinding |
code | Σ | 1..* | CodeableConcept |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 1..* | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | Σ | 1..1 | code |
display | Σ | 1..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
dataPeriod | Σ | 0..1 | Period |
data | Σ | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
meaning | Σ | 1..1 | codeBinding |
reference | Σ | 1..1 | Reference(Resource) |
provision | 0..1 | see (provision) |
Consent | |
Definition | A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. |
Cardinality | 0...* |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | See Mappings |
Mappings |
|
Consent.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Consent.meta.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.meta.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.meta.versionId | |
Definition | The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. |
Cardinality | 0...1 |
Type | id |
Summary | True |
Comments | Apply "2025.01.1". This indicates the FHIR Specs as of year 2025 Jan. |
Invariants |
|
Consent.meta.lastUpdated | |
Definition | When the resource last changed - e.g. when the version changed. |
Cardinality | 0...1 |
Type | instant |
Summary | True |
Comments | Updated: Relax the previously crossed-out elements. |
Invariants |
|
Consent.meta.source | |
Definition | A uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](provenance.html#) information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. |
Cardinality | 0...1 |
Type | uri |
Summary | True |
Comments | In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL. |
Invariants |
|
Consent.meta.profile | |
Definition | A list of profiles (references to [StructureDefinition](structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](structuredefinition-definitions.html#StructureDefinition.url). |
Cardinality | 1...1 |
Type | canonical(StructureDefinition) |
Summary | True |
Comments | Apply "http://ehealth.bc.ca/fhir/StructureDefinition/bc-bcyimmunizationdistribution/Consent" |
Invariants |
|
Consent.meta.security | |
Definition | Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. |
Cardinality | 0...1 |
Type | Coding |
Binding | Security Labels from the Healthcare Privacy and Security Classification System. |
Summary | True |
Comments | The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. |
Invariants |
|
Consent.meta.tag | |
Definition | Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. |
Cardinality | 0...1 |
Type | Coding |
Binding | Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". |
Summary | True |
Comments | The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. |
Invariants |
|
Consent.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. |
Invariants |
|
Consent.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | 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). |
Invariants |
|
Consent.text | |
Definition | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Cardinality | 1...* |
Type | RelatedPerson, PractitionerConsentGivenTo |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Consent.extension | |
Definition | May 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.extension:consentExtension | |
Definition | Optional Extension Element - found in all resources. |
Cardinality | 0...* |
Type | Extension(Complex) |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.modifierExtension | |
Definition | May 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.identifier | |
Definition | Unique identifier for this copy of the Consent Statement. |
Cardinality | 1...1 |
Type | Identifier |
Summary | True |
Comments | 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. |
Invariants |
|
Examples | General { "system": "urn:ietf:rfc:3986", "value": "Local eCMS identifier" } |
Mappings |
|
Consent.identifier.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.identifier.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.identifier.use | |
Definition | The purpose of this identifier. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Invariants |
|
Mappings |
|
Consent.identifier.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Invariants |
|
Mappings |
|
Consent.identifier.type.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.identifier.type.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.identifier.type.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...1 |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
Consent.identifier.type.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | See Mappings |
Invariants |
|
Mappings |
|
Consent.identifier.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | See Mappings |
Invariants |
|
Examples | General http://www.acme.com/identifiers/patient |
Mappings |
|
Consent.identifier.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | See Mappings |
Invariants |
|
Examples | General 123456 |
Mappings |
|
Consent.identifier.period | |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
Consent.identifier.assigner | |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Invariants |
|
Mappings |
|
Consent.status | |
Definition | Indicates the current state of this consent. |
Cardinality | 1...1 |
Type | code |
Binding | Indicates the state of the consent. |
Modifier | True |
Summary | True |
Requirements | The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive. |
Comments | Confirmed (PIR) maps to Active (FHIR). See Mappings. |
Invariants |
|
Mappings |
|
Consent.scope | |
Definition | A selector of the type of consent being presented: ADR, Privacy, Treatment, Research. This list is now extensible. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | The four anticipated uses for the Consent Resource. |
Modifier | True |
Summary | True |
Invariants |
|
Consent.scope.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.scope.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.scope.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
Consent.scope.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.scope.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.scope.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | See Code |
Invariants |
|
Mappings |
|
Consent.scope.coding.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Consent.scope.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Apply "treatment" |
Invariants |
|
Mappings |
|
Consent.scope.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Invariants |
|
Mappings |
|
Consent.scope.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Consent.scope.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Consent.category | |
Definition | A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements. |
Cardinality | 1...* |
Type | CodeableConcept |
Binding | A classification of the type of consents found in a consent statement. |
Summary | True |
Invariants |
|
Mappings |
|
Consent.category.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.category.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.category.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
Consent.category.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.category.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.category.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | See Code |
Invariants |
|
Mappings |
|
Consent.category.coding.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Consent.category.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Apply "59284-0" |
Invariants |
|
Mappings |
|
Consent.category.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Invariants |
|
Mappings |
|
Consent.category.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Consent.category.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Consent.patient | |
Definition | The patient/healthcare consumer to whom this consent applies. |
Cardinality | 0...1 |
Type | Reference(Patient) |
Summary | True |
Comments | Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person. |
Invariants |
|
Mappings |
|
Consent.patient.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.patient.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.patient.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | See Mappings |
Invariants |
|
Mappings |
|
Consent.patient.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Consent.patient.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Consent.patient.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Consent.dateTime | |
Definition | When this Consent was issued / created / indexed. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | This is not the time of the original consent, but the time that this statement was made or derived. |
Invariants |
|
Mappings |
|
Consent.performer | |
Definition | Either the Grantor, which is the entity responsible for granting the rights listed in a Consent Directive or the Grantee, which is the entity responsible for complying with the Consent Directive, including any obligations or limitations on authorizations and enforcement of prohibitions. |
Cardinality | 0...1 |
Type | Reference(Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) |
Summary | True |
Alias | consentor |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.performer.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.performer.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.performer.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | See Mappings |
Invariants |
|
Mappings |
|
Consent.performer.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Consent.performer.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Consent.performer.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Consent.organization | |
Definition | The organization that manages the consent, and the framework within which it is executed. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Summary | True |
Alias | custodian |
Invariants |
|
Mappings |
|
Consent.source[x] | |
Definition | The source on which this consent statement is based. The source might be a scanned original paper form, or a reference to a consent that links back to such a source, a reference to a document repository (e.g. XDS) that stores the original consent document. |
Cardinality | 0...1 |
Type | Attachment |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.policy | |
Definition | The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law. |
Cardinality | 0...1 |
Type | BackboneElement |
Invariants |
|
Consent.policy.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.policy.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.policy.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.policy.authority | |
Definition | Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives. |
Cardinality | 0...1 |
Type | uri |
Invariants |
|
Consent.policy.uri | |
Definition | The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law. |
Cardinality | 0...1 |
Type | uri |
Comments | This element is for discoverability / documentation and does not modify or qualify the policy rules. |
Invariants |
|
Consent.policyRule | |
Definition | A reference to the specific base computable regulation or policy. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | Regulatory policy examples. |
Summary | True |
Requirements | Might be a unique identifier of a policy set in XACML, or other rules engine. |
Comments | If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource. |
Invariants |
|
Consent.policyRule.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.policyRule.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.policyRule.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
Consent.policyRule.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.policyRule.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.policyRule.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | See Code |
Invariants |
|
Mappings |
|
Consent.policyRule.coding.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Consent.policyRule.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Apply "cric" (Common Rule Informed Consent). |
Invariants |
|
Mappings |
|
Consent.policyRule.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Invariants |
|
Mappings |
|
Consent.policyRule.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Consent.policyRule.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Consent.verification | |
Definition | Whether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person. |
Cardinality | 0...1 |
Type | BackboneElement |
Summary | True |
Invariants |
|
Consent.verification.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.verification.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.verification.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.verification.verified | |
Definition | Has the instruction been verified. |
Cardinality | 1...1 |
Type | boolean |
Summary | True |
Invariants |
|
Consent.verification.verifiedWith | |
Definition | Who verified the instruction (Patient, Relative or other Authorized Person). |
Cardinality | 0...1 |
Type | Reference(Patient | RelatedPerson) |
Invariants |
|
Consent.verification.verificationDate | |
Definition | Date verification was collected. |
Cardinality | 0...1 |
Type | dateTime |
Invariants |
|
Consent.provision | |
Definition | An exception to the base policy of this consent. An exception can be an addition or removal of access permissions. |
Cardinality | 1...1 |
Type | BackboneElement |
Summary | True |
Invariants |
|
Consent.provision.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.provision.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.provision.type | |
Definition | Action to take - permit or deny - when the rule conditions are met. Not permitted in root rule, required in all nested rules. |
Cardinality | 0...1 |
Type | code |
Binding | How a rule statement is applied, such as adding additional consent or removing consent. |
Summary | True |
Invariants |
|
Consent.provision.period | |
Definition | The timeframe in this rule is valid. |
Cardinality | 1...1 |
Type | Period |
Summary | True |
Invariants |
|
Consent.provision.period.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.period.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.provision.period.start | |
Definition | The start of the period. The boundary is inclusive. |
Cardinality | 1...1 |
Type | dateTime |
Summary | True |
Comments | See Mappings. |
Invariants |
|
Mappings |
|
Consent.provision.period.end | |
Definition | The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | See Mappings |
Invariants |
|
Mappings |
|
Consent.provision.actor | |
Definition | Who or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers'). |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Consent.provision.actor.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.actor.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.provision.actor.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.provision.actor.role | |
Definition | How the individual is involved in the resources content that is described in the exception. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | How an actor is involved in the consent considerations. |
Invariants |
|
Consent.provision.actor.role.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.actor.role.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.provision.actor.role.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
Consent.provision.actor.role.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.actor.role.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.provision.actor.role.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Mappings |
|
Consent.provision.actor.role.coding.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Consent.provision.actor.role.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Apply "CONSENTER" |
Invariants |
|
Mappings |
|
Consent.provision.actor.role.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Invariants |
|
Mappings |
|
Consent.provision.actor.role.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Consent.provision.actor.role.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Consent.provision.actor.reference | |
Definition | The resource that identifies the actor. To identify actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers'). |
Cardinality | 1...1 |
Type | Reference(Device | Group | CareTeam | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) |
Invariants |
|
Consent.provision.actor.reference.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.actor.reference.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.provision.actor.reference.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | See Mappings |
Invariants |
|
Mappings |
|
Consent.provision.actor.reference.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Consent.provision.actor.reference.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Consent.provision.actor.reference.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Consent.provision.action | |
Definition | Consent or Refusal |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | Detailed codes for the consent action. |
Summary | True |
Comments | 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'. |
Invariants |
|
Consent.provision.action.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.action.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.provision.action.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Slicing | Unordered, Open, by code(Value) |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentInstruction | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...1 |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentInstruction.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.action.coding:sliceConsentInstruction.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentInstruction.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | See Code |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentInstruction.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentInstruction.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | G | R. Refer to IMMS codeset spreadsheet: Consent - Instruction. See Mappings. |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentInstruction.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments | Grant | Refuse |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentInstruction.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentRefusalReaason | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...1 |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentRefusalReaason.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.action.coding:sliceConsentRefusalReaason.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentRefusalReaason.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | See Code |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentRefusalReaason.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentRefusalReaason.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Refer to IMMS codeset spreadsheet: Consent - Reason. See Mappings |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentRefusalReaason.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments | Refer to IMMS codeset spreadsheet: Consent - Reason |
Invariants |
|
Mappings |
|
Consent.provision.action.coding:sliceConsentRefusalReaason.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Consent.provision.action.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Mandatory if Reason for Refusal = "O"ther. See Mappings. |
Invariants |
|
Mappings |
|
Consent.provision.securityLabel | |
Definition | A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception. |
Cardinality | 0...1 |
Type | Coding |
Binding | Security Labels from the Healthcare Privacy and Security Classification System. |
Summary | True |
Comments | 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. |
Invariants |
|
Consent.provision.purpose | |
Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. |
Cardinality | 0...1 |
Type | Coding |
Binding | What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. |
Summary | True |
Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. |
Invariants |
|
Consent.provision.class | |
Definition | The class of information covered by this rule. The type can be a FHIR resource type, a profile on a type, or a CDA document, or some other type that indicates what sort of information the consent relates to. |
Cardinality | 0...1 |
Type | Coding |
Binding | The class (type) of information a consent rule covers. |
Summary | True |
Comments | 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. |
Invariants |
|
Consent.provision.code | |
Definition | If this code is found in an instance, then the rule applies. |
Cardinality | 1...* |
Type | CodeableConcept |
Binding | If this code is found in an instance, then the exception applies. |
Summary | True |
Comments | Typical use of this is a Document code with class = CDA. |
Invariants |
|
Consent.provision.code.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.code.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.provision.code.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
Consent.provision.code.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.code.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Consent.provision.code.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | See Mappings |
Invariants |
|
Mappings |
|
Consent.provision.code.coding.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Consent.provision.code.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Enter Vaccine code for both consent and Consent Refussal. See Mappings. |
Invariants |
|
Mappings |
|
Consent.provision.code.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments | Enter Vaccine Name for Consent or Consent Refussal |
Invariants |
|
Mappings |
|
Consent.provision.code.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Consent.provision.code.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Consent.provision.dataPeriod | |
Definition | Clinical or Operational Relevant period of time that bounds the data controlled by this rule. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Comments | 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. |
Invariants |
|
Consent.provision.data | |
Definition | The resources controlled by this rule if specific resources are referenced. |
Cardinality | 0...1 |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
Consent.provision.data.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Consent.provision.data.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.provision.data.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Consent.provision.data.meaning | |
Definition | How the resource reference is interpreted when testing consent restrictions. |
Cardinality | 1...1 |
Type | code |
Binding | How a resource reference is interpreted when testing consent restrictions. |
Summary | True |
Invariants |
|
Consent.provision.data.reference | |
Definition | A reference to a specific resource that defines which resources are covered by this consent. |
Cardinality | 1...1 |
Type | Reference(Resource) |
Summary | True |
Invariants |
|
Consent.provision.provision | |
Definition | Rules which provide exceptions to the base rule or subrules. |
Cardinality | 0...1 |
Type | see (provision) |
Invariants |
|
<StructureDefinition xmlns="http://hl7.org/fhir"> <url value="http://ehealth.bc.ca/fhir/StructureDefinition/bc-bcyimmunizationdistribution/Consent" /> <name value="Consent" /> <status value="draft" /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Consent" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Consent" /> <derivation value="constraint" /> <differential> <element id="Consent.id"> <path value="Consent.id" /> <comment value="See Mappings" /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value="CONSENT.CONSENT_DIRECTIVE.CONSENT_DIRECTIVE_ID" /> </mapping> </element> <element id="Consent.meta"> <path value="Consent.meta" /> </element> <element id="Consent.meta.versionId"> <path value="Consent.meta.versionId" /> <comment value="Apply "2025.01.1". This indicates the FHIR Specs as of year 2025 Jan." /> </element> <element id="Consent.meta.lastUpdated"> <path value="Consent.meta.lastUpdated" /> <comment value="Updated: Relax the previously crossed-out elements." /> </element> <element id="Consent.meta.profile"> <path value="Consent.meta.profile" /> <comment value="Apply "http://ehealth.bc.ca/fhir/StructureDefinition/bc-bcyimmunizationdistribution/Consent"" /> <min value="1" /> <max value="1" /> </element> <element id="Consent.meta.security"> <path value="Consent.meta.security" /> <max value="1" /> </element> <element id="Consent.meta.tag"> <path value="Consent.meta.tag" /> <max value="1" /> </element> <element id="Consent.contained"> <path value="Consent.contained" /> <min value="1" /> <type> <code value="Resource" /> <profile value="RelatedPerson" /> <profile value="PractitionerConsentGivenTo" /> </type> </element> <element id="Consent.extension:consentExtension"> <path value="Consent.extension" /> <sliceName value="consentExtension" /> <type> <code value="Extension" /> <profile value="http://ehealth.bc.ca/fhir/StructureDefinition/bc-bcyimmunizationdistribution/consent-type-form-doses-comments" /> </type> </element> <element id="Consent.identifier"> <path value="Consent.identifier" /> <min value="1" /> <max value="1" /> </element> <element id="Consent.identifier.type"> <path value="Consent.identifier.type" /> <min value="1" /> </element> <element id="Consent.identifier.type.coding"> <path value="Consent.identifier.type.coding" /> <max value="1" /> </element> <element id="Consent.identifier.type.text"> <path value="Consent.identifier.type.text" /> <comment value="See Mappings" /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value=""PANORAMACONSENTID"" /> </mapping> </element> <element id="Consent.identifier.system"> <path value="Consent.identifier.system" /> <comment value="See Mappings" /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value="https://health.gov.bc.ca/fhir/NamingSystem/ca-bc-panorama-consent-id" /> </mapping> </element> <element id="Consent.identifier.value"> <path value="Consent.identifier.value" /> <comment value="See Mappings" /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value="CONSENT.CONSENT_DIRECTIVE.CONSENT_DIRECTIVE_ID" /> </mapping> </element> <element id="Consent.status"> <path value="Consent.status" /> <code> <system value="http://hl7.org/fhir/ValueSet/consent-state-codes" /> <code value="active" /> </code> <comment value="Confirmed (PIR) maps to Active (FHIR). See Mappings." /> <mapping> <identity value="source-PIR" /> <map value="CONSENT.CONSENT_DIRECTIVE.DIRECTIVE_STATUS_CODE_CNCPT_ID" /> </mapping> </element> <element id="Consent.scope.coding"> <path value="Consent.scope.coding" /> <min value="1" /> </element> <element id="Consent.scope.coding.system"> <path value="Consent.scope.coding.system" /> <code> <system value="http://terminology.hl7.org/CodeSystem/consentscope" /> </code> <comment value="See Code" /> <min value="1" /> </element> <element id="Consent.scope.coding.code"> <path value="Consent.scope.coding.code" /> <comment value="Apply "treatment"" /> <min value="1" /> </element> <element id="Consent.category.coding.system"> <path value="Consent.category.coding.system" /> <code> <system value="http://loinc.org" /> </code> <comment value="See Code" /> <min value="1" /> </element> <element id="Consent.category.coding.code"> <path value="Consent.category.coding.code" /> <comment value="Apply "59284-0"" /> <min value="1" /> </element> <element id="Consent.patient.reference"> <path value="Consent.patient.reference" /> <comment value="See Mappings" /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value="fullURL + "Patient/" + (Patient ID)" /> <comment value="e.g. http://ehealth.bc.ca/panorama/fhir/Patient/59900999"" /> </mapping> </element> <element id="Consent.performer"> <path value="Consent.performer" /> <max value="1" /> </element> <element id="Consent.performer.reference"> <path value="Consent.performer.reference" /> <comment value="See Mappings" /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value=""#RelatedPerson"+(CONSENT.CONSENT_DIRECTIVE.CONSENT_DIRECTIVE_ID)"" /> </mapping> </element> <element id="Consent.organization"> <path value="Consent.organization" /> <max value="1" /> </element> <element id="Consent.policy"> <path value="Consent.policy" /> <max value="1" /> </element> <element id="Consent.policyRule"> <path value="Consent.policyRule" /> <min value="1" /> </element> <element id="Consent.policyRule.coding"> <path value="Consent.policyRule.coding" /> <min value="1" /> </element> <element id="Consent.policyRule.coding.system"> <path value="Consent.policyRule.coding.system" /> <code> <system value="http://terminology.hl7.org/CodeSystem/consentpolicycodes" /> </code> <comment value="See Code" /> <min value="1" /> </element> <element id="Consent.policyRule.coding.code"> <path value="Consent.policyRule.coding.code" /> <comment value="Apply "cric" (Common Rule Informed Consent)." /> <min value="1" /> </element> <element id="Consent.verification"> <path value="Consent.verification" /> <max value="1" /> </element> <element id="Consent.provision"> <path value="Consent.provision" /> <min value="1" /> </element> <element id="Consent.provision.period"> <path value="Consent.provision.period" /> <min value="1" /> </element> <element id="Consent.provision.period.start"> <path value="Consent.provision.period.start" /> <comment value="See Mappings." /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value="CONSENT.CONSENT_DIRECTIVE.EFFECT_FROM_DATE" /> </mapping> </element> <element id="Consent.provision.period.end"> <path value="Consent.provision.period.end" /> <comment value="See Mappings" /> <mapping> <identity value="source-PIR" /> <map value="CONSENT.CONSENT_DIRECTIVE.EFFECT_TO_DATE" /> </mapping> </element> <element id="Consent.provision.actor.role.coding"> <path value="Consent.provision.actor.role.coding" /> <min value="1" /> </element> <element id="Consent.provision.actor.role.coding.system"> <path value="Consent.provision.actor.role.coding.system" /> <code> <system value="http://terminology.hl7.org/CodeSystem/v3-RoleCode" /> </code> <min value="1" /> </element> <element id="Consent.provision.actor.role.coding.code"> <path value="Consent.provision.actor.role.coding.code" /> <comment value="Apply "CONSENTER"" /> <min value="1" /> </element> <element id="Consent.provision.actor.reference.reference"> <path value="Consent.provision.actor.reference.reference" /> <comment value="See Mappings" /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value=""#PractitionerConsentGivenTo"+(CONSENT.CONSENT_DIRECTIVE.CONSENT_DIRECTIVE_ID)"" /> </mapping> </element> <element id="Consent.provision.action"> <path value="Consent.provision.action" /> <short value="Consent or Refusal" /> <definition value="Consent or Refusal" /> <min value="1" /> <max value="1" /> </element> <element id="Consent.provision.action.coding"> <path value="Consent.provision.action.coding" /> <slicing> <discriminator> <type value="value" /> <path value="code" /> </discriminator> <rules value="open" /> </slicing> <min value="1" /> </element> <element id="Consent.provision.action.coding:sliceConsentInstruction"> <path value="Consent.provision.action.coding" /> <sliceName value="sliceConsentInstruction" /> <min value="1" /> <max value="1" /> </element> <element id="Consent.provision.action.coding:sliceConsentInstruction.system"> <path value="Consent.provision.action.coding.system" /> <code> <system value="http://hl7.org/fhir/sid/icd9" /> </code> <comment value="See Code" /> <min value="1" /> </element> <element id="Consent.provision.action.coding:sliceConsentInstruction.code"> <path value="Consent.provision.action.coding.code" /> <comment value="G | R.\nRefer to IMMS codeset spreadsheet: Consent - Instruction. See Mappings." /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value="CONSENT.CONSENT_DIRECTIVE.CONSENT_VALUE_CODED_CNCPT_ID" /> </mapping> </element> <element id="Consent.provision.action.coding:sliceConsentInstruction.display"> <path value="Consent.provision.action.coding.display" /> <comment value="Grant | Refuse" /> <min value="1" /> </element> <element id="Consent.provision.action.coding:sliceConsentRefusalReaason"> <path value="Consent.provision.action.coding" /> <sliceName value="sliceConsentRefusalReaason" /> <min value="1" /> <max value="1" /> </element> <element id="Consent.provision.action.coding:sliceConsentRefusalReaason.system"> <path value="Consent.provision.action.coding.system" /> <code> <system value="https://fhir.infoway-inforoute.ca/NamingSystem/ca-bc-panorama-consent-refusal-reason" /> </code> <comment value="See Code" /> <min value="1" /> </element> <element id="Consent.provision.action.coding:sliceConsentRefusalReaason.code"> <path value="Consent.provision.action.coding.code" /> <comment value="Refer to IMMS codeset spreadsheet: Consent - Reason. See Mappings" /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value="CONSENT.CONSENT_DIRECTIVE.REFUSAL_REASON_CODE_CNCPT_ID" /> </mapping> </element> <element id="Consent.provision.action.coding:sliceConsentRefusalReaason.display"> <path value="Consent.provision.action.coding.display" /> <comment value="Refer to IMMS codeset spreadsheet: Consent - Reason" /> <min value="1" /> </element> <element id="Consent.provision.action.text"> <path value="Consent.provision.action.text" /> <comment value="Mandatory if Reason for Refusal = "O"ther. See Mappings." /> <mapping> <identity value="source-PIR" /> <map value="CONSENT.CONSENT_DIRECTIVE.REFUSAL_REASON_OTHER" /> </mapping> </element> <element id="Consent.provision.securityLabel"> <path value="Consent.provision.securityLabel" /> <max value="1" /> </element> <element id="Consent.provision.purpose"> <path value="Consent.provision.purpose" /> <max value="1" /> </element> <element id="Consent.provision.class"> <path value="Consent.provision.class" /> <max value="1" /> </element> <element id="Consent.provision.code"> <path value="Consent.provision.code" /> <min value="1" /> </element> <element id="Consent.provision.code.coding"> <path value="Consent.provision.code.coding" /> <min value="1" /> </element> <element id="Consent.provision.code.coding.system"> <path value="Consent.provision.code.coding.system" /> <comment value="See Mappings" /> <min value="1" /> <mapping> <identity value="code-NVC" /> <map value="https://nvc-cnv.canada.ca" /> </mapping> <mapping> <identity value="code-SNOMED" /> <map value="http://snomed.info/sct" /> </mapping> <mapping> <identity value="code-PIR" /> <map value="https://fhir.infoway-inforoute.ca/NamingSystem/ca-bc-panorama-code" /> </mapping> </element> <element id="Consent.provision.code.coding.code"> <path value="Consent.provision.code.coding.code" /> <comment value="Enter Vaccine code for both consent and Consent Refussal. See Mappings." /> <min value="1" /> <mapping> <identity value="source-PIR" /> <map value="CONSENT.CONSENT_DIRECTIVE.DIRECTIVE_ANTIGEN_ID" /> </mapping> </element> <element id="Consent.provision.code.coding.display"> <path value="Consent.provision.code.coding.display" /> <comment value="Enter Vaccine Name for Consent or Consent Refussal" /> <min value="1" /> </element> <element id="Consent.provision.data"> <path value="Consent.provision.data" /> <max value="1" /> </element> <element id="Consent.provision.provision"> <path value="Consent.provision.provision" /> <max value="1" /> </element> </differential> </StructureDefinition>
{ "resourceType": "StructureDefinition", "url": "http://ehealth.bc.ca/fhir/StructureDefinition/bc-bcyimmunizationdistribution/Consent", "name": "Consent", "status": "draft", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Consent", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Consent", "derivation": "constraint", "differential": { "element": [ { "id": "Consent.id", "path": "Consent.id", "comment": "See Mappings", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "CONSENT.CONSENT_DIRECTIVE.CONSENT_DIRECTIVE_ID" } ] }, { "id": "Consent.meta", "path": "Consent.meta" }, { "id": "Consent.meta.versionId", "path": "Consent.meta.versionId", "comment": "Apply \"2025.01.1\". This indicates the FHIR Specs as of year 2025 Jan." }, { "id": "Consent.meta.lastUpdated", "path": "Consent.meta.lastUpdated", "comment": "Updated: Relax the previously crossed-out elements." }, { "id": "Consent.meta.profile", "path": "Consent.meta.profile", "comment": "Apply \"http://ehealth.bc.ca/fhir/StructureDefinition/bc-bcyimmunizationdistribution/Consent\"", "min": 1, "max": "1" }, { "id": "Consent.meta.security", "path": "Consent.meta.security", "max": "1" }, { "id": "Consent.meta.tag", "path": "Consent.meta.tag", "max": "1" }, { "id": "Consent.contained", "path": "Consent.contained", "min": 1, "type": [ { "code": "Resource", "profile": [ "RelatedPerson", "PractitionerConsentGivenTo" ] } ] }, { "id": "Consent.extension:consentExtension", "path": "Consent.extension", "sliceName": "consentExtension", "type": [ { "code": "Extension", "profile": [ "http://ehealth.bc.ca/fhir/StructureDefinition/bc-bcyimmunizationdistribution/consent-type-form-doses-comments" ] } ] }, { "id": "Consent.identifier", "path": "Consent.identifier", "min": 1, "max": "1" }, { "id": "Consent.identifier.type", "path": "Consent.identifier.type", "min": 1 }, { "id": "Consent.identifier.type.coding", "path": "Consent.identifier.type.coding", "max": "1" }, { "id": "Consent.identifier.type.text", "path": "Consent.identifier.type.text", "comment": "See Mappings", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "\"PANORAMACONSENTID\"" } ] }, { "id": "Consent.identifier.system", "path": "Consent.identifier.system", "comment": "See Mappings", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "https://health.gov.bc.ca/fhir/NamingSystem/ca-bc-panorama-consent-id" } ] }, { "id": "Consent.identifier.value", "path": "Consent.identifier.value", "comment": "See Mappings", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "CONSENT.CONSENT_DIRECTIVE.CONSENT_DIRECTIVE_ID" } ] }, { "id": "Consent.status", "path": "Consent.status", "code": [ { "system": "http://hl7.org/fhir/ValueSet/consent-state-codes", "code": "active" } ], "comment": "Confirmed (PIR) maps to Active (FHIR). See Mappings.", "mapping": [ { "identity": "source-PIR", "map": "CONSENT.CONSENT_DIRECTIVE.DIRECTIVE_STATUS_CODE_CNCPT_ID" } ] }, { "id": "Consent.scope.coding", "path": "Consent.scope.coding", "min": 1 }, { "id": "Consent.scope.coding.system", "path": "Consent.scope.coding.system", "code": [ { "system": "http://terminology.hl7.org/CodeSystem/consentscope" } ], "comment": "See Code", "min": 1 }, { "id": "Consent.scope.coding.code", "path": "Consent.scope.coding.code", "comment": "Apply \"treatment\"", "min": 1 }, { "id": "Consent.category.coding.system", "path": "Consent.category.coding.system", "code": [ { "system": "http://loinc.org" } ], "comment": "See Code", "min": 1 }, { "id": "Consent.category.coding.code", "path": "Consent.category.coding.code", "comment": "Apply \"59284-0\"", "min": 1 }, { "id": "Consent.patient.reference", "path": "Consent.patient.reference", "comment": "See Mappings", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "fullURL + \"Patient/\" + (Patient ID)", "comment": "e.g. http://ehealth.bc.ca/panorama/fhir/Patient/59900999\"" } ] }, { "id": "Consent.performer", "path": "Consent.performer", "max": "1" }, { "id": "Consent.performer.reference", "path": "Consent.performer.reference", "comment": "See Mappings", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "\"#RelatedPerson\"+(CONSENT.CONSENT_DIRECTIVE.CONSENT_DIRECTIVE_ID)\"" } ] }, { "id": "Consent.organization", "path": "Consent.organization", "max": "1" }, { "id": "Consent.policy", "path": "Consent.policy", "max": "1" }, { "id": "Consent.policyRule", "path": "Consent.policyRule", "min": 1 }, { "id": "Consent.policyRule.coding", "path": "Consent.policyRule.coding", "min": 1 }, { "id": "Consent.policyRule.coding.system", "path": "Consent.policyRule.coding.system", "code": [ { "system": "http://terminology.hl7.org/CodeSystem/consentpolicycodes" } ], "comment": "See Code", "min": 1 }, { "id": "Consent.policyRule.coding.code", "path": "Consent.policyRule.coding.code", "comment": "Apply \"cric\" (Common Rule Informed Consent).", "min": 1 }, { "id": "Consent.verification", "path": "Consent.verification", "max": "1" }, { "id": "Consent.provision", "path": "Consent.provision", "min": 1 }, { "id": "Consent.provision.period", "path": "Consent.provision.period", "min": 1 }, { "id": "Consent.provision.period.start", "path": "Consent.provision.period.start", "comment": "See Mappings.", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "CONSENT.CONSENT_DIRECTIVE.EFFECT_FROM_DATE" } ] }, { "id": "Consent.provision.period.end", "path": "Consent.provision.period.end", "comment": "See Mappings", "mapping": [ { "identity": "source-PIR", "map": "CONSENT.CONSENT_DIRECTIVE.EFFECT_TO_DATE" } ] }, { "id": "Consent.provision.actor.role.coding", "path": "Consent.provision.actor.role.coding", "min": 1 }, { "id": "Consent.provision.actor.role.coding.system", "path": "Consent.provision.actor.role.coding.system", "code": [ { "system": "http://terminology.hl7.org/CodeSystem/v3-RoleCode" } ], "min": 1 }, { "id": "Consent.provision.actor.role.coding.code", "path": "Consent.provision.actor.role.coding.code", "comment": "Apply \"CONSENTER\"", "min": 1 }, { "id": "Consent.provision.actor.reference.reference", "path": "Consent.provision.actor.reference.reference", "comment": "See Mappings", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "\"#PractitionerConsentGivenTo\"+(CONSENT.CONSENT_DIRECTIVE.CONSENT_DIRECTIVE_ID)\"" } ] }, { "id": "Consent.provision.action", "path": "Consent.provision.action", "short": "Consent or Refusal", "definition": "Consent or Refusal", "min": 1, "max": "1" }, { "id": "Consent.provision.action.coding", "path": "Consent.provision.action.coding", "slicing": { "discriminator": [ { "type": "value", "path": "code" } ], "rules": "open" }, "min": 1 }, { "id": "Consent.provision.action.coding:sliceConsentInstruction", "path": "Consent.provision.action.coding", "sliceName": "sliceConsentInstruction", "min": 1, "max": "1" }, { "id": "Consent.provision.action.coding:sliceConsentInstruction.system", "path": "Consent.provision.action.coding.system", "code": [ { "system": "http://hl7.org/fhir/sid/icd9" } ], "comment": "See Code", "min": 1 }, { "id": "Consent.provision.action.coding:sliceConsentInstruction.code", "path": "Consent.provision.action.coding.code", "comment": "G | R.\nRefer to IMMS codeset spreadsheet: Consent - Instruction. See Mappings.", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "CONSENT.CONSENT_DIRECTIVE.CONSENT_VALUE_CODED_CNCPT_ID" } ] }, { "id": "Consent.provision.action.coding:sliceConsentInstruction.display", "path": "Consent.provision.action.coding.display", "comment": "Grant | Refuse", "min": 1 }, { "id": "Consent.provision.action.coding:sliceConsentRefusalReaason", "path": "Consent.provision.action.coding", "sliceName": "sliceConsentRefusalReaason", "min": 1, "max": "1" }, { "id": "Consent.provision.action.coding:sliceConsentRefusalReaason.system", "path": "Consent.provision.action.coding.system", "code": [ { "system": "https://fhir.infoway-inforoute.ca/NamingSystem/ca-bc-panorama-consent-refusal-reason" } ], "comment": "See Code", "min": 1 }, { "id": "Consent.provision.action.coding:sliceConsentRefusalReaason.code", "path": "Consent.provision.action.coding.code", "comment": "Refer to IMMS codeset spreadsheet: Consent - Reason. See Mappings", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "CONSENT.CONSENT_DIRECTIVE.REFUSAL_REASON_CODE_CNCPT_ID" } ] }, { "id": "Consent.provision.action.coding:sliceConsentRefusalReaason.display", "path": "Consent.provision.action.coding.display", "comment": "Refer to IMMS codeset spreadsheet: Consent - Reason", "min": 1 }, { "id": "Consent.provision.action.text", "path": "Consent.provision.action.text", "comment": "Mandatory if Reason for Refusal = \"O\"ther. See Mappings.", "mapping": [ { "identity": "source-PIR", "map": "CONSENT.CONSENT_DIRECTIVE.REFUSAL_REASON_OTHER" } ] }, { "id": "Consent.provision.securityLabel", "path": "Consent.provision.securityLabel", "max": "1" }, { "id": "Consent.provision.purpose", "path": "Consent.provision.purpose", "max": "1" }, { "id": "Consent.provision.class", "path": "Consent.provision.class", "max": "1" }, { "id": "Consent.provision.code", "path": "Consent.provision.code", "min": 1 }, { "id": "Consent.provision.code.coding", "path": "Consent.provision.code.coding", "min": 1 }, { "id": "Consent.provision.code.coding.system", "path": "Consent.provision.code.coding.system", "comment": "See Mappings", "min": 1, "mapping": [ { "identity": "code-NVC", "map": "https://nvc-cnv.canada.ca" }, { "identity": "code-SNOMED", "map": "http://snomed.info/sct" }, { "identity": "code-PIR", "map": "https://fhir.infoway-inforoute.ca/NamingSystem/ca-bc-panorama-code" } ] }, { "id": "Consent.provision.code.coding.code", "path": "Consent.provision.code.coding.code", "comment": "Enter Vaccine code for both consent and Consent Refussal. See Mappings.", "min": 1, "mapping": [ { "identity": "source-PIR", "map": "CONSENT.CONSENT_DIRECTIVE.DIRECTIVE_ANTIGEN_ID" } ] }, { "id": "Consent.provision.code.coding.display", "path": "Consent.provision.code.coding.display", "comment": "Enter Vaccine Name for Consent or Consent Refussal", "min": 1 }, { "id": "Consent.provision.data", "path": "Consent.provision.data", "max": "1" }, { "id": "Consent.provision.provision", "path": "Consent.provision.provision", "max": "1" } ] } }