OMOPHub

OMOPHub is a hosted API that provides programmatic access to the OHDSI OMOP vocabularies. The service indexes more than 11 million concepts drawn from over 120 vocabularies, among them SNOMED CT, ICD‑10‑CM, LOINC and RxNorm. A free tier is available that allows up to 3 000 API calls each month without requiring a credit card.

The platform is built for healthcare data teams, developers and researchers who need to look up, map or resolve medical codes without maintaining a local copy of the ATHENA releases. Typical use cases include ETL pipeline integration, clinical research analytics, EHR enhancement and AI‑assisted mapping. You send a term, a code or a concept identifier to the API and receive structured JSON that contains the matching concept IDs, preferred terms, hierarchy relationships and any cross‑vocabulary mappings. For example, a semantic search request for “acute kidney injury” can return the SNOMED CT concept ID, its domain, and related concepts; a mapping request for ICD‑10‑CM code N17.9 returns the corresponding OMOP concept and the “Maps to” relationship. The FHIR‑to‑OMOP endpoint accepts a FHIR code (such as a LOINC observation) and returns the appropriate OMOP measurement concept, enabling direct integration with FHIR‑based workflows.

Interaction with OMOPHub can be done through raw REST calls or via the officially supported SDKs for Python, R and TypeScript/Node. The SDKs are type‑safe and include auto‑completion, so a developer can write code like `client.search.basic("myocardial infarction", vocabulary_ids=["SNOMED","ICD10CM"], page_size=50)` to retrieve up to 50 matching concepts across selected vocabularies. Another SDK method, `client.concepts.get(id, include_relationships=True)`, returns a concept record together with its parent‑child and mapping relationships. A separate endpoint lists available vocabulary versions, and the service automatically synchronizes with the latest OHDSI ATHENA releases, removing the need for manual updates.

Security is handled through API‑key authentication, HTTPS encryption in transit and optional audit logging on higher‑tier plans. Because the service only processes terminology data and does not accept patient‑identifiable information, it is positioned as a vocabulary lookup tool rather than a full PHI‑handling service. The free plan's 3 000‑call limit makes it suitable for development, testing or low‑volume production, while larger workloads would need a paid plan whose pricing is not disclosed on the site.

Key features

• Access to 11 M+ concepts from 120+ vocabularies via a single managed API