Difference between revisions of "201609 CDS Hooks"
(initial creation) |
(flesh out proposal) |
||
| Line 2: | Line 2: | ||
[[Category:201609_FHIR_Connectathon_Track_Proposals|May 2016 Proposals]] | [[Category:201609_FHIR_Connectathon_Track_Proposals|May 2016 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. | ||
| + | |||
| + | Organizing a CDS Hooks track at the September 2016 Connectathon would allow the community to further develop and explore the possibilities with CDS Hooks. Coming out of the Connectathon in May 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== | ||
| − | + | Kevin Shekleton | |
| + | * Email: kevin dot shekleton at cerner dot com | ||
| + | * Zulip: Kevin Shekleton | ||
| + | |||
See [[Connectathon_Track_Lead_Responsibilities]] | See [[Connectathon_Track_Lead_Responsibilities]] | ||
==Expected participants== | ==Expected participants== | ||
| − | + | ||
| + | * Harvard, Josh Mandel | ||
| + | * Cerner, Kevin Shekleton | ||
| + | * RxREVU | ||
==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== | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ===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 | ||
Revision as of 21:19, 16 June 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 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.
Organizing a CDS Hooks track at the September 2016 Connectathon would allow the community to further develop and explore the possibilities with CDS Hooks. Coming out of the Connectathon in May 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
- Zulip: Kevin Shekleton
See Connectathon_Track_Lead_Responsibilities
Expected participants
- Harvard, Josh Mandel
- Cerner, Kevin Shekleton
- RxREVU
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
