Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Report History screen lists past report generation runs in reverse-chronological order at the in-app route /cl/report-runs.

​
Overview

The page is guarded by cl.report_runs.view. Report runs are fetched from cl_report_runs (joined to cl_report_definitions for report name) via useReportRunList. The table displays the report name (or “Ad-hoc” for runs without an associated definition), a status badge (running, completed, failed), the run start timestamp, and the run completion timestamp (or — if not yet complete). The list is shown most-recent-first. When no runs exist, an empty state with a Clock icon prompts the user to run a report from the Report Definitions page.

​
Who it’s for

Requires permission cl.report_runs.view.

​
Before you start

  • Permission cl.report_runs.view must be granted.
  • Report runs are initiated from the Report Definitions page at /cl/report-definitions (requires cl.report_runs.run).

​
Steps

1

Open Report History

Navigate to /cl/report-runs. The page loads all runs accessible to your organization.
2

Review run status

Each row shows the report name, a status badge (running, completed, or failed), start time, and completion time.
3

Initiate a new run

To run a report, navigate to Report Definitions at /cl/report-definitions and click “Run” on the desired definition row.

​
Key concepts

running (secondary badge), completed (default badge), failed (destructive badge) — from ReportRunStatus in src/cores/cl/types/reporting.ts.
When no runs have been executed, an empty state with a Clock icon is shown with the message “Run a report from the Report Definitions page to see history here.” A skeleton (header + 96px block) is shown while loading.

Clinical

Overview of the Clinical core.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/cl.tsx
  • src/cores/cl/pages/ReportRunsHistoryPage.tsx
  • src/cores/cl/types/reporting.ts