Medical Device Tecnovigilance in Argentina: Disposición ANMAT 8194/2023

1. Key takeaways

Argentina’s medical device tecnovigilancia (technovigilance) obligations are governed by Disposición ANMAT 8194/2023, published on October 3, 2023 and effective on October 4, 2023, aligning Argentina with IMDRF N43 and ISO/TR 20416. The regulation applies to all registration holders, without distinguishing between hardware and software. In practical terms, every marketed device, including software as a medical device, carries the same incident-reporting duties, the same field safety obligations, and the same exposure to enforcement when those duties are missed.

The regulation sets two reporting thresholds:

• Events constituting a serious threat to public health: reportable within 48 hours;
• Events resulting in patient/user death or serious deterioration in health: reportable within 10 calendar days of becoming aware of the event.

Beyond these two thresholds, Field Safety Corrective Actions (FSCA) must be notified to ANMAT within 10 calendar days of implementation, and Field Safety Notices (FSN) must be issued to users without delay. Trend reporting applies as well: where the frequency or severity of non-serious events shows a statistically significant increase, those events must likewise be reported. Companies were given 120 calendar days to adapt their quality management systems to the new framework, and for anyone entering the Argentine market today, that adaptation must already be in place.

2. Legal basis

3. Expert insights

Insight 1: The 48-hour and 10-day clocks start differently, and this is the single most common point of confusion. The 48-hour threshold applies to events constituting a serious threat to public health, and the clock starts when the company becomes aware of that threat. The 10-calendar-day threshold applies to events resulting in death or serious deterioration in health, and the clock starts from awareness of the event. The correct assessment sequence matters as much as the deadlines themselves: first determine whether the event constitutes a serious threat to public health; if it does, the 48-hour track applies. If it does not, determine whether the event resulted in death or serious deterioration; if it did, the 10-day track applies. A reporting SOP that does not encode this two-step sequence invites misclassification, and misclassification in Argentina is not a paperwork issue but a compliance breach with enforceable consequences under Ley 16.463.

Insight 2: The 120-calendar-day adaptation window was a one-time opportunity. The transitional provision gave companies 120 calendar days to adjust their quality management systems to conform with the new rules. For any company entering the Argentine market after 2023, that window closed long ago. The practical consequence is straightforward: the quality system must already satisfy 8194/2023 at the moment of submission. There is no grace period available, no soft-landing mechanism, and no argument that the company is still in transition. Auditors and inspectors treat the adapted system as a precondition of market access, so a submission without a conforming vigilance system is a submission built on sand.

Insight 3: The vigilance obligation makes no hardware-software distinction, so SaMD is fully covered. For software products, a scenario such as an algorithm showing degraded performance in a particular patient population is precisely the kind of event that someone in the organization must be responsible for detecting and reporting. This provision places the post-market obligations of digital health products on exactly the same footing as physical devices. Manufacturers of software cannot rely on the argument that no physical incident occurred; a statistical shift in model behavior is an event in its own right, and it must flow into the same assessment pipeline, the same threshold decision, and the same ARGOS submission path as any hardware failure.

4. Practical recommendations

1. Build a decision flowchart for the two thresholds. Turn the questions of whether the event constitutes a serious threat to public health, and whether it results in death or serious deterioration, into a decision tree attached to the front page of the vigilance SOP. Every assessor should reach the same deadline decision from the same facts.
2. Name three responsible individuals. Decide who collects event information, who makes the threshold determination, and who submits in ARGOS. Fix the three names before launch and write them into job descriptions, so that responsibility never becomes ambiguous during an incident.
3. Turn the 48-hour deadline into an executable internal limit. Once time-zone differences and translation time are subtracted, the time genuinely available for internal assessment is far shorter than 48 hours. Set a tighter internal SLA so that the statutory deadline is never consumed by logistics.
4. Treat quality system adaptation as a pre-market checkpoint. If the quality system has not yet been adjusted to 8194/2023, complete that work before the first submission rather than relying on any transition period, and document the adaptation so it can be shown during inspection.

5. Verification checklist

• □ A decision flowchart for the 48-hour and 10-calendar-day thresholds has been established
• □ Three responsible individuals for collection, determination, and submission have been designated
• □ Internal SLAs have been set after deducting time-zone and translation time
• □ The 10-calendar-day FSCA notification process has been established
• □ The channels for issuing FSN to users have been confirmed
• □ The quality management system has been adapted to 8194/2023
• □ A reporting pathway for algorithm performance degradation has been defined for software products

Regulatory information verified as of October 29, 2026.

In Argentina, GRZAN operates a wholly owned subsidiary that can act as the registration holder and importer for foreign manufacturers, directly handling classification assessment, pathway selection, GMP and CFS documentation chains, Spanish-language technical documentation and label localization, HELENA submissions and deficiency responses, as well as BONITA import notifications, ARGOS vigilance system operation, change maintenance, and 5-year renewal planning.

The GRZAN regulatory team consists of professionals with many years of hands-on international registration experience, tracking the developments of regulators worldwide. All external content follows the drafting standard of conclusions first, traceable basis, and verifiable numbers. For a market access plan tailored to your specific product for Argentina or the MERCOSUR region, contact the GRZAN regulatory team at info@grzanglobal.com.