Stream: cds hooks/github
Topic: docs / Issue #95 Is it required to show all Cards on screen?
Github Notifications (Sep 13 2017 at 15:12):
bvdh opened Issue #95
When a hook is triggered, the related CDS Services are called. They may return one or more Cards.
Is the EHR required to show them all? What happens when there are more cards than can fit the screen?Suggestion: The EHR MUST provide access to all cards. SHOULD display them all. MAY present them in a ListBox.
Github Notifications (Sep 13 2017 at 15:25):
isaacvetter commented on Issue #95
Hey @bvdh ,
MAY present them in a ListBox.
I'm wary of trying to dictate EHR UI. In general, the CDS Hooks spec purposely permits UI to remain the responsibility of the EHR. We want the CDS service's cards to appear native in the EHR UI. Further, my opinion is that dictating UI hinders innovation in UX.
The EHR MUST provide access to all cards. SHOULD display them all.
Further, I think that the EHR should (continue to) be enabled to dynamically decide what guidance to provide to the clinician based upon the priority and amount of internal and external guidance available. In practice, this could mean using the CDS Hooks response indicator element to prioritize the guidance displayed to the user.
Isaac
Github Notifications (Sep 13 2017 at 15:54):
Isaac,
Thanks for the quick response.
The ListBox suggestion is just a suggestion. I have no clear opinion on whether this should be in or out.The second part is more important:
The EHR MUST provide access to all cards. SHOULD display them all
CDS Services work with clinical data and may provide relevant information. The EHR cannot determine what the (medical) risks are for not showing the feedback of the CDS Service. As such I think that it should be mandatory that all cards must be accessible. Preferably shown.
We could limit mandating this to only cards with <warning> and <hard-stop> response indicators.Bas
Last updated: Apr 12 2022 at 19:14 UTC
