FHIR Chat · Slack as Communication · implementers

Stream: implementers

Topic: Slack as Communication


view this post on Zulip Brendan Keeler (Jun 23 2021 at 19:23):

Fun mental exercise. If Slack or Zulip or Teams are used in a medical setting and we were to represent in FHIR, would it be Communication? Does FHIR actually encapsulate the structures inherent to chat like that?

Channels = Recipient (so a Group orList of providers/patients per channel?)
Threads = PartOf with Communication as parent?

view this post on Zulip John Moehrke (Jun 23 2021 at 19:28):

I think that depends on the extent the policy/system sees the native communication mechanism as persistent enough. Meaning, one could expect that Slack/Zulip/Teams are persistent, and thus one only needs to record a Communication with reference to the thread. Where it is deemed not persistent, or not persistent-enough, or other reason... I could see how the whole text might be desired to be copied. With Medical-Records, retention lifespan is critical. Sometimes it is just 5 years, sometimes it is 75 years -- https://library.ahima.org/PB/RetentionDestruction#.YNOLHxGSmUk

view this post on Zulip David Pyke (Jun 23 2021 at 19:46):

It's an interesting question as DirectTrust now has a draft standard for XMPP chat. We'd need a way to reference that.

view this post on Zulip John Moehrke (Jun 23 2021 at 19:49):

I had originally proposed XMPP as my proposal at the original Direct Project solution meetings... interesting...

view this post on Zulip David Pyke (Jun 23 2021 at 19:49):

Yet again, DirectTrust is on the cutting edge of technology

view this post on Zulip Lloyd McKenzie (Jun 25 2021 at 16:46):

Communication seems most reasonable. Quite a few systems use it for "e-mail over FHIR". From that perspective, Slack/Zulip/Teams are just slightly varied forms of 'email'.

view this post on Zulip John Moehrke (Jun 25 2021 at 17:02):

@Lloyd McKenzie the question is not if a Communication is recorded... it is if the Communication must replicate everything actually communicated or if we trust RESTful APIs to these actual communication platforms so as to record in our Communication simply a reference (REST - read)?

view this post on Zulip Lloyd McKenzie (Jun 25 2021 at 21:08):

Communication was designed to be a record of what was shared, but it's being used in many quarters as a means of sharing. It seems to work for both.


Last updated: Apr 12 2022 at 19:14 UTC