FHIR Chat · docs / Issue #221 May 2018 Ballot Comment 15 · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #221 May 2018 Ballot Comment 15

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

cds-hooks-bot opened Issue #221

## May 2018 Ballot Comment 15

Submitted by @bvdh from Philips Healthcare

Chapter: CDS Services
Section: Providing FHIR Resources to a CDS Service
Type: A-S :bulb:
In Person Requested? Yes :bust_in_silhouette:

Proposed Wording:

Each CDS Service will require specific FHIR resources in order to compute the recommendations the EHR requests. If real-world performance were no issue, an EHR could launch a CDS Service passing only context data, and the CDS Service could then request authorization for FHIR resources as they were needed, and then retrieve the resources from the EHR's FHIR server. However, CDS Services SHOULD respond quickly (on the order of 500 ms.), and so we provide performance enhancements that allow a CDS Service to request and obtain FHIR resources more efficiently.

## Triage Information

Triage Notes:
Reviewed with Bas

Proposed Disposition: Persuasive
Proposed Disposition Comment:
We agree with Bas's suggestions and will take as-is:
must to SHOULD
Remove statements around data freshness

---

_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 #221

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

cds-hooks-bot labeled Issue #221

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

cds-hooks-bot edited Issue #221

## May 2018 Ballot Comment 15

Submitted by @bvdh from Philips Healthcare

Chapter: CDS Services
Section: Providing FHIR Resources to a CDS Service
Type: A-S :bulb:
In Person Requested? Yes :bust_in_silhouette:

Proposed Wording:

Each CDS Service will require specific FHIR resources in order to compute the recommendations the EHR requests. If real-world performance were no issue, an EHR could launch a CDS Service passing only context data, and the CDS Service could then request authorization for FHIR resources as they were needed, and then retrieve the resources from the EHR's FHIR server. However, CDS Services SHOULD respond quickly (on the order of 500 ms.), and so we provide performance enhancements that allow a CDS Service to request and obtain FHIR resources more efficiently.

## Triage Information

Triage Notes:
Reviewed with Bas

Proposed Disposition: Persuasive
Proposed Disposition Comment:
We agree with Bas's suggestions and will take as-is:
must to SHOULD
Remove statements around data freshness

---

_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 #221

Proposed Disposition: Persuasive
Proposed Disposition Comment:
We agree with Bas's suggestions and will take as-is:
must to SHOULD
Remove statements around data freshness

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

cds-hooks-bot labeled Issue #221

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

cds-hooks-bot commented on Issue #221

## :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
Disposition Comment:
We agree with Bas's suggestions and will take as-is:
must to SHOULD
Remove statements around data freshness

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

:tada: The motion passed! :tada:

Github Notifications (Jun 14 2018 at 13:35):

cds-hooks-bot assigned Issue #221

Github Notifications (Jul 25 2018 at 15:34):

kpshek closed Issue #221

Last updated: Apr 12 2022 at 19:14 UTC