Uzbekistan Medical Device Variation Management: Reporting Duties and Practice

1. Key takeaways

For the duration of the registration certificate, the applicant carries a continuous reporting obligation: complete information on changes and additions to the registration documents must be submitted to the Center (a licensing requirement established by Article 9 of Resolution No. 213). At the operational level, substantive changes to the manufacturer, design, intended use, labeling and packaging must be declared as variations and must not continue to rely on the original certificate without a declaration. The volume of accumulated changes also directly affects the renewal workload after 5 years — companies with disciplined variation management face a significantly lighter renewal. The reporting obligation is not a one-time event tied to a single filing; it is a standing duty that runs for the entire life of the certificate, and it applies regardless of whether the change originated in design, manufacturing, sourcing or marketing. A new model variant, a moved production line, a revised IFU, a new package configuration and even a software version update all sit inside the scope. The practical consequence is that variation management must be embedded in the company change control system, with a defined assessment step before any change is released, rather than treated as a regulatory afterthought handled when someone remembers to file. What is at stake is not only the validity of the certificate but the continuity of imports, since customs verification and post-market surveillance both read from the same registration documents. In organizational terms, the most effective arrangement gives the regulatory owner of the certificate a defined seat in the change control board, so that every change request reaches a declaration decision before implementation. Companies without that arrangement typically discover undeclared changes during renewal preparation, when the correction cost is highest and the schedule is least flexible.

2. Legal basis

3. Expert insights

Insight 1: the boundary of the variation duty is defined by the scope of the registration documents. Article 9 requires complete information on changes and additions to the registration documents. Whether a given change must therefore be declared depends on whether it alters what the registration documents record — the models, specifications, manufacturing address, intended use, standards list, labeling and instructions for use recorded in Annex 3a all fall within the declaration scope the moment they change. A change that touches none of the registered content needs no variation filing, while anything that does must be assessed before release.

Insight 2: software version updates are the high-frequency zone for variations. Registration decree No. 3888 brings the software version into the device identity information. A firmware update that affects model identification, intended use or safety functions constitutes a variation. Companies should complete a variation assessment before releasing a software update, rather than shipping first and filing afterward. For connected devices with regular release cycles, this assessment step must be built into the release process itself, or the variations will systematically trail the deployed software.

Insight 3: undeclared variations are detected at two checkpoints. First, post-market surveillance sampling uses the consistency between labeling and registration documents as the comparison baseline (Resolution No. 628), so labeling that has changed while the registration documents have not is exposed at sampling. Second, the renewal application requires resubmission of the registration documents, and accumulated undeclared changes surface in a concentrated form at that point, delaying the renewal. There is no third option in which undeclared changes simply remain invisible; both checkpoints are scheduled events.

Insight 4: variations and renewal should be planned together. Because the renewal requires resubmission of the complete registration documents, consolidating accumulated routine changes into the renewal is the most efficient approach. Safety-related changes, however, cannot wait — any change affecting risk control measures should be declared immediately rather than batched with routine changes for the renewal window.

4. Practical recommendations

1. Maintain a variation assessment form: any change to models, specifications, manufacturing address, intended use, standards, labeling or instructions for use is assessed for declaration scope first.
2. Complete the variation assessment before each software version update; do not release first and file afterward.
3. Declare safety-related changes immediately, without batching them with routine changes.
4. Consolidate routine changes quarterly and file them together with the renewal application.
5. Update the instructions for use, labeling and state register information in sync after each variation filing.

5. Verification checklist

• □ Variation assessment form established, covering models, specifications, address, use, standards, labeling and instructions for use
• □ Variation assessment completed before each software version update
• □ Safety-related changes declared immediately, not batched with routine changes
• □ Routine changes consolidated quarterly and filed with the renewal
• □ Instructions for use, labeling and register information updated in sync after variation filings
• □ Variation records archived and retrievable for the renewal application

GRZAN supports manufacturers, importers and authorized representatives with medical device variation management, registration maintenance and market access in Uzbekistan. For assistance with your product portfolio, contact info@grzanglobal.com.

Regulatory information verified as of October 29, 2026.