Stream: cds hooks/github
Topic: docs / Issue #290 May 2018 Ballot Comment 84
Github Notifications (May 16 2018 at 23:00):
cds-hooks-bot milestoned Issue #290
Github Notifications (May 16 2018 at 23:00):
cds-hooks-bot opened Issue #290
## May 2018 Ballot Comment 84
Submitted by @cmoesel from MITRE
Chapter: Hooks
Section: Hook version
Type: NEG :exclamation:
In Person Requested? NoExisting Wording:
Addition of a new field to the context - Minor
Proposed Wording:
Addition of a new REQUIRED field to the context - Major
Addition of a new OPTIONAL field to the context - MinorComment:
While adding a context field is backwards-compatible from the perspective of CDS services, it is not necessarily backwards-compatible from the perspective of the EHR, particularly if the new field is REQUIRED.Consider a hook for which the REQUIRED context field "foo" is added in v1.1 (minor update). If a service implements against v1.1 of the hook, they expect the "foo" to always be provided -- but if the EHR is implemented against v1.0 of the hook, this will not be the case -- and the service will be broken.
_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 labeled Issue #290
Github Notifications (May 16 2018 at 23:00):
cds-hooks-bot edited Issue #290
## May 2018 Ballot Comment 84
Submitted by @cmoesel from MITRE
Chapter: Hooks
Section: Hook version
Type: NEG :exclamation:
In Person Requested? NoExisting Wording:
Addition of a new field to the context - Minor
Proposed Wording:
Addition of a new REQUIRED field to the context - Major
Addition of a new OPTIONAL field to the context - MinorComment:
While adding a context field is backwards-compatible from the perspective of CDS services, it is not necessarily backwards-compatible from the perspective of the EHR, particularly if the new field is REQUIRED.Consider a hook for which the REQUIRED context field "foo" is added in v1.1 (minor update). If a service implements against v1.1 of the hook, they expect the "foo" to always be provided -- but if the EHR is implemented against v1.0 of the hook, this will not be the case -- and the service will be broken.
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (May 18 2018 at 09:24):
cds-hooks-bot commented on Issue #290
Proposed Disposition: Persuasive
Proposed Disposition Comment:
Will update as suggested
Github Notifications (May 18 2018 at 09:45):
cds-hooks-bot labeled Issue #290
Github Notifications (May 30 2018 at 22:22):
cds-hooks-bot commented on Issue #290
## :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:
Will update as suggested:+1: For: 12
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (Jun 14 2018 at 13:41):
cds-hooks-bot assigned Issue #290
Last updated: Apr 12 2022 at 19:14 UTC
