Stream: subscriptions
Topic: FHIRCast not modeled as a subscription
Jeremy Richardson (Mar 13 2018 at 15:44):
@Grahame Grieve wrote on the January Connectathon track topic
at the connectathon, we discussed a simpler approach, where the server just has a pub/sub kind of arrangement where a client can either register a listener end-point or inform the server that the user focus has changed to a different url. And the listeners get informed about the change of url. (probably a triple: user id, client id, focus id). THis is much simpler, and doesn't need any resource.
I had the same thoughts during/after connectathon, and it seemed to me that reaching a judgment/consensus on the thought will come through finding that the current model makes some of the core use cases complex.
It also seemed like there was a lot of concern about not being able to take advantage of FHIR as an organization if it started to push outside FHIR. @Isaac Vetter brought that up.
Last updated: Apr 12 2022 at 19:14 UTC
