FHIR Chat · docs / Issue #365 Batch-mode: Retrieve multiple CDS-cards... · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #365 Batch-mode: Retrieve multiple CDS-cards...


view this post on Zulip Github Notifications (Jul 12 2018 at 07:59):

jmehlbrech opened Issue #365

_Technical scenario_: I would like one client to retrieve a lot of potential CDS-cards from one CDS-service in a performant way (one request-one response)
_Scenario_: I would like to retrieve the status for all inbound-patients of a ward - or for the whole hospital to enable visualizing overviews.
_Issue_: A CDS-Card does not provide context information

  • While it is possible to provide an own hook like this to enable requesting multiple contexts
    “context”: {
    { “patientId”: “1”, “encounterId”: “abc” },
    { “patientId”: “2”, “encounterId”: “def” },
    // ... more....
    }

  • A response for such a request would have multiple CDS-Cards - missing context info - or a way to retrieve it

view this post on Zulip Github Notifications (Jul 12 2018 at 13:40):

kpshek commented on Issue #365

I talked with @jmehlbrech offline about this and to provide more color to this issue, I recall having discussions around this topic previously; though, I cannot find any existing issues around this. The gist of this issue is that cards have no reference to a resource/entity/thing back in the EHR.

For instance, imagine a patient-list-view hook that for its context, informs the CDS Service of each patientId for the patients the user is viewing (see @jmehlbrech's context noted above). The resultant CDS cards have no reference to those individual patients in the list. So, the EHR has no ability to associate an icon/card/etc to individual patients within the list.

Another example would be on some imagined medication-list-view hook where the hook is invoked when the user is viewing all of the medications the patient is taking. The EHR again has no ability to associate the resultant CDS cards with individual medications.


Last updated: Apr 12 2022 at 19:14 UTC