Stream: cds hooks/github
Topic: docs / Issue #317 May 2018 Ballot Comment 111
Github Notifications (May 16 2018 at 23:02):
cds-hooks-bot opened Issue #317
## May 2018 Ballot Comment 111
Submitted by @kensaku-kawamoto on behalf of @euvitudo from University of Utah
Chapter: FHIR Resource Access
Section: https://cds-hooks.org/specification/1.0/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Existing Wording:
Like SMART on FHIR, CDS Hooks requires that clients present a valid access token to the FHIR server with each API call. Thus, a CDS Service must be able to obtain an access token before communicating with the EHR's FHIR resource server.
Comment:
How will the process of registering and using CDS Hooks services compare to what is done with SMART on FHIR apps? Recommend making this explicit and detailed, rather than simply noting it will be "like" what is done with SMART on FHIR.## :de: Köln May 2018 Working Group Vote
@kpshek moved the following disposition, seconded by @brynrhodes.
Disposition: Not Persuasive
Disposition Comment:
The CDS Service OAuth 2 registration process is not defined by the specification.:+1: For: 19
:expressionless: Abstain: 4
:-1: Against: 0:tada: The motion passed! :tada:
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (May 16 2018 at 23:02):
cds-hooks-bot labeled Issue #317
Github Notifications (May 16 2018 at 23:02):
cds-hooks-bot edited Issue #317
## May 2018 Ballot Comment 111
Submitted by @kensaku-kawamoto on behalf of @euvitudo from University of Utah
Chapter: FHIR Resource Access
Section: https://cds-hooks.org/specification/1.0/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Existing Wording:
Like SMART on FHIR, CDS Hooks requires that clients present a valid access token to the FHIR server with each API call. Thus, a CDS Service must be able to obtain an access token before communicating with the EHR's FHIR resource server.
Comment:
How will the process of registering and using CDS Hooks services compare to what is done with SMART on FHIR apps? Recommend making this explicit and detailed, rather than simply noting it will be "like" what is done with SMART on FHIR.## :de: Köln May 2018 Working Group Vote
@kpshek moved the following disposition, seconded by @brynrhodes.
Disposition: Not Persuasive
Disposition Comment:
The CDS Service OAuth 2 registration process is not defined by the specification.:+1: For: 19
:expressionless: Abstain: 4
:-1: Against: 0:tada: The motion passed! :tada:
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (May 16 2018 at 23:02):
cds-hooks-bot milestoned Issue #317
Github Notifications (May 16 2018 at 23:10):
kpshek commented on Issue #317
Closing per the _Not Persuasive_ vote at the :de: Köln May 2018 working group meeting.
Github Notifications (May 16 2018 at 23:10):
kpshek closed Issue #317
Github Notifications (Jun 14 2018 at 13:43):
cds-hooks-bot assigned Issue #317
Last updated: Apr 12 2022 at 19:14 UTC
