Stream: cds hooks/github
Topic: docs / Issue #159 Who is talking to whom in "Obtaining an...
Github Notifications (Jan 29 2018 at 15:40):
jmandel opened Issue #159
I'm having trouble understanding the following text (and everything below it) in "Obtaining an Access Token":
If the EHR chooses to obtain a bearer token for CDS Service use, the authorization MUST be accomplished in accordance with the OAuth 2.0 authorization code grant model, and the authorization request MUST identify the CDS Service by name as the intended user.
Who are the actors in this process? The EHR is a single entity, so I'm not clear on where/how the OAuth code flow is relevant here, and for:
The transaction the EHR uses to request authorization includes the following parameters:
I don't know who the parties to the transaction would be.
Github Notifications (Jan 29 2018 at 15:40):
jmandel labeled Issue #159
Github Notifications (Jan 29 2018 at 15:40):
jmandel milestoned Issue #159
Github Notifications (Jan 29 2018 at 15:43):
kpshek assigned Issue #159
Github Notifications (Jan 30 2018 at 15:32):
kpshek assigned Issue #159
Github Notifications (Jan 30 2018 at 18:16):
jmandel commented on Issue #159
https://github.com/cds-hooks/docs/commit/888d3ad408f7fa5bdcbb48e064a984ca2bf7fb82 is a proposed way to address this.
Github Notifications (Feb 19 2018 at 21:14):
kpshek closed Issue #159
Last updated: Apr 12 2022 at 19:14 UTC
