Vaccine Pharmacovigilance & Materiovigilance · Section 14.10
~6 min read · The Drug Safety Coach — Global PV Career Course
Key points
Full text
Everything this module has covered so far treats vaccine PV and materiovigilance as parallel-but-separate disciplines. Combination products are where they genuinely intersect: a single product integrating a drug (or biologic) and a device into one entity — a prefilled autoinjector delivering a specific medication, a drug-eluting stent releasing a therapeutic agent from its structural device component, an insulin pump with integrated dosing logic. These products are common and increasingly so, and they create a genuine dual-obligation problem that a PV professional needs to recognise immediately rather than discovering partway through an investigation.
A combination product incident typically triggers dual reporting obligations — both conventional drug pharmacovigilance requirements (Module 1’s expedited reporting timelines, Module 6’s causality and seriousness assessment) and device vigilance requirements (Lesson 14.9’s incident reporting pathway) can apply to the very same event simultaneously, rather than one framework substituting for the other. A company processing only through its drug PV pathway, or only through its device vigilance pathway, risks a genuinely incomplete regulatory response to a case that actually needed both.
That dual obligation shapes the investigation itself in a specific way: root-cause analysis for a combination product incident has to work through a genuinely three-way diagnostic question that neither pure drug PV nor pure materiovigilance has to ask on its own — did the issue originate in the drug component (a formulation or stability problem), the device component (a mechanical or design failure), or their interaction (a device that performs correctly in isolation but fails specifically when paired with this particular formulation)? Getting this root-cause attribution right is what determines whether the appropriate corrective action is a formulation change, a device redesign, or a compatibility specification — genuinely different fixes, only reachable through genuinely different investigative pathways.
There’s also a real practical regulatory question combination products raise that neither pure drug products nor pure devices face: which regulatory framework actually leads. This is typically determined by the product’s "primary mode of action" — does the therapeutic effect come principally from the drug, with the device serving mainly as a delivery mechanism, or does it come principally from the device, with the drug playing a supporting role? That determination shapes which regulatory pathway (and which regulatory body, in jurisdictions with separate drug and device regulators) takes the lead, even though — as the first two paragraphs of this lesson established — both vigilance obligations typically still apply regardless of which pathway formally leads the approval process.
Important
A prefilled autoinjector pen malfunctions, and the patient receives an incorrect dose. Is this a drug PV case (Module 6’s causality/seriousness assessment applies to the dosing error’s clinical consequence) or a device vigilance case (Lesson 14.9’s reporting pathway applies to the mechanical malfunction)? The honest answer is often both, simultaneously — and treating it as only one or the other is exactly the kind of gap that leaves a genuine safety issue only partially investigated.
Quick check
Test yourself before moving on — no pressure, just click an answer.
1. A prefilled autoinjector malfunctions, delivering an incorrect dose of medication. What is the correct approach to reporting and investigating this incident?