Stream: fhircast-github
Topic: docs / Issue #35 can a subscribing app create a session?
Github Notifications (FHIRcast) (Jul 16 2018 at 04:14):
isaacvetter opened Issue #35
As part of the standalone launch flow described in PR #25, it seems reasonable to enable the subscribing app to create a session, if it doesn't already exist for the authenticating user.
A context notification message, sent by the subscribing app to the Hub, should cause the driving app to open.
Github Notifications (FHIRcast) (Jul 16 2018 at 13:00):
johns397 commented on Issue #35
It would be useful if there was a mechanism like the CCOW launch mechanism where if a 'driving app' sets the context on a subscribing app it would open that app, 'tuned' to the correct user and patient (and other context subjects as appropriate). This would allow for the use case of an 'app framework' which can control the launching of the EMR as 'just another peer' in the 'shared context', and not as the 'master' of the context. [Not sure of the technical issues around OAuth 2.0 tokens, but the CCOW standard had a concept called 'chain of trust' so that all the peers participating in the shared context trusted each other by some 'out-of-band' pre-arrangement of trust.]
Github Notifications (FHIRcast) (Nov 20 2018 at 21:59):
isaacvetter commented on Issue #35
Hey @johns397 - indeed. PR #36 is intended to provide this capability, although it's implemented slightly differently than how you/CCOW suggest.
Last updated: Apr 12 2022 at 19:14 UTC
