OMOPHub: Medical Terminology API and MCP

Inputs and outputs

The official service description covers concepts and mappings across vocabularies such as SNOMED CT, ICD-10, LOINC and RxNorm, alongside FHIR-to-OMOP resolution. Requests can start with terminology or a code; results provide concepts, identifiers or mappings that your application must interpret in context.

The provider also documents SDK and MCP access. A terminology match does not itself establish that a clinical statement, billing code or treatment decision is correct.

Calls, search features and paid limits

The pricing page lists 3,000 API calls per month on Free and 50,000 on Pro at $39/month. It distinguishes basic semantic search from the full search and bulk-operation capabilities on paid plans. Free also lists a sustained two-requests-per-second rate limit.

Higher plans increase call allowances and other features. Read each limit separately: an unrestricted rate-limit label does not make a finite monthly call allowance unlimited.

Validate mappings before operational use

Use a non-sensitive test set whose expected concepts and vocabulary versions you already know. Check standard-concept status, mapping direction, unmapped values and version changes before using the results in a production data pipeline.

Review vocabulary licenses and your organization's data-handling requirements. This profile has not independently audited security or compliance claims and does not authorize sending patient information to the service.

Start with a documented lookup

Inspect the concept-search documentation and compare its result with your known reference. Only then consider a bulk mapping or agent integration. We have not used an API key, processed patient records or validated a clinical mapping through OMOPHub.