Stream: cds hooks
Topic: CDS Connect and CDS Hooks Connectathons
Chris Moesel (Feb 21 2020 at 19:23):
The CDS Connect project is thinking of participating in a Connectathon. What we have is:
- CQL Services: A Node.js based service for exposing arbitrary CQL as CDS Hooks services (unlike the Java variant, it does not use PlanDefinition).
- CQL Testing: A tool for building and running automated unit tests for CQL libraries.
- CDS Authoring Tool: A graphical tool for building (mostly) rules-based CQL logic
- CDS Repository: An online repository for sharing standards-based artifacts.
As far as CDS Hooks goes, CQL Services seems the best fit, but maybe CQL Testing might be interesting to some as well. Are CDS Hooks tracks generally broad enough that it might make sense for us to participate? I'm thinking maybe we try a few of our own services with EHR vendors that can invoke hooks services, and/or we help others convert their CQL into CDS Hooks services if they're interested. Or do you anticipate very specific tracks for which that type of participation might not be relevant?
Isaac Vetter (Feb 23 2020 at 05:22):
@Chris Moesel , Yes. A cds hooks connectathon easily incorporates CQL Services and you'd be welcomed in our connectathon tracks.
Isaac Vetter (Feb 23 2020 at 05:23):
@Dennis Patterson , @Bryn Rhodes - do you agree?
Bryn Rhodes (Feb 23 2020 at 23:23):
Absolutely, would love to see it!
Dennis Patterson (Feb 24 2020 at 15:07):
Since CDS Hooks is agnostic of the underlying algorithm implementation, you're welcome to use the track for leveraging the API to integrate with clients and having cql services expose themselves as CDS Hooks Services. There may not be anything in the track description specific to CQL, but API usage is encouraged using a variety of implementations!
Chris Moesel (Feb 24 2020 at 15:26):
Thanks all. I figured this was the case, but wanted to get confirmation before formally requesting the travel from AHRQ. Looking forward to it!
Isaac Vetter (Feb 27 2020 at 04:29):
@Chris - Bryn, Dennis and I chatted about the May connectathon this morning and are planning some scenarios within the CDS Hooks track around upcoming CDS Hooks features -- including the interoperable override reasons by which a cds service can provide acknowledgement reasons to an EHR and a feedback service which an EHR informs a remote CDS service of the end-result of a cds suggestion.
Is this beta functionality of interest to you? We'll hoping to learn from implementor experience in May.
Chris Moesel (Feb 27 2020 at 05:12):
@Isaac Vetter -- that's certainly some interesting functionality and looks like some good capability for CDS Hooks to explore. So I'm interested in that regard. That said, I don't know if I'll be able to bring any of that to the table. We have several balls in the air at once and I don't know if implementing those features will gain sufficient priority by May. I think we were hoping just to do some more basic integration testing using features defined in CDS Hooks 1.0. But... you never know!
Last updated: Apr 12 2022 at 19:14 UTC
