Independent technical audit

omophub.com

Overall AI readiness score

A combined result across all audit signals.

Excellent

AI readiness audit: 11/15/2026Public technical data

About the site

Platform:: Next.js

Overall AI readiness assessment

How ready omophub.com is for AI systems

85/100

OMOPHub is a legitimate medical terminology API service. Its llms.txt is accessible, well-formatted, and consistent with the homepage content. No policy violations were found. Approved for inclusion.

Audit context

llms.txt is accessible and contains 650 tokens. No accessible llms-full.txt was detected, so deeper context still has to be assembled from regular pages. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. The homepage exposes Schema.org types Organization, WebSite, SoftwareApplication, FAQPage; 10 OpenGraph tags were found and markup completeness is 100%.

The Google Lighthouse measurement is still collecting. Once complete, performance, accessibility, technical quality, SEO, and experimental browser-agent signals will be added with a limited weight.

Confirmed strengths

Accessible llms.txt
1 sitemap declaration
Schema.org: Organization, WebSite
Complete social metadata

Priority improvements

1Add llms-full.txt for richer first-party context.

llms.txt tokens650

llms-full.txt tokens—

ai.txt

sitemap.xml

Google Lighthouse technical profile

The background queue is collecting mobile Performance, Accessibility, Best Practices, SEO, and experimental browser-agent signals.

Collecting data

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://omophub.com/llms.txt

llms-full.txt

Full version was not found

ai.txt

ai.txt file was not found

robots.txt

File found

https://omophub.com/robots.txt

Sitemap in robots.txt1

1 sitemap found

Schema.org (JSON-LD)

Types: Organization, WebSite, SoftwareApplication, FAQPage

OpenGraph100%

10 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotAllowed

OAI-SearchBotAllowed

ChatGPT-UserAllowed

Google-ExtendedAllowed

ClaudeBotAllowed

Claude-SearchBotAllowed

Claude-UserAllowed

BytespiderAllowed

CCBotAllowed

PerplexityBotAllowed

Perplexity-UserAllowed

Sitemaps

Declared discovery routes for crawlers and agents.

https://omophub.com/sitemap.xml

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 100%

og:titleOMOPHub - Medical Terminology API for SNOMED, ICD-10, LOINC & RxNorm

og:descriptionSearch, map, and resolve medical codes across SNOMED CT, ICD-10, LOINC, and RxNorm - one REST API, 120+ vocabularies, cross-vocabulary mapping built on OMOP. No database setup required.

og:urlhttps://omophub.com

og:site_nameOMOPHub.com

og:localeen_US

og:imagehttps://omophub.com/og-cover.png

og:image:width1200

og:image:height630

og:image:altOMOPHub - OMOP Vocabulary API

og:typewebsite

Schema.org markup

Structured entities and properties exposed on the homepage.

Types found: 4 · Properties: 7

OrganizationWebSiteSoftwareApplicationFAQPage

nameOMOPHub

urlhttps://omophub.com

descriptionStandardized clinical vocabularies for developers

logohttps://omophub.com/logo.png

sameAshttps://github.com/omopHub

contactPointhttps://omophub.com/contact

publisherOMOPHub

# OMOPHub

> Managed API for OHDSI/OMOP medical vocabularies. Search, map, and resolve
> 11M+ concepts across 120+ vocabularies (SNOMED CT, ICD-10-CM, LOINC, RxNorm,
> HPO, and more) without hosting a vocabulary database.

## Access surfaces

- REST API: https://api.omophub.com/v1
- FHIR Terminology Service: https://fhir.omophub.com/fhir/{r4|r4b|r5|r6}/
- MCP Server (hosted): https://mcp.omophub.com

## SDKs

- Python: `pip install omophub`
- R: `install.packages("omophub")`
- Node/TypeScript: `npm install @omophub/omophub-node`
- MCP: `npx -y @omophub/omophub-mcp`

## Key capabilities

- Lexical, semantic (neural embedding), and hybrid concept search
- Bulk search - up to 50 queries per request
- Cross-vocabulary mappings and hierarchy traversal
- FHIR Resolver: Coding/CodeableConcept → OMOP standard concept + CDM target
  table in one call. HL7 FHIR-to-OMOP IG conformant.
- FHIR R4/R4B/R5/R6 terminology service: $lookup, $validate-code, $translate,
  $expand, $subsumes, $find-matches, $closure, plus $diff extension
- 11 MCP tools for Claude, Cursor, VS Code, Windsurf
- PHOEBE concept recommendations, versioned ConceptSets, ATHENA version pinning

## Common tasks

- Find a concept by name or code - REST `/v1/search/concepts`
- Resolve ICD-10/SNOMED/LOINC source code to OMOP standard concept - mappings
- Traverse hierarchy (ancestors/descendants) - relationship endpoints
- Build and version a ConceptSet
- Semantic/neural search over concepts
- Resolve a FHIR Coding/CodeableConcept to OMOP - FHIR Resolver
- Use from Claude/Cursor/VS Code - hosted MCP server

## Documentation

- [Full docs index](https://docs.omophub.com/llms.txt)
- [Complete documentation](https://docs.omophub.com/llms-full.txt)
- [Agent guide](https://docs.omophub.com/skill.md) - preferred workflow (REST
  vs SDK vs MCP), decision rules, canonical terminology, common tasks, gotchas
- [Quickstart](https://docs.omophub.com/quickstart)
- [API reference](https://docs.omophub.com/api-reference)

## Pages

- [Pricing](https://omophub.com/pricing) - free tier: 3,000 calls/month
- [Changelog](https://omophub.com/changelog)
- [Concept Lookup tool](https://omophub.com/tools/concept-lookup)
- [EHDS](https://omophub.com/ehds)
- [About](https://omophub.com/about)

## Notes

OMOPHub is an independent service, not affiliated with OHDSI or ATHENA.
CPT4 and MedDRA are unavailable due to licensing restrictions.
OMOPHub serves vocabulary data only and does not process PHI. It is not a
hosted OMOP CDM / vocabulary database, and not an ATLAS or ETL replacement -
it exposes ATHENA vocabularies through APIs.

Share or continue the analysis

Share this audit