ICH E2C(R2): The PBRER Is a Verdict, Not a Data Recap

FDA finalized its guidance adopting ICH E2C(R2) in July 2016, retiring the older periodic safety update report in favor of a document built around one addition: an integrated benefit-risk analysis. Most drug safety teams absorbed the new template — the section headings, the format — without absorbing the point of it. Nine years later, a large share of PBRERs crossing FDA's desk are still, functionally, aggregate safety-data reports with a benefit-risk section bolted on at the end rather than built from everything that came before it.

What the PBRER kept, and what it added

The PSUR format the PBRER replaced was organized around aggregation: adverse event tabulations, line listings, case narratives, sorted by reporting interval. ICH E2C(R2) keeps all of that — the aggregate safety data still has to be collected, summarized, and evaluated for new signals, building on the identified risks, potential risks, and missing information categories a product's safety specification already defined. What E2C(R2) adds is the requirement that the report not stop at the data: it has to conclude with an evaluation that sets the product's benefit-risk context, weighs the evaluated risks against the evaluated benefits for its approved use, and states what, if anything, should change as a result.

Where the old habit survives

The failure is rarely a missing section. Teams that have run periodic safety reporting for years know the template, and the benefit-risk analysis section is present in nearly every PBRER that reaches a reviewer. What is frequently missing is the argument. A benefit-risk analysis that restates the aggregate adverse-event data already presented earlier in the report, alongside a restatement of the product's known efficacy, and stops there, has not integrated anything — it has summarized two things next to each other. The guideline's own structure answers what integration requires: a stated benefit-risk context naming the medical need and the real alternatives, then an explicit weighing of risk against benefit for the product's approved use specifically, not its broader development history.

• Scope creep dilutes the argument. Evaluating benefit against the full development program rather than the approved indication answers a different, easier question than the one E2C(R2) asks.
• Restating risk is not weighing it. Repeating the identified and potential risks from earlier in the report is not the same as stating how they weigh against the evaluated benefit.
• Actions need to trace back to the analysis. A conclusions-and-actions section that does not visibly follow from the benefit-risk analysis above it reads as two documents stitched together, not one argument.
• The comparison with FDA's narrower tools matters. Where the PBRER argues a comprehensive benefit-risk conclusion every cycle, REMS applies narrower, selectively imposed tools to a specific identified risk — the two are not interchangeable safety documents, and a PBRER cannot be waved off because a REMS already exists.

A benefit-risk section that restates the data already in the report has not integrated anything. Integration means stating how the risk weighs against the benefit — for approved use, not the development history. Why the argument is the deliverable

Writing the argument, not the recap

The fix is not more data. Most sponsors already generate thorough aggregate safety analyses for their postmarketing safety reporting obligations; the data was never the gap. The gap is a drafting discipline: state the benefit-risk context first — what medical need the product meets and what else is available to meet it — then write the integration as an explicit weighing limited to approved use, and let the conclusions and actions section name only what follows from that weighing. A postmarketing safety team that drafts the PBRER in that order produces a shorter, more defensible benefit-risk section than one that drafts the data sections first and writes the integration last as a summary of what came before.

None of this changes what data a PBRER has to include. It changes what the report is for. A PBRER that reads like an aggregate safety report with a benefit-risk appendix has not failed on content — it has skipped the one judgment ICH E2C(R2) actually asks a sponsor to make and write down. Sponsors preparing a BLA safety package or an ongoing postmarketing program are better served treating that judgment as its own drafting step, not a formality that happens after the real work of aggregating data is done.