Generated Narrative: StructureDefinition ext-R4-Consent.provision Name Flags Card. Type Description & Constraints Extension 0..1 Extension R4: Constraints to the base Consent.policyRule #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:type 0..1 Extension R4: type #xD; url 1..1 uri "type" #xD; value[x] 0..1 code deny | permit Binding: ConsentExceptType (required): How a rule statement is applied, such as adding additional consent or removing consent. #xD; extension:period 0..1 Extension R4: Timeframe for this rule #xD; url 1..1 uri "period" #xD; value[x] 0..1 Period Timeframe for this rule #xD; extension:actor 0..* Extension R4: Who|what controlled by this rule (or group, by role) #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:role 1..1 Extension R4: How the actor is involved #xD; url 1..1 uri "role" #xD; value[x] 1..1 CodeableConcept How the actor is involved Binding: R4SecurityRoleTypeForR3 (0.1.0) (extensible): How an actor is involved in the consent considerations. #xD; extension:reference 1..1 Extension R4: Resource for the actor (or group, by role) #xD; url 1..1 uri "http://hl7.org/fhir/StructureDefinition/alternate-reference" #xD; url 1..1 uri "actor" #xD; value[x] 0..0 Value of extension #xD; extension:action 0..* Extension R4: Actions controlled by this rule #xD; url 1..1 uri "action" #xD; value[x] 0..1 CodeableConcept Actions controlled by this rule Binding: Consent Action Codes (example): Detailed codes for the consent action. #xD; extension:securityLabel 0..* Extension R4: Security Labels that define affected resources #xD; url 1..1 uri "securityLabel" #xD; value[x] 0..1 Coding Security Labels that define affected resources Binding: R4SecurityLabelsForR3 (0.1.0) (extensible): Security Labels from the Healthcare Privacy and Security Classification System. #xD; extension:purpose 0..* Extension R4: Context of activities covered by this rule #xD; url 1..1 uri "purpose" #xD; value[x] 0..1 Coding Context of activities covered by this rule Binding: R4V3PurposeOfUseForR3 (0.1.0) (extensible): What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. #xD; extension:class 0..* Extension R4: e.g. Resource Type, Profile, CDA, etc. #xD; url 1..1 uri "class" #xD; value[x] 0..1 Coding e.g. Resource Type, Profile, CDA, etc. #xD; extension:code 0..* Extension R4: e.g. LOINC or SNOMED CT code, etc. in the content additional types #xD; url 1..1 uri "code" #xD; value[x] 0..1 CodeableConcept e.g. LOINC or SNOMED CT code, etc. in the content #xD; extension:dataPeriod 0..1 Extension R4: Timeframe for data controlled by this rule #xD; url 1..1 uri "dataPeriod" #xD; value[x] 0..1 Period Timeframe for data controlled by this rule #xD; extension:data 0..* Extension R4: Data controlled by this rule #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:meaning 1..1 Extension R4: instance | related | dependents | authoredby #xD; url 1..1 uri "meaning" #xD; value[x] 1..1 code instance | related | dependents | authoredby Binding: ConsentDataMeaning (required): How a resource reference is interpreted when testing consent restrictions. #xD; extension:reference 1..1 Extension R4: The actual data reference #xD; url 1..1 uri "reference" #xD; value[x] 1..1 Reference(Cross-version Profile for R4.Resource for use in FHIR STU3(0.1.0) | Resource) The actual data reference #xD; url 1..1 uri "data" #xD; value[x] 0..0 Value of extension #xD; extension:provision 0..* Extension R4: Nested Exception Rules (new) #xD; url 1..1 uri "http://hl7.org/fhir/4.0/StructureDefinition/extension-Consent.provision" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/4.0/StructureDefinition/extension-Consent.provision" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R4: Constraints to the base Consent.policyRule
This extension is part of the cross-version definitions generated to enable use of the element `Consent.provision` as defined in FHIR R4 in FHIR STU3. The source element is defined as: `Consent.provision` 0..1 `BackboneElement` Following are the generation technical comments: Element `Consent.provision` is mapped to FHIR STU3 element `Consent.except` as `SourceIsNarrowerThanTarget`. Creating extension because element `Consent.provision` is a content reference and requires an extesion definition.
Element `Consent.provision` is mapped to FHIR STU3 element `Consent.except` as `SourceIsNarrowerThanTarget`.
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Element `Consent.provision.type` is mapped to FHIR STU3 element `Consent.except.type` as `Equivalent`.
Additional Content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. In order 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.
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.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Action to take - permit or deny - when the rule conditions are met. Not permitted in root rule, required in all nested rules.
How a rule statement is applied, such as adding additional consent or removing consent.
Element `Consent.provision.period` is mapped to FHIR STU3 element `Consent.except.period` as `Equivalent`.
R4: Who|what controlled by this rule (or group, by role)
Element `Consent.provision.actor` is mapped to FHIR STU3 element `Consent.actor` as `Equivalent`. Element `Consent.provision.actor` is mapped to FHIR STU3 element `Consent.except.actor` as `Equivalent`.
Element `Consent.provision.actor.role` is mapped to FHIR STU3 element `Consent.actor.role` as `Equivalent`. Element `Consent.provision.actor.role` is mapped to FHIR STU3 element `Consent.except.actor.role` as `Equivalent`.
How the individual is involved in the resources content that is described in the exception.
How an actor is involved in the consent considerations.
R4: Resource for the actor (or group, by role)
Element `Consent.provision.actor.reference` is mapped to FHIR STU3 element `Consent.actor.reference` as `SourceIsBroaderThanTarget`. Element `Consent.provision.actor.reference` is mapped to FHIR STU3 element `Consent.except.actor.reference` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4 element `Consent.provision.actor.reference` with unmapped reference targets: PractitionerRole.
Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).
Element `Consent.provision.action` is mapped to FHIR STU3 element `Consent.action` as `Equivalent`. Element `Consent.provision.action` is mapped to FHIR STU3 element `Consent.except.action` as `Equivalent`. 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'.
Element `Consent.provision.action` is mapped to FHIR STU3 element `Consent.action` as `Equivalent`. Element `Consent.provision.action` is mapped to FHIR STU3 element `Consent.except.action` as `Equivalent`.
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'.
R4: Security Labels that define affected resources
Element `Consent.provision.securityLabel` is mapped to FHIR STU3 element `Consent.securityLabel` as `Equivalent`. Element `Consent.provision.securityLabel` is mapped to FHIR STU3 element `Consent.except.securityLabel` as `Equivalent`. 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.
Element `Consent.provision.securityLabel` is mapped to FHIR STU3 element `Consent.securityLabel` as `Equivalent`. Element `Consent.provision.securityLabel` is mapped to FHIR STU3 element `Consent.except.securityLabel` as `Equivalent`.
Security Labels that define affected resources
A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception.
If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict.
Security Labels from the Healthcare Privacy and Security Classification System.
R4: Context of activities covered by this rule
Element `Consent.provision.purpose` is mapped to FHIR STU3 element `Consent.purpose` as `Equivalent`. Element `Consent.provision.purpose` is mapped to FHIR STU3 element `Consent.except.purpose` as `Equivalent`. When the purpose of use tag is on the data, access request purpose of use shall not conflict.
Element `Consent.provision.purpose` is mapped to FHIR STU3 element `Consent.purpose` as `Equivalent`. Element `Consent.provision.purpose` is mapped to FHIR STU3 element `Consent.except.purpose` as `Equivalent`.
Context of activities covered by this rule
The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule.
When the purpose of use tag is on the data, access request purpose of use shall not conflict.
What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels.
R4: e.g. Resource Type, Profile, CDA, etc.
Element `Consent.provision.class` is mapped to FHIR STU3 element `Consent.except.class` as `Equivalent`. 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.
Element `Consent.provision.class` is mapped to FHIR STU3 element `Consent.except.class` as `Equivalent`.
The class of information covered by this rule. The type can be a FHIR resource type, a profile on a type, or a CDA document, or some other type that indicates what sort of information the consent relates to.
Multiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.
R4: e.g. LOINC or SNOMED CT code, etc. in the content additional types
R4: `Consent.provision.code` additional types (CodeableConcept) additional types from child elements (text)
Element `Consent.provision.code` is mapped to FHIR STU3 element `Consent.except.code` as `SourceIsBroaderThanTarget`. The mappings for `Consent.provision.code` do not cover the following types: CodeableConcept. The mappings for `Consent.provision.code` do not cover the following types based on type expansion: text. Typical use of this is a Document code with class = CDA.
Element `Consent.provision.code` is mapped to FHIR STU3 element `Consent.except.code` as `SourceIsBroaderThanTarget`. The mappings for `Consent.provision.code` do not cover the following types: CodeableConcept. The mappings for `Consent.provision.code` do not cover the following types based on type expansion: text.
e.g. LOINC or SNOMED CT code, etc. in the content
If this code is found in an instance, then the rule applies.
Typical use of this is a Document code with class = CDA.
R4: Timeframe for data controlled by this rule
Element `Consent.provision.dataPeriod` is mapped to FHIR STU3 element `Consent.dataPeriod` as `Equivalent`. Element `Consent.provision.dataPeriod` is mapped to FHIR STU3 element `Consent.except.dataPeriod` as `Equivalent`. 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.
Element `Consent.provision.dataPeriod` is mapped to FHIR STU3 element `Consent.dataPeriod` as `Equivalent`. Element `Consent.provision.dataPeriod` is mapped to FHIR STU3 element `Consent.except.dataPeriod` as `Equivalent`.
Timeframe for data controlled by this rule
Clinical or Operational Relevant period of time that bounds the data controlled by this rule.
This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.
Element `Consent.provision.data` is mapped to FHIR STU3 element `Consent.data` as `Equivalent`. Element `Consent.provision.data` is mapped to FHIR STU3 element `Consent.except.data` as `Equivalent`.
R4: instance | related | dependents | authoredby
Element `Consent.provision.data.meaning` is mapped to FHIR STU3 element `Consent.data.meaning` as `Equivalent`. Element `Consent.provision.data.meaning` is mapped to FHIR STU3 element `Consent.except.data.meaning` as `Equivalent`.
instance | related | dependents | authoredby
How the resource reference is interpreted when testing consent restrictions.
How a resource reference is interpreted when testing consent restrictions.
Element `Consent.provision.data.reference` is mapped to FHIR STU3 element `Consent.data.reference` as `Equivalent`. Element `Consent.provision.data.reference` is mapped to FHIR STU3 element `Consent.except.data.reference` as `Equivalent`.
A reference to a specific resource that defines which resources are covered by this consent.
R4: `Consent.provision.provision` (new:Consent.provision)
Element `Consent.provision.provision` has a context of Consent.except based on following the parent source element upwards and mapping to `Consent`. Element `Consent.provision.provision` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).