Stream: fhircast-github
Topic: docs / PR #63 better describe non-oauth scenarios
Github Notifications (FHIRcast) (Feb 05 2019 at 16:41):
isaacvetter opened PR #63
from rewrite-launch-scenarios to master
Fixes #62
heavily related to #59
Github Notifications (FHIRcast) (Feb 05 2019 at 16:41):
isaacvetter requested lbergnehr, daliboz, and NiklasSvenzen for a review on PR #63.
Github Notifications (FHIRcast) (Feb 05 2019 at 16:41):
isaacvetter requested lbergnehr, daliboz, and NiklasSvenzen for a review on PR #63.
Github Notifications (FHIRcast) (Feb 05 2019 at 16:41):
isaacvetter requested lbergnehr, daliboz, and NiklasSvenzen for a review on PR #63.
Github Notifications (FHIRcast) (Feb 08 2019 at 17:58):
NiklasSvenzen created PR Review Comment
beunique -> be unique
Github Notifications (FHIRcast) (Feb 08 2019 at 17:58):
NiklasSvenzen submitted PR Review
Github Notifications (FHIRcast) (Feb 08 2019 at 18:31):
NiklasSvenzen submitted PR Review
Github Notifications (FHIRcast) (Feb 08 2019 at 18:33):
NiklasSvenzen submitted PR Review
Github Notifications (FHIRcast) (Feb 08 2019 at 18:33):
NiklasSvenzen created PR Review Comment
Updated text in #70
Github Notifications (FHIRcast) (Feb 11 2019 at 04:38):
isaacvetter updated PR #63
from rewrite-launch-scenarios to master
Fixes #62
heavily related to #59
Github Notifications (FHIRcast) (Feb 14 2019 at 14:55):
daliboz created PR Review Comment
In SMART, a regular launch only requires the "launch" scope to get context returned. A standalone launch also requires special launch/patient (or encounter) scopes so that the auth server knows those need to be established. For FHIRCast, is the presence of the fhircast scope (in both scenarios) what the auth server would trigger off of?
Github Notifications (FHIRcast) (Feb 14 2019 at 14:55):
daliboz submitted PR Review
Github Notifications (FHIRcast) (Feb 14 2019 at 14:55):
daliboz submitted PR Review
Last updated: Apr 12 2022 at 19:14 UTC
