FHIR Chat · docs / Issue #301 May 2018 Ballot Comment 95

Stream: cds hooks/github

Topic: docs / Issue #301 May 2018 Ballot Comment 95

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

cds-hooks-bot opened Issue #301

## May 2018 Ballot Comment 95

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

Chapter: Overview
Section: https://cds-hooks.org/specification/1.0/
Type: A-S :bulb:
In Person Requested? No

Existing Wording:

The CDS Hooks specification describes the RESTful APIs and interactions between EHRs and CDS Services. All data exchanged through the RESTful APIs MUST BE sent and received as JSON structures, and MUST be transmitted over channels secured using Transport Layer Security (TLS).

Proposed Wording:

The CDS Hooks specification describes the APIs and interactions between EHRs and CDS Services. All data exchanged through the APIs MUST BE sent and received as JSON structures, and MUST be transmitted over channels secured using Transport Layer Security (TLS).

Comment:
POST behavior in CDS Hooks is inconsisitent with POST in a RESTful context. The POST In this specification is really an RPC.

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

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

cds-hooks-bot labeled Issue #301

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

cds-hooks-bot edited Issue #301

## May 2018 Ballot Comment 95

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

Chapter: Overview
Section: https://cds-hooks.org/specification/1.0/
Type: A-S :bulb:
In Person Requested? No

Existing Wording:

The CDS Hooks specification describes the RESTful APIs and interactions between EHRs and CDS Services. All data exchanged through the RESTful APIs MUST BE sent and received as JSON structures, and MUST be transmitted over channels secured using Transport Layer Security (TLS).

Proposed Wording:

The CDS Hooks specification describes the APIs and interactions between EHRs and CDS Services. All data exchanged through the APIs MUST BE sent and received as JSON structures, and MUST be transmitted over channels secured using Transport Layer Security (TLS).

Comment:
POST behavior in CDS Hooks is inconsisitent with POST in a RESTful context. The POST In this specification is really an RPC.

_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._

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

cds-hooks-bot commented on Issue #301

Proposed Disposition: Persuasive with Mod
Proposed Disposition Comment:
This is a good observation. We are careful to note that CDS Hooks defines a RESTful API as well as interactions. We use this language in order to described both the Discovery endpoint (RESTful) and the CDS Service request (interactions).

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

cds-hooks-bot labeled Issue #301

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

cds-hooks-bot commented on Issue #301

## :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:
This is a good observation. We are careful to note that CDS Hooks defines a RESTful API as well as interactions. We use this language in order to described both the Discovery endpoint (RESTful) and the CDS Service request (interactions).

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

:tada: The motion passed! :tada: