Stream: cds hooks/github
Topic: docs / Issue #303 discovery endpoint shall include a desc...
Github Notifications (Aug 02 2018 at 22:35):
isaacvetter edited Issue #303(assigned to isaacvetter)
## May 2018 Ballot Comment 97
Submitted by @kensaku-kawamoto on behalf of @euvitudo from University of Utah
Chapter: Discovery
Section: https://cds-hooks.org/specification/1.0/
Type: A-S :bulb:
In Person Requested? NoExisting Wording:
Developers of CDS Services SHALL provide a stable endpoint for allowing EHRs to discover available CDS Services, including information such as the purpose of the CDS Service, when it should be invoked, and any data that is requested to be prefetched.
Proposed Wording:
Developers of CDS Services SHALL provide a stable endpoint for allowing EHRs to discover available CDS Services, including information such as a description of the CDS Service, when it should be invoked, and any data that is requested to be prefetched.
Comment:
The current endpoint descriptor does not have any explicit direction on providing the purpose of the CDS service.
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (Aug 08 2018 at 13:55):
kpshek closed Issue #303
Last updated: Apr 12 2022 at 19:14 UTC
