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

Provenance.... #27

Closed
rossjones opened this issue Nov 23, 2014 · 4 comments
Closed

Provenance.... #27

rossjones opened this issue Nov 23, 2014 · 4 comments

Comments

@rossjones
Copy link
Contributor

... or whatever it is called.

When sending notifications we should include the source of the rule, and why it matched.

@davidmiller
Copy link
Member

What's the use case ?

On 23 November 2014 at 19:28, Ross Jones notifications@github.com wrote:

... or whatever it is called.

When sending notifications we should include the source of the rule, and
why it matched.


Reply to this email directly or view it on GitHub
#27.

Love regards etc

David Miller
http://www.deadpansincerity.com
@thatdavidmiller http://twitter.com/thatdavidmiller
07854 880 883

@rossjones
Copy link
Contributor Author

As a clinician receiving a notification
I want to see the rule, and source of the rule, that generated this alert
So that I can be slightly more confident that this isn't a mistake, or so I can double-check.

@davidmiller
Copy link
Member

Just checking :)

On 24 November 2014 at 08:52, Ross Jones notifications@github.com wrote:

As a clinician receiving a notification
I want to see the rule, and source of the rule, that generated this alert
So that I can be slightly more confident that this isn't a mistake, or so
I can double-check.


Reply to this email directly or view it on GitHub
#27 (comment).

Love regards etc

David Miller
http://www.deadpansincerity.com
@thatdavidmiller http://twitter.com/thatdavidmiller
07854 880 883

@rossjones
Copy link
Contributor Author

This issue was moved to openhealthcare/cedar#8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants