Profile: Subscription
This profile provides guidance for implementing FHIR R5 Subscription resource features & elements using extensions defined in FHIR R4.
It is used by a Subscriber to request subscription to a specific events and get notification whenever these events are created or updated by the Subscription Service.
In order to align with the use of FHIR R4 at OntarioHealth, Subscriptions are expected to conform to the Subscription profile defined by the [Subscriptions R5 Backport Implementation Guide] (https://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription.html).
Simplifier project page: R4/B Topic-Based Subscription
Derived from: FHIR R5 Backport
Formal Views of Profile Content
Description of Profiles, Differentials, Snapshots and how the different presentations work
Differential View
R4BackportedR5Subscription (Subscription) | I | Subscription | There are no (further) constraints on this element Element idSubscription Server push subscription criteria Alternate namesWebHook, Hook, Routing Rule DefinitionThe subscription resource is used to define a push-based subscription from a server to another system. Once a subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined "channel" so that another system can take an appropriate action.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idSubscription.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idSubscription.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idSubscription.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idSubscription.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idSubscription.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSubscription.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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.
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSubscription.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.status requested | active | error | off DefinitionThe status of the subscription, which marks the server state for managing the subscription. A client can only submit subscription resources in the requested or off state. Only the server can move a subscription from requested to active, and then to error. Either the server or the client can turn a subscription off. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. The status of a subscription.
|
contact | Σ | 0..* | ContactPoint | There are no (further) constraints on this element Element idSubscription.contact Contact details for source (e.g. troubleshooting) DefinitionContact details for a human to contact about the subscription. The primary use of this for system administrator troubleshooting.
|
end | Σ | 0..1 | instant | There are no (further) constraints on this element Element idSubscription.end When to automatically delete the subscription DefinitionThe time for the server to turn the subscription off. The server is permitted to deviate from this time but should observe it.
|
reason | Σ | 1..1 | string | There are no (further) constraints on this element Element idSubscription.reason Description of why this subscription was created DefinitionA description of why this subscription is defined.
|
criteria | S Σ | 1..1 | string | There are no (further) constraints on this element Element idSubscription.criteria Rule for server push DefinitionThe rules that the server should use to determine when to generate notifications for this subscription. The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading "/".
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.criteria.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references) | |
extension | I | 0..* | Extension | Element idSubscription.criteria.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Constraints
|
filterCriteria | S I | 0..* | Extension(string) | Element idSubscription.criteria.extension:filterCriteria Optional Extensions Element Alternate namesextensions, user content DefinitionCriteria for topic-based filtering (filter-by) 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionfilterCriteria Constraints
|
value | 0..1 | System.String | There are no (further) constraints on this element Element idSubscription.criteria.value Primitive value for string DefinitionThe actual value System.String Maximum string length1048576 | |
error | Σ | 0..1 | string | There are no (further) constraints on this element Element idSubscription.error Latest error note DefinitionA record of the last error that occurred when the server processed a notification.
|
channel | Σ | 1..1 | BackboneElement | There are no (further) constraints on this element Element idSubscription.channel The channel on which to report matches to the criteria DefinitionDetails where to send notifications when resources are received that meet the criteria.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.channel.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | Element idSubscription.channel.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Constraints
|
NotificationRetryPeriod | I | 0..* | Extension(Complex) | Element idSubscription.channel.extension:NotificationRetryPeriod Optional Extensions Element Alternate namesextensions, user content DefinitionInterval in hours to retry sending notification. 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. Extension(Complex) Extension URLhttp://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionNotificationRetryPeriod Constraints
|
heartbeatPeriod | I | 0..* | Extension(unsignedInt) | Element idSubscription.channel.extension:heartbeatPeriod Optional Extensions Element Alternate namesextensions, user content DefinitionInterval in seconds to send "heartbeat' notifications 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-heartbeatPeriod Constraints
|
timeout | I | 0..* | Extension(unsignedInt) | Element idSubscription.channel.extension:timeout Optional Extensions Element Alternate namesextensions, user content DefinitionTimeout in seconds to attempt notification delivery. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubmissionTimeout Constraints
|
maxCount | I | 0..* | Extension(positiveInt) | Element idSubscription.channel.extension:maxCount Optional Extensions Element Alternate namesextensions, user content DefinitionMaximum number of triggering resources included in notification bundles. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionmaxCount Constraints
|
parameter | I | 0..* | Extension(string) | Element idSubscription.channel.extension:parameter Optional Extensions Element Alternate namesextensions, user content DefinitionThis extension holds the client certificate used for authentication when sending REST-hook notifications. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionParameterExtension Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSubscription.channel.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.channel.type rest-hook | websocket | email | sms | message DefinitionThe type of channel to send notifications on. The type of method used to execute a subscription.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.channel.type.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references) | |
extension | I | 0..* | Extension | Element idSubscription.channel.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Constraints
|
customChannelType | S I | 0..* | Extension(Coding) | Element idSubscription.channel.type.extension:customChannelType Optional Extensions Element Alternate namesextensions, user content DefinitionAdditional channel types not defined before FHIR R5 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. https://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubcriptioncustomChannelType Constraints
|
value | 0..1 | System.String | There are no (further) constraints on this element Element idSubscription.channel.type.value Primitive value for code DefinitionPrimitive value for code System.String | |
endpoint | Σ | 0..1 | url | There are no (further) constraints on this element Element idSubscription.channel.endpoint Where the channel points to DefinitionThe url that describes the actual end-point to send messages to. For rest-hook, and websocket, the end-point must be an http: or https: URL; for email, a mailto: url, for sms, a tel: url, and for message the endpoint can be in any form of url the server understands (usually, http: or mllp:). The URI is allowed to be relative; in which case, it is relative to the server end-point (since there may be more than one, clients should avoid using relative URIs).
|
payload | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.channel.payload MIME type to send, or omit for no payload DefinitionThe 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. Sending the payload has obvious security implications. The server is responsible for ensuring that the content is appropriately secured. The mime type of an attachment. Any valid mime type is allowed.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.channel.payload.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references) | |
extension | I | 1..* | Extension | Element idSubscription.channel.payload.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Constraints
|
content | S I | 1..1 | Extension(code) | Element idSubscription.channel.payload.extension:content Optional Extensions Element Alternate namesextensions, user content DefinitionHow much of the resource content to deliver in the notification payload. The choices are an empty payload, only the resource id, or the full resource content. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-Subscriptioncontent Constraints
|
value | 0..1 | System.String | There are no (further) constraints on this element Element idSubscription.channel.payload.value Primitive value for code DefinitionPrimitive value for code System.String | |
header | Σ | 0..* | string | Element idSubscription.channel.header Usage depends on the channel type DefinitionUse to specify additional information that will be included inside the notification payload when the notification is sent. Each entry consists of a key-value pair. This should support sending client certificates and client keys with validation to determine if it is the certificate itself or just the name. This can convey additional information to the recipient and/or meet security requirements; for example, support of multiple headers in the outgoing notifications for rest-hook type subscriptions.
|
Hybrid View
R4BackportedR5Subscription (Subscription) | I | Subscription | There are no (further) constraints on this element Element idSubscription Server push subscription criteria Alternate namesWebHook, Hook, Routing Rule DefinitionThe subscription resource is used to define a push-based subscription from a server to another system. Once a subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined "channel" so that another system can take an appropriate action.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idSubscription.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idSubscription.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idSubscription.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idSubscription.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idSubscription.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSubscription.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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.
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSubscription.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.status requested | active | error | off DefinitionThe status of the subscription, which marks the server state for managing the subscription. A client can only submit subscription resources in the requested or off state. Only the server can move a subscription from requested to active, and then to error. Either the server or the client can turn a subscription off. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. The status of a subscription.
|
contact | Σ | 0..* | ContactPoint | There are no (further) constraints on this element Element idSubscription.contact Contact details for source (e.g. troubleshooting) DefinitionContact details for a human to contact about the subscription. The primary use of this for system administrator troubleshooting.
|
end | Σ | 0..1 | instant | There are no (further) constraints on this element Element idSubscription.end When to automatically delete the subscription DefinitionThe time for the server to turn the subscription off. The server is permitted to deviate from this time but should observe it.
|
reason | Σ | 1..1 | string | There are no (further) constraints on this element Element idSubscription.reason Description of why this subscription was created DefinitionA description of why this subscription is defined.
|
criteria | S Σ | 1..1 | string | There are no (further) constraints on this element Element idSubscription.criteria Rule for server push DefinitionThe rules that the server should use to determine when to generate notifications for this subscription. The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading "/".
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.criteria.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references) | |
extension | I | 0..* | Extension | Element idSubscription.criteria.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Constraints
|
filterCriteria | S I | 0..* | Extension(string) | Element idSubscription.criteria.extension:filterCriteria Optional Extensions Element Alternate namesextensions, user content DefinitionCriteria for topic-based filtering (filter-by) 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionfilterCriteria Constraints
|
value | 0..1 | System.String | There are no (further) constraints on this element Element idSubscription.criteria.value Primitive value for string DefinitionThe actual value System.String Maximum string length1048576 | |
error | Σ | 0..1 | string | There are no (further) constraints on this element Element idSubscription.error Latest error note DefinitionA record of the last error that occurred when the server processed a notification.
|
channel | Σ | 1..1 | BackboneElement | There are no (further) constraints on this element Element idSubscription.channel The channel on which to report matches to the criteria DefinitionDetails where to send notifications when resources are received that meet the criteria.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.channel.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | Element idSubscription.channel.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Constraints
|
NotificationRetryPeriod | I | 0..* | Extension(Complex) | Element idSubscription.channel.extension:NotificationRetryPeriod Optional Extensions Element Alternate namesextensions, user content DefinitionInterval in hours to retry sending notification. 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. Extension(Complex) Extension URLhttp://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionNotificationRetryPeriod Constraints
|
heartbeatPeriod | I | 0..* | Extension(unsignedInt) | Element idSubscription.channel.extension:heartbeatPeriod Optional Extensions Element Alternate namesextensions, user content DefinitionInterval in seconds to send "heartbeat' notifications 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-heartbeatPeriod Constraints
|
timeout | I | 0..* | Extension(unsignedInt) | Element idSubscription.channel.extension:timeout Optional Extensions Element Alternate namesextensions, user content DefinitionTimeout in seconds to attempt notification delivery. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubmissionTimeout Constraints
|
maxCount | I | 0..* | Extension(positiveInt) | Element idSubscription.channel.extension:maxCount Optional Extensions Element Alternate namesextensions, user content DefinitionMaximum number of triggering resources included in notification bundles. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionmaxCount Constraints
|
parameter | I | 0..* | Extension(string) | Element idSubscription.channel.extension:parameter Optional Extensions Element Alternate namesextensions, user content DefinitionThis extension holds the client certificate used for authentication when sending REST-hook notifications. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionParameterExtension Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSubscription.channel.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.channel.type rest-hook | websocket | email | sms | message DefinitionThe type of channel to send notifications on. The type of method used to execute a subscription.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.channel.type.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references) | |
extension | I | 0..* | Extension | Element idSubscription.channel.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Constraints
|
customChannelType | S I | 0..* | Extension(Coding) | Element idSubscription.channel.type.extension:customChannelType Optional Extensions Element Alternate namesextensions, user content DefinitionAdditional channel types not defined before FHIR R5 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. https://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubcriptioncustomChannelType Constraints
|
value | 0..1 | System.String | There are no (further) constraints on this element Element idSubscription.channel.type.value Primitive value for code DefinitionPrimitive value for code System.String | |
endpoint | Σ | 0..1 | url | There are no (further) constraints on this element Element idSubscription.channel.endpoint Where the channel points to DefinitionThe url that describes the actual end-point to send messages to. For rest-hook, and websocket, the end-point must be an http: or https: URL; for email, a mailto: url, for sms, a tel: url, and for message the endpoint can be in any form of url the server understands (usually, http: or mllp:). The URI is allowed to be relative; in which case, it is relative to the server end-point (since there may be more than one, clients should avoid using relative URIs).
|
payload | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.channel.payload MIME type to send, or omit for no payload DefinitionThe 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. Sending the payload has obvious security implications. The server is responsible for ensuring that the content is appropriately secured. The mime type of an attachment. Any valid mime type is allowed.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.channel.payload.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references) | |
extension | I | 1..* | Extension | Element idSubscription.channel.payload.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Constraints
|
content | S I | 1..1 | Extension(code) | Element idSubscription.channel.payload.extension:content Optional Extensions Element Alternate namesextensions, user content DefinitionHow much of the resource content to deliver in the notification payload. The choices are an empty payload, only the resource id, or the full resource content. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-Subscriptioncontent Constraints
|
value | 0..1 | System.String | There are no (further) constraints on this element Element idSubscription.channel.payload.value Primitive value for code DefinitionPrimitive value for code System.String | |
header | Σ | 0..* | string | Element idSubscription.channel.header Usage depends on the channel type DefinitionUse to specify additional information that will be included inside the notification payload when the notification is sent. Each entry consists of a key-value pair. This should support sending client certificates and client keys with validation to determine if it is the certificate itself or just the name. This can convey additional information to the recipient and/or meet security requirements; for example, support of multiple headers in the outgoing notifications for rest-hook type subscriptions.
|
Snapshot View
R4BackportedR5Subscription (Subscription) | I | Subscription | There are no (further) constraints on this element Element idSubscription Server push subscription criteria Alternate namesWebHook, Hook, Routing Rule DefinitionThe subscription resource is used to define a push-based subscription from a server to another system. Once a subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined "channel" so that another system can take an appropriate action.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idSubscription.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idSubscription.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idSubscription.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idSubscription.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idSubscription.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSubscription.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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.
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSubscription.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.status requested | active | error | off DefinitionThe status of the subscription, which marks the server state for managing the subscription. A client can only submit subscription resources in the requested or off state. Only the server can move a subscription from requested to active, and then to error. Either the server or the client can turn a subscription off. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. The status of a subscription.
|
contact | Σ | 0..* | ContactPoint | There are no (further) constraints on this element Element idSubscription.contact Contact details for source (e.g. troubleshooting) DefinitionContact details for a human to contact about the subscription. The primary use of this for system administrator troubleshooting.
|
end | Σ | 0..1 | instant | There are no (further) constraints on this element Element idSubscription.end When to automatically delete the subscription DefinitionThe time for the server to turn the subscription off. The server is permitted to deviate from this time but should observe it.
|
reason | Σ | 1..1 | string | There are no (further) constraints on this element Element idSubscription.reason Description of why this subscription was created DefinitionA description of why this subscription is defined.
|
criteria | S Σ | 1..1 | string | There are no (further) constraints on this element Element idSubscription.criteria Rule for server push DefinitionThe rules that the server should use to determine when to generate notifications for this subscription. The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading "/".
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.criteria.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references) | |
extension | I | 0..* | Extension | Element idSubscription.criteria.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Constraints
|
filterCriteria | S I | 0..* | Extension(string) | Element idSubscription.criteria.extension:filterCriteria Optional Extensions Element Alternate namesextensions, user content DefinitionCriteria for topic-based filtering (filter-by) 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionfilterCriteria Constraints
|
value | 0..1 | System.String | There are no (further) constraints on this element Element idSubscription.criteria.value Primitive value for string DefinitionThe actual value System.String Maximum string length1048576 | |
error | Σ | 0..1 | string | There are no (further) constraints on this element Element idSubscription.error Latest error note DefinitionA record of the last error that occurred when the server processed a notification.
|
channel | Σ | 1..1 | BackboneElement | There are no (further) constraints on this element Element idSubscription.channel The channel on which to report matches to the criteria DefinitionDetails where to send notifications when resources are received that meet the criteria.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.channel.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | Element idSubscription.channel.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Constraints
|
NotificationRetryPeriod | I | 0..* | Extension(Complex) | Element idSubscription.channel.extension:NotificationRetryPeriod Optional Extensions Element Alternate namesextensions, user content DefinitionInterval in hours to retry sending notification. 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. Extension(Complex) Extension URLhttp://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionNotificationRetryPeriod Constraints
|
heartbeatPeriod | I | 0..* | Extension(unsignedInt) | Element idSubscription.channel.extension:heartbeatPeriod Optional Extensions Element Alternate namesextensions, user content DefinitionInterval in seconds to send "heartbeat' notifications 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-heartbeatPeriod Constraints
|
timeout | I | 0..* | Extension(unsignedInt) | Element idSubscription.channel.extension:timeout Optional Extensions Element Alternate namesextensions, user content DefinitionTimeout in seconds to attempt notification delivery. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubmissionTimeout Constraints
|
maxCount | I | 0..* | Extension(positiveInt) | Element idSubscription.channel.extension:maxCount Optional Extensions Element Alternate namesextensions, user content DefinitionMaximum number of triggering resources included in notification bundles. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionmaxCount Constraints
|
parameter | I | 0..* | Extension(string) | Element idSubscription.channel.extension:parameter Optional Extensions Element Alternate namesextensions, user content DefinitionThis extension holds the client certificate used for authentication when sending REST-hook notifications. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionParameterExtension Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSubscription.channel.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.channel.type rest-hook | websocket | email | sms | message DefinitionThe type of channel to send notifications on. The type of method used to execute a subscription.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.channel.type.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references) | |
extension | I | 0..* | Extension | Element idSubscription.channel.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Constraints
|
customChannelType | S I | 0..* | Extension(Coding) | Element idSubscription.channel.type.extension:customChannelType Optional Extensions Element Alternate namesextensions, user content DefinitionAdditional channel types not defined before FHIR R5 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. https://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubcriptioncustomChannelType Constraints
|
value | 0..1 | System.String | There are no (further) constraints on this element Element idSubscription.channel.type.value Primitive value for code DefinitionPrimitive value for code System.String | |
endpoint | Σ | 0..1 | url | There are no (further) constraints on this element Element idSubscription.channel.endpoint Where the channel points to DefinitionThe url that describes the actual end-point to send messages to. For rest-hook, and websocket, the end-point must be an http: or https: URL; for email, a mailto: url, for sms, a tel: url, and for message the endpoint can be in any form of url the server understands (usually, http: or mllp:). The URI is allowed to be relative; in which case, it is relative to the server end-point (since there may be more than one, clients should avoid using relative URIs).
|
payload | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idSubscription.channel.payload MIME type to send, or omit for no payload DefinitionThe 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. Sending the payload has obvious security implications. The server is responsible for ensuring that the content is appropriately secured. The mime type of an attachment. Any valid mime type is allowed.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSubscription.channel.payload.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references) | |
extension | I | 1..* | Extension | Element idSubscription.channel.payload.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Constraints
|
content | S I | 1..1 | Extension(code) | Element idSubscription.channel.payload.extension:content Optional Extensions Element Alternate namesextensions, user content DefinitionHow much of the resource content to deliver in the notification payload. The choices are an empty payload, only the resource id, or the full resource content. 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. http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-Subscriptioncontent Constraints
|
value | 0..1 | System.String | There are no (further) constraints on this element Element idSubscription.channel.payload.value Primitive value for code DefinitionPrimitive value for code System.String | |
header | Σ | 0..* | string | Element idSubscription.channel.header Usage depends on the channel type DefinitionUse to specify additional information that will be included inside the notification payload when the notification is sent. Each entry consists of a key-value pair. This should support sending client certificates and client keys with validation to determine if it is the certificate itself or just the name. This can convey additional information to the recipient and/or meet security requirements; for example, support of multiple headers in the outgoing notifications for rest-hook type subscriptions.
|
Table View
Subscription | .. | |
Subscription.criteria | .. | |
Subscription.criteria.extension | Extension | .. |
Subscription.channel | .. | |
Subscription.channel.extension | Extension | .. |
Subscription.channel.extension | Extension | .. |
Subscription.channel.extension | Extension | .. |
Subscription.channel.extension | Extension | .. |
Subscription.channel.extension | Extension | .. |
Subscription.channel.type | .. | |
Subscription.channel.type.extension | Extension | .. |
Subscription.channel.payload | 1.. | |
Subscription.channel.payload.extension | 1.. | |
Subscription.channel.payload.extension | Extension | .. |
Subscription.channel.header | .. |
JSON View
{ "resourceType": "StructureDefinition", "url": "http://ontariohealth.ca/fhir/StructureDefinition/ca-on-oh-subscription", "name": "R4BackportedR5Subscription", "status": "draft", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Subscription", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Subscription", "derivation": "constraint", "differential": { "element": [ { "id": "Subscription.criteria", "path": "Subscription.criteria", "mustSupport": true }, { "id": "Subscription.criteria.extension:filterCriteria", "path": "Subscription.criteria.extension", "sliceName": "filterCriteria", "type": [ { "code": "Extension", "profile": [ "http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionfilterCriteria" ] } ], "mustSupport": true, "isModifier": false }, { "id": "Subscription.channel.extension:NotificationRetryPeriod", "path": "Subscription.channel.extension", "sliceName": "NotificationRetryPeriod", "type": [ { "code": "Extension", "profile": [ "http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionNotificationRetryPeriod" ] } ], "isModifier": false }, { "id": "Subscription.channel.extension:heartbeatPeriod", "path": "Subscription.channel.extension", "sliceName": "heartbeatPeriod", "type": [ { "code": "Extension", "profile": [ "http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-heartbeatPeriod" ] } ], "isModifier": false }, { "id": "Subscription.channel.extension:timeout", "path": "Subscription.channel.extension", "sliceName": "timeout", "type": [ { "code": "Extension", "profile": [ "http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubmissionTimeout" ] } ], "isModifier": false }, { "id": "Subscription.channel.extension:maxCount", "path": "Subscription.channel.extension", "sliceName": "maxCount", "type": [ { "code": "Extension", "profile": [ "http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionmaxCount" ] } ], "isModifier": false }, { "id": "Subscription.channel.extension:parameter", "path": "Subscription.channel.extension", "sliceName": "parameter", "type": [ { "code": "Extension", "profile": [ "http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubscriptionParameterExtension" ] } ], "isModifier": false }, { "id": "Subscription.channel.type.extension:customChannelType", "path": "Subscription.channel.type.extension", "sliceName": "customChannelType", "definition": "Additional channel types not defined before FHIR R5", "type": [ { "code": "Extension", "profile": [ "https://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-SubcriptioncustomChannelType" ] } ], "mustSupport": true, "isModifier": false }, { "id": "Subscription.channel.payload", "path": "Subscription.channel.payload", "min": 1 }, { "id": "Subscription.channel.payload.extension", "path": "Subscription.channel.payload.extension", "min": 1 }, { "id": "Subscription.channel.payload.extension:content", "path": "Subscription.channel.payload.extension", "sliceName": "content", "type": [ { "code": "Extension", "profile": [ "http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ext-Subscriptioncontent" ] } ], "mustSupport": true }, { "id": "Subscription.channel.header", "path": "Subscription.channel.header", "definition": "Use to specify additional information that will be included inside the notification payload when the notification is sent. Each entry consists of a key-value pair. This should support sending client certificates and client keys with validation to determine if it is the certificate itself or just the name.", "comment": "This can convey additional information to the recipient and/or meet security requirements; for example, support of multiple headers in the outgoing notifications for rest-hook type subscriptions." } ] } }
Usage Notes
.status
- The status of the subscription - requesters should set this value to "requested" when creating a subscrition request
.criteria
- Used to capture the canonical URL of the SubscriptionTopic
.criteria.extension:filterCriteria
- Used to apply filter criteria, similar to those used in search strings
.channel.extension:heartbeatPeriod
- Interval in seconds to send 'heartbeat' notification
.channel.extension:timeout
- Timeout in seconds to attempt notification delivery
.channel.extension:maxCount
- Maximum number of triggering resources included in notification bundles
.channel.type
- allowed values: rest-hook | websocket
- for rest-hook, must supply bearer certificate for Mutual TLS or authorization header
- user may use polling of notifications as a recovery mechanism via web socket channel
.channel.endpoint
- URL endpoint used to deliver subscription notifications, notably URL for rest-hook and websocket.
.channel.type.extension:customeChannelType
- not used in this implementation
.channel.payload
- MIME type to be used to transmit the payload
.channel.payload.extension:content
- used to convey the type of payload requested: empty (no resource content is sent in notifications), id-only (only resource ids are sent in notifications), or full-resource (entire resource is sent in notification)
.channel.header
- used to specify additional information that will be included inside the notifaction payload when the notification is sent. Each entry consists of a key-value pair. This should support sending client certificates and client keys with validation to determine if it is the certificate itself or just the name.