Define your report's numbers once. Rerun them on every new export.
Omilyra Trace replaces the Excel rework behind a CRO project report. Each metric becomes a definition you can read; each new EDC export becomes a data cut you can check down to the source rows.
Works from the EDC export files you already download.
The wording barely changes. The numbers take days.
Most of a project report is fixed text. The time goes into rebuilding its numbers by hand from each fresh EDC export.
- 1
Export
Download the latest data from the EDC.
- 2
Rebuild in Excel
Recount enrollment, completion and subgroup breakdowns by hand, sheet by sheet.
- 3
Paste into the template
Copy each number into the report everyone already knows.
- 2–5 days
- of data work per report
- Every export
- the same steps, from scratch
- 2–3 years
- the life of a typical trial
From export to checked numbers, without the rebuild.
You set up a project once. After that, each new export is an upload and a data cut.
- Step 1
Import the files you already export
Upload CSV files or Excel workbooks. Trace detects encodings and delimiters, reads one table per sheet, and suggests column types — partial dates like 2025-03-UK included — for you to confirm.
- Step 2
Define each metric once
Pick a table, filter rows, break results down by subgroup and choose how to count: count, distinct count, percent, sum, minimum or maximum. Reshape data first with operations like merge, group, pivot and map values — no code.
- Step 3
Cut the data when a new export arrives
Trace compares the new file with the last import and flags missing or renamed tables and columns before anything runs. A data cut then locks in the files and settings for its cutoff date.
- Step 4
Check, then compare cuts
Open any value to see the rows behind it. Build canvases of number cards, grouped breakdowns and row lists that show this cut next to the previous one, and share a link that keeps the cut and filters.
You switch when the numbers match. So every number can be checked.
Nobody replaces a working spreadsheet on faith. Run Trace alongside your current process and compare, number by number.
Every value traces back
Open any number to see the source rows behind it, each marked as counted or not.
Definitions you can read
Each metric is a structured definition — table, filter, breakdown, aggregate — with formulas limited to a fixed set of checked functions. No scripts to maintain.
Every change is a version
Each save creates a new version of the definitions. See what changed, follow one metric's history, or revert.
Inputs locked per data cut
A cut fixes the exact files, import settings and column types it uses, so you can return to an earlier cut and recompute it.
Access that matches how studies are run.
Workspaces and projects
One project per study, inside your organization's workspace. Belong to several workspaces and switch between them.
Roles and invitations
Owner, Admin, Editor, Viewer or custom roles, for the whole workspace or a single project. Seeing patient-level rows is a permission of its own.
Audit log
See who did what in the workspace, filtered by person, action, project and time.
English and Chinese
The interface is available in English and Simplified Chinese, in a light or dark theme.
Where Trace is going
Trace is in development. Here is what we're building now and what comes after it. We'll add dates when we're sure of them.
In development
Managing sources over a long study
One page for every data cut, and safe deletion of sources, uploads and cuts, with a trash and retention rules.
EDC labels in the editor
The question text from your EDC export shown next to each column name while you define metrics.
PlannedNot available yet
Reports in your own template
Fill the report your leadership already reads with Trace's numbers and export it for delivery. The template stays yours; we don't hand you a new one.
An assistant that proposes, never decides
Ask questions about your data and get proposed processing steps and canvases to review and adopt. It works with your permissions, and project data reaches a model only after you allow it — including a model on your own network.
Enterprise sign-in
Single sign-on through your organization's identity provider.
Running in your environment
A private deployment for organizations whose data has to stay in-house.
What Trace is not
A narrow tool does its one job well. These limits are deliberate.
Not a general BI tool
It does one job: the recurring project report at a CRO. Your BI tools stay where they are.
Not for regulatory submissions
Reports are for internal medical and management review. Trace is not validated for 21 CFR Part 11, and its audit log is for traceability, not compliance.
Not connected to your EDC
It works from the export files you already download, so there's no integration project to start.
Tell us how you build your report today.
Trace is in development. If you prepare project reports from EDC exports — as a medical manager, data manager or statistical programmer — we'd like to show you where it stands, or simply hear how the work is done now.