OpenELIS reporting

Four paths from laboratory records to a dashboard.

Choose a familiar export, import a file into Catalyst, or query a connected source. These paths serve different needs; they are not equivalent competitors.

OpenELIS reporting · Recorded demonstrations

Choose a starting point

Start with a report you already know, or ask a new question. These pathways serve different needs: they are complementary choices, not equivalent alternatives to rank. OpenELIS reporting works independently of Catalyst and AI.

Path 1 · Export and visualize2:33

Use a familiar OpenELIS report

OpenELIS report builder → CSV → Superset

Choose fields and filters, generate a CSV, then upload it into Superset to build a table, chart and dashboard. No Catalyst or AI step is required.

Data: a snapshot for the selected reporting period. Export and upload again when you need a new snapshot.

What the recording shows
  1. Choose and order OpenELIS report columns.
  2. Save the report configuration, provide a fresh reporting period and generate the CSV.
  3. Upload the CSV into Superset.
  4. Create a result table and record-count chart, then arrange the dashboard.

Path 2 · Bring your report2:51

Build on a CSV in Catalyst

OpenELIS report builder → CSV → Catalyst → Superset

Upload the report, review its columns and types, and save a Dataset. Create charts, arrange a dashboard and publish it to Superset without writing SQL.

Data: an imported snapshot with a saved version. A later file does not silently replace an existing published report.

What the recording shows
  1. Generate the same OpenELIS CSV used in Path 1.
  2. Import it into Catalyst and review the detected columns and types.
  3. Save and reopen the imported Dataset without using SQL.
  4. Create a table and count chart, arrange a dashboard and publish it to Superset.

Path 3 · Ask the database1:56

Explore OpenELIS directly

OpenELIS PostgreSQL → Catalyst → Superset

Browse available data, ask and refine a question, review the proposed SQL and choose when to run it. Save the result as a Dataset, then build and publish a dashboard.

Data: queried from the connected operational database. This avoids a file export; results depend on the query and when it runs.

Recorded outcome: context preparation stopped before either selected model ran. The demonstration continues through Catalyst's supported manual-SQL recovery path.

What the recording shows
  1. Select OpenELIS PostgreSQL and browse its available schema.
  2. Prepare a question and inspect the visible preparation failure.
  3. Use the manual SQL recovery path and explicitly retrieve results.
  4. Save the Dataset and publish its dashboard to Superset.

Path 4 · Ask the reporting warehouse2:10

Explore the FHIR reporting source

OpenELIS FHIR → Data Pipes / Spark → Catalyst → Superset

Use the same question, review and dashboard workflow over the FHIR reporting source. The pipeline prepares OpenELIS FHIR data for SQL analysis.

Data: limited to what OpenELIS exports to FHIR and the latest pipeline refresh. Coverage and freshness can differ from the operational database.

Recorded outcome: Gemma 12B drafted the query and Qwen reviewed it. Execution and analyst refinement remain explicit.

What the recording shows
  1. Select the FHIR-derived Spark source and write a reporting question.
  2. Review the generated and reviewed SQL before execution.
  3. Retrieve the result and make an explicit analyst refinement.
  4. Save the Dataset and publish its dashboard to Superset.

All four recordings were reviewed at normal speed. These are real local workflows with synthetic records, recorded September 16, 2026. The linked server dashboards separately verify the updated deployment; the recordings are not presented as server-video evidence. Owner acceptance remains open. The applications currently use their existing sign-ins; shared sign-in and equivalent per-user access are separately planned.

Reporting roadmap and evidence

Captions remain visible for reading, result views are held for inspection and accelerated waits are labelled. Final owner acceptance remains a separate milestone.