Stream: cds hooks/github
Topic: docs / Issue #289 May 2018 Ballot Comment 83
Github Notifications (May 16 2018 at 23:00):
cds-hooks-bot opened Issue #289
## May 2018 Ballot Comment 83
Submitted by @cmoesel from MITRE
Chapter: Hooks
Section: Hook version
Type: NEG :exclamation:
In Person Requested? NoExisting Wording:
Change of prefetch token status of an existing context field - Patch
Proposed Wording:
Change of prefetch token status of an existing context field - Major
Comment:
Changing prefetch token status from "Yes" to "No" would impact any existing services that already use the context field in a prefetch template -- as it would render the prefetch invalid.Changing prefetch token status from "No" to "Yes" would impact EHRs as they now need to support an additional token in prefetch templates that they didn't need to support before.
These seem to be backwards-incompatible changes to me, and so should indicate a Major revision.
## :de: Köln May 2018 Working Group Vote
@kpshek moved the following disposition, seconded by @brynrhodes.
Disposition: Persuasive with mod
Disposition Comment:
We will fix this entry in the table to indicate prefetch token changes (boolean status) to required context fields are breaking changes (major). Prefetch token changes to optional context fields are not breaking changes.Additionally, we will document that the intention behind the table is to outline possible breaking changes and when we are notified of additional scenarios, we will add them.
:+1: For: 19
:expressionless: Abstain: 3
:-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:00):
cds-hooks-bot milestoned Issue #289
Github Notifications (May 16 2018 at 23:00):
cds-hooks-bot labeled Issue #289
Github Notifications (May 16 2018 at 23:00):
cds-hooks-bot edited Issue #289
## May 2018 Ballot Comment 83
Submitted by @cmoesel from MITRE
Chapter: Hooks
Section: Hook version
Type: NEG :exclamation:
In Person Requested? NoExisting Wording:
Change of prefetch token status of an existing context field - Patch
Proposed Wording:
Change of prefetch token status of an existing context field - Major
Comment:
Changing prefetch token status from "Yes" to "No" would impact any existing services that already use the context field in a prefetch template -- as it would render the prefetch invalid.Changing prefetch token status from "No" to "Yes" would impact EHRs as they now need to support an additional token in prefetch templates that they didn't need to support before.
These seem to be backwards-incompatible changes to me, and so should indicate a Major revision.
## :de: Köln May 2018 Working Group Vote
@kpshek moved the following disposition, seconded by @brynrhodes.
Disposition: Persuasive with mod
Disposition Comment:
We will fix this entry in the table to indicate prefetch token changes (boolean status) to required context fields are breaking changes (major). Prefetch token changes to optional context fields are not breaking changes.Additionally, we will document that the intention behind the table is to outline possible breaking changes and when we are notified of additional scenarios, we will add them.
:+1: For: 19
:expressionless: Abstain: 3
:-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 (Jun 06 2018 at 15:33):
isaacvetter labeled Issue #289
Github Notifications (Jun 14 2018 at 13:41):
cds-hooks-bot assigned Issue #289
Github Notifications (Dec 05 2018 at 16:34):
kpshek closed Issue #289
Last updated: Apr 12 2022 at 19:14 UTC
