MHRA Recall Patterns and the Hidden Compliance Architecture Risk

Three MHRA Enforcement Notices, One Structural Pattern

Within a short sequence of MHRA product-action notices, the agency issued three communications concerning different medicinal products: a Class 4 Medicines Defect Notification under EL(26)A/31 for gabapentin oral solution, a Class 2 Medicines Recall under EL(26)A/33 for phenoxymethylpenicillin oral solution, and a Class 2 Medicines Recall under EL(26)A/34 for a chlorhexidine-based cutaneous solution supplied in a 1 mL applicator. The notices concern three different therapeutic uses and distinct quality issues, including crystallisation of preservatives, product-labelling discrepancies and a potential breach of sterility in the packaging process. The notices do not, by themselves, establish a common root cause or a systemic failure across the affected marketing authorisation holders. They do, however, provide a useful starting point for examining how organisations identify and connect post-authorisation quality signals across heterogeneous product portfolios.publishing+1

When MHRA issues recall and defect notifications affecting oral solutions and sterile applicator presentations within a relatively short period, the appropriate regulatory question is not whether the notices prove a portfolio-wide compliance failure, but whether existing quality and regulatory-intelligence processes are sufficiently integrated to identify relevant risks early. The products may be subject to different technical, manufacturing and pharmacovigilance requirements, and the specific implications will depend on the nature of each defect, the product’s authorisation and the outcome of the manufacturer’s investigation. In that context, the gap between internal detection, regulatory assessment and corrective action can represent a material business risk — and fragmented data architecture may make that gap harder to identify and manage.

The Data Architecture Behind Post-Authorisation Quality Failures

Many MAHs managing UK portfolios hold their product-quality data across disconnected systems: SmPC version control sits separately from GMP certificate validity records, which sit separately from PSUR submission schedules, which sit separately from batch-release documentation. The EL notice series — EL(26)A/31 through EL(26)A/34 — represents the point at which MHRA enforcement has become visible externally; it does not, by itself, prove that MHRA detected a common signal that the affected MAHs’ internal systems failed to identify. A Class 2 recall, by MHRA’s own classification criteria, implies a product deficiency where use may cause mistreatment or harm to the patient, but is not life-threatening or serious. Depending on the nature of the defect, it may trigger an immediate review of the SmPC and other product information, an assessment of pharmacovigilance reporting implications under the applicable UK GVP requirements, and, where the authorised quality specification or other terms of the marketing authorisation are affected, a potential variation or other regulatory submission under the Human Medicines Regulations 2012.gov

The challenge for a UK MAH managing 15 or more authorised products is that these obligations do not arrive as a consolidated signal. They arrive as separate administrative triggers across MHRA’s Yellow Card pharmacovigilance system, the MHRA product database and GMP certificate records. No single internal dashboard necessarily connects batch-defect status, PSUR submission schedules, DSUR obligations where relevant under ICH E2F, variation submission history and GMP certificate expiry across a portfolio of this size. The result is that remediation can remain reactive rather than predictive — and reactive remediation, once a Class 2 EL notice has been issued, may carry commercial consequences that extend well beyond the direct cost of the recall itself.

MHRA’s Growing Enforcement Velocity and What It Means for Portfolio Monitoring

MHRA’s 2025–26 Annual Report confirms increased operational capacity and highlights what the agency describes as its growing global influence. This expansion of regulatory capability does not reduce enforcement pressure on MAHs and may, in practice, support more frequent and more targeted post-authorisation surveillance actions. The sequence of EL(26)A/31 through EL(26)A/34 provides a useful example of multiple product actions issued within a relatively short period, although the notices do not by themselves establish a common systemic cause. For in-licensing teams and Series A investors evaluating UK-authorised portfolios, a history of Class 2 or Class 4 enforcement actions against a target MAH is a material due-diligence signal — one that may influence asset valuation, reimbursement positioning and the perceived credibility of the regulatory-affairs function in the eyes of a future acquirer or licensing partner.

The ICH E2F Development Safety Update Report guideline, effective in the EU from September 2011 under EMA/CHMP/ICH/309348/2008, establishes a common framework for periodic safety reporting on medicines under development. It defines the recommended content and format of the DSUR, including cumulative exposure to the investigational drug, updates to the reference safety information and an overview of ongoing and completed clinical trials during the reporting period. Where clinical development continues after a product has been marketed, both DSUR and PSUR obligations may apply, with each report addressing different aspects of safety monitoring and potentially having different reporting periods, recipients and submission schedules. If these obligations are not tracked in an integrated way, the resulting documentation and timing interfaces can create avoidable compliance gaps. A delay in DSUR submission for a product simultaneously subject to a Class 2 recall action may therefore compound the overall compliance exposure, depending on the facts of the case and the applicable regulatory requirements.

Bioequivalence, Generic Portfolio Risk, and the BE Study Documentation Chain

The EL(26)A/33 recall of a phenoxymethylpenicillin oral solution raises a question directly relevant to UK generic MAHs: where a product’s marketing authorisation relies on bioequivalence data, and a post-authorisation quality defect leads to a reformulation or manufacturing-process change, does the existing BE package remain sufficient to support the changed product? Under ICH M13A — the guideline on bioequivalence for immediate-release solid oral dosage forms, adopted by CHMP on 25 July 2024 and effective from 25 January 2025 — the applicant remains responsible for the quality, completeness and integrity of the data submitted to the regulatory authority. M13A applies to immediate-release solid oral dosage forms, including relevant granules or powders for oral suspension, rather than automatically to every liquid oral solution. Where a post-recall manufacturing or formulation change could affect dissolution or systemic exposure, the regulatory pathway should therefore be assessed case by case. An ICH M9 BCS-based biowaiver may be relevant in appropriate circumstances, but eligibility depends not only on whether the active substance meets the applicable BCS Class I or III criteria, but also on the dosage form, strength, comparator, formulation and required in-vitro dissolution evidence.

For a phenoxymethylpenicillin oral solution, the question of whether existing BE evidence or a biowaiver remains sufficient after a Class 2 quality defect and any subsequent reformulation is precisely the type of regulatory issue that may surface during due diligence rather than at the time of the original authorisation. Its assessment requires correlation of the recall history, the nature and scope of the manufacturing or formulation change, the current variation status and the original BE documentation. This type of issue can remain structurally difficult to identify unless the compliance review brings those elements together in a single, scored profile.

From Signal Detection to Structured Compliance Intelligence

Vestango’s automated monitoring pipeline tracks MHRA enforcement signals — including EL notice series, Yellow Card data trends, relevant GMP certificate changes in EudraGMDP, and product-authorisation status updates — across more than 55 regulatory sources simultaneously. EudraGMDP is an EU/EEA database; current UK records should be verified against the relevant MHRA sources, while historical UK records and applicable Northern Ireland information may be available in EudraGMDP. When multiple EL notices are issued across different product categories within a short period, Vestango’s system can flag this as a pattern-level signal rather than treating each notice as an isolated product event. The output is not a regulatory opinion but a structured, scored dataset that maps identified risk surfaces to relevant compliance dimensions, including pharmacovigilance indicators, GMP-record status, variation history and PSUR schedule information, based on the availability and scope of the underlying public and client-provided data.

For a UK MAH reviewing its exposure following the EL(26)A series, or for an in-licensing team assessing a target with a history of MHRA enforcement actions, this structured dataset enables the client to review and independently verify the documented compliance picture rather than relying solely on advisory conclusions. Vestango can conduct an initial review and surface preliminary structured findings within 48 hours, subject to the scope of the review and availability of the relevant data. The initial profile may cover enforcement history, potential variation-record gaps, GMP-record currency and PSUR schedule alignment, providing an early view of the primary risk surfaces before a full portfolio-level engagement is commissioned.

If your UK-authorised portfolio includes products subject to MHRA post-authorisation surveillance, or if you are evaluating a target MAH with a history of Class 2 or Class 4 recall actions, Vestango delivers both dimensions: a compliance-gap analysis mapped to the regulatory obligations potentially engaged by each enforcement action, and an aggregated registry dataset scored across relevant pharmacovigilance indicators, GMP-record status and variation history. Assessment of BE documentation status requires access to the relevant dossier or client-provided study records and should not be represented as a conclusion derived solely from public registries. The analysis may incorporate MHRA product-authorisation records, relevant EudraGMDP records and publicly available pharmacovigilance information, where applicable. Contact Vestango.

The analysis in this article draws on publicly available regulatory data, published guidelines, and the accumulated experience of Vestango Life Sciences in EU and Polish regulatory affairs. It reflects patterns we observe — not universal conclusions. Every regulatory situation is product-specific, market-specific, and jurisdiction-specific. What applies to one portfolio may not apply to yours. If any of the issues raised here resonate with your situation, the right next step is a structured, case-specific conversation — not the application of general conclusions. With our founder Paweł Wojtaszczyk, Ph.D. Eng., we work at the intersection of data science and regulatory affairs, translating that combination into real market implementations. We solve problems and build companies operating in the life sciences market. Contact Vestango.