Primary Care
0.1.0-dft-preBallot 
dft-preBallot - This is the first draft of the P-Care IG. For a full list of available versions, see the Directory of published versions
Consent
Links
Profile
Derived from
http://hl7.org/fhir/StructureDefinition/Consent
Examples
Consent Example 1, Consent Example 2, Consent Example 3
Description
The P-Care profile for recording a person's healthcare consent choices.
References to this resource
Resource Content
| PCareConsent (Consent) | C | Consent | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 0..* | Identifier |
| status | O Σ ?! C | 1..1 | codeBinding |
| scope | O Σ ?! C | 1..1 | CodeableConceptBinding |
| category | O Σ C | 1..* | CodeableConceptBinding |
| patient | O Σ C | 0..1 | Reference(PCarePatient) |
| dateTime | O Σ | 0..1 | dateTime |
| performer | O Σ C | 0..* | Reference(PCareOrganization | PCarePatient | PCarePractitioner | PCarePractitionerRole | RelatedPerson) |
| organization | O Σ C | 0..* | Reference(PCareOrganization) |
| source[x] | Σ | 0..1 | |
| sourceAttachment | Attachment | ||
| sourceReference | Reference(Consent | Contract | DocumentReference | QuestionnaireResponse) | ||
| policy | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| authority | C | 0..1 | uri |
| uri | C | 0..1 | uri |
| policyRule | O Σ C | 0..1 | CodeableConceptBinding |
| verification | Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| verified | Σ | 1..1 | boolean |
| verifiedWith | C | 0..1 | Reference(Patient | RelatedPerson) |
| verificationDate | 0..1 | dateTime | |
| provision | O Σ | 1..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | O Σ | 0..1 | codeBinding |
| period | O Σ C | 0..1 | Period |
| actor | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| role | 1..1 | CodeableConceptBinding | |
| reference | C | 1..1 | Reference(PCareOrganization | PCarePatient | PCarePractitioner | PCarePractitionerRole | CareTeam | Device | Group | RelatedPerson) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | O Σ C | 0..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | Σ | 0..1 | Identifier |
| display | Σ | 0..1 | string |
| action | O Σ C | 0..* | CodeableConcept |
| securityLabel | Σ | 0..* | CodingBinding |
| purpose | Σ | 0..* | CodingBinding |
| class | Σ | 0..* | CodingBinding |
| code | Σ | 0..* | CodeableConcept |
| dataPeriod | Σ C | 0..1 | Period |
| data | Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBinding |
| reference | Σ C | 1..1 | Reference(Resource) |
| provision | 0..* | see (provision) |
| PCareConsent (Consent) | C | Consent | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 0..* | Identifier |
| status | O Σ ?! C | 1..1 | codeBinding |
| scope | O Σ ?! C | 1..1 | CodeableConceptBinding |
| category | O Σ C | 1..* | CodeableConceptBinding |
| patient | O Σ | 0..1 | Reference(PCarePatient) |
| dateTime | O Σ | 0..1 | dateTime |
| performer | O Σ | 0..* | Reference(PCareOrganization | PCarePatient | PCarePractitioner | PCarePractitionerRole | RelatedPerson) |
| organization | O Σ | 0..* | Reference(PCareOrganization) |
| source[x] | Σ | 0..1 | |
| sourceAttachment | Attachment | ||
| sourceReference | Reference(Consent | Contract | DocumentReference | QuestionnaireResponse) | ||
| policy | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| authority | C | 0..1 | uri |
| uri | C | 0..1 | uri |
| policyRule | O Σ C | 0..1 | CodeableConceptBinding |
| verification | Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| verified | Σ | 1..1 | boolean |
| verifiedWith | 0..1 | Reference(Patient | RelatedPerson) | |
| verificationDate | 0..1 | dateTime | |
| provision | O Σ | 1..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | O Σ | 0..1 | codeBinding |
| period | O Σ | 0..1 | Period |
| actor | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| role | 1..1 | CodeableConceptBinding | |
| reference | 1..1 | Reference(PCareOrganization | PCarePatient | PCarePractitioner | PCarePractitionerRole | CareTeam | Device | Group | RelatedPerson) | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | O Σ C | 0..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | Σ | 0..1 | Identifier |
| display | Σ | 0..1 | string |
| action | O Σ C | 0..* | CodeableConcept |
| securityLabel | Σ | 0..* | CodingBinding |
| purpose | Σ | 0..* | CodingBinding |
| class | Σ | 0..* | CodingBinding |
| code | Σ | 0..* | CodeableConcept |
| dataPeriod | Σ | 0..1 | Period |
| data | Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBinding |
| reference | Σ | 1..1 | Reference(Resource) |
| provision | 0..* | see (provision) |
--- We have skipped the narrative for better readability of the resource ---
</text>
</mapping>
</mapping>
</mapping>
</mapping>
</extension>
<short value="A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time" />
<definition value="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." />
<comment value="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." />
</base>
<human value="If the resource is contained in another resource, it SHALL NOT contain nested Resources" />
</constraint>
<human value="If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource" />
<expression value="contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()" />
<xpath value="not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))" />
</constraint>
<human value="If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated" />
<xpath value="not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))" />
</constraint>
<human value="If a resource is contained in another resource, it SHALL NOT have a security label" />
</constraint>
</extension>
<extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-bestpractice-explanation">
<valueMarkdown value="When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time." />
</extension>
</constraint>
</constraint>
<expression value="patient.exists() or scope.coding.where(system='something' and code='patient-privacy').exists().not()" />
<xpath value="exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='patient-privacy'])))" />
</constraint>
<expression value="patient.exists() or scope.coding.where(system='something' and code='research').exists().not()" />
<xpath value="exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='research'])))" />
</constraint>
<expression value="patient.exists() or scope.coding.where(system='something' and code='adr').exists().not()" />
<xpath value="exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='adr'])))" />
</constraint>
<expression value="patient.exists() or scope.coding.where(system='something' and code='treatment').exists().not()" />
<xpath value="exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='treatment'])))" />
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes." />
<comment value="The only time that a resource does not have an id is when it is being submitted to the server using a create operation." />
</base>
</extension>
</type>
</element>
<definition value="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." />
</base>
</type>
</constraint>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
<isModifierReason value="This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation" />
</element>
<comment value="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)." />
</base>
</type>
</constraint>
</extension>
</extension>
</binding>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
</mapping>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</mapping>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="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." />
<requirements value="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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
<isModifierReason value="Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them" />
</mapping>
</element>
<comment value="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." />
</base>
</type>
</valueIdentifier>
</example>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<comment value="This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid." />
<requirements value="The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive." />
</base>
</type>
</constraint>
</constraint>
<isModifierReason value="This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid" />
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<definition value="A selector of the type of consent being presented: ADR, Privacy, Treatment, Research. This list is now extensible." />
</base>
</type>
</constraint>
<human value="Consent.scope is expected to match the source CodeableConcept pattern for CA:eReC compatibility." />
<expression value="coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentscope' and code = 'patient-privacy' and display = 'Privacy Consent').exists()" />
</constraint>
</extension>
</binding>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<definition value="A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements." />
</base>
</type>
</constraint>
<human value="Consent.category is expected to match the source CodeableConcept pattern for CA:eReC compatibility." />
<expression value="coding.where(system = 'http://loinc.org' and code = '59284-0' and display = 'Patient Consent').exists()" />
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<comment value="Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<comment value="This is not the time of the original consent, but the time that this statement was made or derived." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<definition value="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." />
<comment value="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." />
</base>
<targetProfile value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role" />
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<definition value="The organization that manages the consent, and the framework within which it is executed." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</type>
</constraint>
</mapping>
</element>
<definition value="The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law." />
</base>
</type>
</constraint>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="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." />
<requirements value="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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
<isModifierReason value="Modifier extensions are expected to modify the meaning or interpretation of the element that contains them" />
</mapping>
</element>
<definition value="Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives." />
</base>
</type>
</constraint>
</element>
<definition value="The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law." />
<comment value="This element is for discoverability / documentation and does not modify or qualify the policy rules." />
</base>
</type>
</constraint>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<comment value="If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource." />
<requirements value="Might be a unique identifier of a policy set in XACML, or other rules engine." />
</base>
</type>
</constraint>
</extension>
</binding>
</element>
<definition value="Whether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person." />
</base>
</type>
</constraint>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="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." />
<requirements value="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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
<isModifierReason value="Modifier extensions are expected to modify the meaning or interpretation of the element that contains them" />
</mapping>
</element>
</base>
</type>
</constraint>
</element>
</base>
</type>
</constraint>
</element>
</base>
</type>
</constraint>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<definition value="An exception to the base policy of this consent. An exception can be an addition or removal of access permissions." />
</base>
</type>
</constraint>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="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." />
<requirements value="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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
<isModifierReason value="Modifier extensions are expected to modify the meaning or interpretation of the element that contains them" />
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<definition value="Action to take - permit or deny - when the rule conditions are met. Not permitted in root rule, required in all nested rules." />
</base>
</type>
</constraint>
</extension>
<description value="How a rule statement is applied, such as adding additional consent or removing consent." />
</binding>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
</base>
</type>
</constraint>
</element>
<definition value="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')." />
</base>
</type>
</constraint>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="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." />
<requirements value="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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
<isModifierReason value="Modifier extensions are expected to modify the meaning or interpretation of the element that contains them" />
</mapping>
</element>
<definition value="How the individual is involved in the resources content that is described in the exception." />
</base>
</type>
</constraint>
</extension>
</binding>
</element>
<definition value="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')." />
</base>
<targetProfile value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role" />
</type>
</constraint>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<definition value="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." />
<comment value="Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server." />
</base>
</type>
</constraint>
</mapping>
</element>
<definition value="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.\n\nThe 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)." />
<comment value="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." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</element>
<definition value="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." />
<comment value="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. \n\nWhen 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\n\nApplications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.\n\nReference 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)." />
</base>
</type>
</constraint>
</mapping>
</element>
</extension>
<definition value="Plain text narrative that identifies the resource in addition to the resource reference." />
<comment value="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." />
</base>
</type>
</constraint>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/consent|0.1.0" />
</extension>
</extension>
<comment value="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'." />
</base>
</type>
</constraint>
<human value="Consent.provision.action is expected to match the source CodeableConcept pattern for CA:eReC compatibility." />
<expression value="coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentaction' and code = 'disclose').exists()" />
</constraint>
</extension>
</binding>
</element>
<definition value="A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception." />
<comment value="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." />
</base>
</type>
</constraint>
</extension>
<description value="Security Labels from the Healthcare Privacy and Security Classification System." />
</binding>
</element>
<definition value="The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule." />
<comment value="When the purpose of use tag is on the data, access request purpose of use shall not conflict." />
</base>
</type>
</constraint>
</extension>
<description value="What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels." />
</binding>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
</extension>
</binding>
</element>
</base>
</type>
</constraint>
</extension>
</binding>
</element>
<definition value="Clinical or Operational Relevant period of time that bounds the data controlled by this rule." />
<comment value="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." />
</base>
</type>
</constraint>
</element>
</base>
</type>
</constraint>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
<definition value="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." />
<comment value="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." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="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." />
<requirements value="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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
<isModifierReason value="Modifier extensions are expected to modify the meaning or interpretation of the element that contains them" />
</mapping>
</element>
</base>
</type>
</constraint>
</extension>
</binding>
</element>
<definition value="A reference to a specific resource that defines which resources are covered by this consent." />
</base>
</type>
</constraint>
</element>
</base>
</constraint>
</element>
</snapshot>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</constraint>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
<human value="Consent.scope is expected to match the source CodeableConcept pattern for CA:eReC compatibility." />
<expression value="coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentscope' and code = 'patient-privacy' and display = 'Privacy Consent').exists()" />
</constraint>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
<human value="Consent.category is expected to match the source CodeableConcept pattern for CA:eReC compatibility." />
<expression value="coding.where(system = 'http://loinc.org' and code = '59284-0' and display = 'Patient Consent').exists()" />
</constraint>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</type>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
<targetProfile value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role" />
</type>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</type>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
<targetProfile value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role" />
</type>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
<human value="Consent.provision.action is expected to match the source CodeableConcept pattern for CA:eReC compatibility." />
<expression value="coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentaction' and code = 'disclose').exists()" />
</constraint>
</element>
</differential>
</StructureDefinition>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
},
{
},
{
},
{
}
],
{
}
],
{
"short": "A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time",
"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.",
"comment": "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.",
},
{
},
{
"human": "If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource",
"expression": "contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()",
"xpath": "not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))",
},
{
"human": "If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated",
"xpath": "not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))",
},
{
},
{
{
},
{
"valueMarkdown": "When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time."
}
],
},
{
},
{
"expression": "patient.exists() or scope.coding.where(system='something' and code='patient-privacy').exists().not()",
"xpath": "exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='patient-privacy'])))",
},
{
"expression": "patient.exists() or scope.coding.where(system='something' and code='research').exists().not()",
"xpath": "exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='research'])))",
},
{
"expression": "patient.exists() or scope.coding.where(system='something' and code='adr').exists().not()",
"xpath": "exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='adr'])))",
},
{
"expression": "patient.exists() or scope.coding.where(system='something' and code='treatment').exists().not()",
"xpath": "exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='treatment'])))",
}
],
{
},
{
},
{
},
{
}
]
},
{
"definition": "The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.",
"comment": "The only time that a resource does not have an id is when it is being submitted to the server using a create operation.",
},
{
{
}
],
}
],
},
{
"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.",
},
],
{
}
],
},
{
"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.",
"comment": "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.",
},
],
{
}
],
"isModifierReason": "This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation",
},
{
"comment": "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).",
},
],
{
}
],
{
},
{
}
],
}
},
{
"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.",
"comment": "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.",
"narrative",
"html",
"xhtml",
"display"
],
},
],
{
}
],
]
},
{
"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.",
"comment": "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.",
"inline resources",
"anonymous resources",
"contained resources"
],
},
],
]
},
{
"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.",
"comment": "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.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "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.",
"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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).",
"extensions",
"user content"
],
},
],
{
},
{
}
],
"isModifierReason": "Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them",
]
},
{
"comment": "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.",
},
],
{
}
}
],
{
}
],
{
},
{
},
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"comment": "This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.",
"requirements": "The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive.",
},
],
{
},
{
}
],
"isModifierReason": "This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid",
{
}
],
},
{
},
{
},
{
},
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"definition": "A selector of the type of consent being presented: ADR, Privacy, Treatment, Research. This list is now extensible.",
},
],
{
},
{
"human": "Consent.scope is expected to match the source CodeableConcept pattern for CA:eReC compatibility.",
"expression": "coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentscope' and code = 'patient-privacy' and display = 'Privacy Consent').exists()",
}
],
{
}
],
}
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"definition": "A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements.",
},
],
{
},
{
"human": "Consent.category is expected to match the source CodeableConcept pattern for CA:eReC compatibility.",
"expression": "coding.where(system = 'http://loinc.org' and code = '59284-0' and display = 'Patient Consent').exists()",
}
],
{
}
],
},
{
},
{
},
{
},
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"comment": "Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person.",
},
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/patient"
]
}
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"comment": "This is not the time of the original consent, but the time that this statement was made or derived.",
},
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"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.",
"comment": "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.",
"consentor"
],
},
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/organization",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/patient",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson"
]
}
],
{
}
],
{
},
{
},
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"definition": "The organization that manages the consent, and the framework within which it is executed.",
"custodian"
],
},
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/organization"
]
}
],
{
}
],
]
},
{
"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.",
"comment": "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.",
},
{
},
{
"http://hl7.org/fhir/StructureDefinition/Consent|4.0.1",
"http://hl7.org/fhir/StructureDefinition/DocumentReference|4.0.1",
"http://hl7.org/fhir/StructureDefinition/Contract|4.0.1",
"http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse|4.0.1"
]
}
],
{
}
],
]
},
{
"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.",
},
],
{
}
],
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
"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.",
"comment": "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.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "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.",
"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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).",
"extensions",
"user content",
"modifiers"
],
},
],
{
},
{
}
],
"isModifierReason": "Modifier extensions are expected to modify the meaning or interpretation of the element that contains them",
]
},
{
"definition": "Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives.",
},
],
"ppc-1"
],
{
}
],
},
{
"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.",
"comment": "This element is for discoverability / documentation and does not modify or qualify the policy rules.",
},
],
"ppc-1"
],
{
}
],
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"comment": "If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource.",
},
],
"ppc-1"
],
{
}
],
{
}
],
}
},
{
"definition": "Whether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person.",
},
],
{
}
],
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
"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.",
"comment": "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.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "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.",
"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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).",
"extensions",
"user content",
"modifiers"
],
},
],
{
},
{
}
],
"isModifierReason": "Modifier extensions are expected to modify the meaning or interpretation of the element that contains them",
]
},
{
},
],
{
}
],
},
{
},
{
"http://hl7.org/fhir/StructureDefinition/Patient|4.0.1",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson|4.0.1"
]
}
],
{
}
],
},
{
},
],
{
}
],
},
{
{
},
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"definition": "An exception to the base policy of this consent. An exception can be an addition or removal of access permissions.",
},
],
{
}
],
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
"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.",
"comment": "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.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "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.",
"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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).",
"extensions",
"user content",
"modifiers"
],
},
],
{
},
{
}
],
"isModifierReason": "Modifier extensions are expected to modify the meaning or interpretation of the element that contains them",
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"definition": "Action to take - permit or deny - when the rule conditions are met. Not permitted in root rule, required in all nested rules.",
},
],
{
}
],
{
}
],
"description": "How a rule statement is applied, such as adding additional consent or removing consent.",
}
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
},
],
{
}
],
},
{
"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').",
},
],
{
}
],
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
"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.",
"comment": "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.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "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.",
"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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).",
"extensions",
"user content",
"modifiers"
],
},
],
{
},
{
}
],
"isModifierReason": "Modifier extensions are expected to modify the meaning or interpretation of the element that contains them",
]
},
{
"definition": "How the individual is involved in the resources content that is described in the exception.",
},
],
{
}
],
{
}
],
}
},
{
"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').",
},
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/organization",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/patient",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role",
"http://hl7.org/fhir/StructureDefinition/Device",
"http://hl7.org/fhir/StructureDefinition/Group",
"http://hl7.org/fhir/StructureDefinition/CareTeam",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson"
]
}
],
{
}
],
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"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.",
"comment": "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.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"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.",
"comment": "Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure \"/[type]/[id]\" then it should be assumed that the reference is to a FHIR RESTful server.",
},
],
"ref-1"
],
{
}
],
]
},
{
"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.\n\nThe 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).",
"comment": "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.",
},
],
{
}
],
{
}
],
},
]
},
{
"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.",
"comment": "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. \n\nWhen 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\n\nApplications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.\n\nReference 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).",
},
],
{
}
],
]
},
{
{
}
],
"definition": "Plain text narrative that identifies the resource in addition to the resource reference.",
"comment": "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.",
},
],
{
}
],
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"comment": "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'.",
},
],
{
},
{
"human": "Consent.provision.action is expected to match the source CodeableConcept pattern for CA:eReC compatibility.",
"expression": "coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentaction' and code = 'disclose').exists()",
}
],
{
}
],
}
},
{
"definition": "A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception.",
"comment": "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.",
},
],
{
}
],
{
}
],
}
},
{
"definition": "The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule.",
"comment": "When the purpose of use tag is on the data, access request purpose of use shall not conflict.",
},
],
{
}
],
{
}
],
"description": "What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels.",
}
},
{
"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.",
"comment": "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.",
},
],
{
}
],
{
}
],
}
},
{
},
],
{
}
],
{
}
],
}
},
{
"definition": "Clinical or Operational Relevant period of time that bounds the data controlled by this rule.",
"comment": "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.",
},
],
{
}
],
},
{
},
],
{
}
],
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
"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.",
"comment": "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.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "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.",
"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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).",
"extensions",
"user content",
"modifiers"
],
},
],
{
},
{
}
],
"isModifierReason": "Modifier extensions are expected to modify the meaning or interpretation of the element that contains them",
]
},
{
},
],
{
}
],
{
}
],
}
},
{
"definition": "A reference to a specific resource that defines which resources are covered by this consent.",
},
{
}
],
{
}
],
},
{
},
{
}
],
}
]
},
{
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
{
"human": "Consent.scope is expected to match the source CodeableConcept pattern for CA:eReC compatibility.",
"expression": "coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentscope' and code = 'patient-privacy' and display = 'Privacy Consent').exists()",
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
{
"human": "Consent.category is expected to match the source CodeableConcept pattern for CA:eReC compatibility.",
"expression": "coding.where(system = 'http://loinc.org' and code = '59284-0' and display = 'Patient Consent').exists()",
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/patient"
]
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/organization",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/patient",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson"
]
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/organization"
]
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
},
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/organization",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/patient",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role",
"http://hl7.org/fhir/StructureDefinition/Device",
"http://hl7.org/fhir/StructureDefinition/Group",
"http://hl7.org/fhir/StructureDefinition/CareTeam",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson"
]
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
{
"human": "Consent.provision.action is expected to match the source CodeableConcept pattern for CA:eReC compatibility.",
"expression": "coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentaction' and code = 'disclose').exists()",
}
]
}
]
}
}
Constraints
| Path | Id | Grade | Details | Expression |
|---|---|---|---|---|
| Consent.status | pcare-ppc-1 | warning | Consent.status is expected to equal 'active' for ON:eReC compatibility. | $this = 'active' |
| Consent.scope | pcare-ppc-2 | warning | Consent.scope is expected to match the source CodeableConcept pattern for CA:eReC compatibility. | coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentscope' and code = 'patient-privacy' and display = 'Privacy Consent').exists() |
| Consent.category | pcare-ppc-3 | warning | Consent.category is expected to match the source CodeableConcept pattern for CA:eReC compatibility. | coding.where(system = 'http://loinc.org' and code = '59284-0' and display = 'Patient Consent').exists() |
| Consent.provision.action | pcare-ppc-4 | warning | Consent.provision.action is expected to match the source CodeableConcept pattern for CA:eReC compatibility. | coding.where(system = 'http://terminology.hl7.org/CodeSystem/consentaction' and code = 'disclose').exists() |
Obligations
| Element | Actor | Code |
|---|---|---|
| category | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHOULD:persist, SHALL:no-error |
| dateTime | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHALL:persist, SHALL:no-error |
| organization | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHALL:persist, SHALL:no-error |
| patient | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHALL:persist, SHALL:no-error |
| performer | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHALL:persist, SHALL:no-error |
| policyRule | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHOULD:persist, SHALL:no-error |
| provision | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHOULD:persist, SHALL:no-error |
| provision.action | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHOULD:persist, SHALL:no-error |
| provision.actor.reference.reference | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHALL:persist, SHALL:no-error |
| provision.period | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHALL:persist, SHALL:no-error |
| provision.type | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHALL:persist, SHALL:no-error |
| scope | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHOULD:persist, SHALL:no-error |
| status | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHOULD:persist, SHALL:no-error |