FHIR Chat · docs / Issue #312 May 2018 Ballot Comment 106

Stream: cds hooks/github

Topic: docs / Issue #312 May 2018 Ballot Comment 106

Github Notifications (May 16 2018 at 23:01):

cds-hooks-bot opened Issue #312

## May 2018 Ballot Comment 106

Submitted by @kensaku-kawamoto on behalf of @euvitudo from University of Utah

Chapter: Providing FHIR Resources to a CDS Service
Section: https://cds-hooks.org/specification/1.0/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Existing Wording:

Similarly, each EHR will decide what FHIR resources to authorize and to prefetch, based on the CDS Service description's "prefetch" request and on the provider's assessment of the "minimum necessary." The EHR provider and the CDS Service provider will negotiate the set of FHIR resources to be provided, and how these data will be provided, as part of their service agreement.

Comment:
Recommend specifying that prefetch should only include data allowed within scopes.

## :de: Köln May 2018 Working Group Vote

@jmandel moved the following disposition, seconded by @brynrhodes.

Disposition: Not Persuasive
Disposition Comment:
This comment misunderstands that prefetch data does not use the SMART on FHIR authorization mechanism for access FHIR data. As such, OAuth 2 scopes are not in play here.

:+1: For: 23
:expressionless: Abstain: 3
:-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:01):

cds-hooks-bot labeled Issue #312

Github Notifications (May 16 2018 at 23:01):

cds-hooks-bot edited Issue #312

## May 2018 Ballot Comment 106

Submitted by @kensaku-kawamoto on behalf of @euvitudo from University of Utah

Chapter: Providing FHIR Resources to a CDS Service
Section: https://cds-hooks.org/specification/1.0/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Existing Wording:

Similarly, each EHR will decide what FHIR resources to authorize and to prefetch, based on the CDS Service description's "prefetch" request and on the provider's assessment of the "minimum necessary." The EHR provider and the CDS Service provider will negotiate the set of FHIR resources to be provided, and how these data will be provided, as part of their service agreement.

Comment:
Recommend specifying that prefetch should only include data allowed within scopes.

## :de: Köln May 2018 Working Group Vote

@jmandel moved the following disposition, seconded by @brynrhodes.

Disposition: Not Persuasive
Disposition Comment:
This comment misunderstands that prefetch data does not use the SMART on FHIR authorization mechanism for access FHIR data. As such, OAuth 2 scopes are not in play here.

:+1: For: 23
:expressionless: Abstain: 3
:-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._