Recalls and Corrective Actions for Medical Devices in Russia

1. Key takeaways

Recalls and corrective actions in Russia rest on two paths. The first is corrective action and recall initiated by the manufacturer on its own motion. The second is action by decision of RZN — under p. 14 of Order No. 540n, where an event results in death, serious harm to health, permanent disability, or constitutes a threat of any of these, RZN may decide on control measures and suspend the use of the device even before receiving the manufacturer’s information. The outcomes of handling are graded into three levels of severity: strict / medium / minor, and the grade determines the scope of the field action.

The dual-path design means a manufacturer must be ready for two very different dynamics. A voluntary path is driven by the company’s own investigation and its own communication plan, with room to sequence actions. A regulator-driven path can begin with a suspension that the company learns about as a fait accompli, which puts a premium on the speed and credibility of the information the manufacturer submits afterwards. Preparedness for the second path is largely a by-product of preparedness for the first: the same investigation material, notification lists and logistics arrangements serve both.

2. Legal basis

The recall and corrective action framework is assembled from the safety monitoring order, which defines the handling levels and immediate measures, the registration rules, which define the consequences for the certificate, and the reporting order, which defines the starting point of the chain.

3. Expert insights

Insight 1: the coverage of the three severity levels is progressive. The strict level (suspension of the use of the entire device) applies where the report involves two or more models. The medium level covers supervisory measures that do not suspend use but may result in withdrawal from circulation. The minor level applies where no association has been confirmed beyond what is stated in the instructions for use, and the conclusion is published. Understanding this mapping helps a company predict the scope of on-site action from the wording of a report, and target its own investigation at the facts that decide the grade: how many models, how many batches, and whether the association goes beyond the IFU.

Insight 2: suspension of use is reversible, not final. The measures under p. 14 can be adjusted once the manufacturer’s information arrives. What the company must do is provide credible root cause evidence as quickly as possible, so that the suspension converts into conditional use rather than extending into broader measures. Speed here is evidence production, not persuasion: batch documentation, complaint history and design analysis prepared in advance are what make a rapid, credible submission possible at all.

Insight 3: recall execution runs through the channel, not through announcements. Russia lacks a unified product recall announcement platform that would substitute for channel notification, so the notification lists of distributors and healthcare organisations must be kept permanently current — and this is also an item that is invariably checked during inspections. A recall that is legally initiated but physically undeliverable, because contact data in the channel lists are stale, fails in the field while succeeding on paper.

4. Practical recommendations

Recall capability is built between events, not during them, and the recommendations below reflect that premise. A plan that exists only as a heading fails at the first practical question — who calls which customer, in which language, with what script, and within how many hours — so each item below should be tested against those questions before it is considered complete.

1. Build a three-level response plan in which the notification scope, recovery logistics and customer communication wording for each severity level are written in advance, not composed during the event.
2. Sign recall cooperation clauses with key customers, stating the contact persons, response time limits and the duty to verify stock levels, so that execution does not depend on goodwill.
3. After every recall, including voluntary corrections, conduct an effectiveness check and retain the records, since documented effectiveness is both a quality requirement and an inspection asset.
4. Refresh the channel and customer notification lists on a fixed cycle, and reconcile contact data with actual shipment records so that the lists match the devices really in the field.
5. Agree in advance with logistics providers on the collection, return or destruction routes for recalled stock, so that the physical flow starts on the day the decision is made rather than weeks later.

5. Verification checklist

The items below evidence a recall capability that would survive both an inspection and a real event.

• □ The three-level response plan has been written and rehearsed
• □ The channel and customer notification lists are at their latest version
• □ Recall cooperation clauses are written into distribution agreements
• □ Recovery logistics and the disposal / rework options have been determined
• □ Recall effectiveness verification records have been archived
• □ The evidence package supporting rapid root cause submissions under p. 14 is assembled in advance

Regulatory information verified as of 29 October 2026.

GRZAN supports manufacturers and distributors in Russia with recalls and corrective actions across the full cycle — three-level response planning, channel notification, recovery logistics, effectiveness verification and regulator-facing submissions under Order No. 540n — together with vigilance and inspection readiness services. For recall readiness support, contact us at info@grzanglobal.com.