Stream: cds hooks/github
Topic: docs / Issue #203 Ballot comment from HLN Consulting rega...
Github Notifications (May 08 2018 at 03:21):
kpshek opened Issue #203
Daryl Chertcoff, Project Manager at HLN Consulting, LLC made an Affirmative vote for CDS Hooks in the May 2018 ballot. Included with his ballot was the following comment:
1) If possible, for detail returned in Card attributes, suggest requiring that GitHub Flavored Markdown support table extensions, as per https://github.github.com/gfm/#tables-extension
2) Suggest more guidance in the specification about how to define Hooks unambiguously with respect to when CDS Services that subscribe to the hook are actually. For example, in the Workflow section of the new-hook-template, how does does the author unambiguously define the appropriate screen & workflow upon which CDS services that subscribe to the hook are invoked? Can the role of the EHR user be specified as well? (E.g. - A hook is created for an administrative user, but not clinicians)
Github Notifications (May 08 2018 at 03:21):
kpshek labeled Issue #203
Github Notifications (Jun 05 2018 at 08:14):
kpshek commented on Issue #203
1. If possible, for detail returned in Card attributes, suggest requiring that GitHub Flavored Markdown support table extensions, as per https://github.github.com/gfm/#tables-extension
The card
detailsfield is already documented today as supporting GitHub Flavored Markdown and thereby, tables are supported as that is part of GFM. Also see #319 which relates to our support of GFM.Regarding your second comment on defining hooks unambiguously for a particular workflow as well as role specific hooks, I'd break this down into two questions:
_How do we unambiguously define hooks for a particular workflow?_
Other than specifying as clearly as possible the workflow the hook is to be invoked on, I don't know what else we can do here in the specification. I think our eventual hook maturity model (see #195) will help with this (via encouraging multiple implementations of a hook across vendors).
_What about hooks defined for a particular role?_
Right now, this feels like more of a filtering the CDS Service is doing (to only return CDS when called by a user in a particular role) rather than part of the hook definition. Perhaps concrete examples would help be understand this use case better.
Github Notifications (Nov 13 2018 at 14:51):
brettmarquard assigned Issue #203
Last updated: Apr 12 2022 at 19:14 UTC
