Install Jentic One Beta

Connect the OMOPHub Healthcare Vocabulary API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OMOPHub Healthcare Vocabulary API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fomophub.com%2Fomophub" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fomophub.com%2Fomophub" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with OMOPHub Healthcare Vocabulary API.

Resolve a concept by its vocabulary-specific code, such as an ICD10CM or LOINC code, and return its OMOP concept with synonyms and relationships

Map concepts to a target_vocabulary with a mapping_type of direct, equivalent, broader, or narrower, singly or in batch

Translate a FHIR Coding system and code, or a CodeableConcept, into a source concept, standard concept, and target CDM table

Walk a concept's ancestors, descendants, hierarchy, and the path between two concepts with max_levels and include_distance

GET STARTED

Start building with OMOPHub Healthcare Vocabulary API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use OMOPHub Healthcare Vocabulary API for, with concrete tasks.

★ Clinical coding assistant agent

A data engineer's agent maps messy source codes into the OMOP Common Data Model. Through Jentic it searches for 'map a medical code to an OMOP standard concept', loads the OMOPHub concept-by-code operation, and resolves each source code, then maps it to the standard vocabulary, with the bearer key attached at call time. Semantic search results are treated as suggestions for review, as the spec states, not automatic clinical coding decisions.

Call GET /concepts/by-code/{vocabularyId}/{conceptCode} with vocabularyId 'ICD10CM' and conceptCode 'E11.9', then POST /concepts/map with target_vocabulary 'SNOMED' and source_concepts set to the returned concept id

FHIR to OMOP ETL

An ETL pipeline receiving FHIR resources needs each coding resolved to the right standard concept and CDM table. POST /fhir/resolve takes a FHIR Coding system and code with an optional resource_type such as Condition or Observation and returns the source concept, standard concept, target CDM table, and an optional mapping quality signal. POST /fhir/resolve/batch handles many codings in one call, and POST /fhir/resolve/codeable-concept resolves a CodeableConcept with its text.

POST /fhir/resolve/batch with codings from a FHIR Bundle, resource_type 'Condition', and include_quality true, then record the standard concept and CDM table for each

Cohort definition by concept hierarchy

Researchers building a cohort need every concept under a parent condition or drug class. GET /concepts/{conceptId}/descendants returns the concepts below a parent with max_levels and include_distance, filtered by vocabulary_ids and domain_ids, and GET /concepts/{conceptId}/ancestors walks the other way. POST /concepts/hierarchy/batch runs several hierarchy queries at once for a concept set.

Call GET /concepts/{conceptId}/descendants for the Type 2 diabetes mellitus concept with domain_ids 'Condition' and include_distance true, and return the concept set

Mapping quality review

Before loading a source_to_concept_map, a team checks how well its source vocabulary maps. GET /mappings/coverage reports coverage between a source_vocabulary and target_vocabulary, GET /mappings/quality/{sourceVocab}/{targetVocab} returns quality figures for the pair, and POST /mappings/validate verifies a set of mappings so errors are caught before they reach the CDM.

Call GET /mappings/coverage with source_vocabulary 'ICD10CM' and target_vocabulary 'SNOMED', then POST /mappings/validate with the team's draft mappings

Key Endpoints

58 endpoints — the omophub healthcare vocabulary api looks up, searches, and maps medical concepts across the ohdsi standardized vocabularies, including snomed, icd-10, loinc, and rxnorm.

METHOD

PATH

DESCRIPTION

GET

/concepts/by-code/{vocabularyId}/{conceptCode}

Get a concept by vocabulary code

GET

/concepts/{conceptId}

Get a concept by id

POST

/concepts/map

Map concepts between vocabularies

GET

/concepts/{conceptId}/descendants

Get concept descendants

GET

/search/concepts

Search concepts

GET

/search/semantic

Search concepts by meaning

POST

/fhir/resolve

Resolve a FHIR Coding

GET

/vocabularies

List vocabularies

GET

/concepts/by-code/{vocabularyId}/{conceptCode}

Get a concept by vocabulary code

GET

/concepts/{conceptId}

Get a concept by id

POST

/concepts/map

Map concepts between vocabularies

GET

/concepts/{conceptId}/descendants

Get concept descendants

GET

/search/concepts

Search concepts

GET

/search/semantic

Search concepts by meaning

POST

/fhir/resolve

Resolve a FHIR Coding

GET

/vocabularies

List vocabularies

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring OMOPHub by hand means sending a bearer key, choosing among many search and mapping routes, pinning a vocab_release, and handling CPT4 licensing errors. Through Jentic you install once, import OMOPHub from the API Directory, store the key once, and your agent calls it.

Permission scoping

OMOPHub puts the concept id and vocabulary id in the URL path, such as /concepts/{conceptId} and /vocabularies/{vocabularyId}, so a rule can pin your agent to one vocabulary or concept and the operations you pick. Every operation reads or computes over vocabularies, so the choice is about which lookups the agent may run.

Credential isolation

Your OMOPHub API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'map an ICD-10 code to SNOMED' or 'resolve a FHIR coding', and Jentic returns the matching OMOPHub operation with its input schema, including vocabularyId, conceptCode, and target_vocabulary, so the agent calls it correctly.

FAQs

Specific to using OMOPHub Healthcare Vocabulary API through Jentic.

What authentication does the OMOPHub API use?

Per its OpenAPI spec, the OMOPHub API uses HTTP bearer authentication with your API key in the Authorization header. Two routes are open without a key: the API information root and /health. CPT4 concepts additionally need the key owner to complete annual UMLS validation in the OMOPHub Dashboard. Through Jentic the key is stored by your own instance and attached at call time.

Can I map ICD-10-CM codes to SNOMED with the OMOPHub API?

Yes. Resolve the source code with GET /concepts/by-code/{vocabularyId}/{conceptCode}, then call POST /concepts/map with target_vocabulary set to SNOMED, the concept ids in source_concepts or raw codes in source_codes, and an optional mapping_type of direct, equivalent, broader, or narrower. POST /concepts/map/batch handles many mapping_requests in one call.

What are the rate limits for the OMOPHub API?

The OpenAPI spec does not specify rate limits. Check the OMOPHub documentation at https://omophub.com for current limits on your plan.

Is there an OMOPHub MCP server?

You don't need an MCP server to give your agent OMOPHub. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the concept, search, and mapping operations it needs on demand without loading another server's tool definitions into its context.

How do I resolve a FHIR coding through Jentic?

Search Jentic for 'resolve a FHIR coding to an OMOP concept', load the OMOPHub FHIR resolve operation, and execute it with the coding's system and code plus an optional resource_type such as Condition. The response carries the source concept, standard concept, and target CDM table. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Which vocabularies are restricted on OMOPHub?

Per the spec, CPT4 needs annual UMLS validation and the validation expires each January 30 UTC. Unlicensed direct or CPT4-only requests return 403 vocabulary_restricted, while mixed search filters leave out CPT4 and return the accessible vocabularies. GPI and MedDRA are not available.

Can I limit what my agent is allowed to do with the OMOPHub API?

Yes. Write a rule that allows only the concept-by-code lookup and GET /concepts/{conceptId}/mappings, and the agent can resolve source codes and read their mappings but cannot run bulk or semantic search, and every call it makes is logged.

OMOPHub Healthcare Vocabulary API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyHealthcareClinical Databearer58 EndpointsREST

For Agents

Search and resolve OMOP medical concepts, map codes between SNOMED, ICD-10, LOINC, and RxNorm, walk concept hierarchies, and translate FHIR codings into standard OMOP concepts.

Use for: Map this ICD-10-CM code to its standard SNOMED concept, Find the OMOP concept for LOINC code 2345-7, Search for concepts that mean high blood pressure, Get all descendants of a condition concept

Not supported: Does not store patient records, run an EHR, or make clinical coding decisions on its own. Use for looking up, searching, and mapping OMOP medical vocabulary concepts only.

The OMOPHub Healthcare Vocabulary API looks up, searches, and maps medical concepts across the OHDSI standardized vocabularies, including SNOMED, ICD-10, LOINC, and RxNorm. It resolves a concept by id or by vocabulary-specific code, walks ancestors, descendants, hierarchy paths, and typed relationships, and maps concepts between vocabularies with mapping coverage, quality, and validation checks. Search runs as basic, advanced, autocomplete, faceted, semantic, and bulk queries, and FHIR resolve routes translate a FHIR Coding or CodeableConcept into a source concept, standard concept, and target CDM table. CPT4 access requires the key owner to complete annual UMLS validation in the OMOPHub Dashboard, and every lookup can be pinned to a vocabulary release.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

25%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

96%

Example Validity

Percentage of examples that conform to their schemas.

74%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

30%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

85%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the OMOPHub Healthcare Vocabulary API to your agent

Capabilities

Start building with OMOPHub Healthcare Vocabulary API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

OMOPHub Healthcare Vocabulary API

Jentic AI Readiness Score

OMOPHub Healthcare Vocabulary API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness