Stream: subscriptions
Topic: RestHook signals
Jenni Syed (May 05 2019 at 15:45):
A lot of people have been surprised by this: http://hl7.org/fhir/subscription.html#2.46.7.1
Jenni Syed (May 05 2019 at 15:45):
"This requests that a server forward a copy of any matching resource in JSON format to the nominated server as an Update operation using the nominated URL as the service base. "
Jenni Syed (May 05 2019 at 15:46):
2 comments: we've told subscribers to use different roots to differentiate between different subscriptions. If each root is a FHIR server, this is more complicated
Jenni Syed (May 05 2019 at 15:47):
If this is indeed the assumption, it does feel like something needs to come with the alert to say why they received it
Jenni Syed (May 05 2019 at 15:48):
In addition, what if the subscriber subscribed to something with multiple resources? eg: revinclude? include? Compartments?
Paul Church (May 05 2019 at 15:48):
Related point: if the client wants the resource content but is not a fhir server, they would be confused by the /type/ID being appended to their specified endpoint
Jenni Syed (May 05 2019 at 15:48):
Does the fact they can subscribe to criteria that results in many changed resources mean the server needs to now understand transaction and batch/ordering semantics? The changes are likely to have dependencies on each other.
Grahame Grieve (May 05 2019 at 16:01):
transactions will be lost in subscriptions
Grahame Grieve (May 05 2019 at 16:02):
so any system subscribing to an event stream has to deal with losing transaction semantics
Grahame Grieve (May 05 2019 at 16:03):
rest-hook is intended for system - system connections where that behavior is intended. No one had brought forward the idea of just posting to a fixed address
Grahame Grieve (May 05 2019 at 16:03):
at least, I don't remember it
Last updated: Apr 12 2022 at 19:14 UTC
