FHIR Chat · docs / Issue #192 Associating a card response to a partic... · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #192 Associating a card response to a partic...


view this post on Zulip Github Notifications (Mar 30 2018 at 18:52):

yashaskram opened Issue #192

I was thinking about the need to associate a card response to a particular resource in context when there is more than one resource (FHIR bundle) in the context. I am looking for input from this group on this.

An option to tackle this currently, is to send one resource in context per CDS Hooks request and so response by default can be associated to the resource in context but would involve who ever making hooks request to establish this associated back through the hookInstance

One of the use case which triggered this post is suggested content notification use case. Let's take the example of results review hook, where the results review CDS service's jobs is to responds back with info card w/links to results interpretation content (only when the content exist and suggested) for an particular observation in context. The ultimate need for above is the case when you want to show the Card Response as an icon (on mouse over shows the card response and on clicking opens the knowledge content) next to the particular lab result in Context. First question, is if CDS hooks the right solution to tackle this use case?

![results review](https://user-images.githubusercontent.com/10819175/38149606-2ba194e8-3429-11e8-8de0-2ae7c7c585b3.jpg)

If so, what can be the approach? extension or one request per resource or ?

view this post on Zulip Github Notifications (Mar 30 2018 at 18:58):

yashaskram edited Issue #192

I was thinking about the need to associate a card response to a particular resource in context when there is more than one resource (FHIR bundle) in the context. I am looking for input from this group on this.

An option to tackle this currently, is to send one resource in context per CDS Hooks request and so response by default can be associated to the resource in context but would involve who ever making hooks request to establish this association back through the hookInstance

One of the use case which triggered this post is suggested content notification use case. Let's take the example of results review hook, where the results review CDS service's jobs is to responds back with info card w/links to results interpretation content (only when the content exist and suggested) for an particular observation in context. The ultimate need for above is the case when you want to show the Card Response as an icon (on mouse over shows the card response and on clicking opens the knowledge content) next to the particular lab result in Context. First question, is if CDS hooks the right solution to tackle this use case?

![results review](https://user-images.githubusercontent.com/10819175/38149606-2ba194e8-3429-11e8-8de0-2ae7c7c585b3.jpg)

If so, what can be the approach? extension or sending one resource in context per CDS Hooks request or ?


Last updated: Apr 12 2022 at 19:14 UTC