Stream: fhircast-github
Topic: docs / Issue #4 Outsider question related to FHIRCast.org...
Github Notifications (FHIRcast) (Aug 07 2018 at 20:45):
isaacvetter commented on Issue #4
Hey @jeremysrichardson ,
We finally wrote up, reviewed, approved and merged the content in this page: http://fhircast.org/launch-scenarios/ as part of PR #25.
A session identifier is communicated as one of the SMART launch parameters. And the app can be launched using either SMART's so-called "EHR Launch" or the "Standalone launch".
I _think_ that resolved this issue.
Isaac
Github Notifications (FHIRcast) (Aug 07 2018 at 20:45):
isaacvetter closed Issue #4(assigned to isaacvetter)
When looking at FHIRCast.org, it was unclear to me how a subscribing client knows where a server lives.
From the primary use case, the FHIRCast server is always the launching server, and could pass the location to the FHIRCast server in the launch call. If there are N apps in a hospital, each of them could have their own FHIRCast/FHIR Subscription w UserSession server.
In a stand-alone launch call, it's less clear. If each app has its own UserSession, then they won't talk to each other. Talking to Isaac (Connectahon 1/27), he thinks it's implementation configuration (Seems obvious, right?) However, I think this is a key assumption that should be called out, and leads to the problem that the different apps need to share a common UserSession: a simple solution is a SINGLE pre-defined FHIRCast server to allow stand-alone apps to share context.
I think we should make this explicit for both launch types...
Last updated: Apr 12 2022 at 19:14 UTC
