Biotech sponsors running clinical trials in the EU must comply with pharmacovigilance and safety reporting requirements from the first subject enrolled through the end of the development program. The regulatory framework for clinical trial safety is defined by the EU Clinical Trials Regulation (EU) 2014/536, ICH E2A (clinical safety data management), and ICH E2F (Development Safety Update Report).
This article covers the setup of sponsor pharmacovigilance activities, SUSAR reporting obligations, DSUR preparation, and EU CTR/CTIS implementation.
Setting Up Pharmacovigilance for Clinical Trial Sponsors
Regulatory Context
Every clinical trial sponsor must have a pharmacovigilance system capable of:
- Collecting and recording all adverse events (AEs) and serious adverse events (SAEs) from clinical trials
- Identifying Suspected Unexpected Serious Adverse Reactions (SUSARs)
- Reporting SUSARs to regulatory authorities and ethics committees within mandated timelines
- Preparing annual Development Safety Update Reports (DSURs)
- Maintaining a Reference Safety Information (RSI) document (typically the Investigator's Brochure)
Under the EU CTR (EU) 2014/536, these obligations apply to all clinical trials conducted in the EU, regardless of the sponsor's location.
Building the Safety Framework
Step 1: Safety Management Plan (SMP)
The SMP defines how safety will be managed throughout the trial. It should include:
- Roles and responsibilities for safety data collection and reporting
- Processes for AE/SAE collection from investigators
- SUSAR identification and reporting procedures
- Unblinding procedures for blinded trials
- Safety communication plan (to investigators, ethics committees, regulatory authorities)
- Data Safety Monitoring Board (DSMB) or Safety Review Committee (SRC) charter and procedures
Step 2: Safety Database and Reporting Infrastructure
Sponsors need a validated safety database capable of:
- Capturing all trial AEs and SAEs in ICH E2B(R3) format
- Coding events using MedDRA
- Identifying SUSARs through comparison against the Reference Safety Information
- Generating expedited reports for electronic submission to EudraVigilance
- Supporting DSUR data extraction and analysis
Step 3: Training
All personnel involved in safety data handling must be trained on:
- AE/SAE definitions per ICH E2A
- SUSAR identification criteria
- Reporting timelines and procedures
- The sponsor's specific SOPs for safety management
Step 4: Agreements with CROs and Co-Sponsors
If safety activities are delegated to a CRO, the sponsor must establish clear contractual agreements defining responsibilities, timelines, quality expectations, and oversight mechanisms. Per GVP Module I, the sponsor retains ultimate responsibility regardless of delegation.
SUSAR Reporting: Definitions and Timelines
What is a SUSAR?
A Suspected Unexpected Serious Adverse Reaction (SUSAR) is an adverse event that meets all three criteria:
- Suspected: There is a reasonable causal relationship between the drug and the event
- Unexpected: The nature or severity of the event is not consistent with the Reference Safety Information (Investigator's Brochure for investigational products)
- Serious: The event results in death, is life-threatening, requires hospitalization (or prolongation), causes persistent disability, is a congenital anomaly, or is otherwise medically important
These definitions are established in ICH E2A and applied in the EU through the EU CTR (EU) 2014/536, Articles 41-43.
Reporting Timelines
- Fatal or life-threatening SUSARs: 7 calendar days (initial) + 8 additional days (follow-up) from Day 0 — reported to EudraVigilance + ethics committees
- All other SUSARs: 15 calendar days from Day 0 — reported to EudraVigilance + ethics committees
Day 0 is the date the sponsor first becomes aware of the minimum information for a reportable SUSAR.
Investigator Notification
In addition to regulatory reporting, the sponsor must inform all investigators participating in clinical trials with the same investigational product about SUSARs that could affect subject safety. This notification must be timely and documented.
Development Safety Update Report (DSUR)
What is a DSUR?
The Development Safety Update Report is an annual safety assessment of an investigational medicinal product during its clinical development. The format and content are defined by ICH E2F.
DSUR Content Structure (per ICH E2F)
- Introduction: Product name, reporting period, development status
- Worldwide marketing approval status: Any countries where the product is already marketed
- Actions taken for safety reasons: Any safety-related changes to the Investigator's Brochure, protocol amendments, clinical holds, or regulatory actions
- Changes to the Reference Safety Information: Modifications to the RSI during the reporting period
- Status of ongoing and completed clinical trials: Summary of all trials, enrollment numbers, and significant protocol amendments
- Estimated cumulative subject exposure: Number of subjects exposed to the investigational product across all trials
- Summary of important safety findings: Key safety data from the reporting period, including SUSARs, SAEs, and safety signals
- Safety signal assessment: Evaluation of any new or ongoing safety signals identified during the period
- Overall benefit-risk assessment: The sponsor's assessment of the overall benefit-risk balance based on all available safety data
- Conclusion and recommendations: Summary of the safety assessment with recommendations for continued development
DSUR Submission
DSURs are submitted annually to all regulatory authorities in countries where clinical trials are ongoing. Under the EU CTR, DSURs are submitted through the Clinical Trials Information System (CTIS). The reporting period aligns with the Development International Birth Date (DIBD) — the date of the first approval or authorization to conduct a clinical trial anywhere in the world.
EU Clinical Trials Regulation (CTR) and CTIS
Understanding the EU CTR
The EU Clinical Trials Regulation (EU) 2014/536 replaced the previous Clinical Trials Directive (2001/20/EC) and introduced:
- Single submission portal: The Clinical Trials Information System (CTIS) serves as the single entry point for clinical trial applications across all EU member states
- Harmonized assessment: Coordinated assessment of clinical trial applications by member states concerned
- Enhanced safety reporting: SUSARs are reported through EudraVigilance (rather than individually to each NCA)
- Transparency: Clinical trial data and results are publicly available through CTIS
CTIS Operations
Sponsors must use CTIS for:
- Submitting clinical trial applications (initial and amendments)
- Managing safety reporting (SUSAR submission through EudraVigilance integration)
- Uploading DSURs
- Communicating with regulatory authorities and ethics committees
- Reporting trial results
Practical Challenges and Advice
- Training: CTIS is a complex system with a steep learning curve. Ensure that your regulatory and PV team members complete EMA's CTIS training modules before they need to use the system.
- Timeline management: CTIS has strict timelines for application processing, responses to requests for information, and safety report submission. Missing these timelines can delay trial authorization.
- Transition considerations: Trials authorized under the previous Directive were required to transition to the CTR by January 2025. Sponsors with ongoing transitional trials should verify that their safety reporting is aligned with CTR requirements.
Conclusion
Pre-marketing safety is a critical phase where pharmacovigilance infrastructure and processes directly affect patient safety and regulatory timelines. Biotech sponsors must establish robust safety frameworks, maintain vigilant SUSAR identification and reporting, prepare comprehensive DSURs, and navigate the EU CTR/CTIS system effectively.
The regulatory requirements are clear — EU CTR (EU) 2014/536, ICH E2A, and ICH E2F define what is expected. For biotech sponsors without extensive PV experience, partnering with a specialized provider ensures that safety obligations are met from the first patient enrolled.