Skip to content
Reason Health
Menu
Product catalog

reason.health · 01

Knowledge

Give healthcare data a common language.

Medical terminology anchors consistent healthcare data. ReasonHealth Knowledge Cloud brings semantic search across documentation and FHIR artifacts, project-aware AI assistance, and a browser for FHIR packages into one workspace. Knowledge Local runs a versioned terminology API in your environment.

ReasonHealth Knowledge Cloud · AI-first workspace

Knowledge Cloud

Build trusted healthcare knowledge workflows with intelligent tools.

ReasonHealth Knowledge Cloud gives your team a hosted workspace for healthcare knowledge and AI-assisted work. Search documentation and FHIR artifacts, browse package resources, and connect AI assistants to project context and guides.

What you can do
  • AI Assistant (MCP) brings project context and guides into AI workflows.
  • Knowledge Search finds documentation and FHIR artifacts.
  • Resource Browser explores FHIR resources and package contents.
Open ReasonHealth Knowledge Cloud
reason.healthKNOWLEDGE MCP SESSION

YOU

Find ICD-10-CM codes for type 2 diabetes with chronic kidney disease.

Semantic terminology search

Search terminology by clinical meaning, then inspect candidate codes and their definitions before choosing what fits.

MCP WORKFLOW

  1. 01Search codesMatch the clinical phrase
  2. 02Inspect resultsReview descriptions and context
  3. 03Verify selectionCheck the code details
Knowledge CloudExamples of how Knowledge MCP tools help agents work with clinical terminology and FHIR resources.
Terminology API · Customer operated

Knowledge Local

Your infrastructure. A known terminology release.

Run a read-only terminology API in your own environment. Immutable releases keep search and ValueSet expansion tied to a known version of the underlying terminology.

What you can do
  • Search the terminology included in your release.
  • Expand FHIR ValueSets through an API.
  • Choose when to adopt a new terminology release.
Explore the Terminology API
Knowledge LocalCast
Illustrative terminal cast
  1. docker run -d --name knowledge-local \ -p "$PORT:$PORT" \ "$IMAGE:$RELEASE"

    Container started · API available at $API_URL

  2. curl -X POST "$API_URL/v1/search" \ -H "Content-Type: application/json" \ --data @search-request.json

    200 OK · semantic matches for "CBC"

  3. curl -X POST "$API_URL/fhir/R4/ValueSet/\$expand" \ -H "Content-Type: application/fhir+json" \ --data @valueset-parameters.json

    200 OK · expansion.contains[]

Illustrative commands · image, ports, and credentials omitted
Illustrative terminal castPeople, Postman collections, and AI agents can all use the same installed release for terminology search and FHIR ValueSet expansion.

From a product to your workflow

Build with us.

Bring a clinical workflow, a source guideline, or an integration challenge. Vermonster, the team behind reason.health, can help you connect the pieces in your environment.

Work with usExplore the open Toolkit