201705 CDS Hooks

From HL7Wiki
Jump to: navigation, search

Return to May 2017 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 most recent Connectathon in San Antonio (Jan 2017), we had participating from 4 EHR vendors, many more CDS service providers, and nearly 30 developers.

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

Organizing a CDS Hooks track at the May 2017 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.

Track Lead

Kevin Shekleton

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

See Connectathon_Track_Lead_Responsibilities

Expected participants

  • Cerner
  • Epic
  • RxREVU

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

Display SMART App Link

Action: The EHR triggers a patient-view hook to the subscribed CDS Service, which returns a CDS app link card containing a link to a SMART app
Precondition: N/A
Success Criteria: The EHR displays the resultant CDS app link card and clicking the app link launches the desired SMART app
Bonus point: N/A

Implement Security to the FHIR Server

Action: The EHR triggers a patient-view hook to the subscribed CDS Service using the security defined in the CDS Hooks specification
Precondition: N/A
Success Criteria: The CDS information card contains contextually relevant data about the patient based upon information about the patient from the FHIR server, all using a security context.
Bonus point: N/A

CDC Opioid Guideline

This scenario is related to the Clinical Reasoning track scenario of the same name. The intention of this scenario is to build a CDS Service that implements the CDC guideline for prescribing opioids, specifically recommendation #5.

Action: The EHR triggers a medication-prescribe hook to the subscribed CDS Service.
Precondition: N/A
Success Criteria: The CDS Service performs the logic defined outlined in recommendation #5 in the CDC opioid prescribing guidelines.
Bonus point: N/A

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.