Start with your data
Browse a connected source and ask a question, or import a CSV and review its columns.
Catalyst
Explore clinical and program data, review the work and turn the results into saved tables, charts and dashboards. Start with a connected source or bring a CSV.
A step-by-step illustrated example: ask, refine, correct and publish using HIV demo data.
Browse a connected source and ask a question, or import a CSV and review its columns.
Inspect results and correct SQL when needed. AI suggestions are advisory; you choose when a query runs.
Save a Dataset, build charts and tables, arrange a dashboard and publish it to Superset.
OpenELIS reporting
Four complementary paths connect native reporting, CSV imports, direct database queries and FHIR-derived data to dashboards.
See the dated demonstration and acceptance status for the four reporting paths.
Recorded examples · Local deployments
Ask a question, review the proposed query, and turn its results into saved tables, charts and dashboards. The earlier local walkthroughs below use OpenELIS laboratory data and OpenMRS HIV data. Gemma 4 12B drafts each query and Qwen 2.5 14B reviews it; their findings are advisory, and you choose when to run the query. FHIR Data Pipes prepares the source data for the Spark SQL warehouse. The walkthroughs focus on the work you do in Catalyst.
These recordings show local query-to-dashboard journeys. For CSV imports and direct-source examples, explore the four reporting paths above.
A configured SQL source exposes its complete readable schema: source identity, SQL dialect, and every readable table and column.
Findings are advisory. The exact selected SQL runs once and returns typed rows or the database error.
These earlier videos show local validation. The four-pathway status distinguishes recorded local workflows, server-dashboard checks and owner acceptance. Model-team comparison is separately scheduled.
Catalyst pipeline
Catalyst Gateway owns source context, query versions, optional writer/reviewer composition, advisory findings, and execution. It calls Med Agent Hub only to run configured model roles. The four stages below are the lifecycle shown in both local recordings.
A writer model drafts SQL from the source context supplied by the current runtime.
When selected, a reviewer model checks the draft against the same question and schema.
The person can edit the query and inspect advisory findings without losing the draft.
The exact selected query runs through the configured source and returns rows or its database error.