'Maintenance' is not a non-event: make EMA's quiet outputs a standing PV reconciliation task

The week that looked like nothing

On 30 October EMA published single-assessment outcomes for gliclazide, tenoxicam, nitrofurantoin (including nitrofurantoin/pyridoxine), cystine/pyridoxine, aprotinin and nicorandil. Every one ended in 'maintenance'. The same day it issued a list of centrally authorised products whose product information has changed for safety reasons. On 3 November it published QRD Appendix V, covering the standard statement and contact details for reporting suspected adverse reactions.

Read as headlines, none of this demands action. No withdrawals, no suspensions, no new restrictions. That is exactly why it is dangerous. The easiest thing a pharmacovigilance team can do with a run of 'maintenance' outcomes is nod and file them. I think that is the wrong reflex, and this column argues for a different default.

Maintenance is a result, not a release

A PSUSA is a single assessment of periodic safety update reports for an active substance across the products that contain it. A maintenance outcome means the marketing authorisations stay as they are. EMA's records for these procedures also come with a list of nationally authorised products. That list is the practical point. The outcome applies to a whole substance, and each marketing authorisation holder still has to confirm that its own product, its own documentation and its own safety data are consistent with the conclusion.

The records do not tell us what changed, if anything, in any of these products' information, and I won't pretend they do. That gap is the argument. 'Maintenance' tells you the regulator did not act. It does not tell you your file is in order. Only a deliberate check does that.

Three outputs, one job

Put the three outputs side by side and a single workflow emerges. First, the PSUSA outcomes: confirm which of your products are on the national lists and that the conclusion is logged against them. Second, the list of centrally authorised products with safety-related product information changes: check whether any of your products appear, and whether any related products in your portfolio should be read across. Third, Appendix V: the reporting statement and contact details are the front door to your PV system. If a patient or clinician follows the wrong instruction, the signal never reaches you.

The MHRA's MedSafetyWeek push for Yellow Card reports, with low reporting rates flagged in one product area, is a reminder that spontaneous reporting depends on people finding the right route. Product information is where that route is written down. Appendix V is not glamorous, but it is the template for that route.

The strongest counter-argument

The best objection is proportionality. PV teams are stretched, and a maintenance outcome by definition requires no regulatory action. The Appendix V changes are unspecified, and may be minor. Building a process around outputs that mostly confirm the status quo risks diverting effort from live signals, and any team that chased every EMA publication would drown.

That is fair, and I accept the premise: this should not be a heavy exercise. But the cost-benefit points the other way. The check is a short reconciliation: is it in scope, is it logged, does our text match? Skipping it only saves anything if nothing was ever out of step, and nobody knows that until they look. Quiet weeks are the best time to do the looking.

What I would do on Monday

Assign one owner for EMA publication triage, and give them a standing checklist rather than an ad hoc inbox habit. Record a documented 'no action required' decision against each relevant product, with a reason. A recorded decision is evidence of oversight. A silent non-decision is not. Read Appendix V in full, compare it with the reporting text in your current product information, and log the result either way.