Whether a sponsor should own or license its own clinical systems depends on how many studies it plans, how likely it is to work with more than one CRO, how much direct access it needs to its data and documents, and whether it has the capacity to manage systems. Using a CRO's systems is efficient for a single study. Owning key systems gives continuity across studies and vendors, but brings responsibilities a small team must be ready to carry.
Which systems are we talking about?
Electronic data capture, the electronic trial master file, a clinical trial management system, randomization and trial supply management, the safety database and electronic patient-reported outcomes. Each can be provided by the CRO, licensed by the sponsor or, in some cases, run on the sponsor's platform by the CRO.
What are the benefits of using the CRO's systems?
Speed, because the systems are already set up and validated. Integration with the CRO's processes and staff. Lower burden on the sponsor's team. And often simpler pricing, since system costs are bundled into the study.
What are the risks?
Portability. When a sponsor changes CROs or runs a second study elsewhere, data and documents must be exported, transferred and sometimes reformatted. Direct access can be limited or slow. Standards can differ from study to study. Archiving responsibilities may be unclear at close-out. And the sponsor becomes dependent on one vendor's platform for its own records.
When does owning or licensing systems make sense?
When the sponsor expects several studies over the next few years, plans to use more than one CRO, wants consistent data standards across its program, needs real-time access for decision-making or anticipates partnering diligence. The eTMF and EDC are often the first systems sponsors choose to control, because they hold the program's long-term record.
Is there a middle path?
Yes, and it is common. The sponsor licenses a system and grants the CRO access to operate it. The sponsor keeps ownership and continuity, while the CRO does the day-to-day work. The contract should state clearly who administers the system, who validates configurations, how access is managed and how data are exported at the end.
What responsibilities come with owning systems?
Qualifying the system vendor, overseeing validation so the system is fit for purpose, managing user access, protecting data privacy and security, maintaining audit trails and backups, and archiving records for the required retention period. ICH E6(R3) places clear emphasis on computerized systems being fit for purpose and appropriately controlled, whoever operates them.
How should a sponsor decide?
Ask five questions. How many studies do we expect in the next three years? How likely are we to change or add CROs? Who will administer the systems? What budget can we commit? And how quickly do we need access to our own data? The answers usually make the choice clear.
Keep reading: CDISC From Day One: Why Small Sponsors Pay Later
