Stream: cds hooks
Topic: Interview Q5
Josh Mandel (Mar 03 2020 at 22:25):
Can you provide any specific examples of the external CDS services that may be evoked when an EHR triggers a hook? Are they different from previous CDS services used in internal systems?
In this context "internal" and "external" are really just labels about who's responsible for executing the decision-support logic. In other words, does a CDS Service developer need to translate its logic into a common language that EHRs can execute, or does it just communicate a set of results. CDS Hooks focused on the latter. This open up the possibility for CDS Services that continuously improve, or services that base their decisions on machien learning models, or external data sources like Health Information Exchange databases, or Prescription Drug Monitoring databases. In other words, a CDS Service can execute "interesting" logic, but can also join/combine EHR data with other "interesting" external sources.
Josh Mandel (Mar 03 2020 at 22:26):
We did a previous class project on Arden Syntax and learned more about the “curly braces” problem. From our understanding, CDS Hooks is not a solution to the curly braces problem. Instead, it offers a different approach entirely that is able to bypass the “curly braces” because the external CDS systems may use FHIR APIs to obtain any institution/patient specific information. Are we correct in our thinking here?
That's exactrly right, as I hope I've highlighted in the prior answer, too. CDS Hooks focuses on standardizing the API call and response, rather than the expression of logic.
Last updated: Apr 12 2022 at 19:14 UTC
