| OHDSI Home | Forums | Wiki | Github |
Hi, we want to mess around creating some CDM-based web services but are not sure they are going to amount to anything worth inclusion in the OHDSI stack. I hate to pollute a bunch of WebAPI branches for that sort of thing. Is it possible to create a WebAPI Scaffolding repo that just has the WebAPI guts (and maybe a demonstration service like vocabulary) but is otherwise blank. Then people can use for sandbox service building. Or other approaches to meet this goal?
Thanks
Jon
Something else we threw around is moving to a more modular based design. I know it may be way out of scope for now, but I’m just throwing out an idea. It is pretty much based on what OpenMRS is doing. Instead of having one monolithic application, you have a library of modules which can be developed, contributed and installed into an OHDSI environment, without having to disturb OHDSI Core development/code, leaving that to base models and services.
Their architecture isn’t too different from WebAPI. It would provide some nice future flexibility to rapidly develop add-ons for small projects like we are developing, which may or may not be relevant to other OHDSI installations.
We’re working on our own internal project that is kinda-sorta related to functions that are in WebAPI, and we had a similar need where it would be nice if we could create a separate application from WebAPI but still leverage some of the features. I don’t have a specific solution to this but I’m just saying that we feel like we are in a similar boat. For now, we’re thinking of either working on our own branch or creating a fork.
-Chris
Thanks @Chris_Knoll! Glad know we’re not alone. We’ll probably just a put a fork in it as you’ve suggested. @fakeWebAPI 
