MHRA Field Safety Notices & Medical Device Alerts: How to Monitor Them

What the MHRA is

The Medicines and Healthcare products Regulatory Agency (MHRA) is the UK's regulator for medicines, vaccines and medical devices. On the device side, it runs the UK's post-market vigilance system: it receives reports of adverse incidents, oversees manufacturers' corrective actions in the field, and publishes safety information for the NHS and the public. For any manufacturer holding UKCA marking or selling through UK distributors, MHRA output is a primary surveillance source — and one the FDA's MAUDE database will never contain.

Field safety notices (FSNs)

A field safety notice is an urgent communication a manufacturer issues to its customers and users about a field safety corrective action (FSCA) — a recall, a modification, updated instructions, or advice to stop using a device. The FSN is the manufacturer's own document; the MHRA receives it, and publishes FSNs so the wider healthcare system sees them.

The key thing to understand: an FSN is manufacturer-originated. It's the device maker telling the field "here is a problem with our product and here is what to do about it." That makes FSNs one of the most direct early signals about a device — including devices in a category or from a competitor that shares your components or design approach.

MHRA device alerts — and how they differ

Separately from manufacturer FSNs, the MHRA issues its own alerts where it judges that further action is warranted — historically "Medical Device Alerts (MDAs)", now often issued through the National Patient Safety Alert framework. These are regulator-originated: the MHRA directing healthcare providers to act.

Both appear in the MHRA's published safety information, and both matter for monitoring — the FSN is the earliest manufacturer signal, the MHRA alert is the regulator's escalation.

Where the MHRA publishes it

MHRA safety information is published on GOV.UK, principally under "Alerts, recalls and safety information: drugs and medical devices" (gov.uk/drug-device-alerts). You'll find FSNs, device alerts, recalls, and the periodic MHRA Safety Roundup. You can search it and subscribe to email updates.

Yellow Card: the reporting side

The signals the MHRA publishes start as reports in. Adverse incidents involving medical devices are reported to the MHRA through the Yellow Card scheme — the UK's system for reporting suspected problems with medicines and devices. Healthcare professionals can report device incidents directly, increasingly through integrated clinical IT systems (EMIS, SystmOne and others), and manufacturers report FSCAs and adverse incidents to the MHRA through its own reporting channels.

For a manufacturer, Yellow Card matters in both directions: it's a route your own vigilance obligations run through, and the incidents reported through it are part of what eventually surfaces as published safety information about your device class.

Why the UK is now separate from the EU

Before Brexit, UK device signals arrived bundled with EU ones. Now the UK operates its own regime, which has two consequences for monitoring:

• MHRA is a distinct source. UK FSNs and alerts no longer overlap cleanly with EU vigilance data — you have to watch both. An EU MDR post-market surveillance plan that only cites EU and FDA data has a UK-shaped gap.
• Great Britain vs Northern Ireland. Under the Windsor Framework, Northern Ireland continues to follow EU device rules while Great Britain (England, Scotland, Wales) is on the UK regime — so the UK picture itself is split. UKCA marking applies in GB, with CE marking accepted under transitional arrangements whose timelines have shifted more than once (always confirm the current position).

Monitoring it in practice

A workable MHRA monitoring routine looks a lot like the MAUDE workflow, adapted to a source with no API:

1. Subscribe to the GOV.UK drug-device-alerts updates and monitor the weekly FSN listings.
2. Scope by your brand and manufacturer names and your device category — FSNs from other makers in your category are early warnings for shared risks.
3. Triage each hit: is it your device, a competitor's, or a component you rely on?
4. Log findings into your PMS system with the source and date, so your UK coverage is evidenced, not assumed.

The hard part isn't any single source — it's doing this for the UK and the US and Canada, Switzerland and the EU at once, each with its own format, cadence and (mostly) no API, then de-duplicating and cross-referencing it all against your portfolio. That's the manual burden that turns into a permanent gap the moment the team gets busy.