Stream: workflow
Topic: context pattern
Michelle (Moseman) Miller (Jan 26 2018 at 19:28):
Patient Care was questioning why the workflow context pattern supports a reference to Encounter | EpisodeOfCare when the EpisodeOfCare resource boundaries says
The primary difference between the EpisodeOfCare and the Encounter is that the Encounter records the details of an activity directly relating to the patient, while the EpisodeOfCare is the container that can link a series of Encounters together for problems/issues
@Brian Postlethwaite Was there discussion/agreement from Patient Admin that EpisodeOfCare can be used to record details of an activity (implying the boundaries need to be updated)?
Patient Care actually liked the EpisodeOfCare boundaries as currently written, so we felt like it was more a question for Workflow.
Brian Postlethwaite (Jan 26 2018 at 23:28):
I don't recall any discussions, but doesn't feel right to remove that simple distinction.
Lloyd McKenzie (Jan 26 2018 at 23:43):
Not really following why this is a question for workflow?
Lloyd McKenzie (Jan 26 2018 at 23:45):
@Michelle (Moseman) Miller, can you explain the workflow issue? We want to support linking to both because you might want to tie something to a pregnancy or disease episode in addition to or instead of a specific encounter.
Brian Postlethwaite (Jan 26 2018 at 23:59):
I don't have an issue relating tasks to an EoC. If was the outcome of a Task, then would expect something like review this content to see if they meet the basics and worth getting them in for an assessment, so start he EoC, the Encounter will happen later.
Is this the kind of thing we're talking about?
Michelle (Moseman) Miller (Jan 27 2018 at 03:40):
For more context, Patient Care was discussing adding a reference to Encounter from AllergyIntolerance (which we approved). That led into a discussion of whether we should also support a reference to the EpisodeOfCare from AllergyIntolerance (which we didn't approve). Eventually, we started to question why other resources, such as Observation, support a reference to EpisodeOfCare. The way we interpreted the boundaries of EpisodeOfCare was that the Observation (or any other activity relating directly to the patient) should be referencing the Encounter - not the EpisodeOfCare - because the EpisodeOfCare (per the boundaries) is just a container that links a series of encounters together. In sum, the boundaries just felt inconsistent with the workflow pattern (which supports activity data to reference either the Encounter or the EpisodeOfCare)
Lloyd McKenzie (Jan 27 2018 at 04:15):
There won't always be an encounter to link to - e.g. patient-reported observations. And some encounters are tied to multiple episodes. It's relevant to identify which episode something is tied to as well as the encounter.
Lloyd McKenzie (Jan 27 2018 at 04:15):
I agree that AllergyIntolerance shouldn't tie to episode
Last updated: Apr 12 2022 at 19:14 UTC
