FHIR Chat · docs / Issue #212 Is discovery required? Different from r... · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #212 Is discovery required? Different from r...

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

isaacvetter edited Issue #212(assigned to isaacvetter)

## 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 (Aug 09 2018 at 17:48):

isaacvetter closed Issue #212

Last updated: Apr 12 2022 at 19:14 UTC