India Medical Device Vigilance: Reporting SUSAEs Within 15 Days

1. Key takeaways

India’s vigilance obligation for medical device licence holders is built around a single, tightly defined deadline: within 15 days of a suspected unexpected serious adverse event (SUSAE) coming to the notice of the licence holder, the holder must report the occurrence of the event and the actions taken, including any recall, to the State Licensing Authority (SLA) or the Central Licensing Authority (CLA). The decisive feature of this rule is its trigger point. The clock starts when the event comes to the notice of the licence holder — not when the event is confirmed, not when the investigation is completed, and not when a causal link has been established. Everything else in the Indian vigilance framework follows from that early starting point.

• The 15-day period runs from the moment the SUSAE comes to the notice of the licence holder, which means front-line commercial staff can start the clock without anyone in regulatory affairs knowing.
• The reporting duty under Rule 26(ii) of the Medical Devices Rules, 2017 covers both the event and the actions taken, and the rule expressly includes any recall within that scope.
• The statutory obligation is directed at the SLA or the CLA, while the practical reporting channel is the Materiovigilance Programme of India (MvPI); the two operate at different levels and do not conflict.
• The SUSAE definition, drawn from Rule 3(zq) of the MDR 2017 as compiled by industry sources, covers death, serious deterioration in health, fetal distress, fetal death and congenital anomalies.
• Class A exemptions under the MDR 2017 do not remove vigilance-related obligations; labelling and quality duties remain fully intact.

2. Legal basis

The legal architecture of Indian device vigilance sits on two layers. The first layer is the binding rule in the Medical Devices Rules, 2017, which imposes the 15-day notification duty on manufacturing licence holders. The second layer is the national reporting infrastructure, the Materiovigilance Programme of India, through which adverse event information is collected and channelled in practice. The table below sets out the key elements side by side, using the wording of the rules where the rules themselves are the source and clearly labelling industry-compiled material where it is not.

Two features of this table deserve emphasis. First, the 15-day duty in Rule 26(ii) is addressed to licence holders in their manufacturing capacity, which is why the rule names the four manufacturing licence forms. Second, the timelines attributed to MvPI guidance are described here as a practical estimate rather than as statutory text, because they come from programme guidance rather than from the body of the rules.

3. Expert insights

Insight one: the 15-day period is short because the starting point is early. The rule is triggered when the event comes to the notice of the licence holder, and it does not wait for the company to complete its causality assessment or close its investigation. In practical terms, the clock starts the moment a sales representative takes a complaint call from a hospital — before anyone at head office has seen the file, before the device has been returned, and before any technical evaluation has begun. This is the single point at which multinational companies most often lose their compliance footing in India, because the people who first learn of an adverse event are rarely the people who own the regulatory deadline.

Insight two: recalls must be reported as part of the same obligation. The wording of Rule 26(ii) refers to the event and the actions taken, including any recall. This means the reporting duty is not exhausted by the initial notification. Every subsequent action the company takes in response to the event, up to and including a decision to recall the device from the market, falls within the scope of what must be communicated to the authority. Companies that treat the first report as the end of the process misread the rule.

Insight three: the vigilance duty survives the Class A exemption. Devices in Class A that are non-sterile and non-measuring benefit from an exemption from Chapters IV, V, VII, VIII and XI of the MDR 2017. That exemption does not extend to vigilance-related obligations; the labelling and quality requirements for those devices also remain fully applicable. A company holding an exempted Class A product therefore cannot argue that its lighter registration pathway carries a lighter post-market pathway, because the vigilance duty stands on its own.

Insight four: the obligation runs to the authority; the channel runs through MvPI. The legal duty in the rules is framed as a notification to the SLA or the CLA. In day-to-day practice, the submission is made through the adverse event reporting form of the Materiovigilance Programme of India. These are two sides of the same arrangement: the MvPI is the channel, and the SLA or CLA notification is the obligation. Describing the MvPI form as an alternative to the statutory duty, or the statutory duty as satisfied informally through internal tracking, are both errors. The two operate together, and a compliant process respects both.

4. Practical recommendations

• Bring sales and marketing personnel into the awareness chain: specify in writing that any adverse event information they receive must be handed to the regulatory lead within 24 hours, and that the regulatory lead, not the salesperson, starts the 15-day calculation from the moment the information first reached the company.
• Prepare a pre-filled template of the MvPI adverse event reporting form, fixing in advance the fields that recur in every submission, namely the device name, the model, the licence number and the batch number, so that a live report never starts from a blank page.
• Build a 15-day backward calendar for every live event, with checkpoints on day 1, day 5 and day 10, so that the remaining time is visible to the whole team rather than held in one person’s memory.
• Treat recall decisions as reportable events within the same 15-day framework, and route them to the same owner who handles the initial SUSAE notification.
• Record, in the same 24-hour handover instruction, that the trigger is awareness rather than confirmation, and repeat this point in training, because most missed deadlines are not failures of knowledge but failures of internal communication.

The pattern behind most delays is consistent: companies rarely fail to report because they do not know how; they fail because nobody knew the clock had already started. Fixing the awareness chain therefore delivers more compliance value than any amount of additional form-filling guidance.

5. Verification checklist

• ☐ The 15-day starting point has been defined internally as the moment of awareness, not confirmation or completion of investigation
• ☐ Sales and marketing personnel are included in the awareness chain with a 24-hour handover requirement to the regulatory lead
• ☐ A pre-filled MvPI reporting form template exists, covering device name, model, licence number and batch number
• ☐ A 15-day backward calendar with checkpoints has been established for live events
• ☐ Recall actions are expressly included within the reporting scope

Regulatory information verified as of 27 October 2026.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across South Asia, including India. Our team prepares dossiers to CDSCO expectations, manages SUGAM submissions and deficiency responses, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com