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

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

From HL7Wiki
Jump to navigation Jump to search
(Initial creation)
 
(Initial pass)
Line 2: Line 2:
 
[[Category:201605_FHIR_Connectathon_Track_Proposals|May 2016 Proposals]]
 
[[Category:201605_FHIR_Connectathon_Track_Proposals|May 2016 Proposals]]
 
__NOTOC__
 
__NOTOC__
−
=Track Name=
+
=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 [https://github.com/cds-hooks/cds-hooks/wiki CDS Hooks proposal].
  
 
==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. At the [[201601_CDS_on_FHIR_Connectathon_Track_Proposal|January 2016 HL7 WGM in Orlando, we held the first Connectathon track focused around CDS Hooks]]. This track garnered immense interest and support, with over 10 different companies and 20 individuals participating in the track. The work done as a result of that first Connectathon demonstrated that FHIR could be leveraged in open and interoperable and clinical decision support.
 +
 
 +
Organizing a second CDS Hooks track at the May 2016 Connectathon would allow the community to further develop and explore the possibilities with CDS Hooks. Coming out of the Connectathon in January 2016, there were several aspects of CDS Hooks that require more thought and analysis that was apparent from the implementers and holding another track would benefit the CDS Hooks community. CDS Hooks would be also 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==
 
==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
 +
* Skype: 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 (Kevin Shekleton) [EHR, CDS Service]
 +
* SMART Health IT (Josh Mandel) [EHR, CDS Service]
  
 
==Roles==
 
==Roles==
−
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
+
 
−
===Role 1 Name===
+
===EHR===
−
<!-- Provide a description of the capabilities this role will have within the connectathon -->
+
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==
 
==Scenarios==

Revision as of 16:53, 26 January 2016


CDS Hooks

Submitting WG/Project/Implementer Group

The CDS Hooks community, composed of vendors, developers, and CDS service providers whom support the CDS Hooks proposal.

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. At the January 2016 HL7 WGM in Orlando, we held the first Connectathon track focused around CDS Hooks. This track garnered immense interest and support, with over 10 different companies and 20 individuals participating in the track. The work done as a result of that first Connectathon demonstrated that FHIR could be leveraged in open and interoperable and clinical decision support.

Organizing a second CDS Hooks track at the May 2016 Connectathon would allow the community to further develop and explore the possibilities with CDS Hooks. Coming out of the Connectathon in January 2016, there were several aspects of CDS Hooks that require more thought and analysis that was apparent from the implementers and holding another track would benefit the CDS Hooks community. CDS Hooks would be also 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

See Connectathon_Track_Lead_Responsibilities

Expected participants

  • Cerner (Kevin Shekleton) [EHR, CDS Service]
  • SMART Health IT (Josh Mandel) [EHR, CDS Service]

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

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)

Retrieved from "https://wiki.hl7.org/w/index.php?title=201605_CDS_Hooks_Connectathon_Track_Proposal&oldid=114083"