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 2: Line 2:
 
[[Category:201705_FHIR_Connectathon_Track_Proposals|May 2017 Proposals]]
 
[[Category:201705_FHIR_Connectathon_Track_Proposals|May 2017 Proposals]]
 
__NOTOC__
 
__NOTOC__
=Track Name=
+
=CDS Hooks=
  
 
==Submitting WG/Project/Implementer Group==
 
==Submitting WG/Project/Implementer Group==
Line 9: Line 9:
  
 
==Justification==
 
==Justification==
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 
  
==Proposed Track Lead==
+
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.
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
+
 
 +
CDS Hooks has been presented at the [https://amia2016.zerista.com/event/member/286750 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]]
 
See [[Connectathon_Track_Lead_Responsibilities]]
  
 
==Expected participants==
 
==Expected participants==
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
+
* Cerner
 +
* Epic
 +
* RxREVU
  
 
==Roles==
 
==Roles==

Revision as of 13:06, 14 March 2017


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

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)