Generated Narrative: StructureDefinition ext-R3-Consent.except Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) Additional rule - addition or removal of permissions #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:type 1..1 Extension deny | permit #xD; url 1..1 uri "type" #xD; value[x] 0..1 code deny | permit Binding: ConsentProvisionType (required): How an exception statement is applied, such as adding additional consent or removing consent #xD; extension:period 0..1 Extension Timeframe for this exception #xD; url 1..1 uri "period" #xD; value[x] 0..1 Period Timeframe for this exception #xD; extension:actor 0..* Extension Who|what controlled by this exception (or group, by role) #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:role 1..1 Extension How the actor is involved #xD; url 1..1 uri "role" #xD; value[x] 0..1 CodeableConcept How the actor is involved Binding: R3_security_role_type_for_R4 (0.0.1-snapshot-2) (extensible): How an actor is involved in the consent considerations #xD; extension:reference 1..1 Extension Resource for the actor (or group, by role) #xD; url 1..1 uri "reference" #xD; value[x] 0..1 Reference() Resource for the actor (or group, by role) #xD; url 1..1 uri "actor" #xD; extension:action 0..* Extension Actions controlled by this exception #xD; url 1..1 uri "action" #xD; value[x] 0..1 CodeableConcept Actions controlled by this exception Binding: R3_consent_action_for_R4 (0.0.1-snapshot-2) (example): Detailed codes for the consent action. #xD; extension:securityLabel 0..* Extension 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: R3_security_labels_for_R4 (0.0.1-snapshot-2) (extensible): Security Labels from the Healthcare Privacy and Security Classification System. #xD; extension:purpose 0..* Extension Context of activities covered by this exception #xD; url 1..1 uri "purpose" #xD; value[x] 0..1 Coding Context of activities covered by this exception Binding: v3.PurposeOfUse (2014-03-26) (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 e.g. Resource Type, Profile, or CDA etc #xD; url 1..1 uri "class" #xD; value[x] 0..1 Coding e.g. Resource Type, Profile, or CDA etc Binding: R3_consent_content_class_for_R4 (0.0.1-snapshot-2) (extensible): The class (type) of information a consent rule covers #xD; extension:code 0..* Extension e.g. LOINC or SNOMED CT code, etc in the content #xD; url 1..1 uri "code" #xD; value[x] 0..1 Coding e.g. LOINC or SNOMED CT code, etc in the content Binding: R3_consent_content_code_for_R4 (0.0.1-snapshot-2) (example): If this code is found in an instance, then the exception applies #xD; extension:dataPeriod 0..1 Extension Timeframe for data controlled by this exception #xD; url 1..1 uri "dataPeriod" #xD; value[x] 0..1 Period Timeframe for data controlled by this exception #xD; extension:data 0..* Extension Data controlled by this exception #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:meaning 1..1 Extension instance | related | dependents | authoredby #xD; url 1..1 uri "meaning" #xD; value[x] 0..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 The actual data reference #xD; url 1..1 uri "reference" #xD; value[x] 0..1 Reference() The actual data reference #xD; url 1..1 uri "data" #xD; url 1..1 uri "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.except" #xD; Documentation for this format
Cross-version Extension for R3.Consent.except for use in FHIR R4
This cross-version extension represents Consent.except from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 for use in FHIR R4.
Additional rule - addition or removal of permissions
An exception to the base policy of this consent. An exception can be an addition or removal of access permissions.
`Consent.except` maps to R4 `Consent.provision`. Changed from an array to a single value (max cardinality from * to 1). So is mapped as SourceIsBroaderThanTarget.
All FHIR elements must have a @value or children
hasValue() or (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
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Action to take - permit or deny - when the exception conditions are met.
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.
How an exception statement is applied, such as adding additional consent or removing consent
The timeframe in this exception is valid.
Who|what controlled by this exception (or group, by role)
Who or what is controlled by this Exception. Use group to identify a set of actors by some property they share (e.g. 'admitting officers').
How the individual is involved in the resources content that is described in the exception.
How an actor is involved in the consent considerations
Resource for the actor (or group, by role)
The resource that identifies the actor. To identify a actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers').
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).
Security Labels that define affected resources
A set of security labels that define which resources are controlled by this exception. If more than one label is specified, all resources must have all the specified labels.
Security Labels from the Healthcare Privacy and Security Classification System.
Context of activities covered by this exception
The context of the activities a user is taking - why the user is accessing the data - that are controlled by this exception.
What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels
The class of information covered by this exception. 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.
The class (type) of information a consent rule covers
e.g. LOINC or SNOMED CT code, etc in the content
If this code is found in an instance, then the exception applies.
If this code is found in an instance, then the exception applies
Timeframe for data controlled by this exception
Clinical or Operational Relevant period of time that bounds the data controlled by this exception.
The resources controlled by this exception, if specific resources are referenced.
instance | related | dependents | authoredby
How the resource reference is interpreted when testing consent restrictions.
How a resource reference is interpreted when testing consent restrictions
A reference to a specific resource that defines which resources are covered by this consent.