FHIR Chat · proposal to add encounter specific events · FHIRcast

Stream: FHIRcast

Topic: proposal to add encounter specific events


view this post on Zulip Isaac Vetter (Feb 23 2021 at 18:38):

Hey Friends - reviewing some github issues, I noticed that a number of implementers had perhaps reached consensus on creating encounter-open and encounter-close. The justification is to simplify the scenario in which a user switches between encounters for the same patient chart, without ever closing that patient's chart.

view this post on Zulip Isaac Vetter (Feb 23 2021 at 18:38):

Overall, add encounter-open/close is straightforward and probably makes sense. The tricky part is that it would likely also make sense to deprecate the encounter element on patient-open/close.

view this post on Zulip Isaac Vetter (Feb 23 2021 at 18:38):

Any thoughts on this potential course of action? I wrote up a PR here.

view this post on Zulip Gino Canessa (Feb 23 2021 at 20:09):

I'm not sure I love how the events line up. Specifically, since encounter-close says:

User closed patient's medical record encounter context. A previously open and in context patient chart & encounter is no longer open nor in context.

it becomes a lot of work to process moving between encounters on the same patient.

view this post on Zulip Bas van den Heuvel (Feb 24 2021 at 08:52):

Good point. We can also make it easy and just say the encounter is closed.

view this post on Zulip Catie Ladd (Feb 24 2021 at 19:27):

I feel like with the wording of Encounter-Open that it implies a Patient-Open at the same time. Also, it only allows for one encounter to be open at a time with one patient.

User opened patient's medical record in the context of a single encounter. Only a single patient and encounter is currently in context.

view this post on Zulip Gino Canessa (Feb 24 2021 at 20:41):

Good point - how does something like a comparison to a prior encounter work?

view this post on Zulip Bas van den Heuvel (Feb 25 2021 at 09:33):

I wonder whether we should provide such detail in the event description. It deviates from the event signaled by the event and does not make it clearer. The specification already states that the sender needs to be make sure the other events (patient) also need to be send.

The Encounter-open indicates an Encounter has been opened and is currently the "selected" encounter. A new Encounter-open means that another Encounter is the new selected resource.
An Encounter-close signals that an Encounter has been closed.

Multiple Encounters can be open at the same time, as long as they all refer to the same Patient. This use case relates to the more generic topic of multi-tab support, which we still need to resolve.

view this post on Zulip Isaac Vetter (Mar 16 2021 at 13:24):

Guys, I simplified the workflow description of encounter-close in response to Gino's feeedback.

view this post on Zulip Isaac Vetter (Mar 16 2021 at 13:24):

Catie, encounter-open does imply an already open patient record (this is in the same way that an dxreport-open implies an already open patient, right?)

view this post on Zulip Isaac Vetter (Mar 16 2021 at 13:25):

Bas, I really worry that an absence of a human-readable description of the event will make understanding an event more difficult for the typical reader ...

view this post on Zulip Catie Ladd (Mar 16 2021 at 20:01):

Isaac, yes I think you're correct. The wording sounded strange to me the other day, but looking at it again, it seems OK.


Last updated: Apr 12 2022 at 19:14 UTC