OHDSI Home | Forums | Wiki | Github

WebAPI connectivity to CDM and OHDSI schemas

All,

This is an open request for feedback on a minor but important change we are considering on the way the WebAPI connects to the CDM and OHDSI schemas. Currently we require that both schemas reside on the same physical server.

Our challenge is in trying to use a non-traditional MPP database platform (think Netezza, Teradata, but in our case Microsoft PDW/APS) as the environment for the OHDSI schema. The persistence layers of WebAPI have some black-box type features that don’t leverage SQLRender to translate the SQL that is executed and the code it does generate simply isn’t compatible with Microsoft APS.

For this reason we are considering changing the WebAPI to allow for two separate connection strings to separate environments. This should not impact downstream applications of the WebAPI. This also will not impact environments where the connection string will remain the same for both schemas.

There is the potential for performance issues to arise when processing requires access to both schemas, however this will be determined on an environment by environment, and analysis by analysis basis.

Please let me know if there are any comments / issues with this approach.

@Frank,

This is an important change but it makes sense for a number of environments. It might even allow hybridization between PHI and non-PHI data, but that’d be a bit more involved.

Discuss on the call today?

Jon

t