Stream: subscriptions
Topic: Subscriptions support in the CapabilityStatement
John Grimes (Aug 13 2020 at 02:06):
How can I determine whether a server supports subscriptions based on looking at its CapabilityStatement?
Does the presence of the Subscription resource in CapabilityStatement.rest.resource.type imply that the server actually supports the behaviour of pushing out a notification when the criteria is matched? Or just that it can store the resource itself, for example?
How would I be able to tell which channels are supported by the server?
Josh Mandel (Aug 13 2020 at 13:18):
Subscriptions are active resources; a server can only accept a subscription if it will execute the specified channel for any resources subsequently received.
From http://build.fhir.org/subscription get that your first question in the affirmative. There is no defined behavior where a server just stores subscription records without acting on them.
Josh Mandel (Aug 13 2020 at 13:21):
regarding channel types, I don't think there is an upfront automated discovery process, but a server will reject a subscription that requests a channel type it does not support. Server documentation would typically describe support a channel types for developers to interpret. We have had some discussion about providing more discovery capabilities here, but value proposition is not totally clear to me until we have more experience with the overall interaction pattern.
Grahame Grieve (Aug 13 2020 at 13:39):
a server will reject a subscription that requests a channel type it does not support
if they're active
Last updated: Apr 12 2022 at 19:14 UTC
