72-Hour Serious Adverse Event Reporting in Panama: Deadlines and Periodic Reports

1. Key takeaways

Panama sets the reporting clock for serious adverse events at 72 hours. Article 56 of DE 490 requires that a serious adverse event, or a serious adverse incident, involving a device for human use be reported using the format and mechanism established by DNDM, marked as urgent (urgente), and completed within 72 hours of the occurrence. The same decree contains a second 72-hour clock: under Article 52.4.j, the technical unit of a health institution that receives a serious event report must forward it to the Device Vigilance Department in less than 72 hours (menos de 72 horas). Periodic reporting runs on a separate track. Article 57 provides that all event and incident reports, together with the preventive measures taken, are submitted by the technical units in consolidated form at a periodicity determined by DNDM, which is to develop a digital platform and set the reporting cycle itself.

2. Legal basis

The reporting framework combines a hard deadline for serious cases, a periodic channel whose rhythm is left to the regulator, and an obligation that extends well beyond the manufacturer. The table below sets out the provisions in the order in which a case would actually travel: the trigger definitions, the immediate reporting duty, the format, the intermediate role of the hospital technical unit, the internal escalation inside DNDM, and the sanction that attaches to silence.

3. Expert insights

Insight 1: the clock starts at occurrence, not at knowledge. The wording of Article 56 is within seventy-two hours following the occurrence of the event or incident. For a manufacturer headquartered in Asia this is the harshest point in the whole framework, because transit time along the cross-border chain is absorbed into the deadline and the company cannot argue that it only became aware when the hospital wrote to it. The only workable response is to reverse-engineer the 72 hours into a fixed procedure whose zero point is the event itself.

Insight 2: the two 72-hour clocks run in parallel, not in sequence. Article 52.4.j imposes a forwarding duty of less than 72 hours on the hospital technical unit, while Article 56 imposes a 72-hour duty on manufacturers and suppliers measured from occurrence. A slow hospital does not extend the company window. In practice this means a direct channel to the technical unit is not a courtesy but the only way to avoid spending the window without knowing it has started.

Insight 3: the periodic cycle is pending, so no fixed rhythm can be assumed. Article 57 leaves the periodicity to DNDM and names the technical unit, not the company, as the submitting party. A company therefore cannot set its own quarterly schedule, and cannot design periodic reporting as a standalone filing to DNDM. The correct design is to place the company inside the data flow that the hospital technical unit consolidates.

Insight 4: the channel is electronic, and false reports carry consequences. Article 55 requires a reporting application on the DNDM website open to any citizen, and expressly provides for the monitoring, identification and sanctioning of false reports (falsos reportes). Together with the confidentiality rule in Article 53 this is a two-sided design: it lowers the threshold for reporting while retaining a means to counter abuse.

4. Practical recommendations

• Write the 72 hours as an event-zero procedure. State that time runs from occurrence, not internal knowledge; grade the case against the four Article 49 categories in the first hour, draft the Spanish report within 24 hours, obtain internal approval within 48 hours and keep 24 hours as buffer.
• Sign a direct-channel agreement with hospital technical units. Given the forwarding duty in Article 52.4.j, a simultaneous notification channel turns the hospital action into the signal that starts the company clock.
• Use the current DNDM format and do not invent a template. Article 55 requires the forms and procedures set by DNDM and the national vigilance department; check the version published on the DNDM website before filing.
• Design periodic reporting as entry into the technical unit data flow. Confirm the consolidation basis with the technical unit rather than filing on a self-selected cycle.
• Treat late notification as a minor offence. Article 35.2 of Ley 90 places failure to notify in time alongside deliberate concealment, with fines starting at B/.500.00 under Article 44.1.

5. Verification checklist

• □ Procedure states that time runs from occurrence under Article 56, not from internal knowledge
• □ Report template follows the current DNDM format and is marked urgente
• □ Classification against the Article 49 definitions of serious event and serious incident documented
• □ Simultaneous notification channel agreed with key hospital technical units under Article 52.4.j
• □ Periodic reporting basis aligned with the technical unit, with periodicity as set by DNDM under Article 57
• □ Submission route confirmed as the DNDM electronic reporting system under Article 55
• □ Minor offence risk under Article 35.2 of Ley 90 flagged to management

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for the Panamanian market. Our team manages Ministry of Health (MINSA) sanitary registration applications, prepares Spanish-language dossiers, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com