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.
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.
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.
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 feature
Advarra OnCore
CRIO Site CTMS
Study, participant and visit trackingFeature definitions
Supported
Study participants or visits can be tracked.
Extended support
Participant outreach or pre-screening plus visit scheduling are documented.
Advarra OnCore
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.
Visit calendars establish base support; recruitment and pre-screening are not described.
CRIO Site CTMS
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.
Patient searches and pre-screening combine with scheduling into eSource.
Site financesFeature 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.
Advarra OnCore
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.
Budgeting, invoicing and reconciliation include visit/procedure billing designations and a trial checklist.
CRIO Site CTMS
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.
eReg and EDC connect to OnCore, with eIRB linked through an API.
CRIO Site CTMS
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.
Product-specific site, protocol and patient adoption is reported across a stated country count.
Compliance and securityFeature 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.
Advarra OnCore
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.
Part 11 is stated for linked eReg/EDC; public ISO/SOC document access is not established.
CRIO Site CTMS
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.