FHIR Chat · docs / Issue #226 May 2018 Ballot Comment 20

Stream: cds hooks/github

Topic: docs / Issue #226 May 2018 Ballot Comment 20

Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot opened Issue #226

## May 2018 Ballot Comment 20

Submitted by @bvdh from Philips Healthcare

Chapter: CDS Services
Section: Providing FHIR Resources to a CDS Service
Type: A-Q :question:
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 it also required that all data provided as pre-fetch is accessible in the server?

## Triage Information

Triage Notes:
Reviewed with Bas

Proposed Disposition: Persuasive with mod
Proposed Disposition Comment:
We need to clarify this. Intention is:

Prefetch data may not always be available from the FHIR server. For instance, consider data available only in memory in the EHR but not yet persisted in the FHIR server.

In the case that a FHIR Server is accessible to the CDS Service and the prefetch data is available from the FHIR Server as well, if you make a prefetch query and FHIR request (same query) at the same time (and no changes to the data by other users/systems), the resulting data is the same.

We also will be adding further documentation to explain context and prefetch which should also help clarify the commenter's question.

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

Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot milestoned Issue #226

Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot labeled Issue #226

Github Notifications (May 16 2018 at 22:44):

cds-hooks-bot edited Issue #226

## May 2018 Ballot Comment 20

Submitted by @bvdh from Philips Healthcare

Chapter: CDS Services
Section: Providing FHIR Resources to a CDS Service
Type: A-Q :question:
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 it also required that all data provided as pre-fetch is accessible in the server?

## Triage Information

Triage Notes:
Reviewed with Bas

Proposed Disposition: Persuasive with mod
Proposed Disposition Comment:
We need to clarify this. Intention is:

Prefetch data may not always be available from the FHIR server. For instance, consider data available only in memory in the EHR but not yet persisted in the FHIR server.

In the case that a FHIR Server is accessible to the CDS Service and the prefetch data is available from the FHIR Server as well, if you make a prefetch query and FHIR request (same query) at the same time (and no changes to the data by other users/systems), the resulting data is the same.

We also will be adding further documentation to explain context and prefetch which should also help clarify the commenter's question.

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

Github Notifications (May 18 2018 at 09:20):

cds-hooks-bot commented on Issue #226

Proposed Disposition: Persuasive with mod
Proposed Disposition Comment:
We need to clarify this. Intention is:

Prefetch data may not always be available from the FHIR server. For instance, consider data available only in memory in the EHR but not yet persisted in the FHIR server.

In the case that a FHIR Server is accessible to the CDS Service and the prefetch data is available from the FHIR Server as well, if you make a prefetch query and FHIR request (same query) at the same time (and no changes to the data by other users/systems), the resulting data is the same.

We also will be adding further documentation to explain context and prefetch which should also help clarify the commenter's question.

Github Notifications (May 18 2018 at 09:42):

cds-hooks-bot labeled Issue #226

Github Notifications (May 30 2018 at 22:19):

cds-hooks-bot commented on Issue #226

## :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 need to clarify this. Intention is:

Prefetch data may not always be available from the FHIR server. For instance, consider data available only in memory in the EHR but not yet persisted in the FHIR server.

In the case that a FHIR Server is accessible to the CDS Service and the prefetch data is available from the FHIR Server as well, if you make a prefetch query and FHIR request (same query) at the same time (and no changes to the data by other users/systems), the resulting data is the same.

We also will be adding further documentation to explain context and prefetch which should also help clarify the commenter's question.

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

:tada: The motion passed! :tada: