From aggregating data across disparate sources to accelerating content generation, traceability, quality checks, and review cycles, AI-powered authoring is helping life sciences teams shift their focus from manual document assembly to higher-value scientific and regulatory decision-making.
For pharmacovigilance and regulatory affairs teams, drug approval marks the beginning of a continuous documentation obligation.
Two reports remain a crucial part of that obligation: the Periodic Safety Update Report (PSUR) and the Periodic Benefit-Risk Evaluation Report (PBRER). Both are legal requirements for marketing authorization holders (MAHs), and both are submitted at defined intervals to regulators across global markets.
What Is a Periodic Safety Update Report?
The Periodic Safety Update Report is a regulatory document submitted by MAHs at defined intervals following product approval. Also, its purpose is to give regulators a cumulative picture of a product's safety profile during a specified reporting period.
The PSUR was first introduced in 1992. In 1996, the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) harmonized it into a common format for post-marketing safety evaluation across regulatory jurisdictions.
Typical sections in a PSUR include:
Adverse Event Summaries: Cumulative tabulations of adverse drug reactions reported during the interval, categorized by seriousness and expectedness.
Signal Evaluation: Assessment of whether any emerging safety signals warrant label changes or regulatory action.
Exposure Estimates: Quantification of patient exposure to support context for reported ADR frequencies.
Risk Management Updates: A summary of actions taken to minimize identified risks during the reporting period.
Label Change Recommendations: Proposals for updates to the Reference Safety Information where the data support them.
What Is a Periodic Benefit-Risk Evaluation Report?
The PBRER is the successor format introduced under the ICH E2C(R2) guideline. It was formally adopted by the European Medicines Agency (EMA) in December 2013 through the updated Good Pharmacovigilance Practices (GVP) Module VII, Revision 1.
Here's the critical distinction: while the PSUR asks whether the product was safe, the PBRER asks whether the benefits continue to outweigh the risks. The latter is a structurally broader question that reframes the entire purpose of periodic aggregate reporting.
The PBRER integrates clinical trial data, post-marketing surveillance findings, real-world evidence, and published scientific literature into a unified benefit-risk evaluation, rather than compiling them as a periodic safety inventory.
Key sections in a PBRER include:
Cumulative Safety Data: Adverse event data drawn from all available sources, assessed against the established safety profile across the full post-authorization period.
Clinical Trial Outcomes: Efficacy and safety findings from ongoing and completed studies during the reporting interval, evaluated for their effect on the benefit-risk balance.
Integrated Benefit-Risk Evaluation: A structured, evidence-based analysis of whether the product's benefit-risk balance remains favorable for the approved indication.
Risk Minimization Effectiveness: Assessment of whether current risk management measures are achieving their intended objectives at the population level.
Forward-Looking Regulatory Recommendations: Proposals for label updates, risk-minimization changes, or further safety studies where cumulative data support them.
It’s also worth noting that the PBRER reflects a broader evolution in post-marketing pharmacovigilance: from reactive collection of adverse event reports to proactive, lifecycle-level benefit-risk stewardship.
Are PBRER and PSUR the Same?
The PBRER evolved from and has largely replaced the Periodic Safety Update Report in major regulatory jurisdictions, and many regulators use the terms interchangeably in informal communication. In practice, however, they expect submissions to follow the PBRER format and ICH E2C(R2) structure. MAHs who treat that distinction as semantic face real compliance exposure.
Here are the substantive differences:
Core Focus: As mentioned, the PSUR asks whether the drug is safe. The PBRER asks whether the benefits still outweigh the risks. This is a structurally broader and more analytically demanding question.
Data Scope: The PBRER integrates cumulative evidence from clinical trials, post-marketing surveillance, and real-world sources, with explicit benefit-risk analysis woven throughout. The PSUR historically focused on adverse drug reaction data within a defined reporting interval.
Structure: The PBRER follows the strict ICH E2C(R2) format, purpose-built for proactive, evidence-based lifecycle assessment rather than periodic ADR inventory.
Regulatory Evolution: The PBRER has largely superseded the PSUR in major jurisdictions, particularly under the EMA's GVP framework. For periodic aggregate safety reporting, organizations should default to the PBRER format unless a specific regional authority explicitly requires the legacy PSUR structure.
Submission Schedule: Both are legal obligations for MAHs. PBRERs in the EU are submitted according to schedules governed by the European Union Reference Dates (EURD) list, and the frequency and format requirements vary by product. Also, non-EU markets maintain their own submission expectations.
When to Use Which
For most products in EMA and ICH-aligned markets, the working assumption should be PBRER. While the term PSUR remains in common use, the underlying expectation (particularly in the EU) is the PBRER format and ICH E2C(R2) analytical structure.
PBRER submissions are required when a detailed, integrated analysis of both benefits and risks is needed to support ongoing regulatory decisions, label updates, or lifecycle management actions. For EU-approved products, the EURD list determines which products require PBRERs and the applicable submission schedule.
Practical guidance for MAHs:
Default to PBRER-format submissions for EMA and ICH-aligned markets.
Verify regional requirements separately for FDA, PMDA (Japan), and NMPA (China), where submission format expectations and intervals may differ from ICH defaults.
Confirm your product's EURD list entry to establish the correct data lock point and applicable submission cycle.
How Often Is the PBRER Submitted?
Submission frequency is governed by the EURD list and varies significantly by product. Cycles of 1, 2, 3, 5, 6, 8, 10, 13, 15, or 16 years are all possible, depending on the product and its authorization history.
Deadline requirements for MAHs are as follows:
Reporting Intervals up to 12 Months: Submit within 70 calendar days of the data lock point.
Reporting Intervals Exceeding 12 Months: Submit within 90 calendar days of the data lock point.
Ad Hoc Requests from Competent Authorities: Submit within 90 calendar days unless otherwise specified by the relevant authority.
Outside the EU, requirements vary considerably. Some regulators require periodic submissions for a fixed number of years post-approval; others request reports on an ad hoc basis as safety questions arise.
MAHs managing multi-regional product portfolios should maintain a jurisdiction-by-jurisdiction submission calendar to ensure no deadlines are missed across overlapping cycles.
A Note on the US Market: Understanding PADER in Pharmacovigilance
In the United States, the default periodic safety reporting format for approved products is the Periodic Adverse Drug Experience Report (PADER), required under 21 CFR 314.80(c)(2) for approved New Drug Applications (NDAs) and under 21 CFR 600.80(c)(2) for biologics.
PADERs summarize adverse drug experience reports received during the reporting period and differ from the PBRER in one critical respect: they focus on compiling adverse events rather than on integrated benefit-risk evaluation.
1. PADER Submission Schedule
Submission frequency follows a structured post-approval progression:
Quarterly for the first three years following NDA approval, submitted within 30 days of the close of each quarter.
Annually thereafter, the submission is to be made within 60 days of the anniversary date of approval.
2. Submitting PBRER in Place of PADER
The FDA does not require the PADER format exclusively. Under 21 CFR 314.90 and 600.90, MAHs may obtain a waiver to submit a PSUR or PBRER in place of the PADER, accompanied by the required NDA listings (also referred to as the US Supplement or FDA PSUR).
Also, the FDA formally accepts all three formats (PADER/PAER, PSUR, and PBRER) to fulfill postmarketing periodic safety reporting requirements under 314.80(c)(2) and 600.80(c)(2). Each must be submitted according to the content and timelines specified either in US regulations or by ICH guidance.
3. Strategic Efficiency for Multi-Regional Programs
For organizations managing simultaneous EMA and FDA reporting obligations, this waiver pathway creates direct operational efficiency. A single PBRER submission can satisfy both jurisdictions, provided the waiver is in place and US-specific supplement requirements are met. That reduces the documentation burden of maintaining separate PADER and PBRER reporting tracks for the same product.
For global pharmacovigilance programs, it’s important to understand where PBRER, PSUR, and PADER obligations overlap and where the waiver pathway offers strategic efficiency. That vital information is essential to building a compliant and sustainable global reporting architecture.
Why Periodic Safety Reporting Is One of Pharmacovigilance's Most Demanding Authoring Challenges
PBRER and PSUR reporting are not one-time obligations. Every approved product undergoes continuous documentation throughout its approved lifecycle.
Five factors make periodic safety reporting in pharmacovigilance demanding:
Cyclical Production: Submission cycles run continuously for the life of every approved product, often in parallel across portfolios with different EURD-governed timelines.
Multi-Source Data Integration: Each report requires simultaneous data pulls from safety databases, clinical trial registries, surveillance systems, and the published literature, all under fixed deadlines.
Cross-Functional Coordination: Regulatory affairs, medical writing, pharmacovigilance, biostatistics, and clinical teams must all contribute within tight, interdependent timelines.
Portfolio Volume: MAHs managing large portfolios run dozens of simultaneous PBRER cycles, a production capacity problem rather than a scheduling one.
Non-Compliance Consequences: Missed deadlines trigger regulatory inquiries. Inadequate signal evaluation can also escalate to formal risk-management interventions and variation requests.
How AI Is Automating PBRER and PSUR Authoring
No other category of regulatory writing combines the data complexity, cross-functional dependency, and submission frequency of periodic safety reports.
But with PBRER and PSUR AI writing software, you can reduce document preparation timelines and improve consistency across reporting cycles. Pharmacovigilance professionals can free up their time and focus on the scientific analysis that regulators actually care about, rather than the document mechanics that surround it.
AI delivers the highest practical impact among these areas:
Automated Multi-Source Data Integration: Pulls structured and unstructured safety data from safety databases, EDC systems, clinical trial outputs, and published literature into a unified document environment, eliminating the manual aggregation step that precedes every PBRER authoring cycle.
Dynamic Literature Intelligence: Continuously monitors scientific publications and flags emerging safety signals relevant to the benefit-risk assessment, without manual search cycles between reporting periods.
First-Draft Generation: Produces narrative sections, benefit-risk summaries, and signal evaluation write-ups based on source data already loaded into the system, addressing the blank-page problem that consumes disproportionate authoring time.
One-Click Batch Updates: Detects changes in upstream source data and propagates revisions across all interconnected document sections, eliminating the manual cascade that currently drives significant rework hours in late-stage review cycles.
Built-In Compliance Checks: Benchmarks document structure against ICH E2C(R2) requirements and applicable regional specifications, reducing the risk of submitting a structurally non-compliant document to a competent authority.
How AuroraPrime RMA Automates Periodic Benefit-Risk Reporting
AuroraPrime RMA is purpose-built for the exact level of documentation complexity that PBRER, PSUR, and PADER authoring demand. As an AI writing solution for pharmaceutical companies, it operates as a Microsoft Word add-in integrated with Veeva RIM, allowing pharmacovigilance and regulatory teams to work within familiar, validated environments rather than adopting new systems.
Key capabilities directly applicable to periodic safety reporting:
Multi-Source Data Ingestion: Handles structured tables, unstructured safety narratives, and integrated EDC and pharmacovigilance system outputs, consolidating the data aggregation step that precedes every PBRER authoring cycle, regardless of portfolio size.
Pre-Built ICH E2C(R2)-Aligned Templates: Automated PSUR and PBRER drafting begins from templates that enforce structural compliance from the first draft, reducing back-and-forth between authors and QC reviewers in the revision process.
GenAI Quality Control: Benchmarks generated content against golden-standard documents, enforcing consistency in language, structure, and analytical framing across reporting cycles and document versions, a material advantage for teams managing large product portfolios.
Automated Update Triggers: Detect changes in upstream safety data and prompt or generate revised sections accordingly, maintaining document currency without requiring manual intervention at each data revision point.
Veeva RIM and Microsoft Word Integration: All authoring, review, and version control stays within validated, familiar environments, with no separate platform to manage and no disruption to established workflows.
Book a demo to see how AuroraPrime RMA compresses PBRER and PSUR authoring timelines while maintaining the analytical rigor global regulators require.
