- For Quality Assurance: the event reinforces the need for rapid batch-impact assessment after a stability signal.
- For QC and manufacturing: it underlines the importance of tracing a possible particulate source without assuming the cause.
- For QPs and regulatory teams: it shows how post-release evidence can change the status of a distributed batch.
MHRA Recall Details: What Happened to Fingolimod Zentiva?
The affected batch is 4L01372H, with an expiry date of November 2027. It was first distributed on 28 January 2025 in packs of 28 capsules. According to the MHRA, the action is precautionary because of a potential risk of contamination with metal particles.
| Product | Batch | Expiry | First distributed | Action |
|---|---|---|---|---|
|
Fingolimod Zentiva 0.5 mg Capsules |
4L01372H |
11/2027 |
28 January 2025 |
Class 2 recall |
Importantly, the regulator did not report confirmed patient harm. The MHRA said the particles, if present, are known to be small and pose a low risk to the safety or efficacy of the product. It also reported that no cases had been received to date. The potential issue was identified during shelf-life testing.
Healthcare professionals were instructed to stop supplying the affected batch, quarantine any remaining stock and return it through their supplier’s approved process. Meanwhile, patients with the affected batch should contact their pharmacy. The MHRA specifically advises patients not to stop taking their medicine without first speaking to a healthcare professional.
Why This Shelf-Life Signal Matters for Pharma Quality Teams
The timing makes this event particularly relevant for pharmaceutical quality teams. The potential defect emerged during shelf-life testing after the batch had entered distribution. Therefore, the case highlights the continuing role of stability programmes after initial batch release.
It also demonstrates why batch traceability and defect-management procedures must remain effective throughout a product’s marketed lifecycle. When a quality signal emerges later, manufacturers need records that allow them to identify the affected batch and support an appropriate assessment.
However, the MHRA notice does not identify the source of the potential metal particles. Therefore, it would be incorrect to attribute the issue to manufacturing equipment, packaging, raw materials or another specific cause without further evidence. Any root-cause conclusion would depend on the investigation.
If stability testing identifies possible particulate contamination in a distributed batch, which should your quality system initiate first: a formal batch-impact assessment or a CAPA record?
What QA and Manufacturing Teams Should Check Now
- Confirm that recall procedures clearly define quarantine, traceability and escalation responsibilities.
- Review whether stability-testing signals are promptly connected to QA batch-impact assessment.
- Verify that distributed-batch records allow rapid identification of affected stock.
- Ensure investigations require evidence before assigning a contamination source or defining CAPA.
What Could Happen Next After the MHRA Recall?
The key next development is whether Zentiva or the MHRA publishes further information about the investigation, the potential source of the particles or any wider batch impact. Quality teams should also watch for an extension beyond batch 4L01372H or any updated regulatory safety assessment.
How Zamann Pharma Can Support Stronger Quality Systems
Zamann Pharma’s Quality Management System support is the most natural match for teams reviewing deviation handling, CAPA, recall readiness, batch-impact assessment and GMP quality governance. Teams can explore the service when they need practical support strengthening these controls.
Source: Gov.Uk