A requested topic for the next Architecture Call:
Dealing with DB access needs that are not appropriate for WebAPI
There are a few things OHDSI apps may do that may fall outside of what would typically go into an API. The first example that comes to mind, for ACHILLES and HERACLES, is the creation of the ACHILLES_ANALYSIS and ACHILLES_RESULTS tables (and the parallels for HERACLES). I don’t think we want a WebAPI call that creates tables.
HERMES and CIRCE both use existing tables and can live entirely on WebAPI supplied goodness. Not all apps may be as fortunate, so wanted to discuss.
Thanks,
Jon