A somewhat common pattern in OMOP CDM architectures is to have separate schema's for the vocabulary and the OMOP CDM. We implemented that architecture initially and were unable to access the vocab schema in ROMOP. To resolve this issue, we copied over our vocab tables into the OMOP CDM schema. Our initial copy was unsuccessful so we had 1/40th of the concepts in the concept table and thus couldn't get the findPatients and similar functionality to work but this was resolved when we re-loaded the concept table. Achilles and other OHDSI tools ask at connection where the vocab schema and the cdm schema (and potentially other schemas exist). Ideally, ROMOP would be able to support this type of architecture.
A somewhat common pattern in OMOP CDM architectures is to have separate schema's for the vocabulary and the OMOP CDM. We implemented that architecture initially and were unable to access the vocab schema in ROMOP. To resolve this issue, we copied over our vocab tables into the OMOP CDM schema. Our initial copy was unsuccessful so we had 1/40th of the concepts in the concept table and thus couldn't get the findPatients and similar functionality to work but this was resolved when we re-loaded the concept table. Achilles and other OHDSI tools ask at connection where the vocab schema and the cdm schema (and potentially other schemas exist). Ideally, ROMOP would be able to support this type of architecture.