FHIR Chat · docs / Issue #305 May 2018 Ballot Comment 99 · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #305 May 2018 Ballot Comment 99


view this post on Zulip Github Notifications (May 16 2018 at 23:01):

cds-hooks-bot opened Issue #305

## May 2018 Ballot Comment 99

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

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

Existing Wording:

An EHR calls a CDS service by POSTing a JSON document to the service endpoint, which can be constructed from the CDS Service base URL and an individual service id as {baseUrl}/cds-services/{service.id}.

Comment:
If this were a true REST service, then it would provide an explicit absolute URL to the service. Recommend that the services return JSON includes an attribute for the URL where the service can be found. E.g. "url": "http://example.com/cds-services/opioid-mme"

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

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

Disposition: Not Persuasive
Disposition Comment:
This comment is saying that our API design does not follow HATEOS. We agree but don't see a need to change.

:+1: For: 19
: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._

view this post on Zulip Github Notifications (May 16 2018 at 23:01):

cds-hooks-bot labeled Issue #305

view this post on Zulip Github Notifications (May 16 2018 at 23:01):

cds-hooks-bot edited Issue #305

## May 2018 Ballot Comment 99

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

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

Existing Wording:

An EHR calls a CDS service by POSTing a JSON document to the service endpoint, which can be constructed from the CDS Service base URL and an individual service id as {baseUrl}/cds-services/{service.id}.

Comment:
If this were a true REST service, then it would provide an explicit absolute URL to the service. Recommend that the services return JSON includes an attribute for the URL where the service can be found. E.g. "url": "http://example.com/cds-services/opioid-mme"

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

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

Disposition: Not Persuasive
Disposition Comment:
This comment is saying that our API design does not follow HATEOS. We agree but don't see a need to change.

:+1: For: 19
: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._

view this post on Zulip Github Notifications (May 16 2018 at 23:01):

cds-hooks-bot milestoned Issue #305

view this post on Zulip Github Notifications (May 16 2018 at 23:09):

kpshek commented on Issue #305

Closing per the _ Not Persuasive_ vote at the :de: Köln May 2018 working group meeting.

view this post on Zulip Github Notifications (May 16 2018 at 23:09):

kpshek closed Issue #305

view this post on Zulip Github Notifications (Jun 14 2018 at 13:42):

cds-hooks-bot assigned Issue #305


Last updated: Apr 12 2022 at 19:14 UTC