FHIR Chat · docs / Issue #15 Can CDS service discovery flex based upo... · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #15 Can CDS service discovery flex based upo...

Github Notifications (May 10 2017 at 11:21):

kpshek commented on Issue #15

At the Madrid Connectathon this past weekend (2017-05-07), a large group of us participating in the CDS Hooks track discussed this issue in an offline discussion. This group of ~12 represented a broad set of stakeholders, from multiple EHR vendors, several CDS Service providers, and a healthcare organization. What follows is the summary of our discussion and the consensus of the group.

It was noted that the iss value (FHIR base URL) wouldn't satisfy all scenarios for the issue noted here. For instance, imagine a CDS Service that specifies and Observation prefetch query which would completely satisfy the needs/logic of this service. Now, imagine an EHR which does not support the Observation resource in its FHIR server but does support prefetching this data via some proprietary means. If the Discovery endpoint solely based it's decision on the capabilities of the FHIR server, it would mistakenly think this EHR could not call this CDS Service.

We all agreed that we want to move in the direction of streamlining and automating the integration between EHRs and CDS Services to further minimize offline work around integration. However, the group recognized that our current landscape is not here yet and until that time, it does not make any changes around this.

Github Notifications (Jul 26 2017 at 18:24):

kpshek labeled Issue #15

Github Notifications (Jul 26 2017 at 18:25):

kpshek closed Issue #15

Github Notifications (Jul 26 2017 at 18:25):

kpshek commented on Issue #15

Closing this issue as deferred per the discussion amongst the broad stakeholders at the Madrid Connectathon back in May.

Last updated: Apr 12 2022 at 19:14 UTC