Advarra OnCore vs CRIO Site CTMS(CTMS)

Research sites, site networks, hospitals and academic medical centers choosing a CTMS to run their own studies, participant visits and site finances. Sponsor and CRO CTMS products are out of scope.

Scope This list serves research sites, not sponsors and CROs. A site CTMS runs participant visits, site budgets and sponsor invoicing; a sponsor or CRO CTMS oversees many sites and countries (monitoring, country start-up, portfolio views). Their workflows differ, so sponsor and CRO products (Veeva Vault CTMS, Oracle Siebel CTMS, Medidata CTMS, IQVIA) belong on a separate list with their own criteria. Products that support participant follow-up alongside a site CTMS are also included; the feature notes distinguish this from dedicated CTMS operations.

Guide updated How we compare

Compare within CTMS

Study fit, side by side

These notes describe the products in the CTMS guide.

Advarra OnCore

Best for
Academic medical centers, NCI-designated cancer centers and health systems running 50 to 500+ active trials on Epic or Cerner.
What to consider
OnCore documents site finances, billing compliance and EHR integration. A January 2026 University of Arkansas for Medical Sciences release says it is used by 80% of NCI-designated cancer centers. It is built for large, centralized research offices, not small independent sites.
Read product profile

CRIO Site CTMS

Best for
Independent sites and site networks that run most studies on eSource and want CTMS in the same system.
What to consider
CRIO's CTMS is built around its eSource, with feasibility searches, screenings and scheduling. Its 2025 security white paper reports 2,500 sites in 30 countries. Its certifications cover its cloud data centers rather than CRIO itself, and it publishes no prices.
Read product profile

Compare the features

Both products use the same category definitions. Product order is editorial; products are not ranked.

Full CTMS feature comparison

Single and double checks describe documented support for an individual feature. Double checks use the extended definition for that feature. Unknown means the available evidence does not establish support.

Expand a feature definition or support note for context and its original source.

Advarra OnCore vs CRIO Site CTMS (CTMS): category feature evidence and sources. Products are not ranked.
Category featureAdvarra OnCoreCRIO Site CTMS
Study, participant and visit tracking
Feature definitions
Supported
Study participants or visits can be tracked.
Extended support
Participant outreach or pre-screening plus visit scheduling are documented.
Supported

OnCore builds protocol calendars and automatic subject calendars for visit tracking and integrates with Epic, but public material does not describe recruitment or pre-screening tools.

Source
About this support label

Visit calendars establish base support; recruitment and pre-screening are not described.

Extended support

CRIO's Site CTMS combines a patient database with feasibility searches, phone screenings, pre-screening visits and scheduling that flows straight into eSource.

Source
About this support label

Patient searches and pre-screening combine with scheduling into eSource.

Site finances
Feature definitions
Supported
Study budgets, invoicing, receivables or payment reconciliation are documented.
Extended support
Study finance workflows include research billing designations or billing-grid links to an EHR.
Extended support

OnCore covers budget creation and negotiation, automated invoicing and payment reconciliation, and records billing designations per visit or procedure with a qualifying clinical trial checklist.

Source
About this support label

Budgeting, invoicing and reconciliation include visit/procedure billing designations and a trial checklist.

Supported

It sets visit- and procedure-level receivables, generates and tracks invoices, reconciles sponsor payments, supports GAAP reporting and pays patient stipends, but describes no research billing compliance features.

Source
About this support label

Invoicing and payment reconciliation are stated; research billing compliance is not described.

Connected site tools and integrations
Feature definitions
Supported
Integration or data exchange with another system or application is described.
Extended support
Integration with a clinical-trial application plus an API for integration are both stated.
Extended support

Advarra lists Epic and Cerner integration, its Part 11-compliant eReg and EDC, eIRB via API and Advarra Payments as OnCore integrations.

Source
About this support label

eReg and EDC connect to OnCore, with eIRB linked through an API.

Supported

CRIO combines its own eSource, eConsent, eRegulatory and CTMS and integrates with Veeva Vault EDC and Medidata Rave, but documents no EHR integration or public API.

Source
About this support label

Native trial tools and EDC links establish base support; an EHR link or public API is not documented.

Proven fit and adoption
Feature definitions
Supported
Published product or wider-platform adoption, or a named clinical-research deployment.
Extended support
Product-specific study, customer, institution, site or participant figures plus a published country count establish international use.
Supported

A January 2026 University of Arkansas for Medical Sciences release says OnCore is used by 80% of NCI-designated cancer centers.

Source
Extended support

CRIO's 2025 security white paper reports 2,500 sites, 6,000 protocols and 5 million patients in 30 countries.

Source
About this support label

Product-specific site, protocol and patient adoption is reported across a stated country count.

Compliance and security
Feature definitions
Supported
Relevant trial compliance or security controls are stated, with their scope identified.
Extended support
Relevant trial controls and a publicly accessible ISO certificate or SOC audit report covering the product or vendor are documented.
Supported

Advarra states its cloud-based technology holds ISO 27001:2013 and SOC 2 Type 2 certification, but it claims Part 11 for its eReg and EDC rather than the CTMS and makes no HIPAA statement for OnCore.

Source
About this support label

Part 11 is stated for linked eReg/EDC; public ISO/SOC document access is not established.

Supported

CRIO says it supports 21 CFR Part 11, HIPAA, EU Annex 11 and GDPR; its SOC 2 and ISO 27001 statements cover its Google Cloud data centers, not CRIO itself.

Source
About this support label

Trial controls are stated; the ISO/SOC claims cover Google Cloud data centers rather than CRIO.

Published pricing and terms
Feature definitions
Supported
A pricing basis, model or contract terms are published beyond contact sales.
Extended support
Production prices or a free production option are published, with amounts and conditions stated.
Supported

Advarra describes the pricing model (an annual subscription priced on licensed modules and protocol volume) but publishes no prices.

Source
Unknown

CRIO publishes no prices or pricing model.

Source
About this support label

The note finds neither published prices nor a pricing model.

Unknown does not mean unavailable. The public evidence does not establish support under this category’s definition.

The guide update date reflects guide edits. Vendor statements are attributed in the evidence.

Keep the category in view

Compare these products with the other tools in the CTMS guide using the same feature definitions.

More CTMS comparisons featuring one of these products.