[go: up one dir, main page]

Search, map, and resolve medical vocabularies

The terminology layer for FHIR, OMOP, and healthcare AI with 11M+ concepts through one managed API.

Your agent

Search, map, and resolve in one conversation.

Your agent can find standard concepts, retrieve vocabulary mappings, and resolve FHIR codes with OMOPHub’s MCP tools.

Question: Find a standard concept for acute kidney injury.

Tools: search_concepts, get_concept.

Answer: Acute kidney injury is a valid standard SNOMED CT concept in the Condition domain.

Question: Map ICD-10-CM N17.9 to that concept.

Tools: get_concept_by_code, map_concept.

Answer: Yes. N17.9 (OMOP 35209273) maps to 197320 through “Maps to”.

Question: Where does a serum creatinine Observation (LOINC 2160-0) go in OMOP?

Tools: fhir_resolve.

Answer: Use measurement with standard concept 3016723 for serum/plasma creatinine.

Find a standard concept for acute kidney injury.

Medical terminology for your agents, applications, and data pipelines. See how

  • ChatGPT
  • Claude
  • Cursor
  • Codex
  • Grok Bot

Used by researchers and developers at

Developer-first Experience

Stop managing vocabulary databases. Built for healthcare developers
who want API access to ATHENA vocabularies without the infrastructure overhead.

OMOP-Compliant

Access to OHDSI ATHENA vocabularies - SNOMED CT, ICD-10, LOINC, RxNorm, and 120+ more.

  • Synced with official ATHENA releases
  • Cross-vocabulary concept mappings

Developer-First

Production-ready SDKs for Python, R, and TypeScript. Query vocabularies without standing up a local database.

  • Type-safe SDKs with auto-completion
  • No database instance required

Security Controls

Vocabulary lookups without patient data. API key authentication and encrypted connections.

  • Audit logging on eligible plans
  • HTTPS encryption in transit

Everything You Need for Healthcare Data

From concept search to version management, our comprehensive API suite handles all your medical vocabulary needs.

Powerful Vocabulary API

Search, retrieve, and explore medical concepts across 120+ vocabularies with advanced filtering and relationship mapping.

python
import omophub

client = omophub.OMOPHub()

# Search across multiple vocabularies
results = client.search.basic(
    "myocardial infarction",
    vocabulary_ids=["SNOMED", "ICD10CM", "ICD9CM"],
    page_size=50,
)

# Get concept details with relationships
concept = client.concepts.get(
    4329847,
    include_relationships=True,
)

Version Management

OMOPHub.com provides hosted and managed OHDSI Standardized Vocabularies access. Leave the complexity to our experts while you focus on building your applications with automated updates and version management.

python
import omophub

client = omophub.OMOPHub()

# List available vocabulary versions
versions = client.vocabularies.list()

# Get vocabulary details
snomed = client.vocabularies.get("SNOMED")

print(f"SNOMED version: {snomed['vocabulary_version']}")
print(f"Concept count: {snomed['concept_count']}")

Built for Healthcare Workflows

From ETL automation to AI-assisted mapping, see how healthcare teams skip the vocabulary database setup and ship faster.

ETL Pipeline Integration

Transform and standardize healthcare data from multiple sources

  • Automated concept mapping across vocabularies
  • Real-time validation and error detection
  • Scalable batch processing for large datasets
  • Audit trails for regulatory compliance
11M+ concepts/hour
Processing Speed
99.7%
Accuracy Rate

Frequently Asked Questions

Everything you need to know about OMOPHub and healthcare terminology APIs.

OMOPHub provides access to all major medical vocabularies including SNOMED CT, ICD-10-CM, ICD-10-PCS, LOINC, RxNorm, HCPCS, NDC, Read Codes, MeSH, and many more. We sync with official OHDSI ATHENA releases to ensure you always have access to the latest terminology updates. Note: Licensed vocabularies such as CPT and MedDRA are not available on OMOPHub due to license restrictions.
OMOPHub is a vocabulary lookup service intended for medical codes, concept IDs, and search terms without patient-linked information. Do not send Protected Health Information (PHI) to the API. For workflows that do not send PHI, a Business Associate Agreement (BAA) is typically not required; the requirement depends on your architecture and data flow. We apply security controls including HTTPS encryption in transit and API key authentication; audit logging is available on eligible plans. If your architecture would route PHI through the API, contact us before integrating. See Security & Data Handling.

Getting started is simple:

  1. Sign up for a free account at dashboard.omophub.com
  2. Generate an API key from your dashboard
  3. Install our SDK for your preferred language (Python, R, or TypeScript)
  4. Start making API calls

See our quickstart guide for detailed steps, commands, and code examples.

OMOPHub offers a free plan with 3,000 API calls per month and full API access. Need more? Check out our pricing plans.
Our API is optimized for speed with typical response times under 50ms for most queries. We use intelligent caching, optimized database indexes, and global edge distribution to ensure fast, reliable access to vocabulary data regardless of your location.
No, OMOPHub is an independent service and is not affiliated with OHDSI or ATHENA.
Yes - this is one of our most popular use cases. During ETL development, you often need to look up concepts, validate mappings, and explore vocabulary hierarchies. With OMOPHub, you can do this programmatically without going through governance to access a CDM database or standing up your own vocabulary tables. Once your ETL is production-ready, you can continue using the API or switch to a local vocabulary deployment.

Experience reimagined.
Start today.