FHIR Chat · docs / Issue #330 May 2018 Ballot Comment 124

Stream: cds hooks/github

Topic: docs / Issue #330 May 2018 Ballot Comment 124

Github Notifications (May 16 2018 at 23:03):

cds-hooks-bot opened Issue #330

## May 2018 Ballot Comment 124

Submitted by @kensaku-kawamoto on behalf of @euvitudo from University of Utah

Chapter: FHIR resources in context
Section: https://cds-hooks.org/hooks/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Existing Wording:

All FHIR resources in context MUST be based on the same FHIR version

Comment:
A Hook implementer needs to be able to specify what version of FHIR is supported by the service instance. Given that FHIR currently doesn’t self-identify the version being used outside of conformance statements (i.e., at the instance level), recommend we have CDS Hooks instances be specific to specific FHIR versions, with multiple endpoints if multiple FHIR versions are supported.

## :de: Köln May 2018 Working Group Vote

@kpshek moved the following disposition, seconded by @brynrhodes.

Disposition: Persuasive with Mod
Disposition Comment:
We agree this will become an issue and this is something we will focus on for a future release after 1.0.

:+1: For: 21
:expressionless: Abstain: 2
:-1: Against: 0

:tada: The motion passed! :tada:

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

Github Notifications (May 16 2018 at 23:03):

cds-hooks-bot milestoned Issue #330

Github Notifications (May 16 2018 at 23:03):

cds-hooks-bot edited Issue #330

## May 2018 Ballot Comment 124

Submitted by @kensaku-kawamoto on behalf of @euvitudo from University of Utah

Chapter: FHIR resources in context
Section: https://cds-hooks.org/hooks/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Existing Wording:

All FHIR resources in context MUST be based on the same FHIR version

Comment:
A Hook implementer needs to be able to specify what version of FHIR is supported by the service instance. Given that FHIR currently doesn’t self-identify the version being used outside of conformance statements (i.e., at the instance level), recommend we have CDS Hooks instances be specific to specific FHIR versions, with multiple endpoints if multiple FHIR versions are supported.

## :de: Köln May 2018 Working Group Vote

@kpshek moved the following disposition, seconded by @brynrhodes.

Disposition: Persuasive with Mod
Disposition Comment:
We agree this will become an issue and this is something we will focus on for a future release after 1.0.

:+1: For: 21
:expressionless: Abstain: 2
:-1: Against: 0

:tada: The motion passed! :tada:

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