FHIR Chat · docs: pull request 26: Decision activity proposal · cds hooks/committers

Stream: cds hooks/committers

Topic: docs: pull request 26: Decision activity proposal

Github Notifications (Mar 30 2017 at 15:04):

bkaney opened pull request 26

This implements point 3 from https://github.com/cds-hooks/docs/issues/18#issuecomment-282141134

This adds a new concept to the decision return from CDS service to hint at a subsequent action and related resources. This also generalizes the name of "hook catalog" to be called "activity catalog", as it serves as describing actions, of which could be used as web hooks.

Github Notifications (Apr 20 2017 at 20:03):

jmandel commented on pull request 26

Thanks @bkaney! I think the key contributions here are:

1. Generalizing the activities catalog to work in both directions: an EHR can tell a service "hey, the user is doing this activity", and an app can tell the EHR "hey, here's a good activity for the user to do next".

2. Updating the decision data model to support this communication back to the EHR

I'm definitely in favor.

I noticed, in the process, that our docs for decisions.create are missing something: they specify a list of ids, but what we actually need (and the way our test implementations work) is a list of resources. Does this match your expectations?

Github Notifications (Apr 20 2017 at 20:44):

bkaney commented on pull request 26

I noticed, in the process, that our docs for decisions.create are missing something: they specify a list of ids, but what we actually need (and the way our test implementations work) is a list of resources. Does this match your expectations?

Yea, they could be resources. However, as we aren't the FHIR server persisting the resource, we'd have to figure out a way to reference them (in the actions structure). Perhaps the CDS service would mint an ID for each resource and use #anchor-tag style contained reference?

Last updated: Apr 12 2022 at 19:14 UTC