Stream: fhircast-github
Topic: fhircast-docs / Issue #355 Add encounter-open,close
Github Notifications (FHIRcast) (Feb 23 2021 at 22:07):
GinoCanessa commented on Issue #355:
I'm worried about how the events line up. Specifically, since
encounter-closesays: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.
Github Notifications (FHIRcast) (Mar 16 2021 at 13:29):
isaacvetter commented on Issue #355:
it becomes a lot of work to process moving between encounters on the same patient.
Thanks, @GinoCanessa ! I changed to:
User closed patient's medical record encounter context. A previously open and in context patient encounter is no longer open nor in context.
to clarify that the patient's chart was necessary to close to satisfy an
encounter-close. Is it a lot of work to move between encounters on the same patient? I'm not sure. Note that moving between encounters on the same patient isn't a typical clinical workflow, but could be typical in an back-office / audit / review / billing workflow. The work involved is generated an open and close event for each encounter navigated to...What do you think?
Github Notifications (FHIRcast) (Mar 16 2021 at 16:09):
GinoCanessa commented on Issue #355:
Thanks @isaacvetter !
I think it was me incorrectly (or maybe just too aggressively) mapping the event - I was thinking of things like opening and closing notes from prior encounters. If that were the case, reviewing an earlier encounter would close and re-open the patient.
Unfortunately, I'm not sure how to make that clearer. E.g., yes the user is _looking_ at a different encounter, but that's not the one in context so don't generate this message.
Github Notifications (FHIRcast) (Mar 25 2021 at 16:30):
isaacvetter commented on Issue #355:
The InM WG voted on this issue on 3/25/2021.
Bas / Isaac: 9-0-0This isn't obviously an issue that needed a formal HL7 WG vote, because this content isn't yet balloted, but it sure doesn't hurt.
Github Notifications (FHIRcast) (Mar 25 2021 at 16:30):
isaacvetter edited a comment on Issue #355:
The InM WG voted on this issue on 3/25/2021.
@bvdh / @isaacvetter : 9-0-0This isn't obviously an issue that needed a formal HL7 WG vote, because this content isn't yet balloted, but it sure doesn't hurt.
Last updated: Apr 12 2022 at 19:14 UTC
