Skip to content
Reason Health
Menu
Product catalog

reason.health · 03

Clinical Logic Evaluation

Bring reviewed logic into the workflow.

Reviewed clinical logic becomes useful when applications can put it to work. We are developing services for decision support and analytics built on portable clinical definitions. Explore the direction and bring us your use case.

Planned · Clinical decision supportPREVIEW

Decision Services

Connect computable guidance to care delivery.

A planned runtime for bringing computable guidance into provider and payer applications, with CPG operations and APIs for clinical decision support and prior authorization.

Planned capabilities
  • CPG operations for computable clinical guidance.
  • CDS Hooks integration with application workflows.
  • Support for provider and payer prior authorization workflows.
Discuss Decision Services
Illustrative MOPA EHR prior authorization screen showing a draft oncology order beside a coverage and authorization panel with a payer requested substitution.
Decision ServicesIllustrative MOPA EHR workflow showing how a payer requirement could appear beside a draft order. This is a concept image, not a live Decision Services capture.
In development · FHIR analyticsPREVIEW

Analytics

Start with a definition you can inspect.

Reason Analytics is designed to accept SQL and supported CQL, generate portable SQL-on-FHIR view definitions, and map them to Arrow and DataFusion for the chosen backing store. It executes queries and materializes results in the forms each workflow needs, including reports, submissions, dashboards, tables, files, and outputs for BI agents. The open rh toolchain also lowers supported CQL expressions through clinical relational algebra (RA) into SQL-on-FHIR artifacts and SQL queries.

Runtime capabilities
  • Create views and materialized views from FHIR-based view definitions.
  • Materialize analytics tables with Arrow and execute SQL with DataFusion.
  • Run directly authored SQL or queries derived from supported CQL.
  • Use shared results for reporting, submissions, dashboards, and BI agents.
Discuss Analytics
SQL and CQL inputs feed Reason Analytics, which generates SQL-on-FHIR view definitions, maps the backing store to Arrow and DataFusion, then executes queries and materializes results. A general data lake can use S3, Azure Blob, or Google Cloud Storage. Results support reports, submissions, dashboards, tables, files, and BI agents.SQL and CQL inputs feed Reason Analytics, which generates SQL-on-FHIR view definitions, maps the backing store to Arrow and DataFusion, then executes queries and materializes results. A general data lake can use S3, Azure Blob, or Google Cloud Storage. Results support reports, submissions, dashboards, tables, files, and BI agents.
AnalyticsArchitecture overview: SQL and CQL requirements become SQL-on-FHIR view definitions. Reason Analytics maps them to the backing store through Arrow and DataFusion, executes queries, and materializes results for reports, submissions, dashboards, tables, files, and BI agents.

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