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

201605 CDS Hooks Connectathon Track Proposal

From HL7Wiki
Revision as of 16:53, 26 January 2016 by Kpshek (talk | contribs) (Initial pass)
Jump to navigation Jump to search


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)