FHIR Chat · docs / Issue #311 May 2018 Ballot Comment 105 · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #311 May 2018 Ballot Comment 105

---

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

cds-hooks-bot opened Issue #311

## May 2018 Ballot Comment 105

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: A-S :bulb:
In Person Requested? No

Existing Wording:

The second enhancement enables the CDS Service to retrieve FHIR resources for itself, but to do so more efficiently than if it were required to request and obtain its own authorization. If the EHR decides to have the CDS Service fetch its own FHIR resources, the EHR obtains and passes directly to the CDS Service a bearer token issued for the CDS Service's use in executing FHIR API calls against the EHR FHIR server to obtain the required resources. Some EHRs may choose to pass prefetched data, along with a bearer token for the CDS Service to use if additional resources are required. Each EHR may decide which approach, or combination, is preferred, based on performance considerations and assessment of attendant security and safety risks. For more detail, see the FHIR Resource Access section below.

Comment:
Recommend referencing and linking to SMART on FHIR mechanism for data retrieval here.

---

_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 #311

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

cds-hooks-bot edited Issue #311

## May 2018 Ballot Comment 105

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: A-S :bulb:
In Person Requested? No

Existing Wording:

The second enhancement enables the CDS Service to retrieve FHIR resources for itself, but to do so more efficiently than if it were required to request and obtain its own authorization. If the EHR decides to have the CDS Service fetch its own FHIR resources, the EHR obtains and passes directly to the CDS Service a bearer token issued for the CDS Service's use in executing FHIR API calls against the EHR FHIR server to obtain the required resources. Some EHRs may choose to pass prefetched data, along with a bearer token for the CDS Service to use if additional resources are required. Each EHR may decide which approach, or combination, is preferred, based on performance considerations and assessment of attendant security and safety risks. For more detail, see the FHIR Resource Access section below.

Comment:
Recommend referencing and linking to SMART on FHIR mechanism for data retrieval here.

---

_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 milestoned Issue #311

Github Notifications (May 18 2018 at 09:25):

cds-hooks-bot commented on Issue #311

Proposed Disposition: Persuasive with Mod
Proposed Disposition Comment:
We will ensure the SMART on FHIR HL7 specification is linked in all appropriate places

Github Notifications (May 18 2018 at 09:46):

cds-hooks-bot labeled Issue #311

Github Notifications (May 30 2018 at 22:24):

cds-hooks-bot commented on Issue #311

## :telephone_receiver: CDS Working Group Block Vote (5-30-2018)

Meeting notes: http://wiki.hl7.org/index.php?title=File:2018-05-30_CDS_WG_Call_Minutes.docx

Julia Skapik moved the following disposition, seconded by @brynrhodes.

Disposition: Persuasive with Mod
Disposition Comment:
We will ensure the SMART on FHIR HL7 specification is linked in all appropriate places

:+1: For: 12
:expressionless: Abstain: 0
:-1: Against: 0

:tada: The motion passed! :tada:

Github Notifications (Jun 14 2018 at 13:42):

cds-hooks-bot assigned Issue #311

Github Notifications (Aug 02 2018 at 03:53):

isaacvetter commented on Issue #311

Existing references to SMART spec:
* https://cds-hooks.org/specification/1.0/#fhir-resource-access
* https://cds-hooks.org/specification/1.0/#passing-the-access-token-to-the-cds-service

Existing references to OAuth:
* https://cds-hooks.org/specification/1.0/#link

I added an additional deep link to the SMART spec in the Link section to further clarify the appContext parameter.

Github Notifications (Aug 07 2018 at 18:00):

kpshek closed Issue #311

---

Last updated: Apr 12 2022 at 19:14 UTC