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

Difference between revisions of "201601 CDS Hooks Connectathon Track Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Add further detail to this proposed track)
(This proposal has been merged into 201601_CDS_on_FHIR_Connectathon_Track_Proposal)
 
(6 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
=CDS Hooks=
 
=CDS Hooks=
  
CDS Hooks is a [https://github.com/jmandel/cds-hooks/wiki proposal from Josh Mandel] to provide open clinical decision support using both FHIR and SMART.
+
This proposal has been merged into [[201601_CDS_on_FHIR_Connectathon_Track_Proposal]].
 
 
==Submitting WG/Project/Implementer Group==
 
 
 
The CDS Hooks proposal has broad interest and support across both vendors and developers. [https://groups.google.com/forum/#!forum/cds-hooks This group] is asking for this Connectathon track.
 
 
 
==Justification==
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 
 
 
While this track does not cover FHIR solely or a particular ballot change, 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.
 
 
 
Today, CDS Hooks have a relatively small visibility by the FHIR community as it is a fairly new proposal. With a track at a Connectathon, CDS Hooks would be exposed to the larger FHIR community, allowing others to see how FHIR can be used to provide clinical decision support in the EHR.
 
 
 
==Proposed Track Lead==
 
 
 
* Kevin Shekleton
 
** Email: kevin dot shekleton at cerner dot com
 
** Skype: kevin.shekleton
 
 
 
==Expected participants==
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
 
 
* Cerner (Kevin Shekleton)
 
* SMART Health IT (Josh Mandel)
 
 
 
==Roles==
 
 
 
===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.
 
 
 
===CDS Service===
 
 
 
The CDS service will register themselves for the CDS hooks they are interested in and return CDS cards in response to trigger events as necessary.
 
 
 
==Scenarios==
 
<!-- What will be the actions performed by participants? -->
 
 
 
===Display a CDS Information Card===
 
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
 
:Precondition: <!-- What setup is required prior to executing this step? -->
 
:Success Criteria: <!-- How will the participants know if the test was successful? -->
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
 
 
 
<!-- Provide a description of each task -->
 
 
 
===Display a CDS App Link Card===
 
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
 
:Precondition: <!-- What setup is required prior to executing this step? -->
 
:Success Criteria: <!-- How will the participants know if the test was successful? -->
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
 
 
 
<!-- Provide a description of each task -->
 
 
 
===Display a CDS Suggestion Card to Cancel a Medication===
 
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
 
:Precondition: <!-- What setup is required prior to executing this step? -->
 
:Success Criteria: <!-- How will the participants know if the test was successful? -->
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
 
 
 
<!-- Provide a description of each task -->
 
 
 
===Display a CDS Suggestion Card to Place a Medication===
 
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
 
:Precondition: <!-- What setup is required prior to executing this step? -->
 
:Success Criteria: <!-- How will the participants know if the test was successful? -->
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
 
 
 
<!-- Provide a description of each task -->
 
==TestScript(s)==
 
<!-- 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 13:21, 23 November 2015


CDS Hooks

This proposal has been merged into 201601_CDS_on_FHIR_Connectathon_Track_Proposal.