FHIR Chat · Faxing · subscriptions

Stream: subscriptions

Topic: Faxing

Grahame Grieve (Jun 02 2021 at 07:03):

I'm working on a project that is using subscriptions here in Australia. Business analysis suggests that we really need to support faxing - e.g. a faxing channel. has this come up before ?

John Moehrke (Jun 02 2021 at 11:40):

is this April 1st?

John Moehrke (Jun 02 2021 at 11:40):

Avian Carrier too?

David Pyke (Jun 02 2021 at 13:15):

I think a FHIR to fax gateway is the future. We neeeeeeed a fax Resource! I'll put in the Resource proposal

Josh Mandel (Jun 02 2021 at 14:14):

Since we already support email, perhaps you could leverage an email o fax gateway :-) otherwise this feels like just the thing that extension channels are for. As far as I know it has never come up.

Gino Canessa (Jun 02 2021 at 14:34):

I haven't heard about it (beyond jokes... which, to be clear, there have been). I'd say that either a) defining a custom channel type, or b) using a standard channel with a relay server (e.g., Josh's suggestion on email, a REST server that does the conversion, etc.) should be fairly straightforward.

At first glance, I would say that the biggest difference is in how repeatable/consistent you want it to be. Defining a channel type means establishing a standard representation of the data (even if it's something like build a PDF according to these rules), while doing a relay server means you can do whatever you want after receiving the notification (e.g., completely different representations/processes for each connection).

Lloyd McKenzie (Jun 02 2021 at 17:36):

The biggest issue would be how to convey the SubscriptionStatus in a way that would be useful. I guess in this case, it would have to be purely human-readable?