Stream: FHIRcast
Topic: Use of Parameters resource as "context"
Ken Sinn (Apr 16 2019 at 23:01):
We're looking at FHIRCast to maintain Patient context, but we also want to maintain the search parameters like "From-Date" and "To-Date" across the subscribers. Would a Parameters FHIR resource in the "context" array be a good way to capture/maintain this information? Would using Parameters break any established rules in FHIRCast?
Isaac Vetter (Apr 17 2019 at 17:16):
Hey Ken, that's an interesting question.
Isaac Vetter (Apr 17 2019 at 17:16):
FHIRCast to maintain Patient context, but we also want to maintain the search parameters like "From-Date" and "To-Date" across the subscribers.
Could you explain this a bit more? What do these dates represent?
Isaac Vetter (Apr 17 2019 at 17:16):
Overall, using the Parameters resources in the context of a notification would fit perfectly into FHIRcast.
Ken Sinn (Apr 17 2019 at 18:20):
Thanks for the response.
We want to be able to maintain a search range, so that across multiple subscribers, you can maintain the search range of "from January 1st, 2018-Dec 31st, 2018" using FHIRCast, so that each SMART on FHIR app will be updated w/ the appropriate search range and patient context, say, for a Drug Portlet as well as a Labs Portlet.
Isaac Vetter (Apr 17 2019 at 20:02):
Hey Ken, to summarize in different word -- the user's context in your driving application includes not only a patient but also a date range. When context events occur, you need this patient _and_ date range synchronized across all of the subscribing applications. Is that right? That makes sense and the Parameters resource would work well.
Isaac Vetter (Apr 17 2019 at 20:02):
The only caveat I can think of is -- when the patient doesn't change, but the date range does, do you need a custom event? Have you given this any thought, yet?
Ken Sinn (Apr 18 2019 at 17:44):
Does FHIRCast always need to be event-driven? are changes in context allowed happen outside of a defined event? (is there a method to define/extend custom events?)
Isaac Vetter (Apr 23 2019 at 14:24):
Hey Ken, there is a method to define/extend custom events and FHIRcast is currently always event driven.
Isaac Vetter (Apr 23 2019 at 14:25):
The spec talks a bit about custom events in the Event Catalog
The name of the event SHOULD succinctly and clearly describe the activity or event. Event names are unique so event creators SHOULD take care to ensure newly proposed events do not conflict with an existing event name. Event creators SHALL name their event with reverse domain notation (e.g. org.example.patient-transmogrify) if the event is specific to an organization. Reverse domain notation SHALL not be used by a standard event catalog.
Last updated: Apr 12 2022 at 19:14 UTC
