201709 CDS Hooks
Contents
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 Antonio (Jan 2017), we had participating from 4 EHR vendors, many more CDS service providers, and nearly 30 developers. Additionally, we had strong participation at the Madrid Connectathon this past May 2017.
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 September 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.
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
- 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
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
