> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omophub.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> OMOPHub is a REST API platform for OMOP medical vocabularies - search 11M+ OMOP concepts across SNOMED CT, ICD-10, LOINC, RxNorm, and 120+ terminologies.

OMOPHub is a REST API platform that gives you programmatic access to the full OMOP vocabulary set - SNOMED CT, ICD-10, LOINC, RxNorm, and 120+ medical terminologies covering 11 million standardized OMOP concepts. No multi-gigabyte downloads, no local PostgreSQL setup, no quarterly vocabulary maintenance. Get an API key and start querying.

## What You Can Do

> [card] Search by meaning, not just keywords
>
> Full-text search with faceted filtering, fuzzy matching, autocomplete, and semantic similarity powered by OMOPHub's neural embeddings. Find concepts even when the phrasing doesn't match the canonical terminology.

> [card] Resolve FHIR codes to OMOP standard concepts
>
> Send a FHIR system URI + code (or a full `CodeableConcept`) and get back the OMOP standard concept, domain assignment, mapping type, and CDM target table - all in one API call. Handles `Maps to` traversal automatically.

> [card] Map between vocabularies
>
> Translate codes across SNOMED, ICD-10-CM, LOINC, RxNorm, HCPCS, NDC, and every other OMOP vocabulary. Single-code, batch (up to 100 per request), and `CodeableConcept` variants with OHDSI vocabulary preference ranking.

> [card] Traverse concept hierarchies
>
> Walk ancestor / descendant trees, expand concept sets, and explore non-hierarchical relationships (`Has ingredient`, `RxNorm has dose form`, etc.). Build phenotype definitions that catch all relevant codes, not just the ones you knew to look for.

> [card] Serve a standards-compliant FHIR Terminology Service
>
> `$lookup`, `$validate-code`, `$translate`, `$expand`, `$subsumes`, `$find-matches`, `$closure`, plus the OMOP-specific `$diff` for vocabulary-release comparison. R4, R4B, R5, and R6 on the same endpoint. Plugs into HAPI FHIR, EHRbase, and any FHIR-aware client.

> [card] Power AI agents with medical vocabularies
>
> MCP Server exposes 11 tools to Claude, Cursor, VS Code, and any MCP-compatible client. Eliminate hallucinated codes by grounding LLM outputs against the OMOP source of truth - multilingual queries are accepted and translated on the agent side.

## Who Uses OMOPHub

* **ETL developers** mapping source data into OMOP CDM tables
* **FHIR integrators** resolving clinical codes to standard OMOP concepts at the point of care
* **Researchers** building phenotype definitions and concept sets
* **Pharma RWE / HEOR teams** validating vocabulary coverage across studies
* **AI / LLM builders** grounding clinical AI pipelines against real terminology
* **openEHR / EHRbase teams** validating archetype terminology bindings against live vocabularies

More than 400 teams across academic medical centers, pharma, and healthcare-technology companies use OMOPHub.

## Choose Your Starting Point

> [card] [Quick Start](https://docs.omophub.com/quickstart.md)
>
> Get your API key and make your first request in 5 minutes.

> [card] [FHIR Integration](https://docs.omophub.com/guides/integration/fhir-integration.md)
>
> The complete FHIR story - FHIR Resolver for ETL, FHIR R4/R5/R6 Terminology Service for clients, and when to use which.

> [card] [FHIR Terminology Service](https://docs.omophub.com/api-reference/fhir-terminology/overview.md)
>
> Spec-conformant `$lookup`, `$translate`, `$validate-code`, `$expand`, `$subsumes` and OMOP-specific operations.

> [card] [AI & MCP Server](https://docs.omophub.com/ai/onboarding.md)
>
> Connect Claude, Cursor, VS Code, or any MCP client to medical vocabularies.

> [card] [EHRbase / openEHR](https://docs.omophub.com/guides/integration/ehrbase-openehr.md)
>
> Validate openEHR template terminology bindings against OMOP vocabularies via FHIR.

> [card] [HAPI FHIR](https://docs.omophub.com/guides/integration/hapi-fhir.md)
>
> Point a HAPI FHIR server at OMOPHub as a remote terminology backend.

> [card] [Python SDK](https://docs.omophub.com/sdks/python/overview.md)
>
> `pip install omophub` - search, map, resolve, and traverse from Python.

> [card] [Node.js / TypeScript SDK](https://docs.omophub.com/sdks/node/overview.md)
>
> `npm install @omophub/omophub-node` - typed client with discriminated `{ data, error }` returns.

> [card] [R SDK](https://docs.omophub.com/sdks/r/overview.md)
>
> `install.packages("omophub")` - R6 client for vocabulary access in R workflows.

## Quick Example

One API call per common pattern:

```bash Search theme={null}
curl "https://api.omophub.com/v1/search/concepts?query=type+2+diabetes&vocabulary_ids=SNOMED&page_size=3" \
  -H "Authorization: Bearer oh_your_api_key"
```

```bash FHIR Resolve theme={null}
curl -X POST "https://api.omophub.com/v1/fhir/resolve" \
  -H "Authorization: Bearer oh_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "system": "http://snomed.info/sct",
    "code": "44054006",
    "resource_type": "Condition"
  }'
```

```python Python theme={null}
import omophub

client = omophub.OMOPHub()

# Search by meaning (semantic embeddings)
results = client.search.semantic("heart failure with reduced ejection fraction")

# Resolve a FHIR code to its OMOP standard concept + CDM target table
resolved = client.fhir.resolve(
    system="http://snomed.info/sct",
    code="44054006",
    resource_type="Condition",
)
print(resolved["resolution"]["standard_concept"]["concept_name"])
print(resolved["resolution"]["target_table"])  # "condition_occurrence"

# Walk the concept hierarchy
descendants = client.hierarchy.descendants(201826, max_levels=2)
```

```r R theme={null}
library(omophub)

client <- OMOPHubClient$new(api_key = "oh_your_api_key")

# Get a concept
concept <- client$concepts$get(201826)
print(concept$concept_name)  # "Type 2 diabetes mellitus"

# Search concepts
results <- client$search$basic("type 2 diabetes", vocabulary_ids = "SNOMED")

# Map between vocabularies
mappings <- client$mappings$get(201826, target_vocabulary = "ICD10CM")
```

```ts TypeScript theme={null}
import { OMOPHub } from '@omophub/omophub-node';

const client = new OMOPHub();

// Search by meaning (semantic embeddings)
const { data: results } = await client.search.semantic('heart failure with reduced ejection fraction');

// Resolve a FHIR code to its OMOP standard concept + CDM target table
const { data: resolved } = await client.fhir.resolve({
  system: 'http://snomed.info/sct',
  code: '44054006',
  resourceType: 'Condition',
});
console.log(resolved?.resolution.standard_concept.concept_name);
console.log(resolved?.resolution.target_table); // "condition_occurrence"

// Walk the concept hierarchy
const { data: descendants } = await client.hierarchy.descendants(201826, { maxLevels: 2 });
```

```bash FHIR R4 theme={null}
curl "https://fhir.omophub.com/fhir/r4/CodeSystem/\$lookup?system=http://snomed.info/sct&code=44054006" \
  -H "Authorization: Bearer oh_your_api_key"
```

The `FHIR Resolve` call is the single-API-call workflow no other terminology server offers: source code in, OMOP standard concept + CDM target table out, with `Maps to` traversal and semantic fallback handled server-side. See the [FHIR Integration guide](https://docs.omophub.com/guides/integration/fhir-integration.md) for the full response shape and batch variants.

## Platform at a Glance

| | |
| - | - |
| **Concepts** | 11M+ standardized OMOP concepts |
| **Vocabularies** | 120+ including SNOMED CT, ICD-10, LOINC, RxNorm, NDC, HCPCS, ATC |
| **FHIR system URIs** | 20 canonical vocabulary URIs + OMOP unified omnibus |
| **FHIR operations** | `$lookup`, `$validate-code`, `$translate`, `$expand`, `$subsumes`, `$find-matches`, `$closure`, `$diff` |
| **FHIR wire versions** | R4, R4B, R5, R6 on the same endpoint |
| **Search** | Full-text, faceted, fuzzy, autocomplete, semantic |
| **SDKs** | Python (PyPI), R (CRAN), Node.js / TypeScript (npm), MCP Server (npm) |
| **MCP tools** | 11 tools for AI agent integration |
| **Response time** | Sub-50ms typical |
| **Vocabulary updates** | Synced with OHDSI ATHENA releases |

## Need Help?

> [card] [API Reference](https://docs.omophub.com/api-reference/introduction.md)
>
> Full endpoint documentation with request / response examples.

> [card] [Status](https://status.omophub.com)
>
> API uptime and performance.

> [card] [Dashboard](https://dashboard.omophub.com)
>
> Manage API keys, usage, billing, and enterprise plans.

> [card] [GitHub](https://github.com/omophub)
>
> Source for the SDKs, MCP Server, and reference implementations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.