Difference between revisions of "201801 CDS Hooks"

From HL7Wiki
Jump to: navigation, search
(Implement 1.0 spec)
(Expected participants)
Line 29: Line 29:
 
* athenahealth
 
* athenahealth
 
* T-System
 
* T-System
 +
* University of Utah - OpenInfobutton
 
* many, many, more
 
* many, many, more
  

Revision as of 12:45, 15 November 2017

Return to Jan 2018 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 four Connectathon tracks, the CDS Hooks project has garnered immense support and interest from a variety of organizations. At the Connectathon in San Diego (Sept 2017), we had participation from 4 EHR vendors, many more CDS service providers, and 32 developers.

CDS Hooks has been presented at the American Medical Informatics Association (AMIA) 2016 Annual Symposium, the AMIA 2017 Annual Symposium, and the Argonaut Project has chosen CDS Hooks as a focus for 2017.

Organizing a CDS Hooks track at the January 2018 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
  • athenahealth
  • T-System
  • University of Utah - OpenInfobutton
  • 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

Implement 1.0 spec

Action: Both the EHR and CDS Service fully implement the 1.0 spec (includes security)
Precondition: N/A
Success Criteria: TDB
Bonus point: N/A

Implement Infobutton features using 1.0 spec

Action: EHRs to implement chart-view and medication-prescribe Hooks with requests sent to OpenInfobutton (CDS Service) including prefetch data TBD. OpenInfobutton will respond with Information card with links to online resources and App link card with link to a clinical trial visualization app. Further details TBD.
Precondition: N/A
Success Criteria: TDB
Bonus point: N/A

Connectathon Recap

TBD

Copyright © Health Level Seven International ® ALL RIGHTS RESERVED. The reproduction of this material in any form is strictly forbidden without the written permission of the publisher.