Introduction
While Pharmacovigilance (PV) monitors adverse reactions to pharmaceutical molecules, Materiovigilance (MV) is dedicated to monitoring the safety and performance of medical devices.
When a medical device fails, breaks down, or leads to unexpected complications in a clinical setting, safety professionals must investigate whether the issue was caused by a device malfunction, poor maintenance, material fatigue, or user error.
1. Defining a Reportable Incident
In Materiovigilance, an event is classified as a reportable incident if it meets three core conditions:
-
An incident involving a medical device occurred (malfunction, deterioration in characteristics/performance, inadequate labeling, or user error).
-
The medical device is suspected to be a contributing cause of the incident.
-
The incident led to, or has the potential to lead to:
-
Death of a patient, user, or third party.
-
Serious deterioration in state of health (permanent impairment, hospitalization, medical intervention).
-
2. Common Root Causes in Device Surveillance
Unlike drugs, which cause biochemical reactions, device failures fall into distinct engineering and operational categories:
-
Mechanical / Physical Failure: Material fracture, electrical short-circuiting, battery degradation, or tubing leakage.
-
Software Glitches: Firmware bugs, calibration errors, or loss of connectivity in digital monitoring equipment.
-
Use / Ergonomic Error: Confusing user interfaces, unclear instructions for use (IFU), or improper assembly leading to clinician operational mistakes.
3. The Role of Safety Associates in Materiovigilance
Safety professionals working in MV handle device incident logging, coordinate technical investigations with biomedical engineers, file Manufacturer Incident Reports (MIR) to global authorities, and help execute Field Safety Corrective Actions (FSCA) when device recalls are required.