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

Difference between revisions of "201709 CDS Hooks"

From HL7Wiki
Jump to navigation Jump to search
m
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category:201709_FHIR_Connectathon_Track_Proposals|Sept 2017 Proposals]]
 +
 +
[http://wiki.hl7.org/index.php?title=Category:201709_FHIR_Connectathon_Track_Proposals Return to Sept 2017 Proposals]
  
−
[[Category:201709_FHIR_Connectathon_Track_Proposals|Sept 2017 Proposals]]
 
−
__NOTOC__
 
 
=CDS Hooks=
 
=CDS Hooks=
  
 
==Submitting WG/Project/Implementer Group==
 
==Submitting WG/Project/Implementer Group==
−
<!-- Who is asking for this track? -->
+
The [https://groups.google.com/forum/#!forum/cds-hooks CDS Hooks community], composed of vendors, developers, and CDS service providers whom support the [http://cds-hooks.org/ CDS Hooks project].
  
 
==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. -->
+
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 [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 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==
 
==Proposed Track Lead==
−
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
+
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
 +
* athenahealth
 +
* T-System
 +
* many, many, more
 +
 
 +
Please sign up in the [https://bit.ly/cds-hooks-connectathon-tracking google sheet!]
  
 
==Roles==
 
==Roles==
−
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
+
 
−
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
+
===CDS Service===
−
===Role 1 Name===
+
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.
−
<!-- Provide a description of the capabilities this role will have within the connectathon -->
+
 
 +
===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==
 
==Scenarios==
−
<!-- What will be the actions performed by participants? -->
 
  
−
===Scenario Step 1 Name===
+
===Implement 1.0 spec===
−
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: Both the EHR and CDS Service fully implement the 1.0 spec
−
:Precondition: <!-- What setup is required prior to executing this step? -->
+
:Precondition: N/A
−
:Success Criteria: <!-- How will the participants know if the test was successful? -->
+
:Success Criteria: TDB
−
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
+
: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
  
−
<!-- Provide a description of each task -->
+
==Connectathon Recap==
  
−
==TestScript(s)==
+
The presentation for the Connectathon recap is [https://speakerdeck.com/kpshek/cds-hooks-connectathon-sept-2017-summary available here].
−
<!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested.
 
−
These should be committed to SVN under trunk/connectathons/[connectathon]
 
−
-->
 

Latest revision as of 19:37, 10 September 2017


Return to Sept 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 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
  • athenahealth
  • T-System
  • 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
Precondition: N/A
Success Criteria: TDB
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

Connectathon Recap

The presentation for the Connectathon recap is available here.

Retrieved from "https://wiki.hl7.org/w/index.php?title=201709_CDS_Hooks&oldid=145469"