Georgia Medical Device Vigilance Reporting: No Statutory Deadlines and the Practical Estimate Approach

1. Key takeaways

Georgia currently has no codified medical device vigilance reporting deadlines comparable to the European Union MDR timelines for serious incidents, which set a 2-day window for serious public health threats and a 10-day window for other serious incidents. The operational levers that exist today are the documentary production and explanation obligations that the authority can enforce under Government Resolution No. 278 of August 1, 2023, together with the general product safety obligations of the Code of Georgia on Product Safety and Free Movement, Law No. 6157-Iს of May 8, 2012. The timeline figures circulating in industry practice, including the 2-day and 10-day references borrowed from EU practice, belong to the category of practical estimates and not to binding Georgian law. Companies therefore carry the burden of defining their own internal response clocks and documenting that those clocks were observed, because in the absence of statutory deadlines the decisive question in any post-incident review will be whether the company acted with reasonable care.

2. Legal basis

1. Government Resolution No. 278 of August 1, 2023 of Georgia: procedures, rules and conditions of control in the field of medical and pharmaceutical activities, under which the inspected party may be required to provide documents, copies and explanations.
2. Code of Georgia on Product Safety and Free Movement, Law No. 6157-Iს, May 8, 2012: Article 1, subparagraph a (protection of human life and health), Article 2, paragraph 2 (product safety assurance as part of the regulatory mechanism), Article 2, paragraph 1, subparagraph g (advancement of the market surveillance system) and Article 3¹ (national market surveillance strategy, added by Law No. 1447 of April 1, 2026, effective June 1, 2026).
3. Law of Georgia on Drugs and Pharmaceutical Activity, Law No. 1586 (August 10, 2009), Article 11¹⁰, paragraph 6 (cancellation and removal from the register) and Article 11¹¹ (suspension and cancellation of registration).
4. Government Resolution No. 386 of October 3, 2023 of Georgia, Article 4: clinical trials require submission of documents confirming that trial risks and liability are covered.
5. Practical estimate statement: deadlines such as 2 days for serious incidents and 10 days for other incidents do not appear in any verified Georgian statutory text; they reflect industry practice modeled on EU timelines and must not be cited as statutory deadlines.

3. Expert insights

Insight one: the absence of a statutory deadline does not mean the absence of an obligation; it widens the space for discretionary assessment. Article 1, subparagraph a of the Code names the protection of human life and health as a primary purpose, and Article 2, paragraph 2 lists product safety assurance among the principal regulatory mechanisms. Where no specific deadline exists, the authority can rely on these general obligations to require a company to explain its handling of an incident, and the company’s defense rests on whether it exercised reasonable care. Under such a standard, the completeness of records matters more than hitting a date. A documented, methodical assessment completed on day 12 is defensible; an undocumented same-day reaction is not.

Insight two: the vigilance system should be built to the strictest applicable standard. Georgia is formally aligning with MDR and IVDR under the government DCFTA implementation framework, target 3.1.2 of the second-quarter 2025 report. A vigilance system designed to EU timelines today will not need structural rework when Georgian legislation lands; a loose system built on the assumption that no deadline exists will have to be dismantled and rebuilt. The cost asymmetry runs entirely in favor of early alignment, particularly for groups that already operate EU vigilance procedures for other markets and can extend them to Georgia with minimal marginal effort.

Insight three: the risk coverage requirement of Resolution No. 386 offers a localized liability paradigm. That resolution requires clinical trial sponsors to submit documents confirming that trial risks and liability are covered. The same logic transfers naturally to the post-market phase: arranging liability coverage, through insurance or an equivalent instrument, for products already on sale converts the abstract vigilance obligation into a concrete, auditable action and gives inspectors and courts a tangible marker of the company’s seriousness.

Insight four: the verification posture of this topic shapes how vigilance commitments should be worded externally. Because the 2-day and 10-day figures cannot yet be matched to any article of Georgian law, tender documents, quality agreements and distributor contracts should describe them as internal company standards rather than as statutory deadlines. This wording preserves credibility with regulators and customers alike: the company commits to a measurable clock, while the documents avoid asserting a legal obligation that the Georgian framework does not yet contain. When the device statute or the MDR alignment regulations are adopted and codify deadlines, the same documents can be updated by a single controlled revision, replacing the internal standard with the statutory one.

The enforcement machinery behind the general obligation should also be understood concretely. Resolution No. 278 allows the authority, in the course of an unannounced inspection, to demand documents, copies and explanations relating to any incident on the market. This means a vigilance case file may be examined years after closure, and the file must be able to stand on its own: what was received, when it was assessed, what decision was made, what action followed, and how the case was closed. Companies serving multiple markets in the Caucasus region commonly reuse a single European vigilance procedure for Georgia, which is acceptable provided the procedure explicitly covers Georgian distribution and names the local responsible entity as a reporting node.

4. Practical recommendations

1. Establish a vigilance SOP with internal deadlines set at 2 days for serious incidents and 10 days for other incidents as a self-imposed practical estimate, and record every step taken against those clocks.
2. Open a separate case file with a unique number for every adverse event, recording four timestamps: receipt, assessment, reporting and closure.
3. Arrange liability coverage for products on sale and retain the certificates, following the approach of Resolution No. 386.
4. Run a quarterly vigilance drill that verifies, under the documentary production obligations of Resolution No. 278, that every record relevant to an incident can be retrieved on demand.
5. Review the SOP wording annually so that internal deadlines remain clearly labeled as practical estimates and are never presented to regulators as statutory requirements.

5. Verification checklist

• □ Vigilance SOP established with internal deadlines labeled as self-imposed
• □ Adverse events opened as separate cases with four timestamps recorded
• □ Liability coverage certificates retained
• □ Quarterly vigilance drills scheduled
• □ Internal deadline figures marked as practical estimates
• □ DCFTA target 3.1.2 alignment status tracked

Regulatory information verified as of October 30, 2026

This English edition is provided by GRZAN, the international regulatory translation service of the GRZAN global compliance desk. GRZAN translates medical device regulatory guidance for manufacturers, importers and authorized representatives preparing documentation for Eurasian, Caucasian and EU-aligned markets. For translation, regulatory monitoring or compliance support inquiries, contact info@grzanglobal.com.