Send and receive information on adverse drug reactions (ADRs)
How marketing authorisation holders should inform MHRA of a signal or an ADR to a medicine.
Reporting arrangements
Marketing authorisation holders (MAHs) must send all UK individual case safety reports (ICSRs) and serious non-UK ICSRs directly to MHRA via either ICSR Submissions or Gateway.
For cases in respect to Northern Ireland, use the country code XI to send ICSRs to MHRA.
MHRA accepts E2B R2 and R3 format XMLs and will convert E2B R3 cases to E2B R2 for processing into the database. MHRA will transmit Adverse Drug Reaction (ADR) reports received directly to the relevant MAH. This will be decided using the suspect drug in the report.
Those wishing to report to MHRA need to register with MHRA. Follow the guidance on registering to make submissions to MHRA.
New MHRA systems
We are replacing our legacy IT systems, including a new adverse incident database. The new system will be deployed over the weekend of 25 and 26 May 2024 and will be live from Tuesday 28 May 2024. Any files received after 6am on Friday 24 May 2024 will be queued and loaded into our new database and will receive acknowledgements in the E2B R3 format.
R3 standard compliant systems: what’s changing for vigilance reporting for MAHs?
The new MHRA database is compliant with the ICH ICSR R3 standard and conforms with EU implementation guidance.
While the database will be based on the R3 standard, our new system will be able to convert R2 standard XMLs into the R3 standard for ingestion. After go-live of our new systems we will continue to accept ICSRs in both R2 and R3 standards.
All XML files sent from MHRA will be in the R3 standard format. This includes both ASPRs and acknowledgements. It is important that your systems and/or procedures can receive and manage files in the R3 standard effectively as our new systems will not be able to send R2 files.
No updates are necessary to the sender or receiver ID in XMLs. The MHRA receiver ID will continue to be MHRAUK.
There will not be a transition period between databases. Any ICSRs sent before 6am on Friday 24 May 2024 will be acknowledged in R2. Any sent after will be acknowledged in R3.
MHRA gateway users
The gateway will continue to accept R2 and R3 XMLs both for ICSRs and acknowledgements.
You do not need to make any changes to your application programming interface (API) connection to our systems. You do not need to inform us that your organisation is R3 ready.
ASPRs will be sent as individual files rather than in batches.
No testing is required. However, if you wish to test the system it is now available to do so.
As with production, no changes are necessary for using the test environment to either the API or to the sender/receiver ID. The test receiver ID continues to be MHRAUKTEST.
If you would like to receive an R3 ASPR via the gateway, contact [email protected].
ICSR submissions portal users
The portal will continue to accept R2 and R3 XMLs via Post XML.
Portal users will be able to create new reports using either the R2 or R3 form.
Acknowledgements and ASPRs sent from MHRA will be in the R3 format.
Portal users will continue to be able to download ASPRs as a PDF file, but these will now be in the R3 standard.
Literature monitoring
We will not publish a literature monitoring list. Instead, MAHs will be responsible for conducting relevant literature searches and sending these to MHRA. These should include reports received from the EMA Medical Literature Monitoring (MLM) service. Email [email protected] if you have any queries on reporting new literature for ADRs.
Signals
A safety signal is information on a new or known adverse event that may be caused by a medicine and requires further investigation. MHRA is responsible for detecting and managing safety signals in regards to UK products.
In line with GVP IX requirements, you should use the [email protected].
to send standalone notifications of signals toWhen an MAH becomes aware of an emerging safety issue, they should notify it in writing to MHRA ([email protected]). For guidance on emerging safety issues, see GVP IX.
Contact
Email [email protected] with technical queries or to escalate an E2B issue you can speak to a member of the E2B team:
- David Sullivan, [email protected]
If your query specifically relates to ASPRs email [email protected].
Or, if you’re unhappy with how your query is dealt with, contact the pharmacovigilance service coordinator, Faiza Farooq, 0203 080 6312.
Updates to this page
Published 18 December 2014Last updated 9 May 2024 + show all updates
-
Updated dates of new adverse incident database deployment.
-
Updated with information about new MHRA systems.
-
Reporting arrangement sections updated to include a list of reports received via the EMA from the 28 December to the 31 December
-
Reflecting the end of the transition period, removed old information about changes to reporting arrangements. Added new information on literature monitoring and signals.
-
Updated literature report list
-
updated literature report
-
New sections added and text removed
-
Updated literature list
-
Updated literature report list
-
Updated literature report.
-
Updating lit report list.
-
Updated literature report list
-
Literature report document updated.
-
New literature report list added to the page.
-
Updated literature report list added to the page.
-
Updated literature list.
-
New literature report list.
-
Updated literature report
-
New literature report list added to the page.
-
Updated literature report list added to the page.
-
Updated literature report.
-
Updated literature report list.
-
Updated Literature report.
-
New literature report list added to the page.
-
Updated literature report list
-
Updated Literature report list.
-
Updated Literature report list.
-
new literature report list added to the page.
-
Updated the literature report list.
-
Up-to-date literature report added to the page.
-
Updated the Literature report list
-
Updated literature report
-
Updated literature reference list
-
updated literature reference list
-
Updated literature list
-
Updated literature reference list
-
Updated literature report list
-
Updated literature report.
-
updated literature report list added to the page
-
updated literature reference list
-
updated literature report list
-
New literature report list published
-
updated literature reference list
-
Updated literature report list
-
Updated literature list
-
Updated literature report list
-
updated literature list
-
Updated literature reference list
-
Updated literature reporting list
-
Updated literature reference list
-
updated literature reference list
-
Updated literature report.
-
Updated literature report added to the page.
-
Updated literature report.
-
updated literature report list
-
Updated literature report list.
-
Updated literature list
-
Updated literature list
-
Updated literature list
-
Updated literature report added to the page.
-
Updated literature list.
-
Updated PV literature
-
updated literature list
-
Updated literature list
-
Updated literature list
-
Updated literature list
-
Updated literature report.
-
Updated literature list
-
Updated literature reference list.
-
Updated literature reference list
-
Updated literature list
-
Updated literature material
-
Updated literature list
-
Updated literature report list.
-
updated literature list
-
Updated literature list
-
Updated literature report list
-
updated literature list
-
updated literature list
-
Updated literature report list
-
new reference material
-
Updated literature report list.
-
new literature list
-
Updated literature report.
-
new literature list
-
Updated literature list
-
Updated literature report list.
-
Updated literature report list.
-
Updated literature report list.
-
Updated literature report list.
-
Updated literature report list.
-
Updated literature report list
-
Updated literature report list.
-
Updated literature report list
-
Updated literature report list
-
Updated literature report list
-
First published.