Electronic data capture built around the casebook, not the spreadsheet
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.
Request a demoScreening is a lifecycle, not a gate
A registered subject moves through tri-state screening criteria to an explicit enrolment or screen-failure decision. Screen failure can loop back into rescreening, and every terminal state still leaves safety follow-up open.
Enrolment and screen failure are explicit clinical decisions, never a side effect of saving criteria.
Non-blocking validation
Out-of-range values and format warnings never block a save. They persist as visible flags and feed the query workflow instead of stopping site work.
Tri-state eligibility
Yes, No, and Not assessed are all first-class answers, with each criterion persisted independently as it is entered — not batched into one final submit.
Normalized field values
Every captured value lives in a relational field-value table tied to its study field, event and form — not a JSON blob that has to be parsed to be trusted.
See it on your protocol
Bring a protocol or an existing study and we'll show you what this looks like in Arion.