Stream: cds hooks/github
Topic: docs / Issue #232 May 2018 Ballot Comment 26
Github Notifications (May 16 2018 at 22:44):
cds-hooks-bot opened Issue #232
## May 2018 Ballot Comment 26
Submitted by @bvdh from Philips Healthcare
Chapter: CDS Services
Section: Prefetch template
Type: A-Q :question:
In Person Requested? Yes :bust_in_silhouette:Existing Wording:
}}, MUST be named based upon the field they correspond to,
Comment:
Why do we need to enforce this as a mandatory requirement. Is it a requirement at all?## :de: Köln May 2018 Working Group Vote
@jmandel moved the following disposition, seconded by @brynrhodes.
Disposition: Persuasive with Mod
Disposition Comment:
Move the CDS Service request "user" field to the hook context and document that each hook author shall include the "user" context field if it is appropriate for their hook. We acknowledge this breaking change but feel now is the time to do this. In doing this, we will address the ballot comment (by clarifying that prefetch templates relate to context parameters) and possibly allow for non-user initiated CDS Hooks calls.:+1: For: 24
:expressionless: Abstain: 0
:-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 22:44):
cds-hooks-bot milestoned Issue #232
Github Notifications (May 16 2018 at 22:44):
cds-hooks-bot labeled Issue #232
Github Notifications (May 16 2018 at 22:44):
cds-hooks-bot edited Issue #232
## May 2018 Ballot Comment 26
Submitted by @bvdh from Philips Healthcare
Chapter: CDS Services
Section: Prefetch template
Type: A-Q :question:
In Person Requested? Yes :bust_in_silhouette:Existing Wording:
}}, MUST be named based upon the field they correspond to,
Comment:
Why do we need to enforce this as a mandatory requirement. Is it a requirement at all?## :de: Köln May 2018 Working Group Vote
@jmandel moved the following disposition, seconded by @brynrhodes.
Disposition: Persuasive with Mod
Disposition Comment:
Move the CDS Service request "user" field to the hook context and document that each hook author shall include the "user" context field if it is appropriate for their hook. We acknowledge this breaking change but feel now is the time to do this. In doing this, we will address the ballot comment (by clarifying that prefetch templates relate to context parameters) and possibly allow for non-user initiated CDS Hooks calls.:+1: For: 24
:expressionless: Abstain: 0
:-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:28):
isaacvetter labeled Issue #232
Github Notifications (Jun 14 2018 at 13:36):
cds-hooks-bot assigned Issue #232
Github Notifications (Aug 02 2018 at 08:13):
kpshek labeled Issue #232
Github Notifications (Nov 13 2018 at 21:59):
kpshek closed Issue #232
Last updated: Apr 12 2022 at 19:14 UTC
