Skip to content
ARION
Queries & data quality

Data is born clean — queries follow the data, not the other way around

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.

Request a demo
How it works

A closed loop, not a one-way door

A reviewer promotes a candidate to open, the site answers, a reviewer closes it — and a reviewer comment on an answered or closed query always reopens it.

Query lifecycleFour states in sequence: Candidate promoted by a reviewer to Open, answered by the site, then closed by a reviewer. A curved arrow shows that a reviewer comment on an answered or closed query always reopens it.reviewer comment always reopensreviewer promotessite answersreviewer closesCandidateOpenAnsweredClosed

Re-completing a form with the same unresolved issue reuses the existing query instead of creating a duplicate.

Study-level query policy

Two independent toggles — out-of-range and missing-required — each with a configurable initial status, plus an opt-in auto-close for resolved queries.

Severity that means something

Low, Medium, High and Critical are available throughout the workflow, with every real change recorded in the audit trail with old and new values.

Casebook-first, not a side panel

Manual queries can target a patient, visit, form or field directly from the casebook, with scoped thread management inline where the data lives.

Arion Queries workspace showing a study query list and its contextual conversation.
Every query retains its subject, visit, form and field context while sites and reviewers work the same thread.

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