FHIR Chat · docs / PR #26 Decision activity proposal · cds hooks/committers

Stream: cds hooks/committers

Topic: docs / PR #26 Decision activity proposal

Github Notifications (May 06 2017 at 10:41):

isaacvetter commented on PR #26

Hey Guys,

This is a really neat idea. I think that a decision returning an EHR activity is great functionality and we should try to make it happen.

1. I'm not sure that a hook and an activity are actually the same thing. For example, take a look at the proposed hooks, these seem reasonable as hooks, but aren't specific enough to identify an activity.

2. How does the decision define the activity's "parameters". I think that your example specifies a CarePlan as input to a medication-prescribe activity. What does that mean? Is there a medication that should be pre-populated into the EHR's medication-prescribe activity?

Isaac

Github Notifications (May 18 2017 at 17:49):

bkaney synchronized PR #26

Github Notifications (May 18 2017 at 17:53):

bkaney synchronized PR #26

Github Notifications (May 18 2017 at 18:28):

bkaney commented on PR #26

Hi @Isaac Vetter --

I'm not sure that a hook and an activity are actually the same thing. For example, take a look at the proposed hooks, these seem reasonable as hooks, but aren't specific enough to identify an activity.

I see what you mean. I was thinking we avoid having both a "hook catalog" and then another "post hook catalog". Especially after observing the contents both describe what I think of as activities. Instead, there would be a single catalog where the usage context would be as a "hook" or "next action".

How does the decision define the activity's "parameters". I think that your example specifies a CarePlan as input to a medication-prescribe activity. What does that mean? Is there a medication that should be pre-populated into the EHR's medication-prescribe activity?

I updated the example to be a bit more simplified, including expanding the resources inline. Have a look and see if this addresses your questions.

Github Notifications (May 18 2017 at 18:31):

bkaney synchronized PR #26

Github Notifications (Jan 27 2018 at 23:40):

kpshek commented on PR #26

Given that we've moved decisions out of 1.0, and considering that our specification has changed quite radically (eg, slate -> mkdocs) since this PR was opened, I'm closing this.

When we tackle decisions post 1.0, we can look at this PR for great ideas for possible implementation strategies.

Github Notifications (Jan 27 2018 at 23:40):

kpshek closed PR #26

Last updated: Apr 12 2022 at 19:14 UTC