|
|
| Line 4: |
Line 4: |
| | =CDS Hooks= | | =CDS Hooks= |
| | | | |
| − | CDS Hooks is a [https://github.com/jmandel/cds-hooks/wiki proposal from Josh Mandel] to provide open clinical decision support using both FHIR and SMART.
| + | This proposal has been merged into [[201601_CDS_on_FHIR_Connectathon_Track_Proposal]]. |
| − | | |
| − | ==Submitting WG/Project/Implementer Group==
| |
| − | | |
| − | The CDS Hooks proposal has broad interest and support across both vendors and developers. [https://groups.google.com/forum/#!forum/cds-hooks This group] is asking for this Connectathon track.
| |
| − | | |
| − | ==Justification==
| |
| − | <!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
| |
| − | | |
| − | 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==
| |
| − | <!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
| |
| − | | |
| − | * 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==
| |
| − | <!-- What will be the actions performed by participants? -->
| |
| − | | |
| − | ===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: The EHR triggers a patient-view hook to the subscribed CDS Service whom returns a CDS app link card.
| |
| − | :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: The CDS app link card is only returned based upon contextually relevant data from the patient.
| |
| − | | |
| − | ===Display a CDS Suggestion Card to Cancel a Medication===
| |
| − | :Action: The EHR triggers an order-review hook to the subscribed CDS Service whom returns a CDS suggestion card to cancel the proposed order.
| |
| − | :Precondition: A proposed order exists for the patient.
| |
| − | :Success Criteria: The EHR displays the resultant CDS suggestion card to cancel the proposed order for the patient. If the user selects to accept the suggestion, the proposed order is canceled.
| |
| − | :Bonus point: The CDS suggestion card is only returned based upon contextually relevant data from the patient. For instance, perhaps the medication is only suggested for cancellation if the patient is allergic to the medication.
| |
| − | | |
| − | ===Display a CDS Suggestion Card to Place a Medication===
| |
| − | :Action: The EHR triggers an order-review hook to the subscribed CDS Service whom returns a CDS suggestion card to create a new medication.
| |
| − | :Precondition: A proposed order exists for the patient.
| |
| − | :Success Criteria: The EHR displays the resultant CDS suggestion card to replace the proposed order for the patient with a new order. If the user selects to accept the suggestion, the proposal is accepted.
| |
| − | :Bonus point: The CDS suggestion card is only returned based upon contextually relevant data from the patient. For instance, perhaps the medication is only suggested for replacement if a cheaper suitable medication is found.
| |
| − | | |
| − | ==TestScript(s)==
| |
| − | <!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested.
| |
| − | These should be committed to SVN under trunk/connectathons/[connectathon]
| |
| − | -->
| |
