Aggregate Reporting · Section 8.9
~6 min read · The Drug Safety Coach — Global PV Career Course
Key points
Full text
Lesson 8.2 established that ICH E2C(R2) designed the PBRER as a globally harmonised format specifically to reduce duplicated report preparation across regions — and that’s a genuine, substantial improvement over the pre-harmonisation landscape. What it doesn’t mean is that a single, identical document gets submitted unchanged to every regulator worldwide; regional variation in timing, supplementary content, and submission mechanics persists even under the harmonised core format.
India’s CDSCO generally aligns closely with ICH guidance in substance, but companies operating in the Indian market still need to confirm specific local submission timelines and any India-specific procedural requirements — alignment in principle doesn’t always mean identical mechanics in practice. The FDA has historically accepted the PBRER format for US-marketed products but layers certain US-specific supplementary content requirements on top of the core harmonised structure, meaning a PBRER destined for FDA submission isn’t always byte-for-byte identical to the same product’s PBRER submitted to EMA.
Japan’s PMDA, and several other regulatory authorities, can require additional region-specific data elements, or apply different reporting frequency expectations for certain product categories — a pattern that echoes the ICH pillar structure Module 2 introduced, where global harmonisation efforts coexist with legitimate, retained regional variation rather than eliminating it entirely.
The practical implication for a global PV team is that "PBRER-compliant" is necessary but not sufficient for multi-region submission readiness — most large organisations build a core, harmonised PBRER covering the shared ICH E2C(R2) content, then layer region-specific supplements, cover letters, or content additions addressing each regulator’s specific requirements on top of that shared core, rather than either writing entirely separate reports per region or assuming one document satisfies every jurisdiction unchanged.
Note
A common misconception is that PBRER harmonisation means "write one report and submit it everywhere unchanged." In practice, most global companies build a core, harmonised PBRER and then produce region-specific supplements or cover documents addressing local timing, format, or content requirements — harmonisation reduced duplicated core content, it didn’t eliminate every regional difference.
Quick check
Test yourself before moving on — no pressure, just click an answer.
1. What does PBRER harmonisation actually achieve, according to this lesson?