Generated Narrative: StructureDefinition ext-R4B-Subscription.channel Name Flags Card. Type Description & Constraints Extension 1..1 Extension(5.0.0) The channel on which to report matches to the criteria #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:type 1..1 Extension rest-hook | websocket | email | sms | message #xD; url 1..1 uri "type" #xD; value[x] 0..1 code rest-hook | websocket | email | sms | message Binding: R4B_subscription_channel_type_for_R5 (0.0.1-snapshot-2) (required): The type of method used to execute a subscription. #xD; extension:endpoint 0..1 Extension Where the channel points to #xD; url 1..1 uri "endpoint" #xD; value[x] 0..1 url Where the channel points to #xD; extension:payload 0..1 Extension MIME type to send, or omit for no payload #xD; url 1..1 uri "payload" #xD; value[x] 0..1 code MIME type to send, or omit for no payload Binding: MimeTypes (required): BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049) #xD; extension:header 0..* Extension Usage depends on the channel type #xD; url 1..1 uri "header" #xD; value[x] 0..1 string Usage depends on the channel type #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-Subscription.channel" #xD; Documentation for this format
Cross-version Extension for R4B.Subscription.channel for use in FHIR R5
This cross-version extension represents Subscription.channel from http://hl7.org/fhir/StructureDefinition/Subscription|4.3.0 for use in FHIR R5.
The channel on which to report matches to the criteria
Details where to send notifications when resources are received that meet the criteria.
`Subscription.channel` has no related element in R5:Subscription
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
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
rest-hook | websocket | email | sms | message
The type of channel to send notifications on.
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 managable, 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.
The type of method used to execute a subscription.
The url that describes the actual end-point to send messages to.
MIME type to send, or omit for no payload
The mime type to send the payload in - either application/fhir+xml, or application/fhir+json. If the payload is not present, then there is no payload in the notification, just a notification. The mime type "text/plain" may also be used for Email and SMS subscriptions.
Additional headers / information to send as part of the notification.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).