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.
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.
Academic medical centers, hospitals and multi-center research networks that need deep Epic integration, including on-premise deployments.
What to consider
Velos eResearch is a long-standing research management system with deep Epic integration and billing support. WCG publishes little about current customer numbers or pricing.
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.
CRIO Site CTMS vs Velos eResearch (CTMS): category feature evidence and sources. Products are not ranked.
Category feature
CRIO Site CTMS
Velos eResearch
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.
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.
Velos eResearch
Supported
At UMMC, every participant is enrolled in Velos, which searches Epic for patient records and links enrolled participants to the study in Epic; WCG does not describe recruitment or pre-screening workflows.
Participant enrollment and Epic links establish tracking; recruitment and pre-screening are not described.
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.
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.
Invoicing and collections connect study billing calendars and research designations to Epic at UMMC.
Connected site tools and integrationsFeature 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.
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.
Native trial tools and EDC links establish base support; an EHR link or public API is not documented.
Velos eResearch
Extended support
WCG lists its own EDC and eSource, eConsent, a participant portal and APIs, plus integrations with EHRs, IRB, billing and eRegulatory binders; eRegulatory is an integration, not a native module.
Named client usage establishes base adoption; an international product footprint is not established.
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.
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.
Trial controls are stated; the ISO/SOC claims cover Google Cloud data centers rather than CRIO.
Velos eResearch
Supported
WCG holds a HIPAA certification that covers eResearch and says Velos meets 21 CFR Part 11, but its ISO 27001:2022 certificate covers WCG products without naming Velos.