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.
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:
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.