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.
Velos eResearch
Best for
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.
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.
Velos eResearch vs WeGuide (CTMS): category feature evidence and sources. Products are not ranked.
Category feature
Velos eResearch
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.
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.
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.
Invoicing and collections connect study billing calendars and research designations to Epic at UMMC.
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.
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.
Clinical applications and APIs are stated alongside EHR, IRB, billing and eRegulatory integrations.
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.
Named client usage establishes base adoption; an international product footprint is not established.
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.
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.
HIPAA and Part 11 are stated; the ISO certificate scope does not name Velos.
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.