omoponfhir / omoponfhir-omopv5-stu3-mapping Goto Github PK

Hello again,

I was wondering if there was a way to configure this a database that uses multiple schemas that separate the patient-specific data from the vocabulary tables. Here, the patient data in one schema (i.e. "person", "drug_exposure", conditions, visits, etc.) still has foreign keys pointing to another separate schema for the OHDSI Vocabulary tables (concept, concept_relationship, concept_ancestor, domain, etc.).

For our implementation we would like this ability since we have two separate schemas of patient info stored on one RDS instance. Both sets of patient info follow the common data model and we are able to switch between them successfully using the JDBC variable in the Dockerfile. Ideally, though, since the "concept" and its related tables are both pretty large and we want to optimize the storage space available on the RDS instance, it would be even better if we could hold all the vocabulary tables in one schema instead of having it duplicated in both schemas of patient data. Do you know if there's any way of supporting this type of set up?

Thanks!
-Eric