FHIR Chat · Interview Q4 · cds hooks

Stream: cds hooks

Topic: Interview Q4


view this post on Zulip Josh Mandel (Mar 03 2020 at 22:22):

Piggybacking off of our last question, it looks like only one hook is currently beyond a maturity level of 1, “patient-view.” Is this the only hook that has been tested by any actual CDS clients/hospitals?

This is the only formally standardized hook, but it's not the only hook being used! There's often (and there should be) a time lag between when definitions are tested/deployed and when they're formally standardized. This helps ensure that the standards process reflects capabilities that are working in the real world. (Overall, ensuring this level of quality is something that we still struggle with as a community -- but FHIR and CDS Hooks are really focused on getting to this level of real-world implementation in the process of maturing the standard.)

One example from last year is the "CDS Hooks for PAMA" guide, which uses the order-select and order-sign hooks. We've seen this successfully implemented by T-System (on the EHR side) and Evidence.care (on the CDS Service side), and we've seen a partial implementation from Athenahealth and Stanson.

view this post on Zulip Michaela Mirkovich (Mar 04 2020 at 22:07):

Is there a general timeline of how long it may take for a hook to progress through the maturity levels, or is this completely dependent on any issues identified with each individual hook?

view this post on Zulip Josh Mandel (Mar 05 2020 at 02:48):

It's mainly dependant on time to get real world implementation experience; more complex or workflow-intensive hooks of course should take longer.

view this post on Zulip Isaac Vetter (Mar 11 2020 at 04:34):

Michaela, to add on -- I think it's important to understand that "issues identified with [a] hook" is not what holds back maturity. Defining a perfect hook spec doesn't at all guarantee that a hook (or interoperability specification) will be used/mature. Rather, a mature spec/hook is often imperfect in that it's implementable and implemented by a wide variety of the community and industry. A perfect design isn't sufficient to produce a successful interoperability standard; rather, a successful standard is the crystallization of capabilities and intent of a community of implementers.


Last updated: Apr 12 2022 at 19:14 UTC