Specifying a separate schema for OMOP Concept tables? about omoponfhir-omopv5-stu3-mapping HOT 1 OPEN

So, you are trying to have a separate database schema for patient related data while using same schema for common data tables. The mapping layer does not really care where the data is managed. omoponfhir-omopv5-jpabase project is managing the database connection. This project is hibernate based, which is configured to use the same database entity manager. I will need to take a look at the available hibernate config options to see if I can make the service models to point different entity manager. It might be possible by having different service entity manager and let those common table entities to point that.

I can provide you which files need to be edited if you are willing to have this. We would need to create a separate branch for this as this can be destructive edit.

from omoponfhir-omopv5-stu3-mapping.