TermHub™ Plans

Plans and Pricing Information

Choose Your Plan

Basic

$0/mo

  • 30-Day Trial of all TermHub™ Features

  • No Payment Required

  • Lifetime Access to Public Projects

  • Limited Support

Popular

Note: qualified Startups get a full year of TermHub for only $2,000!

Standard

$2000/mo

  • Full TermHub™ Features

  • Private Terminology Server

  • Prioritized Content Requests

  • Pay Per Organization

  • OpenTermhub Syndication

  • Dedicated Support

Platinum

Contact Us

  • Everything from Standard Plan

  • Custom Features

  • Private Content

  • Unlimited Users/Organizations

  • Enhanced Support


Frequently Asked Questions

API Limits & Performance

  • Cloud TermHub doesn’t enforce a hard rate limit, but it expects users not to overwhelm the service (for example, by behaving like a DDoS attack). If you anticipate high request volumes, we recommend deploying the Open TermHub container with your licensed data for local, scalable use.


    Additionally, our terms prohibit creating a front end on TermHub that effectively resells or competes with our service.

  • Cloud TermHub handles hundreds of near-simultaneous requests without issue. We’ll share detailed benchmarks soon.

    At very high volumes, response times may increase, and we may apply throttling through our web application firewall.

  • No. TermHub’s pricing isn’t tied to usage tiers.

    For high-volume needs, we recommend deploying a local Open TermHub container with your managed content, which you can scale horizontally to handle any load.

  • There are no explicit limits today, so there isn’t a defined failure mode. If the system becomes overloaded, responses may slow down and could eventually start failing.

Authentication & Access

  • Cloud TermHub uses username/password authentication under the OAuth2 spec. A successful login returns an access token (valid for 2 hours) and a refresh token (valid for 48 hours). Use the OAuth refresh flow with your refresh token to get a new access and refresh token pair as needed.


    Additionally, our terms prohibit creating a front end on TermHub that effectively resells or competes with our service.

  • Cloud TermHub isn’t available for on-premises deployment without an enterprise agreement.

    However, we do offer a dockerized Open TermHub container that you can deploy locally.

Bulk & Lookup Behavior

  • There is not a strict limit on how many entries can be present in a single lookup call and is mostly limited by available memory.

    Certainly thousands of entries can be provided, but the more that are provided, the longer it will take to get a result. There is generally a 5 minute timeout on calls, so any request taking longer than that will return with a gateway timeout (504).


    Additionally, our terms prohibit creating a front end on TermHub that effectively resells or competes with our service.

  • Currently, Cloud TermHub doesn’t parallelize lookups for multiple values, so response time scales roughly linearly with entity count.

    However, overhead from requesting multiple terminology sets at once is minimal.

  • No. Multiple vocabularies are searched simultaneously, so performance is roughly the same as querying a single terminology.

Terminology Management

  • Cloud TermHub supports BYOD (Bring Your Own Data).

    Right now, this is handled manually: you provide your terminology files to our team, and we load them into TermHub for use within your organization’s projects.

    API and UI-based upload features are on our roadmap.

  • Cloud TermHub automatically updates standard vocabularies with clear publisher endpoints, such as SNOMED CT, SNOMED CT US, RxNorm, and LOINC.

    Terminologies pulled from UMLS follow its May and November release cycle.

    Less frequently updated terminologies are refreshed on demand when new versions are identified. Changelogs and webhooks for release notifications are on our roadmap.

Advanced Functionality & AutoMap

  • Cloud TermHub supports find/get operations across terminologies, mapsets, subsets, and concepts, plus history services to track changes across versions. It offers export features, bulk concept lookups (including export), and a complete set of read-only FHIR R4 and R5 services with Swagger APIs.

    For early access to advanced capabilities—like cross-vocabulary mapping through “Automap”—you can explore the Preview Features Project.

  • In bulk search, the confidence score is simply a raw output from the search engine and isn’t particularly meaningful.

    For Automap, the score is generated by a multi-step algorithm, producing values from 0 to 1. Generally, scores above 0.85 indicate high-quality matches.

  • Not yet. This is a potential future use case, and we expect Automap to eventually support scenarios like discovering which terminologies best cover your data.

    We’re also open to prioritizing such features under partnerships or cost-sharing agreements.

  • Not out of the box.

    Right now, AutoMap focuses on semantic standardization of clinical records and concept-based indexing of narrative content, such as journal articles or help documentation.

    However, risk coding is a valid use case for the AutoMap platform, and it could be configured or tuned to support it.

Associated Solutions

  • AutoMap is TermHub’s intelligent mapping engine that helps convert non-standard content into standardized clinical codes. It supports mapping:

    • Local, proprietary, or legacy codes

    • Free-text terms or labels (e.g., “fasting glucose”)

    • Even full paragraphs of clinical text, such as open-ended responses or provider notes

    This makes AutoMap useful for a wide range of scenarios—from standardizing homegrown lab codes to translating narrative assessments into SNOMED CT, LOINC, RxNorm, or ICD-10-CM.

    Whether you're cleaning up legacy data, prepping for interoperability, or building clinical decision support, AutoMap accelerates the process with consistent, scalable mappings.

  • Open TermHub refers to the self-hosted, open-source deployment of TermHub using Docker. It lets organizations run their own instance of the platform, complete with user interface and API access, on-premises or in a private cloud. It includes:

    • UI for browsing and searching standard terminologies

    • FHIR‑based API access

    • A clean, containerized deployment

    It’s perfect if you want full control over your data and environment without relying on TermHub’s hosted service.