Stream: cds hooks
Topic: Java Client library
Travis Cummings (Nov 12 2016 at 05:45):
Would anyone be interested in collaborating on a Java client library for CDS hooks?
Kevin Shekleton (Nov 12 2016 at 17:08):
I'd be happy to work on that
Josh Mandel (Nov 13 2016 at 16:00):
It'd be instructive to see if we can start from an OpenAPI (Swagger)-generated client.
Josh Mandel (Nov 13 2016 at 16:00):
It may be a non-starter, but I think it's worth a quick experiment.
Nikolai Schwertner (Nov 17 2016 at 15:37):
Are you thinking of an EHR-facing client/toolkit component (i.e. for vendors and reference implementations)? Or something to help with the CDS services components?
Kevin Shekleton (Nov 17 2016 at 17:45):
I think there are opportunities for both EHRs and CDS service providers (not necessarily the same library). However, while Travis didn't explicitly state this, I assumed he was referring to CDS services (since he recently worked on one)
Isaac Vetter (Nov 17 2016 at 17:46):
and there's a lot more cds-service use cases than servers.
Kevin Shekleton (Nov 17 2016 at 17:48):
Josh is correct though in that the reason why we wrote the Swagger API was to enable generated clients in a multitude of languages (for those that want that sort of thing)
Nikolai Schwertner (Nov 17 2016 at 21:31):
Cool. I am interested in exploring generated JS and Python clients to see if they could make the job of scaffolding a CDS service a tad easier (at least as a starting point). https://github.com/swagger-api/swagger-codegen looks like a reasonable tool. Also https://github.com/swagger-api/swagger-js https://github.com/wcandillon/swagger-js-codegen and https://github.com/Yelp/bravado. Does anyone here have experience with these to share?
Travis Cummings (Dec 01 2016 at 02:58):
Yes I also like Josh's suggestion to try a generated client. I'll try to produce a generated Java client from the Swagger so we can evaluate if more functionality would be helpful beyond generation.
Last updated: Apr 12 2022 at 19:14 UTC