FHIR Chat · Suggestions · clinic-arrivals

Stream: clinic-arrivals

Topic: Suggestions

James Berry (Mar 27 2020 at 05:47):

I've noticed that the templates asked patients to respond with a single word "arrived" or "joined" but elsewhere YES or NO.

To avoid confusion can we drop the quote marks and say ARRIVED and JOINED?
Or can we rephrase to only use YES or NO?
Also when we check the incoming answer, are we giving some latitude for case and spelling (haven't checked the code).
Finally, if the templates are changed by the users, what happens if these keywords are altered? Shouldn't they be a parameter?

Grahame Grieve (Mar 27 2020 at 07:07):

lattitude for case and grammar. I haven't decided about spelling. We do recognised y | n | j | a - single letter responses

Grahame Grieve (Mar 27 2020 at 07:07):

the keywords are hard coded. for now

James Berry (Mar 27 2020 at 21:20):

Ok how about this? Y/es N/o H/ere

Grahame Grieve (Mar 29 2020 at 09:15):

hmm. that would be great for IT folks, but I know what my mother in law would do - give up in confusion

Vadim Peretokin (Mar 29 2020 at 10:28):

i think we should be lenient and accept a variety of terms

Vadim Peretokin (Mar 29 2020 at 10:28):

yes/yeah/yea/yep

etc

Grahame Grieve (Mar 29 2020 at 10:44):

PRs are welcome

James Berry (Mar 29 2020 at 21:56):

my suggestion was shorthand, which combined with Vadim's may be:

Anything starting with Y or y is agreement
Anything starting with N or n is disagreement
Anything starting with H or h is arrival or joining a videoconference (do we care about the distinction?)
Note I was also suggesting not enclosing the words in quote marks in the message templates because no-one is sure whether you need to send your reply in quotes. But I'm note sure how to communicate case-insensitivity

Grahame Grieve (Mar 29 2020 at 21:58):

I'll be collecting data around the unexpected responses to see if there's anything we can learn about patterns

Jiawei (Mar 30 2020 at 03:19):

Do you have any plan to move data storage to the cloud side so far? If so, I can develop an interface for this part. I feel like this app will be more general and data is safer.

Grahame Grieve (Mar 30 2020 at 04:12):

@Brian Postlethwaite I have been thinking that the app would be good as a client server app, with a system service doing the actual communication. Not part of MVP so I don't regret that.

But storing the comms record in the cloud rather than local... I have mixed feelings about that... who accepts responsibility for DR on the store?

Brian Postlethwaite (Mar 30 2020 at 04:45):

And exposure of that content, and ownership of that content, and security ....
so many issues that are avoided.

Brian Postlethwaite (Mar 30 2020 at 04:46):

We've tried to keep all the real data in the PMS, and only put things in the local storage where we HAD to. And is only relevant to the local data, and moving to the web also adds another layer of un-reliability too.

Brian Postlethwaite (Mar 30 2020 at 04:47):

The other good part of this is that the GP takes the responsibility of the cost of the text messages too.
(maybe we should have a configuration on the max messages per day or something)