FHIR Chat · docs / Issue #225 May 2018 Ballot Comment 19 · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #225 May 2018 Ballot Comment 19


view this post on Zulip Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot opened Issue #225

## May 2018 Ballot Comment 19

Submitted by @bvdh from Philips Healthcare

Chapter: CDS Services
Section: Providing FHIR Resources to a CDS Service
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Existing Wording:

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.

Comment:
Is this possible? This seems to require that the local state of the prefetch data to be synchronized with the data provided by the server. It also requires that the server cannot be updated while the call is being made.
How to enforce this?

## Triage Information

Triage Notes:
Reviewed with Bas

Proposed Disposition: Persuasive with Mod
Proposed Disposition Comment:
We will be removing the verbiage about "fresh" data per comment #15


_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._

view this post on Zulip Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot milestoned Issue #225

view this post on Zulip Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot labeled Issue #225

view this post on Zulip Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot edited Issue #225

## May 2018 Ballot Comment 19

Submitted by @bvdh from Philips Healthcare

Chapter: CDS Services
Section: Providing FHIR Resources to a CDS Service
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Existing Wording:

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.

Comment:
Is this possible? This seems to require that the local state of the prefetch data to be synchronized with the data provided by the server. It also requires that the server cannot be updated while the call is being made.
How to enforce this?

## Triage Information

Triage Notes:
Reviewed with Bas

Proposed Disposition: Persuasive with Mod
Proposed Disposition Comment:
We will be removing the verbiage about "fresh" data per comment #15


_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._

view this post on Zulip Github Notifications (May 18 2018 at 09:20):

cds-hooks-bot commented on Issue #225

Proposed Disposition: Persuasive with Mod
Proposed Disposition Comment:
We will be removing the verbiage about "fresh" data per comment #15

view this post on Zulip Github Notifications (May 18 2018 at 09:42):

cds-hooks-bot labeled Issue #225

view this post on Zulip Github Notifications (May 30 2018 at 22:18):

cds-hooks-bot commented on Issue #225

## :telephone_receiver: CDS Working Group Block Vote (5-30-2018)

Meeting notes: http://wiki.hl7.org/index.php?title=File:2018-05-30_CDS_WG_Call_Minutes.docx

Julia Skapik moved the following disposition, seconded by @brynrhodes.

Disposition: Persuasive with Mod
Disposition Comment:
We will be removing the verbiage about "fresh" data per comment #15

:+1: For: 12
:expressionless: Abstain: 0
:-1: Against: 0

:tada: The motion passed! :tada:

view this post on Zulip Github Notifications (Jun 14 2018 at 13:36):

cds-hooks-bot assigned Issue #225

view this post on Zulip Github Notifications (Aug 01 2018 at 04:06):

kpshek commented on Issue #225

This was resolved in 28965d7 (PR #369) when fixing #221. Closing.

view this post on Zulip Github Notifications (Aug 01 2018 at 04:06):

kpshek closed Issue #225


Last updated: Apr 12 2022 at 19:14 UTC