Global PV updates, distilled - powered by our community
This week is centred around ICH E2D(R1) β the long-awaited update on post-approval safety data management.
The revision clarifies how modern safety data sources (social media, patient support programs, market research, etc.) should be handled in pharmacovigilance systems.
It will soon start affecting operational PV processes in the EU.
As always, thank you to everyone who shared links, documents, and local insights by email or in Slack - this newsletter exists because of you π
π Start with the 10-Second Summary, then dive deeper if something touches your portfolio.
β±οΈ 10-Second Summary (Read This First)
If you read nothing else this week:
πͺπΊ EU β ICH E2D(R1) implementation begins 18 March 2026 (new guidance on solicited sources & post-approval safety data).
πΊπΈ US β FDA issues final guidance implementing ICH E2D(R1).
πͺπΊ EU β EURD list & PSUR submission frequencies updated.
π©πΏ Algeria β CNPM reminds MAHs: ICSRs must be reported via national e-reporting system + βzero eventβ reporting required.
Details and links below π
π This Period's Highlights
EMA has published the EU implementation strategy for ICH E2D(R1) on post-approval safety data.
The revision modernises the framework for managing safety information collected after marketing authorisation.
Key points
β’ Clarifies handling of solicited safety data sources (social media, patient support programs, market research, etc.)
β’ Updates terminology and standards for post-approval safety reporting
β’ Aligns safety surveillance expectations with current PV practice
Timeline
β’ 18 March 2026 β Guideline becomes effective in the EU
β’ Transition period until 18 September 2026 for MAHs to update processes
GVP Module VI will be revised to formally integrate E2D(R1).
Until then, the revised definitions and guidance should already be applied in line with the EMA implementation strategy.
What to review
PV teams should assess:
β’ handling of solicited programs and organised data collectionβ
β’ case identification and reporting rules
β’ SOP alignment with updated definitions
This is a structural update to post-marketing safety data management.
The FDA has issued final guidance implementing ICH E2D(R1).
The document replaces the original 2003 E2D guidance and aligns US expectations with the updated ICH framework.
The guidance clarifies:
β’ treatment of modern safety data sources
β’ terminology used in post-approval safety reporting
β’ expectations for expedited reporting of ICSRs
This further strengthens global alignment on post-marketing safety surveillance.
The Algerian National Centre for Pharmacovigilance and Materiovigilance (CNPM) issued a regulatory reminder on PV reporting obligations.
Key points:
β’ ICSRs must be reported exclusively via the national e-reporting platformβ
β’ reporting must follow national PV timelines and technical requirements
β’ companies must ensure access to the CNPM system
Zero-event reporting
If no ICSRs are reported for a 3-month period, MAHs must submit a case-free (βzero eventβ) report to CNPM.
The notice aims to reinforce compliance with national pharmacovigilance reporting obligations.
EMA has published an updated EURD list and PSUR submission frequency file.
MAHs should verify whether any products in their portfolio have:
β’ updated EU reference dates (EURD)β
β’ modified PSUR submission timelines
Routine update β but important for compliance planning.
π£οΈ Join the Conversation & Contribute
What did you think of this weekβs edition? Was it helpful?
Hit reply to share your thoughts or tell us if we missed an update.
β
If you found this useful, please share it with one PV colleague or join our growing Slack workspace to discuss these changes.
Until next week - stay compliant, stay curious.
βοΈ Disclaimer
This newsletter is for informational purposes only and does not constitute professional or legal advice.
All summaries are based on publicly available regulatory information. Always verify requirements with the relevant authority or qualified professional before implementation.
RegIntelHub assumes no liability for actions taken based on this content.