This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

201901 CDS Hooks

From HL7Wiki
Revision as of 18:59, 7 November 2018 by Kpshek (talk | contribs) (initial creation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Return to January 2019 Proposals

CDS Hooks

Submitting WG/Project/Implementer Group

The CDS Hooks community, composed of vendors, developers, and CDS service providers whom support the CDS Hooks project.

Justification

CDS Hooks allow for a very important use of both FHIR and SMART that is outside of the normal transactional flow of data. With CDS Hooks, EHRs can further integrate FHIR and SMART into the workflow with clinical decision support. Over the previous Connectathon tracks, the CDS Hooks project has garnered immense support and interest from a variety of organizations. The CDS Hooks track is now consistently the most attended track at each Connectathon.

Organizing a CDS Hooks track at the January 2019 Connectathon would allow the community to further develop and explore the possibilities with CDS Hooks. Holding another Connectathon track for CDS Hooks will further draw more developers and companies to HL7 and allow the community to work within the FHIR ecosystem. Additionally, the CDS Hooks community has found great benefit from participating in the Connectathons so continuing that participation would be appreciated.

Proposed Track Lead

Kevin Shekleton

  • Email: kevin dot shekleton at cerner dot com
  • Zulip: Kevin Shekleton

See Connectathon_Track_Lead_Responsibilities

Expected participants

  • Cerner
  • Epic
  • many, many, more

Please sign up in the google sheet!

Roles

CDS Service

The CDS Service role provides real-time clinical decision support as a remote service. The CDS Server is invoked on a desired hook and returns the decision support in the form of CDS cards.

EHR

The EHR will allow for the registration of interested CDS services on various CDS hooks, triggering each appropriately. The EHR will also display the CDS cards (obtained from the CDS services) to the user.

Scenarios

1 - Implement 1.0 specification

Action: Both the EHR and CDS Service fully implement the 1.0 specification
Precondition: N/A
Success Criteria: TDB
Bonus point: N/A

2 - TDB

TDB - Details to follow

Connectathon Recap

TBD