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

Difference between revisions of "201705 CDS Hooks"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 +
[http://wiki.hl7.org/index.php?title=Category:201705_FHIR_Connectathon_Track_Proposals Return to September 2017 Proposals]
 +
[[Category:201705_FHIR_Connectathon_Track_Proposals|March 2017 Proposals]]
  
 
[[Category:201705_FHIR_Connectathon_Track_Proposals|May 2017 Proposals]]
 
[[Category:201705_FHIR_Connectathon_Track_Proposals|May 2017 Proposals]]

Revision as of 14:10, 21 March 2017

Return to September 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

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Role 1 Name

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

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

TestScript(s)