FHIR Chat · docs / Issue #124 Update prefetch section to remove todo ... · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #124 Update prefetch section to remove todo ...


view this post on Zulip Github Notifications (Dec 13 2017 at 16:56):

isaacvetter opened Issue #124

During the Argonaut security review, Dixie Baker identified a potential risk of pre-fetch'd data becoming stale, and pointed out that Calling a CDS Service -> HTTP Request -> prefetch contains an outstanding todo.

We should:
1) remove the todo
2) Note that pre-fetch is an optional performance enhancement and is a negotiation between the EHR and the cds service. Pre-fetch data naturally includes a potential risk of clinical data becoming outdated. The longer the running time of the CDS service, the greater this risk. The EHR/provider should weigh this potential risk against the benefits of using pre-fetch'd data.

view this post on Zulip Github Notifications (Dec 13 2017 at 16:56):

isaacvetter milestoned Issue #124

view this post on Zulip Github Notifications (Jan 29 2018 at 15:44):

kpshek assigned Issue #124

view this post on Zulip Github Notifications (Feb 21 2018 at 16:42):

isaacvetter unassigned Issue #124

view this post on Zulip Github Notifications (Feb 21 2018 at 16:42):

isaacvetter assigned Issue #124

view this post on Zulip Github Notifications (Feb 23 2018 at 20:35):

isaacvetter commented on Issue #124

Note that the new-ish Providing FHIR resources to a CDS service section of the specification includes this guidance:

Regardless of the method used to provide FHIR resources to a CDS Service, the EHR must assure that clinical data provided to the CDS Service are the most current data available to the EHR user. Decisions based on stale clinical data pose a safety threat to the patient and must be avoided.

view this post on Zulip Github Notifications (Mar 01 2018 at 16:01):

kpshek edited Issue #124(assigned to isaacvetter)

During the Argonaut security review, Dixie Baker identified a potential risk of pre-fetch'd data becoming stale, and pointed out that Calling a CDS Service -> HTTP Request -> prefetch contains an outstanding todo.

We should:
1) remove the todo
2) Note that pre-fetch is an optional performance enhancement and is a negotiation between the EHR and the cds service. Pre-fetch data naturally includes a potential risk of clinical data becoming outdated. The longer the running time of the CDS service, the greater this risk. The EHR/provider should weigh this potential risk against the benefits of using pre-fetch'd data.

view this post on Zulip Github Notifications (Mar 01 2018 at 16:14):

kpshek closed Issue #124


Last updated: Apr 12 2022 at 19:14 UTC