FHIR Chat · docs / Issue #407 The term EHR is inaccurate

Stream: cds hooks/github

Topic: docs / Issue #407 The term EHR is inaccurate

Github Notifications (Aug 16 2018 at 04:32):

isaacvetter opened Issue #407

In the spec, we've consciously chosen to use the term "EHR" to illustrate a primary use-case of CDS Hooks.

For some users of CDS Hooks, this minimizes their role and suggests that CDS Hooks is not applicable -- even when it is!

We should define a new term, such as "_CDS Hooks Client_" and add an explanatory sentence, such as:

The CDS Hooks specification uses the term CDS client to generically refer to the clinical workflow system in which a CDS services returned cards are displayed.

and remove references to "EHR".

Isaac

Github Notifications (Aug 16 2018 at 04:37):

kpshek commented on Issue #407

I am strongly in favor of this change. While we are extremely reluctant to introduce any new scope into the impending 1.0 release, I think this change would be an easy and welcome addition to 1.0. It doesn't introduce any new features of implementers and simply clarifies the actor we've had trouble describing (narrowly using EHR).

Github Notifications (Aug 16 2018 at 06:02):

lmckenzi commented on Issue #407

It would be good to list EHRs as an example of a client so that readers realize they're one of the targets, but agree that generic terms would be best throughout the spec. (I've tried to use the term 'client' throughout DaVinci - I'm hoping pharmacy management systems, dental systems and others may come online at some point too :>)

Github Notifications (Aug 16 2018 at 15:57):

kensaku-kawamoto commented on Issue #407

I agree with this.

Github Notifications (Aug 16 2018 at 16:03):

gdelfiol commented on Issue #407

I suggest appending the description above with something like "The CDS Hooks specification uses the term CDS client to generically refer to the clinical workflow system in which a CDS service's returned cards are displayed or processed."

This would cover use cases where a CDS service response is consumed by a backend process and not intended to be displayed to a user (e.g., a population health management system that automatically enrolls a patient into a chronic disease management program).

Github Notifications (Aug 16 2018 at 16:43):

isaacvetter edited Issue #407

[Updated proposed explanatory sentence to incorporate Lloyd and Guilherme's feedback.]
In the spec, we've consciously chosen to use the term "EHR" to illustrate a primary use-case of CDS Hooks.

For some users of CDS Hooks, this minimizes their role and suggests that CDS Hooks is not applicable -- even when it is!

We should define a new term, such as "_CDS Hooks Client_" and add an explanatory sentence, such as:

The CDS Hooks specification uses the term CDS client to generically refer to the clinical workflow system, such as an EHR, in which a CDS services returned cards are displayed or processed.

and remove other references to "EHR".

Isaac

Github Notifications (Aug 16 2018 at 16:44):

isaacvetter edited Issue #407

[_Updated proposed explanatory sentence to incorporate Lloyd and Guilherme's feedback._]
In the spec, we've consciously chosen to use the term "EHR" to illustrate a primary use-case of CDS Hooks.

For some users of CDS Hooks, this minimizes their role and suggests that CDS Hooks is not applicable -- even when it is!

We should define a new term, such as "_CDS Hooks Client_" and add an explanatory sentence, such as:

The CDS Hooks specification uses the term CDS client to generically refer to the clinical workflow system, such as an EHR, in which a CDS services returned cards are displayed or processed.

and remove other references to "EHR".

Isaac