FHIR Chat · docs / Issue #212 May 2018 Ballot Comment 6 · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #212 May 2018 Ballot Comment 6

Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot opened Issue #212

## May 2018 Ballot Comment 6

Submitted by @bvdh from Philips Healthcare

Chapter: CDS Services
Section: Discovery
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Comment:
How does discovery work? The spec seems to suggest that a CDS Service Provider provides a URL listing the supported CDS Services to be added to the EHR list.
The sections above seem to suggest that registration is out-of-scope, still the CDS Service Provider must provide a stable end-point.
As the model is backed with mandatory statements (see below, some text (and a picture) explaining this model would be required.
Alternatively, keep the discovery model out of scope and make the mandotory text lower case.

## Triage Information

Triage Notes:
Reviewed with Bas

Proposed Disposition: Persuasive
Proposed Disposition Comment:
Bas will help us get a PR together. The intention is that we communicate:

CDS Services MUST implement Discovery
EHRs MAY use Discovery

Additionally, we need to clearly distinguished between registration and Discovery.

---

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

Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot milestoned Issue #212

Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot labeled Issue #212

Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot edited Issue #212

## May 2018 Ballot Comment 6

Submitted by @bvdh from Philips Healthcare

Chapter: CDS Services
Section: Discovery
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Comment:
How does discovery work? The spec seems to suggest that a CDS Service Provider provides a URL listing the supported CDS Services to be added to the EHR list.
The sections above seem to suggest that registration is out-of-scope, still the CDS Service Provider must provide a stable end-point.
As the model is backed with mandatory statements (see below, some text (and a picture) explaining this model would be required.
Alternatively, keep the discovery model out of scope and make the mandotory text lower case.

## Triage Information

Triage Notes:
Reviewed with Bas

Proposed Disposition: Persuasive
Proposed Disposition Comment:
Bas will help us get a PR together. The intention is that we communicate:

CDS Services MUST implement Discovery
EHRs MAY use Discovery

Additionally, we need to clearly distinguished between registration and Discovery.

---

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

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

cds-hooks-bot commented on Issue #212

Proposed Disposition: Persuasive
Proposed Disposition Comment:
Bas will help us get a PR together. The intention is that we communicate:

CDS Services MUST implement Discovery
EHRs MAY use Discovery

Additionally, we need to clearly distinguished between registration and Discovery.

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

cds-hooks-bot labeled Issue #212

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

cds-hooks-bot commented on Issue #212

## :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:
Bas will help us get a PR together. The intention is that we communicate:

CDS Services MUST implement Discovery
EHRs MAY use Discovery

Additionally, we need to clearly distinguished between registration and Discovery.

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

:tada: The motion passed! :tada:

Github Notifications (Jun 14 2018 at 13:35):

cds-hooks-bot assigned Issue #212

Github Notifications (Aug 06 2018 at 20:44):

isaacvetter commented on Issue #212

Hey @bvdh ,

I slightly modified the relevant sentence from PR #359 from:

The discovery endpoint SHALL always be available at {baseUrl}/cds-services. For example, if the baseUrl is https://example.com, the EHR would invoke:
to
The discovery endpoint SHALL always be available at {baseUrl}/cds-services. For example, if the baseUrl is https://example.com, the EHR MAY invoke:

With these two PRs -- do we still need to further distinguish between registration and discovery? There's a couple of places in the spec where we already talk about registration.

Isaac

Last updated: Apr 12 2022 at 19:14 UTC