Stream: implementers
Topic: Subscription channel.type
Hannah Riggs (Feb 04 2022 at 22:00):
When Subscription.channel.type == message (https://www.hl7.org/fhir/valueset-subscription-channel-type.html) is that type intended to be the messaging using FHIR resources described in the spec (https://www.hl7.org/fhir/messaging.html)?
Or can it be used for any other type of messaging/events that fit the description of: "The channel is executed by sending a message (e.g. a Bundle with a MessageHeader resource etc.) to the application identified in the URI."? For example, triggering some internal event, but not sending a Bundle with a MessageHeader to do so?
Gino Canessa (Feb 04 2022 at 22:28):
The intention is FHIR Messaging. In R4B (via extension) and R5 the channels are extensible, so you can define your own if none of the pre-defined ones work.
Hannah Riggs (Feb 07 2022 at 14:28):
Thanks for the info; that clarifies it!
Hannah Riggs (Feb 07 2022 at 14:53):
I'm also not clear on the correct use of rest-hook ("The channel is executed by making a post to the URI. If a payload is included, the URL is interpreted as the service base, and an update (PUT) is made."). Does this imply making an HTTP request somewhere?
Gino Canessa (Feb 07 2022 at 16:31):
Yes, a rest-hook subscription is used for a server to send notifications via an HTTP request to the endpoint specified in the subscription, so the FHIR server makes an HTTP request when the subscription is triggered.
I want to note that there have been a lot of changes to subscriptions for R5 (and R4B), so there is a lot more documentation available on those branches (e.g., Subscriptions Framework R5 and R4B Backport IG). I also walked through topic-based subscriptions, the specs, a reference implementation, etc. for the last connectathon and posted the videos on YouTube if that is helpful.
Hannah Riggs (Feb 07 2022 at 16:55):
Very helpful - thank you so much!
Last updated: Apr 12 2022 at 19:14 UTC
