A Step-by-Step Guide to Compiling Safety Data for PSUR Submission

The Periodic Safety Update Report (PSUR) is a critical pharmacovigilance document that requires comprehensive and well-organized safety data. Whether you’re compiling information from ongoing clinical trials or post-marketing surveillance, the success of your PSUR submission depends on the quality, completeness, and clarity of your safety data. This guide walks through the entire process of compiling safety data for PSURs in compliance with ICH E2C(R2), EMA, and USFDA expectations.

Why Accurate Safety Data Compilation Matters

Regulatory authorities evaluate PSURs to determine the evolving benefit-risk profile of a medicinal product. Poorly compiled data can lead to regulatory queries, delayed approvals, or even safety-related label changes. Key objectives of safety data compilation for PSUR include:

• Providing a cumulative view of adverse events (AEs)
• Identifying new or changing safety signals
• Quantifying patient exposure with accuracy
• Supporting benefit-risk assessment with validated metrics
• Ensuring compliance with regional and global standards

Step 1: Establish Your Data Lock Point (DLP)

The Data Lock Point is the cutoff date for the inclusion of safety data in the PSUR. All data compiled must be as of the DLP, and no subsequent information should be included unless specifically requested.

Ensure all stakeholders are aligned with the DLP, including data management, pharmacovigilance, medical writing, and regulatory teams.

Step 2: Identify and Extract Data Sources

Compile safety information from the following core sources:

• Clinical trial safety databases: Data on treatment-emergent AEs, SAEs, and discontinuations
• Spontaneous AE reports: Individual case safety reports (ICSRs) from global systems (e.g., EudraVigilance, FAERS)
• Post-Marketing Surveillance: Registries, patient support programs, and call center logs
• Medical literature: Safety signals or case reports found via systematic review
• Stability-related adverse findings from Stability Studies
• Ongoing or completed PASS: Post-authorization safety studies and observational data

Ensure data consistency across all sources to prevent duplication or omissions.

Step 3: Generate Core Safety Tables

Tabulation is a key part of safety data presentation in a PSUR. Below are the typical tables required:

• Summary of cumulative AEs by system organ class (SOC) and preferred term (PT)
• Serious vs. non-serious AEs
• Expected vs. unexpected AEs (based on RSI)
• Fatal outcomes and medically significant events
• AE frequency by population (adult, pediatric, elderly)

Use standard formats compliant with pharma SOP templates to maintain consistency across reports.

Step 4: Create Line Listings of Individual Cases

Line listings should include:

• Case ID and country
• Patient demographics and medical history
• Suspected product and indication
• Adverse event details with dates
• Outcome and causality assessment

Cases should be filtered to remove duplicates and must include both clinical trial and post-marketing cases.

Step 5: Conduct Cumulative Signal Evaluation

Safety signal detection is a key output of PSUR preparation. Use tools and methods such as:

• Disproportionality analysis (e.g., PRR, ROR)
• Time-trend graphs for AE frequency
• Comparison against historical data
• Use of signal management platforms

Document ongoing, new, or closed signals and reference their impact on the benefit-risk profile.

Step 6: Estimate Patient Exposure

Accurately estimating drug exposure is crucial for contextualizing AE data. Consider:

• Sales data converted into defined daily doses (DDDs)
• Number of patients in clinical trials per protocol
• Real-world usage data (if available)

Ensure clear distinction between estimated vs. calculated values and provide justification for assumptions.

Step 7: Review RSI and Label Changes

Any updates to the Company Core Safety Information (CCSI) or the Reference Safety Information (RSI) must be tracked:

• List changes to contraindications, warnings, precautions
• Highlight additions or removals of adverse reactions
• Track consistency across SmPCs in different countries

This section supports transparency and justifies data trends observed in safety tables.

Step 8: Perform Internal QC and Validation

Prior to finalization, all compiled data must undergo:

• Peer review by pharmacovigilance leads
• Cross-verification with clinical trial databases
• Validation checks for missing or inconsistent data
• Audit trail documentation for each source used

Ensure that the compiled safety dataset is audit-ready and meets both internal and GMP compliance expectations.

Best Practices for Efficient Compilation

1. Begin PSUR data compilation 60–90 days before DLP
2. Automate AE data extraction and filtering using validated tools
3. Use centralized data repositories for real-time signal monitoring
4. Standardize formatting and coding using MedDRA terminology
5. Maintain traceability from source document to PSUR summary

Common Pitfalls to Avoid

• Inconsistent AE classification across sources
• Failure to account for duplicate cases
• Incomplete or outdated RSI comparison
• Neglecting non-serious AE trends
• Late alignment between pharmacovigilance and regulatory teams

Conclusion

Safety data compilation is a foundational aspect of preparing a robust, compliant PSUR. By adopting a structured, stepwise approach and leveraging both automation and expert review, pharma professionals can ensure that PSURs reflect the true safety profile of a product. As PSURs evolve from static reports to dynamic tools for safety signal evaluation, accurate data compilation remains at the heart of regulatory success and patient protection.

Understanding the Purpose and Structure of a PSUR in Clinical Trials

In clinical trials and post-authorization safety monitoring, a Periodic Safety Update Report (PSUR) is a critical regulatory document that compiles cumulative safety data to evaluate the benefit-risk profile of a medicinal product. Globally harmonized under ICH E2C (R2), the PSUR helps sponsors maintain ongoing pharmacovigilance compliance, detect emerging signals, and communicate risk trends to regulatory authorities like the EMA or USFDA. This tutorial explores the core components, format, and strategic role of PSURs in clinical development and beyond.

What Is a PSUR and Why Is It Important?

The Periodic Safety Update Report is a structured document that summarizes all relevant safety data of an investigational or marketed drug at defined intervals, often every six months or annually. The PSUR aims to:

• Provide a cumulative assessment of the drug’s safety profile
• Identify new safety signals or trends over time
• Evaluate risk minimization measure effectiveness
• Support regulatory decisions for continued development or label changes
• Ensure synchronization between global regulatory expectations

While initially more common in the post-marketing phase, PSURs are increasingly integrated into advanced-stage clinical trial pharmacovigilance planning.

Regulatory Foundation and PSUR Periodicity

As per ICH E2C(R2) and EMA’s Module VII-GVP, PSURs must be submitted periodically for authorized medicinal products. Clinical trial sponsors may be required to submit similar cumulative safety summaries during investigational phases.

Typical PSUR Timelines:

• Initial Post-Authorization: Every 6 months for first 2 years
• Thereafter: Annually for 3 more years
• After Year 5: Every 3 years unless otherwise specified

The frequency can vary depending on country-specific regulations and risk classification of the product.

PSUR vs. PBRER

The term PSUR is often used interchangeably with PBRER (Periodic Benefit-Risk Evaluation Report). While both documents share similar objectives, the PBRER format emphasizes a more comprehensive benefit-risk evaluation aligned with ICH E2C(R2). In the EU, the PBRER is the required format for all PSUR submissions.

In practice, most companies use the PBRER format to fulfill PSUR requirements globally.

Core Structure of a PSUR (PBRER Format)

The PSUR is organized into clearly defined sections. Below is a breakdown of the standard structure:

1. Introduction

Defines the scope, time interval (Data Lock Point), and product summary, including formulation and indications.

2. Worldwide Marketing Authorization Status

Lists all countries where the product is authorized, suspended, or withdrawn, and reasons for any changes.

3. Actions Taken for Safety Reasons

Summarizes regulatory actions based on safety signals, including labeling updates or risk mitigation changes.

4. Changes to Reference Safety Information (RSI)

Describes changes made to the Investigator’s Brochure or Company Core Safety Information (CCSI).

5. Estimated Exposure and Usage Patterns

• Clinical trial exposure by indication and population
• Post-marketing exposure (patient-year estimates)

6. Data in Summary Tabulations

Aggregate safety data across spontaneous reports, literature, and clinical trials, stratified by seriousness and outcome.

7. Summaries of Significant Individual Case Histories

Detailed narratives of key adverse events (AEs), especially fatal or unexpected cases.

8. Signal and Risk Evaluation

Assessment of new, ongoing, or closed signals, with impact on benefit-risk balance.

9. Benefit-Risk Evaluation

Integrated discussion on the evolving benefit-risk profile with scientific justification.

10. Conclusions and Actions

Final assessment and proposed regulatory actions (if any).

Supporting appendices include line listings, literature references, and exposure data.

Data Sources Used in PSURs

PSURs gather safety information from multiple data streams:

• Spontaneous adverse event reporting systems
• Clinical trial databases (CDMS)
• Medical literature (e.g., PubMed, Embase)
• Regulatory databases (e.g., EudraVigilance)
• Stability studies impacting product safety profile
• Ongoing PASS and registries

The comprehensiveness of data significantly influences the accuracy of benefit-risk evaluations.

Common Challenges and Best Practices

Generating a robust PSUR requires cross-functional collaboration between pharmacovigilance, regulatory, clinical, and biostatistics teams. Challenges include:

• Inconsistent data capture across regions or systems
• Late signal detection due to inadequate AE coding
• Version control issues in RSI and labeling history
• Insufficient narrative detail in individual case reports

Best practices to improve PSUR quality include:

1. Automating data aggregation from safety databases
2. Standardizing template and writing SOPs from Pharma SOP templates
3. Conducting regular quality reviews and mock audits
4. Integrating statistical analysis for trend evaluation
5. Including KPIs to assess PSUR impact over time

Submission and Review Timelines

PSURs are submitted electronically through platforms such as the EMA’s EVMPD or FDA’s ESG. Deadlines are defined by the EU Reference Date (EURD) list or by national regulators.

Upon submission, authorities may:

• Accept the report without action
• Request clarifications or additional data
• Mandate changes to SmPC, labeling, or RMP

Maintaining a clear audit trail of submission dates, changes, and follow-up ensures smooth compliance.

Conclusion

The PSUR serves as a cornerstone of pharmacovigilance documentation, enabling a dynamic understanding of product safety in clinical and real-world contexts. By following ICH E2C(R2) standards and leveraging best practices in data collection and narrative analysis, pharmaceutical companies can ensure their PSURs are not only regulatory compliant but also meaningful tools for proactive safety monitoring. Whether in clinical trials or post-marketing phases, a well-structured PSUR aligns all stakeholders in the collective mission of protecting patient health.