Skip to main content
Canadian Regulatory Affairs

PBRER Submissions to Health Canada: What Drug Sponsors Get Wrong About Periodic Pharmacovigilance Reporting

Health Canada's PBRER requirements under ICH E2C(R2) differ meaningfully from FDA and EMA submissions. Here's what Canadian drug sponsors consistently miss.

Nour Abochama Quality & Regulatory Advisor, Androxa

Key Takeaway

Health Canada's PBRER requirements under ICH E2C(R2) differ meaningfully from FDA and EMA submissions. Here's what Canadian drug sponsors consistently miss.

Most sponsors who file PBRERs simultaneously for FDA and EMA treat the Health Canada submission as a near-identical exercise. Add the Canadian patient exposure data, swap out the cover letter header, push it through the Common Electronic Submissions Gateway. Done.

It’s not that simple. Health Canada has specific expectations around benefit-risk framing, Canadian labelling implications, and how regional signal activity gets documented — and reviewers notice when a PBRER reads like a US or EU document with a Canadian flag stapled to it. After working through dozens of these submissions with pharmaceutical clients across Canada, the same gaps come up with surprising regularity.

Here’s what the ICH E2C(R2) framework actually demands in a Canadian context, and where sponsors consistently stumble.

What Health Canada Requires: The Shift from PSUR to PBRER

Health Canada formally adopted ICH E2C(R2) — the Periodic Benefit-Risk Evaluation Report guideline — replacing the earlier PSUR format. If your regulatory team is still structuring periodic safety submissions under the old PSUR framework, that’s already a significant problem that will flag immediately on review.

The shift isn’t cosmetic. The PSUR was primarily a safety data compendium: here are the adverse events, here are the cases, here is the signal summary. The PBRER is explicitly a benefit-risk document. That reframing matters enormously. Health Canada reviewers expect the 18-section PBRER structure to build toward an integrated benefit-risk conclusion in Section 16 — one that directly addresses the approved Canadian indication and the Canadian patient population, not a copy-pasted global conclusion.

The PBRER applies to all marketed Division I prescription drugs holding a Drug Identification Number (DIN). Non-prescription drugs, biologics regulated under the Biologics and Genetic Therapies Directorate (BGTD), and Natural Health Products (NPNs) operate under distinct post-market reporting frameworks, though the underlying pharmacovigilance principles overlap considerably with what ICH E2C(R2) requires.

One distinction worth establishing early: the PBRER is not a signal detection tool. Real-time signal detection and management are handled separately under Health Canada’s pharmacovigilance framework through mechanisms like the Canada Vigilance Program. The PBRER synthesizes and evaluates signals that have already been characterized during the reporting period — it doesn’t identify them in real time. Sponsors who conflate the two and use the PBRER as a primary signal analysis exercise tend to produce submissions that are simultaneously over-detailed on signal detection methodology and under-developed on actual benefit-risk integration.

The Sections That Get Underweighted for Canadian Submissions

The 18-section PBRER template is standardized under ICH E2C(R2). What varies — and what Health Canada looks at closely — is the depth and regional specificity in certain sections that are easy to shortchange when the primary submission target is FDA or EMA.

Section 6 (Estimated Patient Exposure) is consistently underweighted in Canadian submissions. Generic language like “global wholesaler data is used as a proxy for patient exposure” doesn’t satisfy a Canadian reviewer who needs to understand Canadian-specific utilization patterns. If you have Canadian pharmacy dispensing data, provincial formulary reimbursement data, or post-authorization safety study (PASS) enrollment numbers from Canadian sites, those belong here — separated from global figures, not blended into them. Even rough Canadian estimates based on market-share allocation are better than no Canadian numbers at all.

Section 9 (Signal and Risk Evaluation) needs to reflect Health Canada’s signal communications if any were exchanged during the reporting period. This includes responses to Health Canada safety queries, risk communication activities initiated in Canada, or Canadian-specific expedited reporting that occurred. Sponsors who copy-paste the FDA/EMA Section 9 without cross-referencing Canadian regulatory correspondence create a documentation gap that reviewers notice and flag.

Section 10 (Regulatory Agency Actions) is where Canadian regulatory activity must be captured explicitly — label changes initiated at Health Canada’s request, Dear Healthcare Professional (DHCP) letters issued in Canada, or any product monograph amendments from the reporting period. Many sponsors document EMA and FDA actions in detail, then add a single line like “no Canadian actions” without verifying this against their Canadian regulatory correspondence files. That’s a documentation control issue as much as a pharmacovigilance issue.

Section 16 (Benefit-Risk Evaluation) is the most consequential section and the most frequently underdeveloped for Canadian submissions. The benefit-risk framework must be anchored to the approved Canadian product monograph — not the global SmPC, not the US PI. If the Canadian indication is narrower than what’s approved elsewhere (a situation that’s more common than sponsors expect, particularly with drugs that pursued expanded indications in the EU or US after the Canadian authorization was granted), the benefit-risk analysis must reflect that Canadian scope. Health Canada reviewers in the Marketed Biotherapeutics, Vigilance, and Pharmaceutical Sciences Bureau are evaluating what’s on your Canadian product monograph, and they’ll flag a benefit-risk section that addresses indications or patient populations not reflected in the Canadian label.

Submission Timelines and the International Birth Date

Health Canada follows the ICH E2C(R2) birth date convention. The International Birth Date (IBD) is the date of first marketing authorization worldwide for the active substance — not the Canadian DIN authorization date, which can be years later. Your PBRER Data Lock Point (DLP) aligns to this IBD.

The standard PBRER reporting schedule under ICH E2C(R2), which Health Canada observes:

  • Every 6 months for the first 2 years post-IBD
  • Annually for the following 3 years
  • Every 3 years thereafter, unless Health Canada specifies otherwise

Sponsors running concurrent submissions across FDA, EMA, and Health Canada should confirm the DLP is consistent across jurisdictions. Discrepancies in DLPs between a simultaneous FDA and Health Canada submission are not invisible to reviewers — they create questions about data lock discipline that can complicate review.

Once the DLP is established, Health Canada expects the completed PBRER within 70 calendar days. That’s the ICH E2C(R2) standard, and Health Canada hasn’t deviated from it. In practice, sponsors with complex multi-product portfolios sometimes request timeline extensions — the relevant Health Canada bureau handles these on a case-by-case basis, and reasonable requests submitted in advance with a rationale are typically accommodated. Last-minute requests or retroactive extension requests are a different matter.

Ad hoc PBRERs operate on a different timeline entirely. Health Canada can request an out-of-cycle PBRER when a safety signal warrants it — an unexpected cluster of serious adverse events from Canadian post-market surveillance, a new safety communication issued mid-period, or emerging data from a key study. These requests are not negotiable on timing, and sponsors who aren’t maintaining continuous surveillance readiness tend to struggle with the turnaround.

Five Documentation Gaps That Delay Health Canada Review

Across submissions we’ve worked through with Canadian sponsors and CMO partners, five deficiencies account for the majority of Health Canada review queries on PBRERs.

1. Missing or estimated-only Canadian exposure data. Bundling Canadian dispensing figures into global totals is the single most common issue. Section 6 needs Canadian numbers — separated, estimated transparently, and sourced.

2. Benefit-risk framing not tied to the Canadian product monograph. The Section 16 analysis must reference the Canadian PM, especially if it differs from global labelling. If your PM hasn’t been updated to reflect recent safety data, that gap becomes visible in the PBRER and may prompt a concurrent PM amendment request from Health Canada.

3. Omission of Canadian-specific regulatory history. Any DHCP letters, product recalls, or Health Canada-initiated label amendments from the reporting period belong in Section 10. Sponsors who treat this section as “only for EMA/FDA actions” create a traceable documentation inconsistency if Health Canada pulls their regulatory correspondence file.

4. Inadequate acknowledgement of Canadian patient population differences. Some risk groups are proportionally different in Canada due to regional disease prevalence, prescribing practices, or provincial formulary access patterns. A benefit-risk analysis that doesn’t acknowledge any Canadian context reads as a template exercise, not genuine pharmacovigilance thinking.

5. Submission formatting not aligned with Health Canada’s eCTD requirements. The CESG has specific technical requirements for volume organization, document metadata, and eCTD structure. A PBRER packaged for EMA submission that isn’t re-formatted for the CESG can trigger administrative returns — delays that have nothing to do with the pharmacovigilance content itself.

Coordinating Multi-Regional PBRERs Without Cutting Canadian Content

If you’re running aligned PBRERs across FDA, EMA, and Health Canada simultaneously, the efficiencies are genuine — most of the core benefit-risk infrastructure is portable across regions. But the Canadian-specific content in Sections 6, 9, 10, and 16 is not portable. It needs to be built deliberately, not retrofitted at the last minute before the CESG submission.

The practical approach: build the global PBRER core first, then develop Canadian regional inserts for each relevant section as a discrete workstream before final assembly. Treat it as additive, not corrective. The sponsors who run into trouble are the ones who start with the complete EMA or FDA package and try to “Canadianize” it in the final 72 hours before the deadline.

For organizations without dedicated Canadian pharmacovigilance expertise in-house, involving a Canadian regulatory advisor at the DLP planning stage — not just the submission assembly stage — consistently produces cleaner submissions and fewer review queries. The PBRER timeline is tight enough at 70 days that any substantive back-and-forth with Health Canada post-submission is costly.


Written by Nour Abochama, Quality & Regulatory Advisor, Androxa. Learn more about our team

Talk to our team about Health Canada compliance Contact us

Nour Abochama

Written by

Nour Abochama

Quality & Regulatory Advisor, Androxa

Chemical engineer with 17+ years of experience in laboratory operations, quality assurance, and regulatory compliance. VP of Operations at Qalitex (ISO/IEC 17025 accredited laboratory). Expert in Health Canada NHP regulations, NHPD licensing, pharmaceutical GMP, and ISO 17025 laboratory management. Master's in Biomedical Engineering from Grenoble INP – Ense3. Former Director of Quality at American Testing Labs and Labofine. Executive Producer and co-host of the Nourify & Beautify Podcast.

Chemical Engineering17+ Years Lab OperationsISO 17025 ExpertHealth Canada, FDA & GMP Compliance
View LinkedIn Profile →
🍁

Free: Health Canada NHPD Testing Checklist

Every test your natural health product needs for NPN license applications — from identity and potency to heavy metals and microbiology.

Request the free checklist →

Need Health Canada compliant lab testing?

Get a quote from our Health Canada NHPD-compliant laboratory. Fast turnaround for NPN applications.

Get a Testing Quote →