Stream: implementers
Topic: event cascades
Erich Schulz (May 17 2016 at 08:59):
just curious if there has been much work on laying out event patterns and the internal updates they trigger?
Erich Schulz (May 17 2016 at 09:00):
sort of thing I'm thinking is "referral request" leads to both and "episode of care" and an "appointment"
Erich Schulz (May 17 2016 at 09:01):
having the appointment creates an encounter, with observations, and clinical impression, and care plan
Erich Schulz (May 17 2016 at 09:02):
a bit more interestingly "discharge from care" closes off the already created episode
Erich Schulz (May 17 2016 at 09:02):
i'm sure this has been thought about very much ... i just haven't stumbled upon a synopsis (yet)
Erich Schulz (May 17 2016 at 09:41):
I guess much of this is implied and i see examples of the expected exchanges scattered around
Grahame Grieve (May 17 2016 at 09:59):
we typically do not specify things like this; these internal business rules might be done in implementation guides
Erich Schulz (May 17 2016 at 10:06):
cool - I'm coming into all this from a standing start - just trying to get my head wrapped around 100+ entities
Erich Schulz (May 17 2016 at 10:07):
everything is much more coherent than last time I looked (which was almost 20 years ago!)
Erich Schulz (May 17 2016 at 10:07):
(ontology was my thing back before I wondered off to "get a real job")
Peter Bernhardt (May 17 2016 at 15:28):
Isn't the Task resource motiviated, at least in part, to solve this problem? It's only half a solution, because the focus with Task is on the state transitions of the Task itself. An IG would be useful if it describes the state transitions of a particular resource - like EoC, Appointment, etc. - within a given workflow.
Grahame Grieve (May 17 2016 at 19:40):
yes, task is the instantiation of a point of control in a workflow. it's not the orchestration itself though
Last updated: Apr 12 2022 at 19:14 UTC
