DSUR — The Clinical-Trial-Stage Cousin of the PBRER

Everything this module has covered so far describes the PBRER, which applies to marketed products. The DSUR (Development Safety Update Report), governed by ICH E2F, is the equivalent periodic, cumulative safety review for products still in clinical development — and understanding it as the PBRER’s clinical-trial-stage cousin, rather than an entirely separate concept, is the fastest way to build genuine fluency across both.

The core purpose is structurally similar: a periodic, cumulative review of accumulated safety data, prepared and submitted on a defined schedule. What differs is everything downstream of that shared purpose. A DSUR is assessed against the Investigator’s Brochure (IB) rather than the CCSI, because an investigational product doesn’t yet have an approved product label to compare expectedness against — the IB serves the same reference function the CCSI serves once a product reaches market. Its reporting anchor is the Development International Birth Date (DIBD) rather than the IBD used for marketed products.

The audience differs meaningfully too. A PBRER is fundamentally a regulator-facing document. A DSUR’s audience explicitly includes ethics committees and investigators actively running the trial, alongside regulators — because the DSUR’s findings can directly inform decisions about whether a trial should continue as designed, need protocol modifications, or, in a serious enough case, be paused or stopped. That’s a genuinely different kind of stakes than a PBRER’s post-marketing benefit-risk re-evaluation, even though both documents share the same underlying discipline of periodic, cumulative safety review.

A single product, over its lifecycle, typically moves from DSUR reporting to PBRER reporting as it transitions from investigational to approved and marketed status — they’re sequential phases of the same underlying safety-monitoring commitment, not two permanently parallel report types for the same product. Recognising that continuity — the same core discipline, adapted to the product’s current stage and the correspondingly different reference document, audience, and stakes — is exactly the kind of connective understanding that distinguishes genuine fluency from memorised acronyms.