Difference between revisions of "201701 CDS Hooks"
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
m |
||
| (14 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
[[Category:201701_FHIR_Connectathon_Track_Proposals|Jan 2017 Proposals]] | [[Category:201701_FHIR_Connectathon_Track_Proposals|Jan 2017 Proposals]] | ||
__NOTOC__ | __NOTOC__ | ||
| − | = | + | =CDS Hooks= |
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
| − | + | ||
| + | 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== | ||
| − | + | ||
| + | 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. | ||
| + | |||
| + | At the [[201605_CDS_Hooks_Connectathon_Track_Proposal|May 2016 Connectathon]] in Montreal, we again had a great turnout of support for participants from several clients and two leading EHR vendors. We further developed the CDS Hooks specification, with all participants implementing and providing feedback on major changes to the specification. | ||
| + | |||
| + | Most recently, at the [[201609_CDS_Hooks|Sept 2016 Connectathon]] in Baltimore, we had the largest participation in a single track with 21 developers representing 16 different organizations. In November 2016, we will be presenting the work done thus far in CDS Hooks at the [https://amia2016.zerista.com/event/member/286750 American Medical Informatics Association (AMIA) 2016 Annual Symposium]. | ||
| + | |||
| + | Organizing a CDS Hooks track at the January 2017 Connectathon would allow the community to further develop and explore the possibilities with CDS Hooks. Coming out of the previous Connectathon and the AMIA 2016 presentation, there is immense interest in 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== | ||
| + | Kevin Shekleton | ||
| + | * Email: kevin dot shekleton at cerner dot com | ||
| + | * Zulip: Kevin Shekleton | ||
| + | |||
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | <!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | ||
See [[Connectathon_Track_Lead_Responsibilities]] | See [[Connectathon_Track_Lead_Responsibilities]] | ||
==Expected participants== | ==Expected participants== | ||
| − | + | ||
| + | Planning on attending the Connectathon and participating in the CDS Hooks track? Please add your name to our [http://bit.ly/cds-hooks-connectathon-tracking Google Sheet]! | ||
| + | |||
| + | * Cerner | ||
| + | * Epic | ||
| + | * Allscripts | ||
| + | * athenahealth | ||
| + | * RxREVU | ||
| + | * SureScripts | ||
| + | * Elsevier | ||
| + | * Regenstrief | ||
| + | * Premier | ||
| + | * MedAppTech | ||
| + | * MCG | ||
| + | * HSPC | ||
| + | * First Databank | ||
| + | * Cigna | ||
| + | * McKesson | ||
==Roles== | ==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== | ==Scenarios== | ||
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
| − | === | + | ===Display SMART App Link=== |
| − | :Action: | + | :Action: The EHR triggers a patient-view hook to the subscribed CDS Service, which returns a CDS app link card containing a link to a SMART app |
| − | :Precondition: | + | :Precondition: N/A |
| − | :Success Criteria: | + | :Success Criteria: The EHR displays the resultant CDS app link card and clicking the app link launches the desired SMART app |
| − | :Bonus point: | + | :Bonus point: N/A |
| + | |||
| + | ===Implement Security=== | ||
| + | :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 Summary== | |
| − | + | The Connectathon summary presentation [https://speakerdeck.com/kpshek/cds-hooks-connectathon-jan-2017-summary can be viewed here]. | |
| − | |||
| − | |||
| − | -- | ||
Latest revision as of 21:49, 15 January 2017
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. 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.
At the May 2016 Connectathon in Montreal, we again had a great turnout of support for participants from several clients and two leading EHR vendors. We further developed the CDS Hooks specification, with all participants implementing and providing feedback on major changes to the specification.
Most recently, at the Sept 2016 Connectathon in Baltimore, we had the largest participation in a single track with 21 developers representing 16 different organizations. In November 2016, we will be presenting the work done thus far in CDS Hooks at the American Medical Informatics Association (AMIA) 2016 Annual Symposium.
Organizing a CDS Hooks track at the January 2017 Connectathon would allow the community to further develop and explore the possibilities with CDS Hooks. Coming out of the previous Connectathon and the AMIA 2016 presentation, there is immense interest in 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
Planning on attending the Connectathon and participating in the CDS Hooks track? Please add your name to our Google Sheet!
- Cerner
- Epic
- Allscripts
- athenahealth
- RxREVU
- SureScripts
- Elsevier
- Regenstrief
- Premier
- MedAppTech
- MCG
- HSPC
- First Databank
- Cigna
- McKesson
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 SMART App Link
- Action: The EHR triggers a patient-view hook to the subscribed CDS Service, which returns a CDS app link card containing a link to a SMART app
- Precondition: N/A
- Success Criteria: The EHR displays the resultant CDS app link card and clicking the app link launches the desired SMART app
- Bonus point: N/A
Implement Security
- 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 Summary
The Connectathon summary presentation can be viewed here.
