Generated Narrative: StructureDefinition ext-R5-Permission.rule Name Flags Card. Type Description & Constraints Extension ?! 0..* Extension(4.3.0) R5: Constraints to the Permission (new) This is a modifier extension #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:type 0..1 Extension R5: deny | permit (new) #xD; url 1..1 uri "type" #xD; value[x] 0..1 code deny | permit Binding: ConsentProvisionType (required): How a rule statement is applied. #xD; extension:data 0..* Extension R5: The selection criteria to identify data that is within scope of this provision (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:resource 0..* Extension R5: Explicit FHIR Resource references (new) #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:meaning 1..1 Extension R5: instance | related | dependents | authoredby (new) #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 R5: The actual data reference (new) #xD; url 1..1 uri "reference" #xD; value[x] 1..1 Reference(Cross-version Profile for R5.Resource for use in FHIR R4B(0.1.0) | Resource) The actual data reference #xD; url 1..1 uri "resource" #xD; value[x] 0..0 Value of extension #xD; extension:security 0..* Extension R5: Security tag code on .meta.security (new) #xD; url 1..1 uri "security" #xD; value[x] 0..1 Coding Security tag code on .meta.security #xD; extension:period 0..* Extension R5: Timeframe encompasing data create/update (new) #xD; url 1..1 uri "period" #xD; value[x] 0..1 Period Timeframe encompasing data create/update #xD; extension:expression 0..1 Extension R5: Expression identifying the data (new) #xD; url 1..1 uri "expression" #xD; value[x] 0..1 Expression Expression identifying the data #xD; url 1..1 uri "data" #xD; value[x] 0..0 Value of extension #xD; extension:activity 0..* Extension R5: A description or definition of which activities are allowed to be done on the data (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:actor 0..* Extension R5: Authorized actor(s) (new) #xD; url 1..1 uri "actor" #xD; value[x] 0..1 Reference(Cross-version Profile for R5.Device for use in FHIR R4B(0.1.0) | Device | Cross-version Profile for R5.Group for use in FHIR R4B(0.1.0) | Group | Cross-version Profile for R5.CareTeam for use in FHIR R4B(0.1.0) | CareTeam | Cross-version Profile for R5.Organization for use in FHIR R4B(0.1.0) | Organization | Cross-version Profile for R5.Patient for use in FHIR R4B(0.1.0) | Patient | Cross-version Profile for R5.Practitioner for use in FHIR R4B(0.1.0) | Practitioner | Cross-version Profile for R5.RelatedPerson for use in FHIR R4B(0.1.0) | RelatedPerson | Cross-version Profile for R5.PractitionerRole for use in FHIR R4B(0.1.0) | PractitionerRole) Authorized actor(s) #xD; extension:action 0..* Extension R5: Actions controlled by this rule (new) #xD; url 1..1 uri "action" #xD; value[x] 0..1 CodeableConcept Actions controlled by this rule Binding: ConsentActionCodes (example): Detailed codes for the action. #xD; extension:purpose 0..* Extension R5: The purpose for which the permission is given (new) #xD; url 1..1 uri "purpose" #xD; value[x] 0..1 CodeableConcept The purpose for which the permission is given Binding: http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|2.0.0 (preferred): What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. #xD; url 1..1 uri "activity" #xD; value[x] 0..0 Value of extension #xD; extension:limit 0..* Extension R5: What limits apply to the use of the data (new) #xD; url 1..1 uri "limit" #xD; value[x] 0..1 CodeableConcept What limits apply to the use of the data Binding: R5SecurityLabelEventExamplesForR4B (0.1.0) (example): Obligations and Refrains #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-Permission.rule" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R5: `Permission.rule` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `Permission.rule` as defined in FHIR R5 in FHIR R4B. The source element is defined as: `Permission.rule` 0..* `BackboneElement` Following are the generation technical comments: Element `Permission.rule` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Child element `type` is a modifier, so this extension must be a modifier.
Element `Permission.rule` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children unless an empty Parameters resource
hasValue() or (children().count() > id.count()) or $this is Parameters
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
This extension is a modifier because the source element `Permission.rule` is flagged as a modifier element.
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
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Element `Permission.rule.type` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension. Element `Permission.rule.type` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.type` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
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.
R5: The selection criteria to identify data that is within scope of this provision (new)
R5: `Permission.rule.data` (new:BackboneElement)
Element `Permission.rule.data` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension. Element `Permission.rule.data` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.data` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
R5: Explicit FHIR Resource references (new)
R5: `Permission.rule.data.resource` (new:BackboneElement)
Element `Permission.rule.data.resource` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension. Element `Permission.rule.data.resource` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.data.resource` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
R5: instance | related | dependents | authoredby (new)
R5: `Permission.rule.data.resource.meaning` (new:code)
Element `Permission.rule.data.resource.meaning` is part of an existing definition because parent element `Permission.rule.data.resource` requires a cross-version extension. Element `Permission.rule.data.resource.meaning` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.data.resource.meaning` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
instance | related | dependents | authoredby
How the resource reference is interpreted when testing consent restrictions.
How a resource reference is interpreted when testing consent restrictions.
R5: `Permission.rule.data.resource.reference` (new:Reference(Resource))
Element `Permission.rule.data.resource.reference` is part of an existing definition because parent element `Permission.rule.data.resource` requires a cross-version extension. Element `Permission.rule.data.resource.reference` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.data.resource.reference` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
A reference to a specific resource that defines which resources are covered by this consent.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4B/extensibility.html) for a list).
R5: Security tag code on .meta.security (new)
R5: `Permission.rule.data.security` (new:Coding)
Element `Permission.rule.data.security` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension. Element `Permission.rule.data.security` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.data.security` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Note the ConfidentialityCode vocabulary indicates the highest value, thus 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 `Permission.rule.data.security` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension. Element `Permission.rule.data.security` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.data.security` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
The data in scope are those with the given codes present in that data .meta.security element.
Note the ConfidentialityCode vocabulary indicates the highest value, thus 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.
R5: Timeframe encompasing data create/update (new)
R5: `Permission.rule.data.period` (new:Period)
Element `Permission.rule.data.period` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension. Element `Permission.rule.data.period` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.data.period` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). This has a different sense to the .validity.
Element `Permission.rule.data.period` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension. Element `Permission.rule.data.period` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.data.period` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Timeframe encompasing data create/update
Clinical or Operational Relevant period of time that bounds the data controlled by this rule.
This has a different sense to the .validity.
R5: Expression identifying the data (new)
R5: `Permission.rule.data.expression` (new:Expression)
Element `Permission.rule.data.expression` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension. Element `Permission.rule.data.expression` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.data.expression` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Used when other data selection elements are insufficient.
R5: A description or definition of which activities are allowed to be done on the data (new)
R5: `Permission.rule.activity` (new:BackboneElement)
Element `Permission.rule.activity` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension. Element `Permission.rule.activity` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.activity` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
R5: `Permission.rule.activity.actor` (new:Reference(Device,Group,CareTeam,Organization,Patient,Practitioner,RelatedPerson,PractitionerRole))
Element `Permission.rule.activity.actor` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension. Element `Permission.rule.activity.actor` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.activity.actor` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
The actor(s) authorized for the defined activity.
R5: Actions controlled by this rule (new)
R5: `Permission.rule.activity.action` (new:CodeableConcept)
Element `Permission.rule.activity.action` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension. Element `Permission.rule.activity.action` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.activity.action` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). 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 `Permission.rule.activity.action` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension. Element `Permission.rule.activity.action` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.activity.action` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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'.
R5: The purpose for which the permission is given (new)
R5: `Permission.rule.activity.purpose` (new:CodeableConcept)
Element `Permission.rule.activity.purpose` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension. Element `Permission.rule.activity.purpose` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.activity.purpose` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
The purpose for which the permission is given
The purpose for which the permission is given.
What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels.
R5: What limits apply to the use of the data (new)
R5: `Permission.rule.limit` (new:CodeableConcept)
Element `Permission.rule.limit` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension. Element `Permission.rule.limit` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped. Element `Permission.rule.limit` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
What limits apply to the use of the data
What limits apply to the use of the data.