Stream: subscriptions
Topic: Chaining Subscription
ArunSrinivasan (Apr 30 2018 at 20:43):
We are working on a feasibility of a use case using subscriptions. The goal is to send a notification when a patient is discharged with an observation having a certain result from a value set. We, however, found that most of the current FHIR implementation servers have not yet fully implemented the complex subscription criteria where the criteria spans across multiple FHIR resources types e.g. Pt, Observation and Encounter.
To get around this limitation, we tried chaining of subscriptions see below:
We divided the subscriptions into two and chained them. When the first subscription fires (Observation), we used a CDS service to dynamically register a new subscription (pt context+encounter). This chaining actually worked. Any comments if this is a proper use of such transactions.
@Rishi Tarar
Rishi Tarar (Apr 30 2018 at 20:49):
@Grahame Grieve @Isaac Vetter @Christiaan Knaap any insights would be helpful... Our need is purely non UI based CDS triggering to a remote service.. for further adjudication using CQL.
Grahame Grieve (Apr 30 2018 at 20:53):
well, it would be better if everyone supported everything, but that's not the world we live in... so I think it's a proper use...
Christiaan Knaap (May 03 2018 at 06:50):
For lack of better, yes. But I have been looking for a use case that justifies implementing chained subscriptions for Vonk (if at all possible in a performing way), so thanks for this one.
Last updated: Apr 12 2022 at 19:14 UTC
