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
m (Add Craig Parker per his request)
Line 44: Line 44:
  
 
===Display a CDS Information Card===
 
===Display a CDS Information Card===
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: The EHR triggers a patient-view hook to the subscribed CDS Service whom returns a CDS information card.
: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: The EHR displays the resultant CDS information card.
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
+
:Bonus point: The CDS information card contains contextually relevant data about the patient based upon information about the patient from the FHIR server.
 
 
<!-- Provide a description of each task -->
 
  
 
===Display a CDS App Link Card===
 
===Display a CDS App Link Card===

Revision as of 12:22, 23 November 2015


CDS Hooks

CDS Hooks is a proposal from Josh Mandel to provide open clinical decision support using both FHIR and SMART.

Submitting WG/Project/Implementer Group

The CDS Hooks proposal has broad interest and support across both vendors and developers. This group is asking for this Connectathon track.

Justification

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

  • Cerner (Kevin Shekleton)
  • SMART Health IT (Josh Mandel)
  • Intermountain Health Care (Craig Parker)

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

Display a CDS Information Card

Action: The EHR triggers a patient-view hook to the subscribed CDS Service whom returns a CDS information card.
Precondition: N/A
Success Criteria: The EHR displays the resultant CDS information card.
Bonus point: The CDS information card contains contextually relevant data about the patient based upon information about the patient from the FHIR server.

Display a CDS App Link Card

Action:
Precondition:
Success Criteria:
Bonus point:


Display a CDS Suggestion Card to Cancel a Medication

Action:
Precondition:
Success Criteria:
Bonus point:


Display a CDS Suggestion Card to Place a Medication

Action:
Precondition:
Success Criteria:
Bonus point:

TestScript(s)