Local Regulatory Experts
Connect with regulatory affairs consultancies specializing in this region.
View More Consultancies in This RegionNovember 26, 2025
Approximately 5 minutes
Regulatory Alert: EMA Automates ICSR Pharmacovigilance Compliance Monitoring
Regulatory Alert: EMA Automates ICSR Compliance Monitoring
The European Medicines Agency (EMA) has officially initiated its compliance monitoring program, utilizing the EudraVigilance Data Analysis System (EVDAS) to generate automated monthly reports on ICSR (Individual Case Safety Report) submission timelines. This change necessitates that all Marketing Authorisation Holders (MAHs) and Sponsors review and adjust their Pharmacovigilance (PV) systems.
The New Automated Workflow
Starting December 2025, the EMA will automate compliance tracking:
- Monthly Reports: All sender organizations will receive automated monthly PDF reports analyzing their ICSR adherence.
- Recipient: Reports will be sent directly to the organization's Qualified Person for Pharmacovigilance (QPPV) or Regulatory Point (RP).
- Reporting Windows: Reports will specifically analyze adherence to the regulatory 7-day, 15-day, and 90-day reporting windows.
The Compliance Trap: Understanding the Deadline
Compliance is calculated strictly based on the timestamp difference between two key data points:
$$\text{Compliance} = \text{EudraVigilance Gateway Date} - \text{Receipt Date (E2B R3 C.1.5)}$$
- Receipt Date (C.1.5): This is the date the MAH or Sponsor first received the case.
- Gateway Date: This is the exact time the EudraVigilance Gateway timestamps the submission.
Critical Tip: Submitting ICSRs late in your local time zone (e.g., at "Close of Business") carries a high risk. If the EudraVigilance Gateway timestamps the submission as the next calendar day, the report will be flagged as late.
Action Plan for MAHs and Sponsors
To ensure compliance ("stay green on the dashboard"), organizations must take proactive steps:
- Check QPPV Details: Verify that the EU-QPPV email is correctly registered in EudraVigilance to ensure critical monthly notifications are received.
- Monitor Gateways: Do not rely on a "send and forget" process. Always verify that the submission received a positive ACK code and explicitly note the Gateway Date as evidence of timely submission.
- Review Nullifications: Be aware that while nullified or amended reports are excluded from compliance statistics, the original valid report still counts against the submission timeline.
Related Articles
Approximately 5 minutes
UK Medical Device Registration (MHRA): Compliance, UKCA Marking, and the UK Responsible Person
To sell medical devices in Great Britain, manufacturers must comply with the **UK MDR**, obtain the **UKCA Marking**, and mandatorily register their devices with the **MHRA**. Foreign manufacturers must appoint a **UK Responsible Person (UKRP)** to handle registration and post-market responsibilities on their behalf.
Approximately 5 minutes
UK Medical Device and IVD Registration: The UKCA Transition and UK Responsible Person Requirements
To place devices on the Great Britain market, manufacturers must comply with the UK MDR and register with the MHRA. Foreign manufacturers must appoint a UK Responsible Person (UKRP) and use a UK importer. While the UKCA marking is the new standard, CE-marked devices remain acceptable until up to June 30, 2030, depending on the device's classification.
Approximately 5 minutes
UK Medical Device Registration Process: A 6-Step Guide to MHRA Compliance
Registering a medical device for the UK market involves mandatory compliance with the **MHRA**. This guide outlines the 6 essential steps, from device classification and conformity assessment to appointing a **UK Responsible Person (UKRP)** and final submission via the **DORS** system.
Approximately 5 minutes
The Regulatory Trilemma: Navigating MDR, AI Act, and GDPR for Medical AI in the EU
Medical AI in the EU faces a "regulatory trilemma" where the **MDR's static framework** conflicts with the **AI Act's dynamic requirements** for continuously learning models. This, coupled with **GDPR data constraints**, slows innovation by forcing AI's self-improvement cycle to stop for repeated evaluation.