FHIR Chat · docs / Issue #303 May 2018 Ballot Comment 97 · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #303 May 2018 Ballot Comment 97


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

cds-hooks-bot opened Issue #303

## 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? No

Existing 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._

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

cds-hooks-bot labeled Issue #303

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

cds-hooks-bot milestoned Issue #303

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

cds-hooks-bot edited Issue #303

## 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? No

Existing 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._

view this post on Zulip Github Notifications (May 18 2018 at 09:25):

cds-hooks-bot commented on Issue #303

Proposed Disposition: Persuasive
Proposed Disposition Comment:
We will update as suggested

view this post on Zulip Github Notifications (May 18 2018 at 09:46):

cds-hooks-bot labeled Issue #303

view this post on Zulip Github Notifications (May 30 2018 at 22:23):

cds-hooks-bot commented on Issue #303

## :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
Disposition Comment:
We will update as suggested

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

:tada: The motion passed! :tada:

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

cds-hooks-bot assigned Issue #303


Last updated: Apr 12 2022 at 19:14 UTC