llms.txt Content
# OMOPHub
> Managed API for OHDSI/OMOP medical vocabularies. Search, map, and resolve
> 11M+ concepts across 130+ 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/concepts/search`
- 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)
## Pag