Uzbekistan Recognition Pathway: Proving the Identical Configuration Requirement

1. Key takeaways

The core of a recognition-pathway submission is a declaration of identical configuration: confirmation that the device placed on the Uzbekistan market is fully identical to the device covered by the reference approval in model, specification, manufacturing site, and intended purpose. This element is the most frequent source of problems in recognition-pathway applications, because any single deviation from the reference approval, whether a different model number, a different sterilization method, or a different software version, triggers a full review or an outright refusal. What the recognition pathway exempts is the work of generating evidence; it does not exempt the work of proving consistency. Manufacturers should therefore treat the configuration comparison as a formal deliverable with sign-off, not as an assumption carried over from the foreign approval, and should resolve every known deviation before submission rather than explaining it after a deficiency notice arrives.

The comparison work also has a documentation dimension. The foreign approval, the Uzbekistan dossier, the labeling, and the certificates that support the submission must all describe the same device in the same terms, and the coding entries under registered order No. 3888 give reviewers a quick technical check of that alignment. A manufacturer who reconciles these documents before submission turns the recognition application into a confirmation exercise; a manufacturer who discovers the differences after submission turns it into a deficiency negotiation, with the review clock suspended while the explanation travels back and forth. In both cases the underlying device is the same, but the project outcomes differ sharply, which is why the comparison table should be treated as a controlled deliverable with named owners and dates.

2. Legal basis

3. Expert insights

Insight one: identical configuration means four-dimensional consistency, not the same product name. Model, specification, manufacturing site, and intended purpose are all required, and none can be missing. When GRZAN reviews a recognition-pathway application, the reference approval documents and the Uzbekistan submission are compared cell by cell in a structured table, rather than checking whether the product names match.

Insight two: software versions and sterilization methods are the two most commonly overlooked variables. Once the firmware version of an active device is updated, its configuration already differs from the configuration covered by the reference approval; likewise, changing the sterilization method or the sterilization supplier of a sterile device constitutes a configuration change. Inside companies these are often treated as minor changes that do not affect the main model, but in the comparison logic of the recognition pathway they are substantive differences.

Insight three: the unique coding requirements provide a practical tool for the consistency comparison. Registered order No. 3888 requires each device to be declared with a unique GMDN code and a unique UDI code. These two codes can serve as technical anchors when comparing the reference approval with the submitted configuration: if the codes differ, additional written explanation of the configuration consistency will be needed.

Insight four: Uzbekistan-specific requirements can override consistency. Even with an identical configuration, the center may still refuse if the labeling, intended purpose, or manufacturing circumstances differ from the reference dossier, or if local requirements on language, electrical standards, and sterile claims are not met. Consistency is therefore a necessary condition, not a sufficient one, and localization compliance remains a separate gate that must be cleared on its own.

4. Practical recommendations

1. Build a four-column comparison table of the reference approval versus the Uzbekistan submission (model, specification, manufacturing site, intended purpose) and obtain sign-off for each cell.
2. Include software versions and sterilization methods in the comparison table and manage them alongside the model number.
3. Use the GMDN and UDI codes as auxiliary tools for the consistency comparison, and prepare a written explanation whenever the codes differ.
4. Before submitting a recognition-pathway application, complete the localization check covering language, electrical standards, and sterile claims.
5. Provide verified copies of the reference approval documents and retain records of verification through public channels.

5. Verification checklist

• □ The four-column comparison table (model, specification, manufacturing site, intended purpose) is complete and confirmed cell by cell
• □ Software versions and sterilization methods are included in the comparison table
• □ The unique GMDN code and the unique UDI code have been declared
• □ Labeling, instructions for use, and packaging have passed the localization check (language, electrical standards, sterile claims)
• □ The reference approval documents are verified copies, with verification records retained
• □ It is confirmed that consistency is a necessary condition and not a sufficient one

GRZAN provides registration support in Uzbekistan for manufacturers, importers, and authorized representatives, including configuration comparison against reference approvals. For assistance, contact info@grzanglobal.com.

Regulatory information verified as of October 29, 2026.