Stream: cds hooks
Topic: AcceptedSuggestion Enhancement Request
adam strickland (Jan 21 2021 at 18:58):
Hi everyone,
I have an enhancement for the feedback endpoint. Currently, if a Suggestion is accepted then we only report the id of the suggestion to the feedback endpoint. We should also include an acceptedDetail of sorts to include optional information on what specific follow-up was taken for that suggestion.
For instance, there may be a workflow where a CDS Service returns a generic/broad category of follow-up (for instance, an HCC Condition Category rather than a specific ICD-10 or SNOMED code). In those scenarios, the CDS Client can choose to have the user pick a specific follow-up as a result of the generic suggestion from the CDS Service. It would be nice if the feedback endpoint could optionally include a set of Coding attributes in a given AcceptedSuggestion attributes, with coding systems to be defined by the CDS Client. This way, the CDS Service could learn meaningful information on how it's generic suggestions are translating to discrete ones.
Any thoughts? I think the AcceptedSuggestion item is the best place for this, and that multiple acceptedDetail coding entries should be allowed to account for more complicated workflows.
Isaac Vetter (Jan 27 2021 at 06:08):
Hey Adam, in this scenario, it sounds like we're placing a lot of the effort/complexity on the client: "CDS Service returns a generic/broad category of follow-up". I'd like to question why this is appropriate or even reasonable. At a high level, a CDS Hooks Service is enabled to interrupt / enhance a clinician's workflow in exchange for providing valuable decision support. I'm uncertain that the clinician is served by "pick[ing] a specific follow-up as a result of the generic suggestion from the CDS Service".
Am I getting this wrong? Could anyone provide more details about the use-case?
Last updated: Apr 12 2022 at 19:14 UTC
