Skip to content
ARION
Platform

One database for design, capture, review and analysis

Arion brings study design, casebook data entry, queries, SDV, protocol deviations, eCOA and built-in statistics into a single controlled workspace — no export ever leaves the platform.

Request a demo
How it works

Four stages, one closed loop

Design, capture, review and analyse are not four systems handed off in sequence — they are four views of the same database, so nothing is ever exported to get from one to the next.

The Arion loopDesign, Capture, Review and Analyse arranged in a closed circle around the label "One database, one audit trail", showing that all four stages run on the same underlying data rather than a pipeline of separate systems.One databaseone audit trailDesignevents, pages, fieldsCapturecasebook, eCOAReviewqueries, SDV, deviationsAnalysebuilt-in statistics

The same field value a site enters in the casebook is the one a statistician analyses — no copy in between.

Inside Arion

See the workflow, not a feature checklist

The study definition, the site casebook and the reviewer workspace are three views of the same clinical data. Decisions made during design remain visible when a value is captured, queried and verified.

01 · Design

Turn the protocol into an operational study

Build events, pages and fields alongside validation, eligibility, visit workflow and SDV policy. The structure is not documentation beside the system; it is what the system runs.

One definition drives capture and review

Explore the guide: Study Builder Guide
Arion Study Builder with pages and structured form fields.
Arion patient casebook showing a clinical visit form.
02 · Capture

Keep site work inside the patient context

Site teams move from eligibility to visits and forms without losing the patient timeline. Validation stays non-blocking, while completion and query signals remain visible where data is entered.

Visit, form and field context stays attached

Arion patient SDV workspace with verification status and actions.
03 · Review

Review at the level where the issue lives

Monitors move from patient progress to visit, page and field SDV. A discrepancy can become a linked query in the same action, and re-verification closes the loop.

SDV and queries share one review trail

The platform

One workspace, the whole study

Every stage of a study — from designing the protocol to reading the final statistics — lives in the same controlled environment.

EDC & eCRF Capture

Visit-based eCRF forms, tri-state screening and eligibility, and a normalized field-level data model that keeps every value traceable back to its visit and form — with validation that never blocks a save.

Learn more

Study Builder

AI-assisted protocol extraction, a drag-and-drop event and field builder, and a structural-change workflow that shows the exact impact on existing patient data before you confirm it.

Learn more

Queries & Data Quality

Saves are never blocked. Out-of-range and missing-required findings become candidate queries on a study-defined policy, and reviewers manage the full lifecycle from one workspace.

Learn more

Source Data Verification

Configure verification requirements once in study design; monitors verify or flag discrepancies from a dedicated patient SDV workspace, with linked queries that auto-close when the discrepancy is resolved.

Learn more

Protocol Deviations

Out-of-window visits, prohibited medications, missed visits and eligibility waivers raise deviations automatically; review, severity, and CAPA tracking happen alongside manually reported ones.

Learn more

eCOA & Remote Capture

Access-code protected, signed-JWT public forms with SMS invitations, delivered in a menu-less mobile canvas that keeps the patient focused on one form at a time.

Learn more

Built-in Analytics

Descriptive statistics, group comparison, survival analysis and explainable ML run directly against live study data, with no reconciliation step between the eCRF and the report.

Learn more

Audit, RBAC & Signatures

Organization- and center-scoped role definitions enforced identically in the API and the UI, append-only audit entries with before/after values, and password-confirmed PI signatures.

Learn more

See it on your protocol

Bring a protocol or an existing study and we'll show you what this looks like in Arion.

Request a demo