Adverse Event Reporting in Russia under Order No. 541n

1. Key takeaways

The Order No. 541n of the Ministry of Health, dated 26 May 2026 (in force from 1 September 2026 until 1 September 2032) replaces Order No. 1113n (dated 19 October 2020) and establishes a unified adverse event reporting procedure. Two core changes define the new regime. First, the submission channel is consolidated into the single entry point of the RZN automated information system, excluding alternative routes such as postal mail and email. Second, the content of the report is fixed by law: the list of mandatory data elements is set out in the order and its annex, so a submission is incomplete if any statutory field is missing. Reports must be submitted within 20 working days of the date of discovery.

The practical consequence of the single-channel rule is often underestimated. Submissions sent by email to a familiar contact, or by post to a regional office, no longer satisfy the procedure; what matters is a validated account in the RZN automated information system, with the access rights and workflow to produce a compliant report inside the twenty working day window. Organisations that only discover an account or permissions problem after an event has occurred will burn days of the deadline on administrative setup rather than on the report itself.

2. Legal basis

The reporting procedure sits between the safety monitoring framework of Order No. 540n, which governs what happens after a report, and the registration rules that govern the certificate itself. The instruments and provisions are summarised below.

3. Expert insights

Insight 1: the circle of reporting subjects extends to whoever discovers the event. The duty no longer falls only on the manufacturer; whoever discovers an event reports it — the authorised representative, suppliers, sellers, healthcare organisations and service organisations may all become the starting point of a report. This has two consequences. The regulator gains earlier visibility of events that previously died inside a distribution chain, and channel organisations themselves need the capability to identify and escalate an event. Manufacturers should assume that a first report may reach RZN without their involvement, and design their own monitoring so that they are never the last to know.

Insight 2: the coverage spans the full life cycle. From the stage of technical tests and toxicological studies, through production, storage, transport, installation and commissioning, use including maintenance, repair, and up to disposal, adverse events discovered at any stage fall within the reporting scope. Even events discovered at the research and development stage are covered — an arrangement that is uncommon internationally. Development teams therefore need a defined route for escalating observations that would previously have stayed in engineering notebooks, and the route must be established before 1 September 2026, not improvised after the first event.

Insight 3: the content list is almost an investigation form. The report must state the device and manufacturer information, the registration certificate information, the model (version, batch, serial number), the potential risk level, the quantity in circulation, the place and course of the event, the users and the persons harmed, a description of the event and its consequences, and the measures already taken together with the current status. Where new information appears, a supplementary report must be filed. In other words, the statutory template forces the reporter to document not only the event but also the state of the response, which makes disciplined internal record-keeping a precondition for compliant reporting.

4. Practical recommendations

The following measures convert the statutory requirements into an operating routine that survives the pressure of a real event.

1. Open the information loop on the channel side: write the escalation paths of distributors, service outlets and healthcare organisations into agreements, so that contract obligations back up the reporting duty.
2. Build the reporting template around the statutory fields set out in the annex to Order No. 541n, so that each report is assembled from pre-defined fields instead of being improvised under deadline pressure.
3. Define trigger rules for supplementary reports: once new information appears, file immediately rather than waiting for a periodic summary, because the duty to supplement attaches to the appearance of new information, not to a reporting calendar.
4. Register and test the RZN automated information system account and submission permissions in advance, and keep the credentials under a named owner.
5. Assign ownership of the 20 working day deadline to a specific person, with a reminder mechanism set at the moment of discovery rather than at the end of the window.

5. Verification checklist

Treat the checklist as the minimum evidence of readiness for the reporting regime that applies from 1 September 2026.

• □ The account and submission permissions for the RZN automated information system are opened and tested
• □ The report template contains every field required by the annex to Order No. 541n
• □ Escalation paths on the channel side are written into agreements
• □ The owner and reminder mechanism for the 20 working day deadline are set
• □ Trigger rules for supplementary reports on new information are defined
• □ The escalation route for events discovered at the research and development stage is documented

Regulatory information verified as of 29 October 2026.

GRZAN supports manufacturers, authorised representatives and channel partners in Russia with adverse event reporting under Order No. 541n, including RZN information system submissions, statutory report templates and supplementary reporting, together with the wider post-market programme of vigilance, recalls and inspection readiness. For assistance, contact us at info@grzanglobal.com.