Skip to content
ARION
Study builder

Design events, pages and fields — and change them safely once patients exist

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.

Request a demo
How it works

Design and capture share one model

A field defined in the study builder is not just a label — it is the object every captured field value points back to, across every patient and every visit.

Protocol design binds to operational dataA protocol row (Study, Event, Page, Field) sits above an operational row (Patient/Enrollment, Occurrence, Form instance, Field value), with dashed lines binding Event to Occurrence, Page to Form instance, and Field to Field value -- showing that captured data always traces back to the design object that defines it.PROTOCOL · DESIGN TIMEStudyEventPageFieldOPERATIONAL · CAPTURE TIMEPatient · EnrollmentOccurrenceForm instanceField valueevery captured value traces back to its field definition

Change the field definition and every downstream value stays traceable to it.

AI-assisted extraction

Upload a protocol PDF or a CSV/XLS/XLSX and get inferred fields and structure back in minutes, not a services engagement.

Impact-aware structural changes

A save that would orphan patient data returns a structured impact summary — patients, visits, forms, SDV and signatures affected — before anything is touched.

Derived fields with formula IntelliSense

Computed fields reference other fields across forms in the same event, with inline diagnostics while you write the formula, not after you save it.

Arion Study Builder Forms tab showing pages and their structured field definitions.
Pages stay visible while the selected form is shaped field by field, including type, requiredness and SDV policy.

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