Skip to content
ARION
For investigator sites

A casebook site staff actually want to use

Visit-centered navigation, inline query and SDV context, and non-blocking validation reduce the friction sites feel with heavier EDC systems.

Request a demo
How it works

Access scoped to exactly one center

Site PI and site coordinator roles see their own center only, with the casebook, query and SDV actions they actually use in daily visits.

Role-based access, by capability areaA matrix of six representative roles (of thirteen total) against five capability areas, showing which roles can access study design, patient data, queries and SDV, reports and export, and PI signature. Site PI and Site coordinator are marked as center-scoped -- limited to their single assigned center.Study designPatient dataQueries & SDVReports/exportPI signaturePlatform adminStudy builderData managerCRA / monitorSite PISite coordinatorcenter-scoped6 of 13 seeded roles shown, each org- and center-scoped identically in the API and the UI.

No cross-center visibility a site role has to be trained to ignore.

Visit-centered casebook

Navigation follows the patient's visit timeline, not a flat list of forms — the next thing to do is usually the next thing on screen.

Query and SDV context inline

Open and answered queries show right on the visit, form and field they belong to — no separate workspace to check before starting a visit.

Saves that never block

An out-of-range value is a visible warning, not a wall — the visit gets recorded and the finding gets reviewed on its own track.

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