European Health Data Space

The vocabulary layer
your EHDS pipeline
can't afford to skip

EHDS mandates secondary use of health data across the EU. OMOP CDM is the recommended semantic standard. Your pipeline needs the vocabularies - reliably, programmatically, now.

March 2025
EHDS Regulation entered into force
2029
EHR secondary use mandatory across EU
2031
Clinical trials & genomic data in scope
Standard
OMOP CDM explicitly recommended for secondary use

The problem

Three things standing betweenyour data and EHDS compliance

Building an EHDS-ready pipeline means solving vocabulary access before anything else.

01 -

ATHENA downloads don't scale

5 GB+ compressed. Millions of rows. Local PostgreSQL required. Every team does it separately. Every 6-months you do it again.

02 -

openEHR need OMOP mappings

SNOMED CT bindings are standard in openEHR. Translating them to OMOP standard concepts programmatically, at scale - is where pipelines stall.

03 -

EHDS timelines are not optional

Healthcare organisations across 27 EU member states have a regulatory deadline. Vocabulary infrastructure that blocks your ETL is a compliance risk.

How OMOPHub helps

Vocabulary infrastructure,without headache

One REST API. 100+ OMOP vocabularies. No setup, no local database, no 6-months download cycle.

Concept lookup

Resolve any concept in milliseconds

Query SNOMED CT, ICD-10, LOINC, RxNorm, and 100+ vocabularies via a single endpoint. Your ETL pipeline calls the API instead of querying a local database that may be months out of date.

Cross-vocabulary mapping

SNOMED → OMOP standard concepts, resolved

openEHR archetypes are bound to SNOMED. OMOPHub returns the corresponding OMOP standard concept with domain, class, and relationship data - so your pipeline never guesses.

Semantic search

Find the right concept from clinical text

BioLORD-powered semantic search understands clinical language. Map free text or ambiguous terms to the correct OMOP concept, ready for EHDS-compliant secondary use analytics.

SDK & MCP Server

Integrate in minutes, not days

Python SDK on PyPI, R package on CRAN, and an MCP Server for AI-assisted workflows. pip install omophub and your EHDS pipeline has vocabulary access on the next deploy.

Built for European healthcare

Reliable by design

Healthcare data pipelines run on schedules. Vocabulary lookups need to work when your ETL runs at 2 AM.

GDPR-aligned data handling

OMOPHub serves vocabulary metadata only - no patient data flows through our infrastructure. GDPR Article 5 considerations are built into the architecture.

Always-current vocabulary versions

Vocabularies are updated quarterly in line with OHDSI ATHENA releases. No manual downloads. Your pipeline uses the same version as the OHDSI community.

Production-grade uptime

Built on Google Cloud Run with Redis caching. Response times under 50ms for concept lookups. Uptime SLAs available on Pro, Scale and Enterprise plans.

Audit-ready access controls

API key scoping, usage logs, and per-key rate limits. Scale and Enterprise plans include access audit logs. Ready for EHDS data governance requirements.

Get started

Your EHDS pipeline deserves
better vocabulary infrastructure

Trusted by 100+ healthcare data teams. Free tier available.