Stream: implementers
Topic: Subscribing to changes
Richard Kavanagh (Apr 14 2016 at 15:50):
Was any work undertaken on subscribing to changes in FHIR?
Brian Postlethwaite (Apr 15 2016 at 05:14):
This is the resource that has been tried out in the past covering this functionality.
http://hl7.org/fhir/subscription.html
David Hay (Apr 15 2016 at 18:26):
There is also the possible of simply 'polling' for changes since a particular date/time (a la RSS)...
Brian Postlethwaite (Apr 16 2016 at 01:07):
Which is the pull version of the subscription resource
David Hay (Apr 16 2016 at 23:09):
I was thinking of history: http://hl7.org/fhir/http.html#history
Richard Kavanagh (Apr 17 2016 at 08:30):
I'm not sure History will not work for us:
Richard Kavanagh (Apr 17 2016 at 08:33):
1) A lot of systems will not support History, especially if the FHIR interface is a facade over a legacy system
2) For larger systems it will not be efficient. Say you are interested in a cohort of 750,000 patients in a system that caters for 40,000,000 patients. Find the updates for the patients of interest will be challenging.
Grahame Grieve (Apr 17 2016 at 09:02):
well, if history is a facade. if the underlying features to support it are not enabled in the legacy framework, why would any other method work?
Kevin Mayfield (Apr 17 2016 at 09:02):
Get the facade to query it's own or the integration engines message history? (Unless you can access the audit trail of the PAS/EPR system). You
Grahame Grieve (Apr 17 2016 at 09:02):
efficiency is a different question. for such a large system, there's enough economy of scale to do real work, and it's not obvious which interface is going to lead to the best bang for your buck
Kevin Mayfield (Apr 17 2016 at 09:02):
i.e. For Patient resource you will have a history of HL7v2 A28/31/40 messages.
Last updated: Apr 12 2022 at 19:14 UTC
