DDReg Pharma

Quailty Driven by Passion

Home » Blogs » DSUR for Clinical-Stage Companies: Building a Development Safety Update Report That Protects Your Trial

DSUR for Clinical-Stage Companies: Building a Development Safety Update Report That Protects Your Trial

DSUR for clinical Trials companies

Clinical-stage pharmaceutical and biopharmaceutical companies operate in a demanding regulatory environment where the safety of trial participants is both a moral obligation and a regulatory bedrock. The Development Safety Update Report (DSUR) is one of the most important and one of the most frequently underestimated regulatory documents in a clinical development programme. Its function is substantive: to provide a comprehensive, periodic, and analytical safety overview of an investigational product’s development status, with specific focus on identifying any new information that may alter the benefit-risk profile for ongoing clinical trials. 

For early-stage companies those running their first or second clinical trial, often without an established regulatory affairs infrastructure, DSUR preparation can feel like an administrative burden layered onto an already resource-constrained operation. That characterisation fundamentally misunderstands what the DSUR is and what it does. A well-prepared DSUR is a regulatory and scientific asset. A poorly prepared DSUR or a late one is a compliance failure with direct consequences for trial authorisation, IND or CTA continuity, and regulatory agency confidence.

Regulatory Basis for the DSUR

The DSUR is governed primarily by ICH E2F, Development Safety Update Report, adopted in 2011 and now implemented across all major ICH regions, including the EU, US, Japan, and Canada. Under ICH E2F, the DSUR must be prepared annually, covering 12 months beginning from the Development International Birth Date (DIBD), defined as the date of the first authorisation to conduct a clinical trial in any country. 

In the EU, DSURs are submitted under GCP Regulation (EU) No 536/2014 (the Clinical Trials Regulation, or CTR) via the Clinical Trials Information System (CTIS). In the US, DSURs are submitted to the FDA under applicable IND regulations (21 CFR Part 312), though the FDA refers to the document as an Annual Report under 21 CFR 312.33. In practice, ICH E2F-format DSURs are accepted by the FDA as a compliant annual report when accompanied by the US-specific IND annual report elements that are not captured in the E2F structure. 

Most major regulatory agencies that accept ICH guidelines, including Health Canada, TGA, MFDS in Korea, PMDA in Japan, and Swissmedic, require DSURs for ongoing clinical trials within their jurisdictions. The submission deadline is typically within 60 calendar days of the DIBD anniversary, though some agencies (including Health Canada) specify their own timelines.

The DIBD and Its Importance

The Development International Birth Date (DIBD) is the anchor for all DSUR-related timelines. It is defined as the date of first authorisation to conduct a clinical study with the investigational medicinal product (IMP) anywhere in the world. This is not necessarily the date the IND was submitted; it is the date the first authorisation (approval or non-objection) was granted. 

For clinical-stage companies with multiple active studies across multiple countries, the DIBD may predate current trials by several years. Companies that cannot definitively confirm their DIBD should audit their regulatory submission history before preparing any DSUR, as an incorrect DIBD will misdate every past and future reporting period. 

If a company is acquired or if a licensing agreement transfers development rights, the DIBD transfers with the product. Assuming a clean reporting slate after an acquisition is a compliance error; historical DSUR obligations follow the product. 

Structure and Content of the DSUR Under ICH E2F

ICH E2F defines a specific structure for the DSUR, and regulatory agencies expect submissions that conform to this structure. Deviations generate questions, and questions during DSUR review can trigger agency attention to the underlying safety data. 

Clinical Overview and Trial Status Summary

The DSUR opens with a brief description of the investigational product, its mechanism of action, the development rationale, and a summary of all ongoing, completed, and planned clinical trials within the reporting period. This section must be accurate, and current agencies will compare the trial status information in the DSUR against what is registered in public clinical trial databases (ClinicalTrials.gov, EudraCT/CTIS, WHO ICTRP). 

Discrepancies between the trial status reported in the DSUR and public registry information are a common source of regulatory queries. All trials, including those initiated and completed within the reporting period, as well as those terminated or suspended, must be included. 

Actions Taken for Safety Reasons

This section requires disclosure of any actions taken during the reporting period that were motivated by safety concerns, including protocol amendments, investigational brochure (IB) updates, informed consent revisions, dose modifications, study pauses, or regulatory notifications related to safety. This is one of the most closely scrutinised sections of the DSUR, because it documents the sponsor’s responsiveness to safety signals during the reporting period. 

A DSUR that reports no actions taken for safety reasons in a programme with meaningful clinical safety events will generate scrutiny. Conversely, a DSUR that lists actions without explaining the safety rationale will also generate questions. The analytical narrative that connects safety events to sponsor action (or to a reasoned decision not to act) is the core of effective DSUR writing. 

IB Changes

Any updates to the Investigator’s Brochure (IB) during the reporting period must be described, with the nature of the change and the safety basis for each update. The IB is the primary safety communication document for clinical investigators. Changes to it during the DSUR reporting period reflect the evolution of the sponsor’s understanding of the product’s safety profile. 

Where an IB change was prompted by a regulatory authority’s request, this should be explicitly noted. Where an IB change was pre-emptive initiated by the sponsor based on emerging safety information, the scientific basis for the change should be explained. 

Safety Data from Clinical Trials

The quantitative core of the DSUR is the presentation and analysis of safety data from all clinical trials active or completed during the reporting period. This includes: 

  • Serious Adverse Events (SAEs): All SAEs occurring in clinical trials, with narratives for fatal and life-threatening events and sponsor causality assessments 
  • Deaths: All deaths on study, with cause of death, relationship to study treatment, and sponsor assessment 
  • Discontinuations due to adverse events: Frequency, pattern, and causality assessment 
  • Notable non-serious adverse events: Where frequency or pattern suggests a class effect or dose-related signal 
  • Laboratory abnormalities and vital sign findings: Where these suggest emerging safety signals 
  • Pregnancy and lactation safety data: If the product profile warrants inclusion 

The presentation of safety data should be by System Organ Class (SOC) using MedDRA terminology. Aggregate frequencies should be presented with denominators (total subjects exposed, total exposure time) to allow meaningful rate calculations. 

Signal Analysis in DSUR

The signal analysis section is where many DSUR submissions are weakest and where sophisticated regulatory agencies focus most attention. ICH E2F expects sponsors to conduct a genuine benefit-risk analysis of the emerging safety profile, not simply to tabulate adverse events. 

Signal analysis in the DSUR should address: 

  • New signals identified during the reporting period: What new safety findings emerged from the clinical data, post-marketing safety reports (if the product is already approved for another indication), literature, or non-clinical studies? 
  • Assessment of causality: For each potential signal, what is the sponsor’s current assessment of the likelihood that the product causes the observed effect? 
  • Frequency and severity assessment: Is the signal a common finding of minor clinical significance, or a rare but potentially serious safety concern? 
  • Implication for the ongoing benefit-risk profile: Does the signal alter the sponsor’s assessment of whether the benefit-risk balance for ongoing trials remains favourable? 

A DSUR that presents safety data without signal analysis, or that concludes every section with “no new safety signals identified” without demonstrating a methodologically sound review process, will not satisfy ICH E2F’s analytical requirements. 

Common DSUR Deficiencies and How to Avoid Them

Regulatory agencies across the EU and the US have documented the following as the most common DSUR deficiencies: 

Incomplete trial status information: Not all trials are listed, or trial status is not current at the time of the data lock. Cross-reference trial status against all active IRB/EC approvals and clinical trial registry entries. 

No genuine signal analysis: The safety data section presents SAE tables without any analytical commentary on the significance of the data or the sponsor’s assessment of the product’s evolving safety profile. 

SUSAR reporting inconsistency: The SUSARs listed in the DSUR do not match the expedited reports submitted to regulators during the reporting period. This requires a reconciliation check before finalisation. 

Outdated benefit-risk conclusion: The benefit-risk assessment section repeats generic language about the product’s acceptable safety profile without reference to the specific data presented in the current DSUR. 

Missing literature review: ICH E2F explicitly requires a review of relevant published literature during the reporting period. Omitting this section or including a cursory reference to “no relevant literature identified” without a documented search strategy is a common deficiency. 

Conclusion

The DSUR is not a bureaucratic formality. It is the primary mechanism through which regulatory agencies assess whether an investigational product’s benefit-risk profile continues to support the conduct of ongoing trials. A DSUR that presents complete, analytically sound, and honestly characterised safety data with a clear narrative connecting data to conclusions builds agency confidence and protects the trials it covers. For clinical-stage companies, investing in DSUR capability early in the development programme is a strategic necessity, not an optional addition. 

DDReg’s clinical regulatory affairs and pharmacovigilance teams support clinical-stage pharmaceutical and biotech companies across the full DSUR lifecycle — from DIBD determination and DSUR programme setup through annual data preparation, signal analysis, benefit-risk assessment, and multi-jurisdictional submission. DDReg’s DSUR services are calibrated to the ICH E2F framework and adapted to specific agency requirements for the EU CTR/CTIS, US FDA IND Annual Reports, Health Canada, TGA, and MFDS submissions. 

Frequently Asked Questions

Is a DSUR required if a company only has one ongoing Phase 1 clinical trial?

Yes. The DSUR is required for any investigational medicinal product that has received regulatory authorisation for a clinical study, regardless of the number of ongoing trials or the development phase. The ICH E2F standard applies from the DIBD onward and continues annually until the programme is terminated or until marketing authorisation is granted and the DSUR transitions to a periodic safety update report (PSUR/PBRER).

What is the difference between a SUSAR report and a DSUR, and how do they relate?

SUSARs (Suspected Unexpected Serious Adverse Reactions) are individual case safety reports that must be submitted to regulatory authorities within expedited timelines (7 days for fatal or life-threatening events, 15 days for all other serious unexpected reactions). DSURs are annual aggregate documents that review all safety information, including SUSARs reported during the period, to assess the overall evolving safety profile of the investigational product. The DSUR includes a tabulation and analysis of SUSARs submitted during the reporting period, and discrepancies between the SUSAR tabulation in the DSUR and the expedited reports actually filed with agencies are a common inspection finding. Both are mandatory they serve different but complementary safety oversight functions.

What happens if a DSUR is submitted late?

Late DSUR submission is a GCP compliance failure with potentially significant consequences. In the EU, where DSURs are submitted through CTIS, late submission is simultaneously visible to all EU member states where the trial is authorised. Member states can trigger compliance assessments, and persistent late submission can lead to trial suspension or authorisation withdrawal. In the US, late IND Annual Reports (which incorporate the DSUR) are noted by FDA and may result in IND review actions or inspection priority escalation.