Kyrgyzstan Medical Device Risk Management and Benefit-Risk Assessment: Requirements and Best Practices

1. Key takeaways

Under Kyrgyz law, national registration requires a positive expert assessment of the safety, quality and effectiveness of the device, taking into account the class of its potential risks in use. One of the core elements of that assessment is the benefit-risk ratio: whether the clinical benefit delivered by the device outweighs its residual risks. This means the risk management file is not an annex to the dossier but the main thread connecting the technical evidence to the expert conclusion. What matters is not how thick the risk management file is, but whether it can actually support the benefit-risk judgment that the expert reviewer is required to make. A disciplined, argument-driven risk file is therefore one of the highest-leverage documents in the entire submission.

2. Legal basis

1. Law No. 216, Article 14: products of foreign manufacture must obtain a positive expert assessment of safety, quality and effectiveness, taking into account the class of the device’s potential risks in use.
2. Resolution No. 513 of the Cabinet of Ministers, dated August 27, 2024, paragraph 2 of Article 2: safety and effectiveness requirements follow Decision No. 27 of the Council of the Eurasian Economic Commission dated February 12, 2016 (with item 63 excluded).
3. Resolution No. 513, paragraph 1 of Article 2: classification follows Board Decision No. 173 of the Eurasian Economic Commission dated December 22, 2015.
4. Annex 1 to Resolution No. 513, Article 2: defines verification and validation.
5. Explanatory note to the 2026 draft amendments of the competent authority: the reason for retaining the current overall registration timeline is the need for expert assessment of safety, quality and effectiveness.

3. Expert insights

Insight 1: The wording of Article 14 ties the depth of the assessment directly to the risk class.

The statute requires a positive expert assessment taking into account the class of the device’s potential risks in use. The implication of this wording is that the depth of the assessment is modulated by the risk class rather than applied uniformly. For a Class 1 product, the benefit-risk judgment can rest on general technical evidence; a Class 3 product requires full clinical evidence. Companies should determine the class first and the evidence depth second (see articles 04 and 19 of this series). Sequencing the program this way prevents the twin failures of over-investing in low-risk products and under-documenting high-risk ones.

Insight 2: The role of the risk management file is to organize conformity evidence into a decidable conclusion.

The conformity evidence table (article 24 of this series) answers whether each individual requirement is met; the risk management file answers whether the residual risks are acceptable and whether the benefit exceeds the risk. The former is checklist-style; the latter is argumentative. What the expert reviewer ultimately needs is the latter: a document that organizes dispersed evidence into a judgment. Preparing the two documents so that they interlock, with the risk file citing the evidence table and the evidence table flagging the risk controls it supports, produces a file that reads as one coherent argument rather than two parallel piles of paper.

Insight 3: The benefit-risk evaluation should be dynamic, not one-time.

Article 15 of Law No. 216 lists the emergence of new systematic data indicating that risks outweigh benefits as a ground for revocation of the registration certificate. This provision binds the continued validity of the certificate to the current state of the benefit-risk balance, which means the benefit-risk evaluation is not a single exercise performed at certification but a judgment that is continuously updated as evidence accumulates (see article 43 of this series). Post-market surveillance, complaint trends and vigilance reports all feed this judgment, and the file should be structured to absorb them.

Insight 4: Verification and validation correspond to two kinds of risk-control evidence.

Article 2 of Annex 1 to Resolution No. 513 defines verification as confirming that specified requirements have been fulfilled, and validation as confirming that requirements for a specific intended use or application have been met. Within the risk management framework these map onto two families of risk-control measures: conformity of design outputs (verification) and effectiveness in the context of use (validation). The risk management file should provide separate indexes to both families of evidence, so the reviewer can trace each control measure to the proof that it works as designed and works in the field.

Insight 5: The risk management file is a high-frequency retrieval target during inspections.

Article 16 of this series recommends maintaining an inspection-ready package, and the risk management file belongs in it. Inspections can occur at the registration stage or be launched independently at the distribution stage under Cabinet Resolution No. 450. The risk management file will be retrieved in both scenarios, so it should be maintained as a standing, current document rather than drafted once for registration and never touched again. An outdated risk file found during a distribution inspection is a self-inflicted finding.

4. Practical recommendations

First, write the risk management file as an argument, not a checklist. We recommend the structure: intended use and patient population; identified risks and control measures; residual risk evaluation; benefit evidence; benefit-risk conclusion. The conclusion section must state a clear judgment, not stop at the single sentence that the risks are acceptable.

Second, set evidence depth standards per risk class. We recommend an internal standard: Class 1 relies mainly on general technical evidence; Class 2a adds biological effect evaluation and sterilization validation; Class 2b adds technical testing and clinical evaluation; Class 3 requires complete clinical evidence together with cooperation in a manufacturing inspection.

Third, cross-index the risk management file and the conformity evidence table. Each control measure in the risk file should point to a specific item in the evidence table, and each item of evidence should state the risk control it supports. The cross-references let reviewers move between argument and proof without friction.

Fourth, establish an annual review mechanism. Reassess the benefit-risk conclusion once a year against post-market surveillance data, complaint data and vigilance reports, and retain the review records. This satisfies compliance expectations and doubles as inspection preparation.

5. Verification checklist

• □ Risk management file uses an argumentative structure: intended use; risks and controls; residual risk; benefit evidence; benefit-risk conclusion;
• □ Evidence depth standards defined per risk class (1 / 2a / 2b / 3);
• □ Risk management file and conformity evidence table are cross-indexed;
• □ The benefit-risk conclusion states an explicit judgment, not merely that risks are acceptable;
• □ An annual review mechanism exists, updating the conclusion with post-market surveillance, complaint and vigilance data;
• □ The risk management file is included in the inspection-ready package and kept current.

Regulatory information verified as of October 29, 2026.

Our services cover: pre-market pathway selection and feasibility assessment, registration dossier preparation and submission, authorized representative arrangements, local testing and clinical trial organization, manufacturing site inspection coordination, quality management system compliance support, post-market surveillance and device vigilance system setup, import and distribution compliance, and fee calculation and project budget management.

The GRZAN regulatory team consists of professionals with many years of hands-on experience in Eurasian Economic Union registration. We maintain a stable local cooperation network in Bishkek, Almaty, Tashkent and Moscow, work in Chinese, Russian and English, and provide executable solutions for foreign manufacturers on the issues most commonly encountered in CIS markets: authorized representative arrangements, notarization and legalization chains for powers of attorney, technical documentation localization, and inspection readiness. GRZAN supports manufacturers, importers and authorized representatives throughout the Kyrgyzstan registration lifecycle.

We adhere to one principle: every regulatory conclusion we publish must rest on verifiable official sources. Any figure or timeframe that cannot be verified is labeled as a practical estimate and is never presented as a legal requirement.

For project consultation on market access in Kyrgyzstan or the Eurasian Economic Union, please contact us at info@grzanglobal.com.

GRZAN | Global Medical Device Regulatory Registration and Compliance Services