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.
Research sites and study teams that need ongoing participant engagement, screening, consent, questionnaires and follow-up across clinical trials and research studies
What to consider
WeGuide supports the participant-engagement side of running clinical trials and research studies. Screening, consent, questionnaires, reminders and remote follow-up work together in one study program, and dashboards show participant check-ins and questionnaire progress. The Integration Engine connects existing study systems where needed. Sites requiring study budgets, sponsor invoicing or site-wide operational management can use a dedicated CTMS alongside it; the need for additional software depends on those workflows.
Less suitable for
Replacing a site CTMS for study budgets, sponsor invoicing, billing compliance or site-wide operational management.
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 WeGuide (CTMS): category feature evidence and sources. Products are not ranked.
Category feature
CRIO Site CTMS
WeGuide
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.
WeGuide
Supported
Dashboards show participant check-ins and questionnaire progress. This is participant follow-up, not a claim of full site visit-calendar or monitoring management.
Participant progress is documented; site-wide visit scheduling is not established here.
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 payment reconciliation are stated; research billing compliance is not described.
WeGuide
Unknown
No public evidence reviewed establishes study-budget, sponsor-invoicing or site-receivables workflows in WeGuide. Its published role is a participant layer alongside the CTMS.
Unknown does not mean unavailable. The public evidence does not establish support under this category’s definition.
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.
WeGuide
Extended support
The Integration Engine connects participant data with REDCap and other EDC systems using REST or FHIR APIs. Confirm any specific CTMS connector and field mapping.
Product-specific site, protocol and patient adoption is reported across a stated country count.
WeGuide
Supported
BRACE and INHERIT document participant research deployments. These examples are not CTMS customer counts or evidence that WeGuide performs full site operations.
Named research use establishes base support; adoption here concerns the participant platform rather than a CTMS product.
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.
WeGuide
Supported
WeGuide states ISO 27001:2022 certification and support for GDPR, HIPAA and 21 CFR Part 11. The public material does not provide the certificate or an audit report.