Periodic Safety Update Report (PSUR): The Complete Pharmacovigilance Compliance Guide
A Periodic Safety Update Report (PSUR) is a pharmacovigilance report used to present the evolving post-marketing benefit-risk profile of a medicinal product. In ICH-aligned settings, the modern format is the Periodic Benefit-Risk Evaluation Report (PBRER) described in ICH E2C(R2). Exact submission frequency and due dates are jurisdiction-specific: for example, EMA states that EU PSUR frequency follows the legally binding EURD list, while FDA's periodic postmarketing reporting requirements are set out in 21 CFR 314.80. Sponsors should not assume one global timetable applies everywhere.
Key Takeaways
Key Takeaways
- ICH E2C(R2) introduced the PBRER format with 19 standardized sections emphasizing integrated benefit-risk evaluation.
- In the EU, PSUR frequency and data lock points are controlled by the EURD list, which can override the standard legislative cycle.
- ICH E2C(R2) and EMA materials state that reports covering intervals up to 12 months are generally due within 70 days of the data lock point, and intervals longer than 12 months within 90 days.
- FDA's periodic postmarketing reporting requirements for many approved drugs are governed by 21 CFR 314.80 rather than a universal PSUR timetable.
- Late or incomplete PSUR submissions can lead to regulatory follow-up under the applicable pharmacovigilance framework.
- A periodic safety update report (PSUR) is a pharmacovigilance document that may be required by regulatory authorities to provide a comprehensive assessment of a drug's benefit-risk profile during the post-marketing phase. These reports support ongoing post-marketing surveillance of product safety where periodic reporting obligations apply.
- For drug safety professionals, PSUR reporting is a core post-authorisation compliance activity wherever periodic safety reporting applies. Missing submission deadlines or providing incomplete safety data can trigger regulatory questions, assessment findings, or other follow-up depending on the jurisdiction.
- The challenge? PSUR preparation requires coordinating global safety data, analyzing thousands of adverse event reports, conducting literature searches across multiple databases, and synthesizing complex risk-benefit assessments into a standardized regulatory format - all within strict regulatory timelines.
- In this guide, you'll learn:
- What a periodic safety update report is and when it's required under ICH guidelines
- Key differences between PSUR and PBRER (Periodic Benefit-Risk Evaluation Report) formats
- PSUR submission timelines, frequency requirements, and data lock points across FDA, EMA, and other regulatory authorities
- Essential components of PSUR reporting including safety data analysis, signal detection, and risk management updates
- Best practices for efficient PSUR preparation, quality review, and regulatory submission
- ---
What Is a Periodic Safety Update Report (PSUR)?
A Periodic Safety Update Report (PSUR) is a comprehensive pharmacovigilance document submitted to regulatory authorities at defined intervals following a drug's marketing authorization that provides an integrated analysis of all available safety data-including adverse event reports, clinical trial results, literature findings, and non-clinical studies-to assess whether the product's benefit-risk balance remains favorable.
A periodic safety update report is a comprehensive pharmacovigilance document submitted to regulatory authorities at defined intervals following a drug's marketing authorization. The PSUR provides an integrated analysis of all available safety data, including adverse event reports, clinical trial results, literature findings, and non-clinical studies, to assess whether the product's benefit-risk balance remains favorable.
Key characteristics of periodic safety update reports:
- Periodic submission requirement where the product and jurisdiction are subject to periodic post-marketing reporting obligations
- Global data aggregation encompassing worldwide safety information from all sources (spontaneous reports, clinical trials, literature, post-authorization studies)
- Standardized format following ICH E2C(R2) guidelines with defined sections covering exposure data, clinical safety findings, signal evaluation, and benefit-risk analysis
- Regulatory assessment tool allowing health authorities to monitor ongoing product safety and determine if regulatory action is needed
The ICH E2C(R2) guideline, implemented in 2012, harmonized PSUR requirements across ICH regions and introduced the Periodic Benefit-Risk Evaluation Report (PBRER) format that emphasizes benefit-risk assessment throughout the report structure, replacing the previous ICH E2C(R1) traditional PSUR format.
PSUR vs PBRER: Understanding the Regulatory Evolution
The pharmacovigilance landscape underwent significant harmonization with the introduction of the Periodic Benefit-Risk Evaluation Report (PBRER) format, which evolved from traditional PSUR requirements.
Format Comparison: PSUR vs PBRER
| Feature | Traditional PSUR | PBRER (ICH E2C R2) | Current Status |
|---|---|---|---|
| Primary Focus | Safety data compilation | Integrated benefit-risk evaluation | PBRER is preferred format |
| Guideline Basis | ICH E2C(R1) | ICH E2C(R2) - 2012 | PBRER follows current ICH standard |
| Benefit Assessment | Limited or separate section | Integrated throughout document | PBRER requires comprehensive benefit analysis |
| Signal Evaluation | Reactive reporting | Proactive signal detection and assessment | PBRER mandates systematic signal evaluation |
| Regulatory Preference | Legacy format | ICH-aligned format used in many jurisdictions, subject to local implementation | Local terminology and legal requirements still govern |
| Document Structure | 15 sections | 19 standardized sections | PBRER has more detailed requirements |
Regional Terminology Variations
Different regulatory authorities use distinct terminology for essentially equivalent periodic safety reports:
| Region/Authority | Official Term | Abbreviation | Notes |
|---|---|---|---|
| European Union | Periodic Safety Update Report | PSUR | Term still used despite PBRER adoption |
| ICH Guideline | Periodic Benefit-Risk Evaluation Report | PBRER | International harmonized format |
| United States (FDA) | Periodic Adverse Drug Experience Report | PADER | FDA periodic postmarketing reporting is governed by FDA regulations such as 21 CFR 314.80 |
| Japan (PMDA) | Local requirements apply | Varies | Confirm current local terminology and format expectations with PMDA |
| Health Canada | Local requirements apply | Varies | Confirm current Canadian reporting expectations for the product type |
| WHO | Periodic Safety Update Report | PSUR | For prequalification program |
Why the Shift from PSUR to PBRER?
The evolution from traditional PSUR to PBRER format reflects a fundamental change in pharmacovigilance philosophy:
Traditional PSUR limitations:
- Focused primarily on adverse event compilation without integrated benefit analysis
- Inconsistent structure across regions led to duplicate reporting with regional variations
- Limited emphasis on signal detection and evaluation
- Benefit assessment often treated as afterthought in separate section
PBRER improvements:
- Integrated benefit-risk assessment woven throughout the entire document
- Systematic signal evaluation with transparent methodology
- Standardized structure accepted across ICH regions (reducing duplication)
- Enhanced focus on what the data means for prescribers and patients, not just what happened
- Required inclusion of cumulative summary tabulations and interval data comparisons
When transitioning from legacy PSUR documentation to PBRER format, don't just rename the old sections. Instead, systematically reconstruct the benefit-risk narrative throughout the report. Reviewers can immediately spot PSURs that are reformatted without substantive benefit integration. Invest time in re-analyzing your benefit data and weaving it throughout sections 7-18, not just in the final section 19.
“Key Insight: While many regions still use the term "PSUR," the content structure often follows ICH E2C(R2) PBRER principles in ICH-aligned settings. The controlling legal requirement is still the local regulation, guideline, or authority instruction.
PSUR Reporting Timeline and Frequency Requirements
Periodic safety update reports must be submitted according to the schedules set by the applicable regulatory framework. The International Birth Date (IBD) concept is important in ICH and EU contexts, but sponsors should confirm whether it is the controlling date in their jurisdiction.
International Birth Date (IBD) Concept
The International Birth Date is the date of the first marketing authorization for a medicinal product granted to any company in any country worldwide. The IBD serves as the anchor point for calculating PSUR submission dates globally.
IBD determination:
- Based on first approval anywhere in the world (not company-specific or region-specific)
- Remains constant regardless of subsequent approvals in other regions
- Used to calculate data lock points for all periodic safety reports
- Typically corresponds to the first ICH region approval date
Frequency Rules Depend on Jurisdiction
| Jurisdiction / Framework | Official baseline position | Important qualifier |
|---|---|---|
| EU PSUR framework | EMA states that the EURD list sets the frequency, data lock point, and submission date for substances in scope | The EURD list is legally binding and can override the standard legislative cycle |
| EU standard legislative cycle | EMA states that the standard cycle is 6-monthly, yearly, and thereafter 3-yearly | This applies only where not overruled by the EURD list or another legal exemption or condition |
| FDA 21 CFR 314.80 | FDA requires quarterly periodic adverse drug experience reports for 3 years from approval, then annual reports, unless FDA changes the timing by written notice | This is an FDA postmarketing reporting framework, not a general PSUR rule |
Regional Variations in Submission Requirements
European Union (EMA):
- Uses the EURD list to set the legally binding frequency, data lock point, and submission date for substances in scope
- Conducts single assessment through the EU PSUR single-assessment process where applicable
- Can change submission expectations through legally binding EU processes
United States (FDA):
- Uses periodic adverse drug experience reporting requirements in 21 CFR 314.80 for many approved drugs
- May require different timing by written notice in specific circumstances
- May also impose separate product-specific postmarketing commitments or REMS assessment schedules
Japan (PMDA):
- Follow current PMDA pharmacovigilance and re-examination requirements for the product
- Confirm the reporting cycle, format, and language expectations locally
Health Canada:
- Confirm current Canadian periodic safety reporting expectations for the product and authorization type
- Use any product-specific conditions or authority correspondence to set the schedule
PSUR Submission Deadlines
After the data lock point (DLP), the official deadline depends on the applicable framework:
| Framework | Official timing statement | Notes |
|---|---|---|
| ICH E2C(R2) / EMA PSUR guidance | 70 calendar days for intervals up to 12 months; 90 calendar days for intervals longer than 12 months | EMA states the legally binding submission date is published in the EURD list |
| FDA 21 CFR 314.80 | Quarterly reports are due within 30 days of the close of the quarter; annual reports within 60 days of the approval anniversary date | FDA can change the timing by written notice |
Set an internal review and approval deadline ahead of the legal filing deadline. The amount of buffer should reflect product complexity, governance steps, and publishing requirements.
Data Lock Point Planning
Because frequencies and due dates vary by jurisdiction, sponsors should build the reporting calendar from the legally controlling source for the product:
- the EURD list and GVP Module VII in the EU;
- the product's approval date and 21 CFR 314.80 timing rules for FDA periodic adverse drug experience reports;
- any product-specific commitments or authority correspondence that changes the default cycle.
Essential Components of PSUR/PBRER Structure
The ICH E2C(R2) guideline defines a standardized 19-section structure for PBRERs. Understanding each component is critical for complete and compliant reporting.
PBRER Core Sections (ICH E2C R2)
| Section | Title | Key Content Requirements | Typical Length |
|---|---|---|---|
| 1 | Executive Summary | Benefit-risk conclusion, important findings, regulatory actions | 2-3 pages |
| 2 | Worldwide Marketing Authorization Status | All countries where marketed, approval dates, formulations | 1-2 pages + tables |
| 3 | Actions Taken for Safety Reasons | Withdrawals, label changes, restrictions during reporting period | 1-2 pages |
| 4 | Changes to Reference Safety Information | Updates to company core safety information (CCSI) | 1 page or none |
| 5 | Estimated Exposure | Patient exposure estimates by indication, age, geographic region | 1-2 pages |
| 6 | Data Sources | Description of all safety data sources analyzed | 1 page |
| 7 | Summary of Data | Cumulative and interval data presentation | Variable |
| 8 | Summaries of Significant Findings from Clinical Trials | Key safety findings from ongoing and completed trials | 2-5 pages |
| 9 | Findings from Non-Interventional Studies | Post-authorization safety studies, registries, epidemiological studies | 1-3 pages |
| 10 | Information from Other Clinical Trials and Sources | Investigator-sponsored trials, compassionate use programs | 1-2 pages |
| 11 | Non-Clinical Data | Relevant toxicology, animal studies conducted during period | 0-2 pages |
| 12 | Literature | Systematic literature review findings | 2-4 pages |
| 13 | Other Periodic Reports | Cross-reference to Development Safety Update Reports (DSURs) | 1 page |
| 14 | Lack of Efficacy | Cases suggesting potential efficacy concerns | 1-2 pages |
| 15 | Late-Breaking Information | Critical safety information after DLP | 0-1 page |
| 16 | Overview of Signals: New, Ongoing, or Closed | Signal detection and evaluation summary | 3-10 pages |
| 17 | Signal and Risk Evaluation | Detailed analysis of important identified risks, important potential risks, missing information | 5-15 pages |
| 18 | Benefit Evaluation | Efficacy data, therapeutic use patterns, benefit assessment | 3-8 pages |
| 19 | Integrated Benefit-Risk Analysis | Synthesis of all data, overall benefit-risk conclusion | 3-5 pages |
Critical PSUR Data Requirements
Section 5: Estimated Exposure - Calculation Methods
Exposure estimation is essential for understanding the denominator when assessing adverse event rates. Common methods include:
| Exposure Metric | Calculation Approach | When Used | Limitations |
|---|---|---|---|
| Patient Exposure | Total number of patients prescribed/dispensed drug | Acute treatments, single courses | Doesn't account for duration |
| Patient-Years | Sum of duration all patients received treatment | Chronic medications | Requires dispensing data |
| Defined Daily Dose (DDD) | Total doses sold / WHO standard daily dose | When patient data unavailable | Assumes standard dosing |
| Prescription Volume | Number of prescriptions issued | Retail pharmacy data available | Doesn't indicate actual use |
Don't rely on a single exposure metric. Cross-validate using multiple methods to identify data quality issues. If your patient-years calculation and DDD estimates differ significantly, investigate the discrepancy-it often reveals problems with data completeness, regional variations in dosing, or off-label use patterns that should be addressed before submission.
Section 16: Signal Detection Requirements
Signal evaluation must address:
- Methodology for signal detection (statistical methods, data mining, literature monitoring)
- New signals identified during reporting period
- Status of ongoing signal evaluations from previous reports
- Closed signals with rationale for closure
- Prioritization criteria for signal investigation
Create a signal tracking log that documents every signal identified (even those determined to be non-signals) with dates, methodology, key findings, and decision rationale. This log becomes invaluable evidence of your pharmacovigilance system's diligence during regulatory inspections and demonstrates compliance with ICH E2E signal evaluation guidelines.
Section 19: Integrated Benefit-Risk Analysis - Core Questions
The final section must address:
- Has the benefit-risk balance changed during this reporting period?
- What are the implications for the product's marketing authorization?
- Are regulatory actions warranted (label updates, restrictions, additional studies)?
- What benefit-risk information should be communicated to prescribers and patients?
PSUR Preparation: Best Practices and Common Challenges
Efficient PSUR preparation requires systematic data collection, cross-functional coordination, and rigorous quality control to meet regulatory timelines.
PSUR Preparation Sequence
The internal preparation sequence should be built backward from the legally applicable submission date and usually includes:
- locking the reporting period dataset in line with the governing rule;
- extracting case, literature, clinical, and exposure data;
- preparing cumulative and interval summaries;
- evaluating signals and benefit-risk implications;
- completing medical, quality, and regulatory review before submission.
Common PSUR Preparation Challenges
| Challenge | Impact | Mitigation Strategy |
|---|---|---|
| Global data aggregation | Multiple safety databases, regional systems, inconsistent coding | Implement centralized global safety database; standardize MedDRA coding procedures |
| Literature search comprehensiveness | Missing relevant publications leads to incomplete analysis | Use systematic search strategy across PubMed, Embase, conference databases; document search terms |
| Exposure data accuracy | Unreliable denominators for rate calculations | Establish relationships with sales/distribution teams; use multiple estimation methods |
| Signal detection consistency | Inconsistent signal identification across products | Implement standardized signal detection algorithms; maintain signal management log |
| Cross-functional coordination | Clinical development, medical affairs, regulatory not aligned | Establish PSUR governance with defined roles; conduct kickoff meetings at DLP |
| Quality review bottlenecks | Last-minute reviews delay submission | Build review into timeline; use staged review approach (sections as completed) |
| Regulatory intelligence gaps | Unaware of label changes in other regions | Subscribe to regulatory intelligence services; maintain global authorization tracker |
PSUR Quality Control Checklist
Before submission, verify:
Implement your quality control checklist in phases rather than as a final gate. Use staged review: conduct section-specific QC as drafts are completed (sections 1-7 early, sections 16-19 after all analysis), not just at the end. This approach prevents the last-minute discovery of missing data that forces timeline extensions. Quality should be built into the writing process, not bolted on afterward.
Completeness:
- [ ] All 19 ICH E2C(R2) sections present and complete
- [ ] Summary tabulations include both cumulative and interval data
- [ ] Literature search covers full reporting period with documented methodology
- [ ] All ongoing signals from previous PSUR have status updates
- [ ] Exposure estimates provided with calculation methodology explained
Accuracy:
- [ ] Data lock point and reporting period dates correct and consistent throughout
- [ ] Adverse event numbers reconcile between narrative and tabulations
- [ ] MedDRA coding version specified and consistent
- [ ] References to previous PSURs accurate (section 13)
- [ ] Marketing authorization dates verified against official sources
Consistency:
- [ ] Company Core Safety Information (CCSI) referenced is current version
- [ ] Signal conclusions align with risk management plan updates
- [ ] Benefit-risk conclusion consistent with data presented in sections 7-18
- [ ] Regulatory actions reported match actual label changes and restrictions
Compliance:
- [ ] Submission timing checked against the applicable legal deadline for the product
- [ ] Electronic format meets the applicable regional submission-system requirements
- [ ] Document version control and approval signatures documented
- [ ] Cross-references to risk management plan, REMS, or safety specifications included
PSUR Submission Procedures by Region
Regulatory authorities have specific submission requirements, formats, and procedures for periodic safety update reports.
European Union PSUR Submission
EMA states that, as of 13 June 2016, MAHs are required to submit all EU PSURs to the central PSUR repository. EMA also states that the repository is mandatory for both centrally and nationally authorised medicines. From January 2025, MAHs should use the IRIS platform when managing PSURs, while initial PSUR submission and responses to requests for supplementary information still require submission in the PSUR repository.
United States (FDA) PSUR/PBRER Submission
FDA's periodic postmarketing reporting rules are governed by FDA regulations such as 21 CFR 314.80 rather than a single universal PSUR submission pathway. Sponsors should follow the current FDA electronic submission instructions applicable to the product and application type.
Other Major Markets
For markets outside the EU and FDA frameworks, sponsors should verify the current local reporting format, language, filing route, and due dates directly against the applicable authority guidance and any product-specific commitments.
Signal Detection and Management in PSUR Context
Signal detection represents a core component of PSUR preparation, requiring systematic evaluation of safety data to identify new risks or changes to known risks.
What Constitutes a Signal?
ICH E2E definition: "Information that arises from one or multiple sources (including observations and experiments), which suggests a new potentially causal association, or a new aspect of a known association between an intervention and an event or set of related events, either adverse or beneficial, that is judged to be of sufficient likelihood to justify verificatory action."
Signal Detection Methods for PSUR
| Method | Data Source | Strengths | Limitations |
|---|---|---|---|
| Disproportionality Analysis | Safety database (company or WHO) | Quantitative; identifies statistical associations | Susceptible to reporting bias; requires sufficient case volume |
| Systematic Literature Review | PubMed, Embase, conferences | Captures published findings | Publication bias; time lag between event and publication |
| Clinical Trial Safety Data | Ongoing and completed trials | High-quality data; controlled setting | Selected populations; may not reflect real-world use |
| Observational Study Findings | Registries, claims databases | Large populations; real-world evidence | Confounding; selection bias |
| Data Mining Algorithms | Large safety databases | Automated screening; consistent application | Generates many false positives |
Never rely on a single signal detection method. The strength of your signal detection program lies in convergent evidence from multiple sources. If disproportionality analysis identifies a potential signal but literature review and clinical trial data don't support it, investigate why. This discordance often reveals important data quality issues or identifies false signals early, preventing unnecessary regulatory actions or labeling updates that might confuse prescribers.
Signal Prioritization Framework
Not all signals warrant equal attention. Prioritization considers:
Seriousness:
- Does the signal involve death, hospitalization, disability, or other serious outcomes?
- What is the medical significance of the event?
Frequency:
- How many cases have been reported?
- What is the reporting rate relative to exposure?
Strength of Evidence:
- Is there a temporal relationship (drug preceded event)?
- Is there biological plausibility?
- Are there positive rechallenge or dechallenge cases?
- Do multiple independent data sources support the signal?
Public Health Impact:
- What is the estimated population exposure?
- Are vulnerable populations (pediatrics, elderly) affected?
- Is the indication for serious or life-threatening condition (where benefit may outweigh risk)?
Signal Evaluation Process
| Stage | Activities | Output |
|---|---|---|
| Detection | Statistical screening, literature monitoring, clinical trial review | List of potential signals |
| Validation | Case review, causality assessment, confounder evaluation | Confirmed or refuted signals |
| Analysis | In-depth data analysis, biological mechanism review, consultation with experts | Signal assessment report |
| Action | Determine if labeling update, additional studies, or other regulatory action warranted | Recommendation for signal closure or escalation |
| Communication | Report in PSUR section 16-17; communicate to authorities if urgent | Signal documented in PSUR or escalated separately |
Common Signal Categories in PSUR
New Signals:
- Previously unrecognized adverse reactions not in current labeling
- New populations at risk (e.g., drug-drug interaction identified)
- New aspect of labeled reaction (e.g., longer time to onset than previously known)
Ongoing Signals:
- Signals under evaluation from previous PSUR that remain open
- May be awaiting additional data (e.g., completion of post-authorization safety study)
- Status update required in each PSUR until closed
Closed Signals:
- Signals evaluated and determined not to represent true risk
- Signals confirmed and addressed through labeling update
- Must provide rationale for closure
Integration with Risk Management Plans and REMS
Periodic safety update reports do not exist in isolation but are integrated with broader pharmacovigilance systems including Risk Management Plans (EU) and Risk Evaluation and Mitigation Strategies (US).
PSUR and Risk Management Plan (RMP) Relationship
The European Medicines Agency requires Risk Management Plans for most new marketing authorization applications. The RMP identifies important identified risks, important potential risks, and missing information.
PSUR-RMP Integration Points:
| RMP Component | How PSUR Addresses It | Section Reference |
|---|---|---|
| Safety Specification | Updates to important identified risks, important potential risks, missing information | Section 17 |
| Pharmacovigilance Plan | Status of ongoing safety studies; preliminary results if available | Section 9 |
| Risk Minimization Measures | Effectiveness of risk minimization activities; need for additional measures | Section 17 |
| Post-Authorization Safety Studies (PASS) | Progress updates; interim or final results | Section 9 |
When RMP Updates Trigger:
- PSUR identifies new important identified risk or important potential risk
- Missing information has been addressed through newly available data
- Post-authorization safety study completed during reporting period
- Effectiveness evaluation suggests risk minimization measures inadequate
PSUR and REMS (US) Relationship
For products with FDA-mandated Risk Evaluation and Mitigation Strategies, the periodic safety report must address REMS performance.
REMS Assessment Report vs. PSUR:
| Feature | REMS Assessment | PSUR/PBRER |
|---|---|---|
| Purpose | Evaluate if REMS meeting goals of mitigating specific risks | Comprehensive benefit-risk evaluation of all product safety |
| Frequency | As specified in the approved REMS or FDA correspondence | Product-specific and separate from general PSUR or PADER rules |
| Focus | Metrics on REMS component performance (e.g., prescriber enrollment rates, patient comprehension) | All safety data from all sources |
| Submission Requirement | Mandatory for products with approved REMS | Depends on the applicable periodic safety reporting framework |
| Integration | PSUR should reference REMS; may be submitted concurrently | REMS assessment may be appendix to PSUR or separate |
Regulatory Inspections: PSUR as Assessment Tool
Health authorities use submitted PSURs to assess a company's pharmacovigilance system compliance and may conduct inspections based on PSUR findings.
What Inspectors Evaluate in PSURs
Completeness and Timeliness:
- Were PSURs submitted on time for all products?
- Are all required sections present and complete?
- Is the reporting period correct based on IBD or other specified schedule?
Data Quality:
- Are adverse event numbers consistent with safety database?
- Is literature search systematic, comprehensive, and documented?
- Are exposure estimates reasonable and methodology explained?
Signal Management:
- Were appropriate signal detection methods applied?
- Are signals from previous PSURs tracked with documented outcomes?
- Is signal prioritization and evaluation scientifically sound?
Benefit-Risk Assessment:
- Is the integrated benefit-risk analysis supported by data presented?
- Are conclusions reasonable given the safety and efficacy data?
- Are regulatory action recommendations appropriate?
Cross-Functional Coordination:
- Is clinical development data integrated (trial safety updates)?
- Are risk management plan and REMS activities addressed?
- Is there evidence of medical and regulatory oversight?
Common PSUR Inspection Findings
| Finding Category | Example Deficiency | Corrective Action |
|---|---|---|
| Late Submission | PSUR submitted after the applicable legal due date | Implement submission tracking system and set an internal deadline ahead of the regulatory deadline |
| Incomplete Signal Evaluation | Signal identified in previous PSUR not addressed in current report | Establish signal tracking log; require status update for all open signals |
| Inconsistent Data | Adverse event counts differ between PSUR tables and source database | Implement reconciliation procedure; independent quality check before submission |
| Inadequate Literature Search | Search limited to PubMed only; conference abstracts not reviewed | Expand search to Embase and other databases; include conference proceedings |
| Missing Exposure Data | No patient exposure estimates provided | Establish process to obtain sales data; develop methodology for exposure calculation |
PSUR Automation and Technology Solutions
The complexity and volume of PSUR data have driven adoption of specialized pharmacovigilance software and automation tools.
Technology Solutions for PSUR Preparation
| Solution Type | Functionality | Vendors (Examples) | Benefits |
|---|---|---|---|
| Safety Database Systems | Case management, MedDRA coding, adverse event tracking | Oracle Argus, ArisGlobal LifeSphere, AB Cube | Centralized data repository; automated report generation |
| Signal Detection Software | Disproportionality analysis, data mining, statistical screening | Empirica Signal (Oracle), VigiMatch, WHO VigiBase access | Systematic signal identification; quantitative methods |
| Literature Monitoring Services | Automated PubMed/Embase searches, relevance screening, case extraction | Evaluator (Certara), GOLIATH (Generis), Panalgo | Comprehensive literature coverage; reduces manual effort |
| PSUR Authoring Tools | Template management, section workflow, version control | Safety Intelligence Platform modules | Standardized structure; collaboration features |
| Submission Management | Regional gateway connectivity, eCTD compilation, tracking | Extedo SUBMIT, Lorenz Docubridge, Freyr | Streamlined electronic submission; reduces errors |
Automation Opportunities
High-Value Automation:
- Summary tabulation generation from safety database
- Literature search execution and duplicate removal
- Exposure data extraction from sales systems
- Standard text population (e.g., marketing authorization tables, previous PSUR summaries)
- Cross-reference verification between sections
Requires Human Expertise:
- Signal evaluation and causality assessment
- Integrated benefit-risk analysis
- Regulatory action recommendations
- Medical review and interpretation of clinical significance
- Quality review of conclusions and consistency
Data Integration Challenges
Common Data Sources for PSUR:
- Safety database (adverse event cases)
- Clinical trial management systems (ongoing trial safety data)
- Medical information systems (patient inquiries, off-label use reports)
- Literature monitoring services (published case reports, epidemiology studies)
- Regulatory intelligence databases (label changes, Dear Healthcare Provider letters)
- Sales and distribution systems (exposure data)
- Quality systems (product complaints, manufacturing deviations)
Integration Barriers:
- Different data formats and structures across systems
- Multiple regional or legacy databases requiring reconciliation
- Inconsistent coding (e.g., different MedDRA versions, in-house terms)
- Access and permission limitations across systems
- Real-time synchronization vs. periodic data extracts
Key Takeaways
A periodic safety update report is a comprehensive pharmacovigilance document used for periodic post-authorisation safety reporting where required by the applicable authority. The PSUR provides an integrated analysis of available safety data, including adverse event reports, clinical trial findings, literature searches, and non-clinical studies, to assess whether the product's benefit-risk balance remains favorable. In ICH-aligned settings, modern reports follow the ICH E2C(R2) PBRER structure with 19 standardized sections.
Key Takeaways
- A periodic safety update report (PSUR) is a pharmacovigilance document used in periodic safety reporting to provide a structured assessment of a drug's benefit-risk profile where that reporting framework applies.
- The PBRER format (ICH E2C R2) has replaced traditional PSUR structure in most regions, emphasizing integrated benefit-risk evaluation rather than just safety data compilation, with 19 standardized sections.
- Submission frequency is jurisdiction-specific - in the EU, the EURD list controls the legally binding frequency and due date; in FDA postmarketing reporting, 21 CFR 314.80 sets quarterly and annual periodic reporting timelines unless FDA directs otherwise.
- Signal detection and evaluation represent critical PSUR components requiring systematic analysis of safety data from multiple sources to identify new risks or changes to known risks using validated methodologies.
- PSURs integrate with broader risk management systems including Risk Management Plans (EU) and REMS (US), and serve as key assessment tools during pharmacovigilance inspections.
- ---
Next Steps
Understanding periodic safety update report requirements is essential for maintaining pharmacovigilance compliance and ensuring continuous monitoring of your product's benefit-risk profile throughout its lifecycle.
Organizations managing regulatory submissions benefit from automated validation tools that catch errors before gateway rejection. Assyro's AI-powered platform validates eCTD submissions against FDA, EMA, and Health Canada requirements, providing detailed error reports and remediation guidance before submission.
Sources
References
Sources
- ICH E2C(R2): Periodic Benefit-Risk Evaluation Report (PBRER)
- EMA Guideline on Good Pharmacovigilance Practices Module VII - Periodic Safety Update Report
- EMA Periodic Safety Update Reports (PSURs)
- FDA Guidance for Industry: Postmarketing Safety Reporting for Human Drug and Biological Products
- 21 CFR 314.80 - Postmarketing Reporting of Adverse Drug Experiences