Stream: cds hooks
Topic: docs / Issue #42 Improve analytics functionality - let cd...
Github Notifications (May 06 2017 at 05:57):
isaacvetter opened Issue #42
In discussion with @brynrhodes and @kpshek regarding aligning Clinical Reasoning and CDS Hooks, one of the topics of discussion was around the ability of the cds service to know when a suggestion was rejected by the end user.
Currently, our analytics endpoint accepts a uuid when "a button is clicked", as we necessarily complicate the suggestion model, this may not be sufficient to describe the actual suggestion accepted by the user and does not capture a concept of rejection.
This issue is related to, but not necessarily the same as #41. Overall, I think that we need to re-design the analytics endpoint, so that the cds service is able to improve its behavior and so that the end-user has a positive and meaningful experience with the cds.
Github Notifications (May 06 2017 at 11:56):
bdoolittle commented on Issue #42
@Isaac Vetter Issue #21 was posted a few months ago and addresses this same problem with the analytics endpoint. There is a proposed solution without any discussion around it. Please take a look and see if the proposal fits your needs.
Github Notifications (May 07 2017 at 10:51):
isaacvetter commented on Issue #42
Thanks, @brian doolittle !
Closing in favor of @robs16's #21.
Github Notifications (May 07 2017 at 10:51):
isaacvetter closed Issue #42
Github Notifications (May 07 2017 at 10:52):
kpshek labeled Issue #42
Last updated: Apr 12 2022 at 19:14 UTC
