Peru Adverse Incident Reporting: 24-Hour and 20-Calendar-Day Deadlines Explained

Regulatory information verified as of October 29, 2026

1. Key takeaways

Peru applies severity-tiered deadlines to suspected adverse incidents involving medical devices: serious incidents must be reported to the competent authority within 24 hours of becoming aware of them, while moderate and mild incidents must be reported within 20 calendar days. Both deadlines derive from R.M. N° 539-2016/MINSA (published on 2016-07-27), the sanitary standard governing pharmacovigilance and tecnovigilance activities. The required sequence of judgment is to classify first and start the clock second, not to investigate fully first and then decide whether to report — the latter is the most common form of non-compliance committed by offshore manufacturers in Peru, because it converts a reporting deadline into an investigation project and exhausts the window before any submission is made. Regulatory information verified as of October 29, 2026.

2. Legal basis

3. Expert insights

Insight 1 | The clock starts on awareness, not on confirmed causality

R.M. N° 539-2016/MINSA uses the term sospecha (suspected), which means the trigger point falls at the moment reasonable suspicion is established. Mechanically, what the competent authority needs is not a root-cause report that has already reached a clean conclusion, but an early timestamp showing entry into the vigilance channel. Our SOPs instruct clients to treat the moment the distributor receives the complaint call as the start of the clock, rather than waiting for the quality department to issue its investigation conclusion — placing investigación before reporte compresses the 24-hour deadline into a negative number.

Insight 2 | The three-tier classification keys on consequences, not on product value

The anchors for classifying an event as serious, moderate or mild are the health consequences and urgency for the patient, user or third party: cases involving death, a life-threatening situation, or intervention required to avoid permanent impairment are serious; those causing reversible harm or requiring medical intervention to resolve are moderate; and the remainder, without substantive impact on health outcomes, are mild. Adjusting the classification according to unit price or customer importance is the practice most easily pierced in an audit. We recommend turning the classification table into a single-selection form and forbidding free-text entry of the severity level.

Insight 3 | The difference in units between the two deadlines creates a cross-month trap

The 24-hour deadline runs continuously by the hour and does not stop over weekends or holidays; the 20 calendar days are counted in calendar days, which likewise include non-working days (in contrast to review clocks computed in working days under the Texto Único de Procedimientos Administrativos, TUPA). What the two have in common is that neither is extended by internal approval flows. A complaint received on the last working day before a long holiday therefore requires a holiday-duty escalation mechanism; scheduling the public-holiday calendar in advance is a routine step in our Peru projects.

4. Practical recommendations

1. Build a 24-hour emergency channel defining who is authorized to submit the initial report on behalf of the registration holder (PRH) before the investigation is complete, with the in-depth analysis to follow as a supplement.
2. Write the awareness-starts-the-clock rule into the agreements with Droguería, Laboratorio and hospital counterparties, requiring immediate relay of any report received, without prior independent judgment.
3. Produce a classification matrix form: the consequence type is checked first, and the form derives the severity level and the applicable reporting deadline automatically; manual entry of the level is prohibited.
4. Mark public holidays and long weekends in the calendar, and arrange a substitute vigilance responsible person and contact routes in advance.
5. Retain original timestamp evidence for all deadline determinations (email receipt time, call records, ticket creation time in the system), so that the starting point of the clock can be reconstructed if challenged.
6. When responding to supplementary inquiries from the National Authority of Pharmaceutical Products, Medical Devices and Products for Health (Autoridad Nacional de Productos Farmacéuticos, Dispositivos Médicos y Productos Sanitarios, ANM) — that is, DIGEMID — draw on the same ledger to avoid conflicting versions.

5. Verification checklist

□ The severity of the incident — serious, moderate or mild — has been confirmed and cross-reviewed by at least two persons (regulatory information verified as of October 29, 2026).

□ The moment of awareness has been fixed, and the original timestamps of emails, calls or system tickets have been retained.

□ The initial report for the serious incident was submitted within 24 hours; any overrun is documented with a written explanation and corrective records.

□ The moderate or mild incident was reported within 20 calendar days and scheduled for ledger follow-up.

□ The computation units have been confirmed: 24 hours counted continuously by the hour and 20 calendar days counted in calendar days, neither extended by internal approvals or holidays.

□ The report content includes the product name, registration number, batch or serial number, event description, consequence assessment and user facility.

□ The submission follows the format requirements of R.D. N° 101-2019-DIGEMID-DG-MINSA, with format details subject to the official publication of DIGEMID.

Regulatory information verified as of October 29, 2026.

GRZAN provides medical device registration and post-market compliance support in Peru for manufacturers, importers and authorized representatives. For assistance, contact info@grzanglobal.com.