Stream: smart
Topic: CCOW
Grahame Grieve (Aug 29 2016 at 13:59):
Welcome @Jens Villadsen , here you go...
Jens Villadsen (Aug 29 2016 at 14:07):
@Grahame Grieve thx
Pascal Pfiffner (Aug 29 2016 at 16:56):
While SMART is definitely covering some cases of context management, there are still usecases that are not addressed. As Josh has shown, some thoughts on inter-app communication are outlined here: https://github.com/smart-on-fhir/smart-on-fhir.github.io/wiki/thoughts-on-inter-app-communication
This (and CCOW) don't address other use-cases however. One that often comes up with mobile developers for example is that currently, there is no standard way to discover a physician's patient list or even the last-looked-at patient. If I log in on a workstation and look at a patient, and within a minute open an app on my phone I'm very likely to want to check the same patient. Or at least have a way to see a List of the patients currently on my ward. This space is still very much unexplored.
Jens Villadsen (Aug 29 2016 at 21:27):
I would argue that this is actually discussed in the original CCOW spec. It resembles the case where your applications are hosted on multiple different Citrix application servers.
Jens Villadsen (Aug 29 2016 at 21:27):
Basically, it is the same case
Jens Villadsen (Aug 29 2016 at 21:28):
One would like to share the context between machines/instances
Jens Villadsen (Aug 29 2016 at 21:29):
@Josh Mandel
Jens Villadsen (Aug 29 2016 at 22:09):
I won't say that it takes up a lot of space in the spec but the case is mentioned
Jens Villadsen (Aug 29 2016 at 22:10):
And actually possible to conduct using eg. the HTTP CCOW Binding
Jens Villadsen (Aug 29 2016 at 22:12):
I do like some of the interapp thoughts, but there are some details missing
Jens Villadsen (Aug 29 2016 at 22:13):
How are you going to notify other applications on other machines? Web sockets?
Jens Villadsen (Aug 29 2016 at 22:13):
Server Side Events?
Josh Mandel (Aug 30 2016 at 02:30):
Indeed! Lots of details to think through. (Communicating across machines hasn't been one of the use cases we've tried to address explicitly.) Our basic assumption has been that we can go pretty far with postMessage, for the kinds of launch/return scenarios we've discussed.
Brian Postlethwaite (Aug 30 2016 at 04:07):
This should also have some relationship to the CDS hooks functionality too right?
Grahame Grieve (Aug 30 2016 at 04:07):
CDS-hooks removed a lot of my desire to beef up smart on fhir for this stuff
Jens Villadsen (Aug 30 2016 at 07:30):
I know pretty much nothing about CDS hooks - just the intro part found on cds-hooks-org
Jens Villadsen (Aug 30 2016 at 07:31):
But it seems pretty focused on CDS ... go figures ...
Jens Villadsen (Aug 30 2016 at 07:32):
while this may allign with parts of CCOW, it is focused on CDS
Jens Villadsen (Aug 30 2016 at 07:33):
If we/me/you/someone was to think of a more modern CCOW approach, sync on multiple devices must be one of the inital use cases
Jens Villadsen (Aug 30 2016 at 07:39):
and then a whole bunch of the thoughts from the original CCOW spec should be taken into consideration regarding maintaining sync state, escape mechanisms and what not ...
Jens Villadsen (Aug 30 2016 at 07:43):
@Jonathan Bunde-Pedersen here you are
Last updated: Apr 12 2022 at 19:14 UTC
