Skip to content
ARION
eCOA & remote capture

A mobile form patients can actually complete on their phone

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.

Request a demo
How it works

Still the same one database

A patient completing an eCOA form on their phone writes into the same field-value model as a site coordinator in the casebook — no separate ePRO system to reconcile against.

A typical EDC pipeline compared to ArionA typical EDC hands data off through three export seams -- EDC to export file to CDMS to statistician, each marked with a warning for where data can drift. Arion runs Design, Capture, Review and Analyse inside one continuous bounded system with no export seams.A typical EDCEDCExportCDMSStatisticianThree export seams. Each one is a place the report can drift from what the site typed.ArionDesignCaptureReviewAnalyseOne database. No export, no reconciliation, no provenance gap.

The public ECOA form issues its own signed access token — it is never stored in the database.

Code-verified public access

A 6-digit code, valid 24 hours with 3 attempts and a single submission, gates the public form before any data is shown.

SMS invitations built in

Study editors create an ECOA identifier from name and phone; the invitation, opened and completed timestamps are tracked automatically.

A canvas built for one thing

No navigation, no menu — just the Arion mark and a responsive field grid, so patients on any device can finish the form without getting lost.

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