FHIR Chat · docs / Issue #24 What does a 'success' card represent?

Stream: cds hooks

Topic: docs / Issue #24 What does a 'success' card represent?

Github Notifications (Apr 25 2017 at 15:59):

@Josh Mandel - Do you have thoughts on the success indicator since you came up with our original indicators (success, info, warning, and hard-stop)? I admit that I don't know when a CDS service would use that particular indicator value.

@robs16 - I logged #29 several days ago to address documenting what should be returned from the CDS service in the case that no decision support is required. Let's continue the discussion on that question over there.

Github Notifications (Apr 25 2017 at 15:59):

kpshek labeled Issue #24

Github Notifications (May 04 2017 at 20:40):

kpshek milestoned Issue #24

Github Notifications (May 04 2017 at 20:59):

jmandel commented on Issue #24

When I was putting this together, I just grabbed terms from bootstrap to have something quick to work with. So the short answer is: we might strip this out altogether.

If I had to justify, I guess the best I could do would be: "a card communicating the fact that a user's choice 'looks good' to the CDS system".

-J

Github Notifications (May 04 2017 at 21:04):

kpshek commented on Issue #24

Thanks @Josh Mandel!

Based upon this, my opinion is we remove 'success' as an indicator option. While there is a semantic difference between "your choice looks good" and "there is no decision support", I'm not sure this is needed. When I think about Cerner's proprietary rule engine and the 3rd party rules we have incorporated today, none of them offer a "your choice looks good" message to the user (at least none that I am aware of).

I'd love to hear other thoughts on this.

Github Notifications (May 04 2017 at 21:07):

jmandel commented on Issue #24

If nobody says they want it, I'm A-OK with stripping it!

Github Notifications (May 05 2017 at 10:23):

robs16 commented on Issue #24

In my opinion, there is a need for something like 'success' though not necessarily implemented as a card. #29 suggests an empty set of cards, but you cant get to a solution for #13 without some data in the response (not saying this must be a card).

Github Notifications (May 05 2017 at 14:53):

brynrhodes commented on Issue #24

I agree with the ability to represent "success", possibly even with a message, though that message may not be given to the user in that case. For example, we have decision support right now where we want to say "we looked at the meds you provided and they did not have any opioids". The user might not care, but it might be useful for retrospective analysis of how the service was used.

Github Notifications (May 05 2017 at 15:41):

jmandel commented on Issue #24

We should be clear to separate out the issue of saying "the CDS Service ran successfully", from a user-facing card indicating a happy message. This issue is about the latter. If we want to contemplate the former, let's capture it in a separate issue?

Github Notifications (May 05 2017 at 23:17):

kpshek commented on Issue #24

Well put @Josh Mandel.

#13 deals with something close to recording the fact that the CDS Service ran successfully and this needs to be recorded somehow. Let's continue the discussion with that use case there.

@robs16 - Do you have a need at Stanson Health for showing the user a card that informs them everything is good?

I've added this issue to our list of notable issues for Connectathon participants to weigh in on. It would be great to hear from other CDS Service providers to get their thoughts here.