Hello, community! As my first post in the OHDSI forum, I would like to introduce a research project I’ve been working on related to OHDSI vocabularies, and any help or feedback would be greatly appreciated!
I work for the University of Leicester; however, this research is my own. I’ve been building a terminology server that offers multiple vocabularies, ontological exploration, semantic similarity search, auto-completion, and related workflow components using an efficient API. It currently supports multiple vocabularies, including ontologies like HPO and SNOMED, genetic symbols like Ensembl and HGNC, and pathways like Reactome. As a recent addition, it now supports OHDSI.
However, unlike many other ontologies, OHDSI vocabulary is actually many ontologies combined into one, where each concept and relationship receives an OHDSI ID but still keeps its own original properties. I wonder if there is an official mapping between the different concepts, relationships, etc. of various sub-vocabularies inside the OHDSI vocabulary? Is my current implementation correct or efficient, or does it have any important issues?
The software itself is open source, hosted at GitHub - Firefox2100/biomedical-terminology-service: This is a FastAPI service for using with biomedical terminologies, such as ontologies or vocabularies. · GitHub. One demo server is hosted by University of Leicester, under separate branding but running the same code, at https://similarity.cafevariome.org/. Please feel free to check out the software or the demo implementation, and any feedback or help is appreciated!