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.