On 13 October 2026, IQVIA selected Veeva CTMS, eTMF, Study Startup, and Site Connect as standard applications across its clinical development studies. The choice extends an earlier EDC partnership, while leaving customers free to choose their EDC, randomization, and patient-reported outcome systems. IQVIA’s announcement lists the applications and the choices it leaves open.
The selection gives IQVIA a shared operational stack. Across sponsor, CRO, and site, who owns the status people use to decide what happens next? The operating model is the constraint. A Clinical Trial Management System (CTMS) can put site activity, milestones, monitoring, and issues in view. The people running the study decide what each status means and who acts on it.
What “complete” means across systems
A trial uses several systems. EDC records participant data required by the protocol. The eTMF holds essential trial documents. RTSM handles randomization and investigational product supply. The CTMS tracks site activity, milestones, and monitoring. Veeva describes connections across these functions in its CTMS workflows, randomization and supply tools, and clinical operations suite.
Consider a site after a protocol change. Staff finish new training; the site records it, the CRO checks it, and the sponsor decides whether enrollment can resume. The training record may sit in the eTMF, the task in CTMS, and a local copy at the site. A “complete” field can travel between systems. The parties still need a rule for which staff and protocol version count. That small status hides three decisions. Which staff are in scope? What record proves training on the active protocol version? Which role can release the site? A system can carry those fields and route an exception, but the workflow has to assign an owner to each one. Otherwise, the CRO may finish its check while the sponsor is still waiting on approval.
Veeva says its CTMS supports monitoring, issue resolution, reporting, and daily data transfers between sponsors and CROs. Its EDC connection can make enrollment information visible in CTMS. The pages document product functions; IQVIA’s eventual configuration remains unreported. Veeva’s CTMS page describes the functions and connections.
A delegated task still has an owner
Sponsors assign trial work to CROs and other service providers. ICH E6(R3) says transferred activities should be documented in an agreement. The sponsor remains responsible for activities it did not transfer and retains ultimate responsibility for its trial-related work. It also has to oversee important activities carried out by service providers. Sections 3.6 and 3.9 of ICH E6(R3) describe this relationship.
That responsibility boundary gives the status its consequence. Here, the CRO verifies the training record and updates CTMS. The sponsor decides what evidence is enough to reopen enrollment. These records mark different steps in the handoff; the operating model names which role accepts each one.
E6(R3) also calls for documentation of computerized systems, their functions and interfaces, validation status, user roles, and access. In practice, the team needs to know where an event is recorded, how it reaches the next system, and who may change it. A connected application makes the route visible; the study documents the roles along it. The final guidance covers sponsor oversight and computerized-system controls.
One sponsor stack meets many site workflows
IQVIA chose four applications and kept customer choice over EDC, randomization, and patient-reported outcomes. That gives its teams a standard set of operational tools while leaving some connected systems open. The announcement reports the selection; it gives no deployment results or site workload measures. The announcement states the selected applications and remaining choices.
Sites work with many sponsors and CROs. In Advarra’s 2023 Study Activation Survey, 55% of respondents rated sponsor-technology setup and training very or extremely burdensome. Sixty-seven percent said the burden had risen over five years, and nearly 70% reported six or more logins per study. The survey covered more than 500 North American clinical research professionals and was sponsored by Advarra, a research technology provider. The measure covered setup and training across sponsor technologies as a group. Advarra’s release provides the results and respondent profile.
A 2025 WCG survey asked more than 600 sites across several countries to name their three biggest challenges. Trial complexity led at 35%, study start-up at 31%, and staffing at 30%. Sponsor-provided technology ranked lower at 20%. WCG asked sites to rank their pressures; Advarra asked about setup and training burden. One survey rates a specific task; the other ranks it against wider site pressures. WCG’s release describes its survey and results.
Read together, the surveys put two views side by side. A sponsor can consolidate its applications while sites handle separate access, training, and exception processes across studies. That difference makes site workload a separate design question. Integration inside one organization says little about how many steps a site repeats for the next sponsor. The reports describe current burdens; no follow-up tracks IQVIA’s choice through to a site.
I read the IQVIA selection as a decision about its own operating stack. A site joins studies from many sponsors, each with separate access and training. Veeva documents daily CTMS transfers between sponsor and CRO, giving those teams a shared view of selected records. Sites still carry separate files and access rules across studies; a coherent sponsor portfolio can sit alongside a long list of site logins. The surveys offer no measure of what IQVIA’s selection will change. Veeva describes the daily transfer in its CTMS product page.
A common protocol field still needs an owner
FDA’s final M11 guidance, template, and technical specification give protocols common digital fields and terms for electronic exchange. A structured field could save teams from rebuilding the same protocol detail when they configure study systems. The format still leaves the study to decide who updates a site’s status after an amendment, which CRO role reports an exception, and who responds to a late milestone. FDA dates the final material to May 2026. The guidance page describes the protocol format and specification.
The CTMS can carry the site’s training update to the sponsor and CRO. The operating model decides whether that record clears the site to resume enrollment. A dashboard can show “complete”; the study still needs someone with authority to act on it.