ReasonHub
  • Use Cases
  • Blog
  • Contact
  • About
  • Get Started
ReasonHub
LinkedInGitHub
TERMS & CONDITIONSACCESSIBILITYPRIVACY POLICY© 2026 VERMONSTER
  • Capabilities
  • Use Cases
  • Blog
  • About

Contact Us

info@reason.health

75 Broad St
Boston, MA

LinkedInGitHub
TERMS & CONDITIONSACCESSIBILITYPRIVACY POLICY© 2026 VERMONSTER
  • Use Cases
  • Blog
  • Contact
  • About
Get Started

Follow us on

Introducing ReasonHub: A Platform for Computable Healthcare Knowledge
Back to Blog

Introducing ReasonHub: A Platform for Computable Healthcare Knowledge

Turn disconnected information into computable, standards-aligned knowledge. ReasonHub brings CRMI-native authoring, terminology services, MCP-enabled APIs, and secure syndication together in one place.

Nov 17, 2025•By Brian Kaney
announcement
Share

At a fundamental level, healthcare runs on knowledge: the guidelines, measures, terminologies, and policies that inform every clinical decision. But today that knowledge is mostly trapped in PDFs, spreadsheets, custom databases, or single-purpose tools. As interoperability in healthcare matures, the next step beyond today's data interoperability is obvious: make clinical knowledge computable, governable, and deployable the same way we treat code.

ReasonHub is a modern platform for managing and distributing healthcare knowledge artifacts using FHIR. It’s designed to help teams author, validate, version, and publish the artifacts that power clinical reasoning (including Library (CQL), Measure, ValueSet, ConceptMap, PlanDefinition, and related assets) while integrating with your existing infrastructure and workflows.

What ReasonHub Does

ReasonHub provides the following core capabilities:

  • Unified FHIR knowledge platform: Manage clinical content (terminology, logic, measures, and guidelines) in one place.
  • CRMI-native authoring: Author and package computable artifacts following HL7’s CRMI guidance so your content is portable and standards-aligned.
  • Terminology services: Manage CodeSystem, compose and expand ValueSet, translate with ConceptMap, and validate codes during authoring and deployment.
  • AI enablement via MCP: Expose semantic search, ValueSet expansion, and deterministic reasoning through REST and the Model Context Protocol (MCP) so that IDEs, agents, and CLIs can safely use your knowledge.
  • Secure syndication: Distribute artifacts to partners and downstream systems with versioning, governance, and subscriptions.

These capabilities are reflected throughout the product: a private FHIR registry for public and internal packages, governance and roles, conformance validation built into authoring, and direct support for “ContentOps": the same operational rigor you expect for code, now applied to knowledge.

It's Designed for Real Use Cases

ReasonHub supports what we call “Generation 2” FHIR use cases, which go beyond data exchange and conformance to enable clinical reasoning at scale:

  • Population health and quality measures using Measure + CQL
  • Decision support and clinical pathways using PlanDefinition and ActivityDefinition
  • SDOH and patient assessments with Questionnaire and QuestionnaireResponse
  • Prior authorization and policy automation with computable rules and forms

If you’re building any of these, you already rely on terminologies, libraries, and artifact packaging. ReasonHub centralizes those building blocks, validates them, and makes them easy to share and integrate.

It's Built for Informatics and Engineering

  • Works with your ecosystem: Bring your existing HL7 authoring tools, VS Code workflows, and CI/CD. ReasonHub integrates cleanly without forcing a rewrite.
  • Deterministic operations: Validate CQL libraries, expand ValueSets, and verify ConceptMap translations as part of authoring and review.
  • Enterprise-ready registry: Mirror public/partner packages locally, apply role-based access, and keep everything versioned and auditable.

Standards It's Built On

ReasonHub is built on open standards, including many we're proud to have helped define. We believe that only through the adoption of open standards can a rich marketplace of knowledge (both commercial and non-commercial) emerge and thrive.

  • CRMI (Canonical Resource Management Infrastructure): Guidance for packaging and distributing canonical FHIR artifacts. The foundation for shareable computable content.
  • CPG-on-FHIR (CQF Recommendations): Patterns for representing guideline recommendations and pathways.
  • Structured Data Capture (SDC): Best practices for structured assessments and forms.
  • CQL and related guidance: Authoring and evaluation of clinical logic and the US CQL IG prior authorization example

What’s Next

Over the coming weeks, we’ll share deeper dives into "Generation 2" FHIR use cases, CRMI in practice, guideline implementation (CPG-on-FHIR), and our developer tooling. If you want to see ReasonHub in action—managing terminology, validating CQL, and publishing full guideline bundles—we'd love to show you.

Ready to turn your clinical knowledge into a scalable, computable asset? ReasonHub makes it practical.