Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

May 2018 Ballot Comment 114 #320

cds-hooks-bot opened this issue May 16, 2018 · 1 comment

May 2018 Ballot Comment 114 #320

cds-hooks-bot opened this issue May 16, 2018 · 1 comment


Copy link

@cds-hooks-bot cds-hooks-bot commented May 16, 2018

May 2018 Ballot Comment 114

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

Chapter: Card Attributes
Type: NEG ❗
In Person Requested? Yes πŸ‘€

Existing Wording:

suggestions: Allows a service to suggest a set of changes in the context of the current activity (e.g. changing the dose of the medication currently being prescribed, for the medication-prescribe activity). If used, the user MUST BE allowed to choose no more than one suggestion.

Why only up to one suggestion? What if for back pain, you are suggesting physical therapy AND NSAIDS? Why would we make the user only be ablet o give the patient one or the other?

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

@cds-hooks-bot cds-hooks-bot added this to the 1.0 milestone May 16, 2018
Copy link

@kpshek kpshek commented May 30, 2018

πŸ“ž CDS Working Group Vote (5-30-2018)

Meeting notes:

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

Disposition: Persuasive with Mod
Disposition Comment:
We will add a new REQUIRED selectionBehavior string field (within each response card) with only one allowed value: "at-most-one" (both the default value and the only allowed value). This would allow us to add additional values in the future based upon implementer feedback at future Connectathons. The intention is to keep this new field inline with the same field from PlanDefinition from Clinical Reasoning. EHRs that do not understand the value MUST treat the card as an error (see other documentation/ballot comment on handling errors). EHRs MUST support a value of "at-most-one".

πŸ‘ For: 15
πŸ˜‘ Abstain: 0
πŸ‘Ž Against: 0

πŸŽ‰ The motion passed! πŸŽ‰

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants