Stream: fhircast-github
Topic: docs / Issue #23 open-imaging-study event should optional...
Github Notifications (FHIRcast) (Apr 19 2018 at 17:40):
isaacvetter opened Issue #23
In offline conversation with @NiklasSvenzen , @wmaethner and @lbergnehr, we talked about adding an optional _upcomingStudies_ context to the open-imaging-study event. The _upcomingStudies_ would define a FHIR List of ImagingStudy resources.
The intent is to support existing, ad hoc productions integrations which use a feature like this to allow the subscriber to cache or pre-load a list of studies that are next in line on the user's worklist.
I considered Bundle, but these resources should be ordered. The required pieces of data on the List should be the _status=current_, and then the array of entry.item. I'm not sure if the ImagingStudy resources referenced in the List should be contained, limited by the _elements parameter or simply references (or perhaps not specified in FHIRcast).
Github Notifications (FHIRcast) (Apr 19 2018 at 18:37):
ElliotSilver commented on Issue #23
I'm not sure that this is the correct place to trigger pre-fetching. I'm not sure the sender should be dictating ordering of studies.
Github Notifications (FHIRcast) (Apr 19 2018 at 19:23):
isaacvetter commented on Issue #23
Hey @ElliotSilver !
We were thinking more of "pre-loading" than "pre-fetching". I think that pre-fetching means the loading of images from long-term storage and often happens in batch even overnight. "Pre-loading" is simply the identification of upcoming studies on the worklist in order.
Does that change your feedback?
Isaac
Last updated: Apr 12 2022 at 19:14 UTC
