The QPPV's blind spot is the device: vigilance can't stop at the medicine

The signals that didn't come from a drug

Read this week's records as a pharmacovigilance professional and notice how many safety items concern the thing around the medicine, not the molecule. FDA's device centre flagged an early alert on B. Braun Streamline Bloodline Sets for Dialog+ after the company found that a missing solvent step left some dialyzer connectors inadequately bonded in three lots. The Dutch inspectorate IGJ published an urgent field safety notice for Löwenstein's LM150TD ventilator, covering a possible communication failure. IGJ also reported that updating Abbott's FreeStyle Libre 3 app fixes both a previously reported security vulnerability and a signal-loss problem.

Slovenia's JAZMP, in its tenth Pharmacovigilance Bulletin, features a change in the formulation and preparation of Amoksiklav oral suspension. The records flag this as relevant to medication-error and product-information handling. Even when the active ingredient is unchanged, how a product is made up or presented can become the safety issue.

My position: PV teams, and the QPPVs who answer for them, should stop treating this material as someone else's inbox. The failure modes these items describe are manufacturing process gaps, connectivity loss, software defects and preparation changes. They reach patients in the same way an adverse reaction does, and they are often noticed first by the same people.

Reporting channels already blur the line

The reporting infrastructure has stopped separating the two. The MHRA's #MedSafetyWeek announcement, running 2 to 8 November 2026, asks the public to report suspected medicine side effects and medical device incidents, and notes updates to the Yellow Card website and app. The Paul-Ehrlich-Institut's campaign focuses on adverse drug reactions, and reminds us that spontaneous reporting underpins signal detection. A patient reaching for the Yellow Card does not first decide which regulatory regime their problem belongs to.

That matters for intake. A report about a glucose-monitoring app, a ventilator alarm or a dialysis set may land with a company's PV function, or with a medicines regulator's channel, regardless of how the legal competencies are drawn. Teams that can only route what is plainly a drug event will lose time, or lose the report.

The strongest counter-argument

The best objection is about scope and accountability. Medical devices have their own vigilance rules, their own notified-body and competent-authority relationships, and in the US a separate FDA centre. A QPPV is accountable for the pharmacovigilance system for medicinal products, not for every ventilator or dialyzer in the supply chain. Pulling device events into PV risks diluting attention, blurring responsibility and creating duplicate reporting. Several of these notices, such as the B. Braun and Löwenstein items, concern products that are not medicines at all, and the records do not state that any of them involve patient harm.

I accept all of that. The argument is not that PV should take over device vigilance. It is that PV should be able to see it. The records show the signal source is diversifying, and a PV function that learns about a relevant device or preparation issue only when a colleague forwards an email is working with a delay it has chosen.

What a sensible response looks like

The practical step is modest: a shared watch and triage routine, not a merged department. Someone in PV should routinely scan the device and field-safety feeds that touch the portfolio, including FDA early alerts, national field safety notices and MHRA's monthly roundup. Each item should be recorded with a decision: relevant, not relevant, or needs a conversation with the device or quality owner. Several records this week are indexes or digests with no item-level detail, such as the MHRA Safety Roundup, the CBER communications list and the PEI bulletin. Those only help if someone opens them and logs the outcome.