Stream: cds hooks/committers
Topic: docs / PR #193 Result review hook
Github Notifications (Mar 30 2018 at 19:07):
yashaskram opened PR #193
from result-review-hook to master
I don't exactly recollect the process for proposing new hooks. Not sure doing a PR is the right way compared to doing it formally through an issue. But I think result-review should be straightforward. This should not affect 1.0 spec finalization for upcoming HL7 ballot and so sending this your for review...
Github Notifications (May 15 2018 at 09:03):
@yashaskram - I apologize for not responding on this PR sooner. Thanks for taking the time to document and propose this new hook!
We've been mulling over the process for documenting, publicizing, and evaluating the maturity of hooks. As part of this, we intentionally separated the specific hooks with the specification as we expect there to be new hooks and changes to existing hooks far more frequently than updates to the specification.
We think that storing the hooks there in its own wiki repository will be more manageable and better reflect the relationship between CDS Hooks (the organization & specification) and the hooks defined by the community. We haven't fleshed out the details yet of the maturity model, so perhaps if a hook reaches a sufficient maturity it will be hosted on cds-hooks.org (or some other place outside of the wiki). However, we know we want to start here with the wiki.
Can you add a new Wiki page at cds-hooks/hooks/wiki for your proposed
result-reviewhook? Once you've done that I'll go ahead and close this PR.
Github Notifications (Jul 12 2018 at 00:56):
yashaskram commented on PR #193
Ok @kpshek. I will go ahead and create a Wiki page for the result-review hook.
Github Notifications (Aug 01 2018 at 04:54):
Thanks @yashaskram. Closing this.
Github Notifications (Aug 01 2018 at 04:54):
kpshek closed PR #193
Last updated: Apr 12 2022 at 19:14 UTC
