Compare software for research-site operations and participant workflows across study operations, finances, integrations, adoption, security and published pricing. WeGuide supports participant engagement alongside a CTMS; it does not replace site budgeting, billing or operational management. Public sources are linked per feature.
Best forResearch 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.
Updated Nov 13, 20267 tools compared
CTMS
What does CTMS software do?
CTMS stands for clinical trial management system. It organizes the operational side of research: studies, participants, visits, staff tasks and finances. This guide focuses on research-site systems, where calendars, budgets and sponsor invoicing are common requirements.
See documented feature support at a glance. Select a symbol for the explanation and source. Double checks indicate documented extra capabilities; unknown does not mean unavailable.
Products are not ranked. Table order is chosen for each guide and does not indicate a recommendation.
Columns 6 of 6
Feature 1 of 6
Select a symbol to read its evidence and source. Scroll sideways for all features.
Documented feature support for each product. Symbols describe individual features, not overall product ratings.
Visit calendars establish base support; recruitment and pre-screening are not described.
Supported means: Study participants or visits can be tracked.
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.
Budgeting, invoicing and reconciliation include visit/procedure billing designations and a trial checklist.
Extended support means: Study finance workflows include research billing designations or billing-grid links to an EHR.
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.
Part 11 is stated for linked eReg/EDC; public ISO/SOC document access is not established.
Supported means: Relevant trial compliance or security controls are stated, with their scope identified.
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.
Participant outreach combines with scheduling, check-in/out and staff capacity planning.
Extended support means: Participant outreach or pre-screening plus visit scheduling are documented.
Clinical Conductor supports scheduling, check-in and check-out, staff calendars and capacity planning across sites, plus participant outreach by text, email and phone.
Billing reconciliation is documented alongside an EMR billing-grid integration.
Extended support means: Study finance workflows include research billing designations or billing-grid links to an EHR.
It centralizes billing across sites, reconciles visit and non-visit revenue, shows gaps between expected and realized revenue and pays participants through CCPay, and Advarra lists an EMR billing-grid integration.
Connected eReg and eSource/EDC tools are listed alongside the CTMS API partner program.
Extended support means: Integration with a clinical-trial application plus an API for integration are both stated.
Advarra lists integrated eReg and eSource + EDC, EMR integrations (billing grid, demographics, subject and protocol data), Advarra Payments and a general-ledger link, and runs an API partner program for its CTMS products.
Part 11 covers linked eReg/eSource and HIPAA covers CCText; public ISO/SOC document access is not established.
Supported means: Relevant trial compliance or security controls are stated, with their scope identified.
Advarra states its cloud-based technology holds ISO 27001:2013 and SOC 2 Type 2 certification, but claims Part 11 only for the linked eReg and eSource products and HIPAA only for the CCText module.
Patient searches and pre-screening combine with scheduling into eSource.
Extended support means: Participant outreach or pre-screening plus visit scheduling are documented.
CRIO's Site CTMS combines a patient database with feasibility searches, phone screenings, pre-screening visits and scheduling that flows straight into eSource.
Invoicing and payment reconciliation are stated; research billing compliance is not described.
Supported means: Study budgets, invoicing, receivables or payment reconciliation are documented.
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.
Native trial tools and EDC links establish base support; an EHR link or public API is not documented.
Supported means: Integration or data exchange with another system or application is described.
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.
Extended support means: Product-specific study, customer, institution, site or participant figures plus a published country count establish international use.
CRIO's 2025 security white paper reports 2,500 sites, 6,000 protocols and 5 million patients in 30 countries.
Trial controls are stated; the ISO/SOC claims cover Google Cloud data centers rather than CRIO.
Supported means: Relevant trial compliance or security controls are stated, with their scope identified.
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.
Recruitment queries and pre-screening combine with visit target dates and window enforcement.
Extended support means: Participant outreach or pre-screening plus visit scheduling are documented.
RealTime-CTMS tracks subjects from referral to completion, calculates visit target dates with window enforcement, and supports recruitment database queries and pre-screening tracking.
Study finances and stipends are stated; research billing compliance is not described.
Supported means: Study budgets, invoicing, receivables or payment reconciliation are documented.
It tracks budgets, completed visits, invoices with aging reports, receivables, payables and subject stipends through SitePay, but RealTime does not describe research billing compliance features.
Budgeting, invoicing and reconciliation are stated; research billing compliance is not described.
Supported means: Study budgets, invoicing, receivables or payment reconciliation are documented.
It tracks study budgets, generates invoices automatically, reconciles payments and reports earned versus forecasted revenue, with no research billing compliance features described.
SiteVault connects eISF and eConsent; API access requires the Enterprise tier.
Extended support means: Integration with a clinical-trial application plus an API for integration are both stated.
It shares data with SiteVault eISF and eConsent and with sponsors on Veeva's platform; API access is an Enterprise feature, and no eSource or EHR integration is described.
Participant progress is documented; site-wide visit scheduling is not established here.
Supported means: Study participants or visits can be tracked.
Dashboards show participant check-ins and questionnaire progress. This is participant follow-up, not a claim of full site visit-calendar or monitoring management.
The available evidence does not establish this feature. This does not mean it is unavailable.
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.
Named clinical-trial system connections and integration APIs meet the shared definition; a specific CTMS connector still needs confirmation.
Extended support means: Integration with a clinical-trial application plus an API for integration are both stated.
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 research use establishes base support; adoption here concerns the participant platform rather than a CTMS product.
Supported means: Published product or wider-platform adoption, or a named clinical-research deployment.
BRACE and INHERIT document participant research deployments. These examples are not CTMS customer counts or evidence that WeGuide performs full site operations.
Public statements establish the documented-support level; no public certificate or audit report establishes extended support.
Supported means: Relevant trial compliance or security controls are stated, with their scope identified.
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.
Participant enrollment and Epic links establish tracking; recruitment and pre-screening are not described.
Supported means: Study participants or visits can be tracked.
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.
Clinical applications and APIs are stated alongside EHR, IRB, billing and eRegulatory integrations.
Extended support means: Integration with a clinical-trial application plus an API for integration are both stated.
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.
HIPAA and Part 11 are stated; the ISO certificate scope does not name Velos.
Supported means: Relevant trial compliance or security controls are stated, with their scope identified.
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.
Every product uses the same definitions. Double checks indicate documented extra capabilities in that column; they do not indicate an overall winner. Unknown means the available sources do not establish support.
Study, participant and visit tracking
Supported: Study participants or visits can be tracked.
Extended support: Participant outreach or pre-screening plus visit scheduling are documented.
Site finances
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.
Connected site tools and integrations
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.
Proven fit and adoption
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.
Compliance and security
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.
Published pricing and terms
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.
Read the detailed feature comparison
Columns 6 of 6
Feature 1 of 6
Select a feature label for its details and source. Scroll sideways for all features.
Feature statements for each product, with public sources. Products appear in editorial order.
Visit calendars; recruitment not documented — details and source
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.
Budgets, invoicing + billing designations — details and source
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.
ISO/SOC stated; Part 11 in linked modules — details and source
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.
Scheduling, capacity + participant outreach — details and source
Clinical Conductor supports scheduling, check-in and check-out, staff calendars and capacity planning across sites, plus participant outreach by text, email and phone.
Billing reconciliation + CCPay stipends — details and source
It centralizes billing across sites, reconciles visit and non-visit revenue, shows gaps between expected and realized revenue and pays participants through CCPay, and Advarra lists an EMR billing-grid integration.
eReg, eSource, EMR + API partner program — details and source
Advarra lists integrated eReg and eSource + EDC, EMR integrations (billing grid, demographics, subject and protocol data), Advarra Payments and a general-ledger link, and runs an API partner program for its CTMS products.
ISO/SOC stated; Part 11 in linked modules — details and source
Advarra states its cloud-based technology holds ISO 27001:2013 and SOC 2 Type 2 certification, but claims Part 11 only for the linked eReg and eSource products and HIPAA only for the CCText module.
Feasibility, screening + eSource scheduling — details and source
CRIO's Site CTMS combines a patient database with feasibility searches, phone screenings, pre-screening visits and scheduling that flows straight into eSource.
Invoices + stipends; billing compliance not described — details and source
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.
Native suite + EDC links; EHR/API not documented — details and source
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.
Part 11/HIPAA stated; ISO/SOC cover data centers — details and source
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.
Referral tracking, screening + visit windows — details and source
RealTime-CTMS tracks subjects from referral to completion, calculates visit target dates with window enforcement, and supports recruitment database queries and pre-screening tracking.
Budgets, invoices + SitePay stipends — details and source
It tracks budgets, completed visits, invoices with aging reports, receivables, payables and subject stipends through SitePay, but RealTime does not describe research billing compliance features.
Budgets, auto-invoicing + reconciliation — details and source
It tracks study budgets, generates invoices automatically, reconciles payments and reports earned versus forecasted revenue, with no research billing compliance features described.
eISF + eConsent; API on Enterprise — details and source
It shares data with SiteVault eISF and eConsent and with sponsors on Veeva's platform; API access is an Enterprise feature, and no eSource or EHR integration is described.
Participant progress and response dashboards — details and source
Dashboards show participant check-ins and questionnaire progress. This is participant follow-up, not a claim of full site visit-calendar or monitoring management.
Site budgets and invoicing not documented — details and source
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.
Named EDC connections and REST/FHIR APIs — details and source
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 multinational participant research — details and source
BRACE and INHERIT document participant research deployments. These examples are not CTMS customer counts or evidence that WeGuide performs full site operations.
Trial/privacy controls and ISO certification stated — details and source
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.
Epic enrollment at UMMC; recruitment not described — details and source
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.
EDC, eSource + APIs; eReg via integration — details and source
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.
HIPAA stated; ISO scope does not name Velos — details and source
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.
Advarra OnCoreStudy fit: academic medical centers, NCI-designated cancer centers and health systems running 50 to 500+ active trials on Epic or Cerner.
Advarra Clinical ConductorStudy fit: site networks, hospitals and independent research sites that run research as a business and need finances across several sites.
CRIO Site CTMSStudy fit: independent sites and site networks that run most studies on eSource and want CTMS in the same system.
RealTime-CTMSStudy fit: independent research sites and site networks that want CTMS, eSource, eReg and participant payments from one vendor.
Veeva SiteVault CTMSStudy fit: small and mid-size sites with up to 20 active studies, especially sites already using SiteVault eISF with sponsors on Veeva.
WeGuideStudy fit: research sites and study teams that need ongoing participant engagement, screening, consent, questionnaires and follow-up across clinical trials and research studies
Velos eResearchStudy fit: academic medical centers, hospitals and multi-center research networks that need deep Epic integration, including on-premise deployments.
HIPAA certification covering WCG MyPatient and eResearch; ISO 27001:2022 for WCG products supported by its Technology Solutions shared services (Velos not named)
Study fit: academic medical centers, NCI-designated cancer centers and health systems running 50 to 500+ active trials on Epic or Cerner.
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.
Study, participant and visit tracking
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.
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.
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.
Study fit: site networks, hospitals and independent research sites that run research as a business and need finances across several sites.
Clinical Conductor supports site operations and finances for networks and independent sites, including scheduling, participant outreach and centralized billing. Advarra publishes no pricing and no customer count for this product alone.
Study, participant and visit tracking
Clinical Conductor supports scheduling, check-in and check-out, staff calendars and capacity planning across sites, plus participant outreach by text, email and phone.
It centralizes billing across sites, reconciles visit and non-visit revenue, shows gaps between expected and realized revenue and pays participants through CCPay, and Advarra lists an EMR billing-grid integration.
Advarra lists integrated eReg and eSource + EDC, EMR integrations (billing grid, demographics, subject and protocol data), Advarra Payments and a general-ledger link, and runs an API partner program for its CTMS products.
Advarra states its cloud-based technology holds ISO 27001:2013 and SOC 2 Type 2 certification, but claims Part 11 only for the linked eReg and eSource products and HIPAA only for the CCText module.
Study fit: independent sites and site networks that run most studies on eSource and want CTMS in the same system.
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.
Study, participant and visit tracking
CRIO's Site CTMS combines a patient database with feasibility searches, phone screenings, pre-screening visits and scheduling that flows straight into eSource.
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.
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.
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.
Study fit: independent research sites and site networks that want CTMS, eSource, eReg and participant payments from one vendor.
RealTime pairs strong participant and visit tracking with a full set of its own site tools. It publishes no customer count or prices and lists no EHR integration.
Study, participant and visit tracking
RealTime-CTMS tracks subjects from referral to completion, calculates visit target dates with window enforcement, and supports recruitment database queries and pre-screening tracking.
It tracks budgets, completed visits, invoices with aging reports, receivables, payables and subject stipends through SitePay, but RealTime does not describe research billing compliance features.
Study fit: small and mid-size sites with up to 20 active studies, especially sites already using SiteVault eISF with sponsors on Veeva.
SiteVault CTMS is the only free option here and has strong compliance backing. It is a young product (announced in 2025) with lighter recruitment, eSource and EHR features than the established site CTMS tools.
Study, participant and visit tracking
SiteVault CTMS supports study-specific visit calendars and real-time logging of visits and procedures; Veeva does not describe recruitment features.
It tracks study budgets, generates invoices automatically, reconciles payments and reports earned versus forecasted revenue, with no research billing compliance features described.
It shares data with SiteVault eISF and eConsent and with sponsors on Veeva's platform; API access is an Enterprise feature, and no eSource or EHR integration is described.
Study fit: research sites and study teams that need ongoing participant engagement, screening, consent, questionnaires and follow-up across clinical trials and research studies
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.
Study, participant and visit tracking
Dashboards show participant check-ins and questionnaire progress. This is participant follow-up, not a claim of full site visit-calendar or monitoring management.
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.
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.
BRACE and INHERIT document participant research deployments. These examples are not CTMS customer counts or evidence that WeGuide performs full site operations.
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.
Quoted per study, with hosting, support and modules included. Email hello@weguide.health for a study-specific quote; price amounts are not published.Source
Compliance claims
Supports 21 CFR Part 11 requirements (stated); EU Annex 11 not statedSource
Compliance claims
WeGuide states 21 CFR Part 11 and HIPAA support; confirm the study-specific validation scope and BAA requirements.Source
Security certifications
ISO 27001:2022 (stated; certificate not published); no SOC 2 claim foundSource
Less suitable for replacing a site CTMS for study budgets, sponsor invoicing, billing compliance or site-wide operational management.
Study fit: academic medical centers, hospitals and multi-center research networks that need deep Epic integration, including on-premise deployments.
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.
Study, participant and visit tracking
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.
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.
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 certification covering WCG MyPatient and eResearch; ISO 27001:2022 for WCG products supported by its Technology Solutions shared services (Velos not named)Source
Less suitable for small independent sites looking for published pricing or a free entry tier.
This guide compares 7 products across the same feature topics. Each statement describes what the available public sources document, including limitations and study requirements.
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.
Study, participant and visit tracking
Site finances
Connected site tools and integrations
Proven fit and adoption
Compliance and security
Published pricing and terms
A vendor’s published claim is not independent confirmation that a product will meet your study’s needs. Check deployment, validation, integrations and commercial terms with the vendor.
Outside this comparison: Florence is not included: it sells eISF (eBinders), SiteLink, eTMF and eConsent and connects to a site's CTMS rather than offering its own. Sponsor and CRO CTMS products (Veeva Vault CTMS, Oracle Siebel CTMS, Medidata CTMS, IQVIA) are out of scope for this site list.
A clinical trial management system (CTMS) tracks the operational side of trials: studies, participants and visits, staff tasks and money. Site CTMS products focus on visit schedules, site budgets and sponsor invoicing; sponsor and CRO CTMS products focus on oversight across many sites and countries.
Is there a free CTMS for research sites?
Yes. Veeva SiteVault Free includes CTMS, eISF and eConsent at no cost for sites managing 20 or fewer concurrent active studies; larger sites move to the paid SiteVault Enterprise edition.
Which CTMS do cancer centers use?
Mostly OnCore. A January 2026 University of Arkansas for Medical Sciences release says OnCore is used by 80% of NCI-designated cancer centers, and Advarra says its CTMS products are used by more than 90 of the top 125 academic medical centers.
What is the difference between OnCore and Clinical Conductor?
Both are Advarra products. Advarra positions OnCore for academic medical centers, NCI-designated cancer centers and health systems with centralized research operations, and Clinical Conductor for site networks, hospitals and independent research sites.
Why are Veeva Vault CTMS, Oracle Siebel CTMS and Medidata CTMS not on this list?
They are built for sponsors and CROs that oversee trials across many sites and countries, which is a different job from running a site's own studies and finances. They belong on a separate sponsor and CRO list with its own criteria.