Stream: cds hooks
Topic: Limiting CDS Hook requests by vendor type
Joseph Sadlon (Sep 17 2021 at 01:09):
Hello, I am wondering what others have done, or if there is a recommendation to limit the CDS Hook requests sent from a client to a service. Specifically, if the service is a payer, have others implemented strategies to only make CDS Hook requests to a specific payer for orders where that payer is documented on the order or the patient chart?
Lloyd McKenzie (Sep 17 2021 at 02:01):
More generically, can a hook service specify pre-conditions for when they're interested in receiving a hook?
Lloyd McKenzie (Sep 17 2021 at 02:01):
I know this was talked about a few years ago, but there doesn't seem to be anything that's been added to the draft spec to support the capability.
Isaac Vetter (Sep 22 2021 at 16:02):
Hey Joseph, Lloyd's right. We've colloquially referred to this as "trigger guards". Generally, the work to standardize trigger guards would require pretty broad support for something CQL to enable robust expressions. Whereas, it seems like many CDS Clients already have a rule engine sufficiently capable of implementing these rules.
Isaac Vetter (Sep 22 2021 at 16:02):
Further, there's lots of reasons why a CDS Client shouldn't call a service depending upon the workflow. The CDS Client will always be better able to determine what the workflow should be; therefore, there will always need to be "trigger guards" that the service doesn't know about.
Isaac Vetter (Sep 22 2021 at 16:05):
The middle ground that we're discussing adding to the specification a textual description of the "trigger guard", proposed name is "usageRequirements" see this jira: https://jira.hl7.org/browse/FHIR-28651
Last updated: Apr 12 2022 at 19:14 UTC
