Stream: FHIRcast
Topic: Context Event Service
Preston Lee (Jan 15 2019 at 22:41):
@Bas van den Heuvel @Isaac Vetter I don't have a 30-second summary version of Context Event Service (CES), but do have some good working material. The main reference implementation materials are (1) service https://github.com/preston/context-event-service, and (2) exemplar (optional) client library for Angular and React apps https://github.com/preston/context-event-client . The example apps themselves don't seem online at the moment. The are a few exemplar complex event processing "agent" templates included in the CES server reference, including clock event generation which is super useful for client development and debugging.
Bas van den Heuvel (Jan 15 2019 at 22:42):
thx
Preston Lee (Jan 15 2019 at 22:43):
Here is the poster from MCBK 2018: ARTAKA-CES-Poster-MCBK.pdf
Preston Lee (Jan 15 2019 at 22:44):
And discussion starting at absolute page 81 of the attached. (really sorry for the length.. dissertation) Automated-Injection-of-Curated-Knowledge-Into-Real-Time-Clinical-Systems-CDS-Architecture-for-the-21st-Century.pdf
Preston Lee (Jan 15 2019 at 22:46):
HSPC's reference implementation of the HL7 Marketplace R1 specification is here https://github.com/preston/hsp-marketplace-server , and the intent is to remove the older websockets stuff and replace with either CES or, more ideally, some form reconciled CES/FHIRcast capability.
Preston Lee (Jan 15 2019 at 22:57):
There are concepts adapted from other domains (notably event "timeline" partitioning from the simulation space) that can be ignored if desired. Ultimately, the design intent is to make the common cases trivial for developers to get started with yet allow for extremely advanced cases possible, e.g. knowledge-driven applications and providing CDS as a dynamic, continuous stream of events that may be previously unknown to the client(s), as opposed to forcing clients to manually invoke external support services.
Preston Lee (Jan 15 2019 at 22:57):
But ignoring all that and just using it as glorified CCOW is also fine :)
Isaac Vetter (Jan 16 2019 at 15:18):
Hey Preston,
I'm reading through parts of your dissertation. I'd like to learn from your efforts and research to inform FHIRcast. Our strategy with FHIRcast is implementer-first. We've focused on available, simply understood, and an accessible specification along with the resources to get a developer up and running with minimal time and effort required.
Isaac Vetter (Jan 16 2019 at 15:19):
Overall, (I think) your December, 2018 dissertation is an informative/narrative description of a context event publishing, distribution and brokering system for the purpose of creating an event stream for clinical decision support.
Isaac Vetter (Jan 16 2019 at 16:00):
I see the use of SSE as problematic do to the prevalence of classic IE in healthcare provider IT environments. Our discussion on this happened/is happening in #33.
Isaac Vetter (Jan 16 2019 at 16:08):
I found this diagram helpful to understand CES:
pasted image
Isaac Vetter (Jan 16 2019 at 16:11):
(Note that the Hub/Broker stores and exposes a historical record of events via the "timeline". A client requests context changes/events by creating an alternate timeline via REST.)
Last updated: Apr 12 2022 at 19:14 UTC
