search

cds-hooks / docs

CDS Hooks website & specification
http://cds-hooks.org
Apache License 2.0
166 stars 61 forks source link

Is it required to show all Cards on screen? #95

Open bvdh opened 7 years ago

bvdh commented 7 years ago

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.

isaacvetter commented 7 years ago

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

bvdh commented 7 years ago

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 and response indicators.

Bas