Generated Narrative: StructureDefinition ext-R5-Subscription.parameter Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) R5: Channel type (new) #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:name 1..1 Extension R5: Name (key) of the parameter (new) #xD; url 1..1 uri "name" #xD; value[x] 1..1 string Name (key) of the parameter #xD; extension:value 1..1 Extension R5: Value of the parameter to use or pass through (new) #xD; url 1..1 uri "value" #xD; value[x] 1..1 string Value of the parameter to use or pass through #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-Subscription.parameter" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R5: `Subscription.parameter` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `Subscription.parameter` as defined in FHIR R5 in FHIR R4. The source element is defined as: `Subscription.parameter` 0..* `BackboneElement` Across FHIR versions, the element set has been mapped as: * R5: `Subscription.parameter` 0..* `BackboneElement` Following are the generation technical comments: Element `Subscription.parameter` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.parameter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `Subscription.parameter` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.parameter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Exactly what these mean depend on the channel type. They can convey additional information to the server or recipient and/or meet security requirements; for example, support of multiple headers in the outgoing notifications for rest-hook type subscriptions. Note that names are not required to be unique, but channel definitions can impose restrictions.
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")])
R5: `Subscription.parameter.name` (new:string)
Element `Subscription.parameter.name` is part of an existing definition because parent element `Subscription.parameter` requires a cross-version extension. Element `Subscription.parameter.name` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.parameter.name` has no mapping targets in FHIR R4. 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.
Parameter name for information passed to the channel for notifications, for example in the case of a REST hook wanting to pass through an authorization header, the name would be Authorization.
R5: Value of the parameter to use or pass through (new)
R5: `Subscription.parameter.value` (new:string)
Element `Subscription.parameter.value` is part of an existing definition because parent element `Subscription.parameter` requires a cross-version extension. Element `Subscription.parameter.value` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.parameter.value` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Value of the parameter to use or pass through
Parameter value for information passed to the channel for notifications, for example in the case of a REST hook wanting to pass through an authorization header, the value would be `Bearer 0193...`.
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).