Stream: cds hooks
Topic: CDS Service Provider
Virginia Lorenzi (Jul 22 2019 at 18:17):
I can see how we could create a service and test it using the CDS Hooks Service sandbox. However, if we have a service ready to go, we will need a production CDS Hooks Service Provider. Do these exist? In specific, looking to use CDS Hooks within informatics research projects.
Virginia Lorenzi (Jul 23 2019 at 02:42):
@Josh Mandel it seems that until there are real CDS Service Providers, CDS Hooks will not be useful. Or am I missing something? When will there be CDS Service Providers and who will they be?
Brendan Keeler (Jul 24 2019 at 03:36):
Do you mean EHR vendors?
Josh Mandel (Jul 24 2019 at 13:35):
Absolutely: a standard becomes useful when it's supported in real systems @Virginia Lorenzi . My understanding is that Epic and Cerner both have some support and growing, but perhaps @Isaac Vetter and @Dennis Patterson can comments (and others).
Isaac Vetter (Jul 24 2019 at 17:36):
Hi @Virginia Lorenzi - Epic has released our initial support for CDS Hooks, and Josh is correct that we intend to grow this support over time. Right now, as part of the Argonaut project, we're looking at potentially expanding our support for ordering hooks and suggestions.
Dennis Patterson (Jul 24 2019 at 18:32):
@Virginia Lorenzi , at Cerner we're building out support and are focused on ordering workflows within the context of Argonaut (mentioned above). We continue to be involved in CDS Hooks connectathon tracks and would love to hear more on your informatics use-cases.
Virginia Lorenzi (Jul 24 2019 at 19:55):
Thanks. But my understanding is the EHR is the CDS Client. I am trying to figure where a CDS Service I create could live. In the cdshooks specification it talks about CDS providers or external CDS providers. It seems I would want my CDS Service to live in one of those but there arent any except for the cdshooks sandbox - or are ehr vendors also providing the server side for cds service discovery? reference to spec:
"Call discovery endpoint¶
The CDS discovery endpoint provides the list of services a CDS provider supports, and the hooks a service should be invoked on. A CDS Client may configure their system to support a set of hooks at a certain location in their users work flow, or build a dynamic capability to interact with a CDS Service provider within a work flow. For the best end-user experience, this guide recommends a business analyst configure which hooks a CDS Client will support."
Isaac Vetter (Jul 24 2019 at 21:04):
Hey Virginia, I might be misunderstanding. Afaik, no ehr vendor is providing hosting for CDS Hooks services. Typically, a CDS Hooks service is hosted somewhere on the internet. Often contracted through one of the cloud providers.
Virginia Lorenzi (Jul 26 2019 at 15:31):
Are there any cds hooks already out there hosted somewhere? @Josh Mandel or others can you read my question and help me? I might just be confused.
Josh Mandel (Jul 26 2019 at 15:32):
This is a question about commercially available CDS providers that support CDS Hooks? I wonder if @Alex Tatiyants might be able to share thoughts on the Stanson/Premier side.
Alex Tatiyants (Jul 29 2019 at 21:24):
If the question is about how to host your CDS Hooks enabled services, we have ours hosted on our api.stansonhealth.com domain, which is a fairly common pattern.
Virginia Lorenzi (Sep 11 2019 at 06:30):
If the question is about how to host your CDS Hooks enabled services, we have ours hosted on our api.stansonhealth.com domain, which is a fairly common pattern.
thanks
Last updated: Apr 12 2022 at 19:14 UTC
