Risk Management Documentation under ISO 14971 for Belarus Registration

1. Key takeaways

Risk management documentation is not a file that passes review by attaching an ISO 14971 certificate; what reviewers examine is whether the chain of risk identification, evaluation, control, and re-evaluation can be traced end to end. Both Belarus and the Union level treat risk management as a component of the justification of safety and effectiveness, and the burden of proof sits with the manufacturer.

In Belarus and at the Union level alike, the risk management file touches every other document in the dossier: design, testing, clinical evaluation and post-market surveillance all feed into it, and it feeds back into all of them. Treating it as the backbone of the technical file, rather than as one annex among many, is the practical difference between a file that passes review and one that collects queries.

2. Legal basis

3. Expert insights

Insight one: reviewers examine the chain, not the conclusion. A risk management file that merely states that risks are acceptable, without explaining how the risks were identified, which evaluation criteria were applied, which control measures were adopted, and how residual risks were re-evaluated after control, will normally be sent back for completion. Every link of the chain must be locatable within the document, so that a reviewer moving from one section to the next can follow the same risk from its first identification through to its final residual assessment without gaps.

Insight two: the risk management file must correspond to the actual product design. Reviewers cross-check the risk list against the design documents and the verification reports. If the risk list contains failure modes that do not exist in the product design, or omits risks that are obviously present, the file is treated as disconnected from the actual product. This correspondence check is routine, and discrepancies in either direction, whether invented hazards or missing ones, weigh against the credibility of the whole justification.

Insight three: the risk management file and the clinical evaluation cite each other. Risk points raised in the clinical evaluation should have corresponding entries in the risk management file, and risks identified in the risk management file that require clinical data support should be answered in the clinical evaluation. Cross-references between the two files are a common checkpoint during review, and a unified numbering scheme makes the mutual lookup effortless for both sides.

Insight four: the market is not the end point. Risk management is a continuing activity: adverse event information, collected and analyzed by Gosfarmnadzor since 2026-07-30, should flow back into updates of the risk management file. This feedback loop is elaborated in article 41 of this series, and manufacturers should treat it as a standing obligation rather than a one-off registration task.

Insight five: the quality of a risk management file is judged by its internal logic as much as by its content. Reviewers expect the severity and probability scales to be defined before they are used, the acceptability criteria to be stated before the evaluation, and the residual risks to be judged against those same criteria rather than against a general impression of safety. A file in which the criteria appear after the conclusions reads as a retrofitted justification, and the impression it creates is difficult to correct in a single response to queries.

4. Practical recommendations

1. Organize the file in four sections: identification, evaluation, control, re-evaluation. Each section should be locatable in the table of contents, which makes the file easy for reviewers to navigate.
2. Establish a correspondence between the risk list and the design documents. Annotate each risk with the design feature it relates to and the verification report in which its control measure is demonstrated.
3. Cross-reference the clinical evaluation. Unify the risk entry numbering across both files so that each entry is retrievable from the other.
4. Write the post-market feedback rule into the update procedure. State explicitly in the file how post-market data triggers an update of the risk management documentation.

5. Verification checklist

• □ The risk management file is organized in the four-section structure
• □ The risk list has been mapped against the design documents and the verification reports
• □ Risk entries are numbered consistently with the clinical evaluation and cross-referenced
• □ The rule under which post-market data triggers file updates is stated in writing
• □ The file satisfies the document requirements of the annex to No. 55

Regulatory information verified as of October 30, 2026.

In the Eurasian Economic Union market, the core capabilities of GRZAN concentrate on three points. First, distinguishing between the two channels of Union-wide registration and national registration in each member state, including their applicable conditions and remaining time windows. The national registration procedure of Belarus has been fully restructured by Council of Ministers Resolution No. 211 of April 28, 2026 (state register number 6-1/55925, effective May 1, 2026), which compressed the total time limit for preliminary technical work to 90 calendar days, applied a closed list that the implementing organization is prohibited from expanding, while applications under the national procedure face the key deadline of December 31, 2027, so pathway selection must be decided in sync with the time window. Second, local authorized representative services, acting as the legal representative of the manufacturer in Belarus, handling registration submission, responses to technical queries, changes to the registration dossier, and post-market reporting obligations; GRZAN has updated its coordination mechanisms after Council of Ministers Resolution No. 378 of July 27, 2026 (effective July 30, 2026) transferred adverse event functions to the state institution Gosfarmnadzor. Third, quality system and testing support, assisting in establishing a quality management system compliant with ISO 13485 and organizing the technical documentation according to the target pathway: for the national pathway, the annex to Ministry of Health Resolution No. 55; for the Union pathway, Decision No. 46 of the Council of the Eurasian Economic Commission.

Business inquiries: info@grzanglobal.com