Generated Narrative: StructureDefinition ext-R4B-SubscriptionTopic.notificationShape Name Flags Card. Type Description & Constraints Extension 0..* Extension R4B: Properties for describing the shape of notifications generated by this topic (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:resource 1..1 Extension R4B: URL of the Resource that is the focus (main) resource in a notification shape (new) #xD; url 1..1 uri "resource" #xD; <a href="StructureDefinition-ext-R4B-SubscriptionTopic.notificationShape-definitions.html#Extension.extension:resource.value[x]" title="URL of the Resource that is the type used in this shape. This is the "focus" of the topic (or one of them if there are more than one) and the root resource for this shape definition. It will be the same, a generality, or a specificity of SubscriptionTopic.resourceTrigger.resource or SubscriptionTopic.eventTrigger.resource when they are present.">value[x] 1..1 uri URL of the Resource that is the focus (main) resource in a notification shape Binding: R4BDefinedTypesForR3 (0.1.0) (extensible): Either a resource or a data type, including logical model types. #xD; extension:include 0..* Extension R4B: Include directives, rooted in the resource for this shape (new) #xD; url 1..1 uri "include" #xD; <a href="StructureDefinition-ext-R4B-SubscriptionTopic.notificationShape-definitions.html#Extension.extension:include.value[x]" title="Search-style _include directives, rooted in the resource for this shape. Servers SHOULD include resources listed here, if they exist and the user is authorized to receive them. Clients SHOULD be prepared to receive these additional resources, but SHALL function properly without them.">value[x] 0..1 string Include directives, rooted in the resource for this shape #xD; extension:revInclude 0..* Extension R4B: Reverse include directives, rooted in the resource for this shape (new) #xD; url 1..1 uri "revInclude" #xD; <a href="StructureDefinition-ext-R4B-SubscriptionTopic.notificationShape-definitions.html#Extension.extension:revInclude.value[x]" title="Search-style _revinclude directives, rooted in the resource for this shape. Servers SHOULD include resources listed here, if they exist and the user is authorized to receive them. Clients SHOULD be prepared to receive these additional resources, but SHALL function properly without them.">value[x] 0..1 string Reverse include directives, rooted in the resource for this shape #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-SubscriptionTopic.notificationShape" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R4B: Properties for describing the shape of notifications generated by this topic (new)
R4B: `SubscriptionTopic.notificationShape` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `SubscriptionTopic.notificationShape` as defined in FHIR R4B in FHIR STU3. The source element is defined as: `SubscriptionTopic.notificationShape` 0..* `BackboneElement` Across FHIR versions, the element set has been mapped as: * R4B `SubscriptionTopic.notificationShape` 0..* `BackboneElement` Following are the generation technical comments: Element `SubscriptionTopic.notificationShape` is not mapped to FHIR STU3, since FHIR R4B `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `SubscriptionTopic.notificationShape` is not mapped to FHIR STU3, since FHIR R4B `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
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
R4B: URL of the Resource that is the focus (main) resource in a notification shape (new)
R4B: `SubscriptionTopic.notificationShape.resource` (new:uri)
Element `SubscriptionTopic.notificationShape.resource` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension. Element `SubscriptionTopic.notificationShape.resource` is not mapped to FHIR STU3, since FHIR R4B `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.resource` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). URL of the Resource that is the type used in this shape. Relative URLs are relative to the StructureDefinition root of the implemented FHIR version (e.g., http://hl7.org/fhir/StructureDefinition). For example, "Patient" maps to http://hl7.org/fhir/StructureDefinition/Patient. For more information, see [ElementDefinition.type.code](https://hl7.org/fhir/elementdefinition-definition.html#ElementDefinition.type.code).
Element `SubscriptionTopic.notificationShape.resource` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension. Element `SubscriptionTopic.notificationShape.resource` is not mapped to FHIR STU3, since FHIR R4B `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.resource` has no mapping targets in FHIR STU3. 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. 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.
URL of the Resource that is the focus (main) resource in a notification shape
URL of the Resource that is the type used in this shape. This is the "focus" of the topic (or one of them if there are more than one) and the root resource for this shape definition. It will be the same, a generality, or a specificity of SubscriptionTopic.resourceTrigger.resource or SubscriptionTopic.eventTrigger.resource when they are present.
URL of the Resource that is the type used in this shape. Relative URLs are relative to the StructureDefinition root of the implemented FHIR version (e.g., http://hl7.org/fhir/StructureDefinition). For example, "Patient" maps to http://hl7.org/fhir/StructureDefinition/Patient. For more information, see [ElementDefinition.type.code](https://hl7.org/fhir/elementdefinition-definition.html#ElementDefinition.type.code).
Either a resource or a data type, including logical model types.
R4B: Include directives, rooted in the resource for this shape (new)
R4B: `SubscriptionTopic.notificationShape.include` (new:string)
Element `SubscriptionTopic.notificationShape.include` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension. Element `SubscriptionTopic.notificationShape.include` is not mapped to FHIR STU3, since FHIR R4B `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.include` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Include directives, rooted in the resource for this shape
Search-style _include directives, rooted in the resource for this shape. Servers SHOULD include resources listed here, if they exist and the user is authorized to receive them. Clients SHOULD be prepared to receive these additional resources, but SHALL function properly without them.
R4B: Reverse include directives, rooted in the resource for this shape (new)
R4B: `SubscriptionTopic.notificationShape.revInclude` (new:string)
Element `SubscriptionTopic.notificationShape.revInclude` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension. Element `SubscriptionTopic.notificationShape.revInclude` is not mapped to FHIR STU3, since FHIR R4B `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.revInclude` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Reverse include directives, rooted in the resource for this shape
Search-style _revinclude directives, rooted in the resource for this shape. Servers SHOULD include resources listed here, if they exist and the user is authorized to receive them. Clients SHOULD be prepared to receive these additional resources, but SHALL function properly without them.
Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).