Kazakhstan Medical Device Adverse Event Reporting: Timelines and Practical Requirements

1. Key takeaways

Adverse event reporting for medical devices in Kazakhstan is governed by Order No. ҚР ДСМ-320/2020 of the Minister of Health. Reporting obligations are tiered by the severity of the event: events involving a serious public health risk, death or serious injury carry the shortest reporting timelines, while other events are subject to longer timelines. Products on the Union pathway are additionally subject to Decision No. 174. The recommendation of GRZAN is to set internal response timelines by the strictest practical estimate and to treat regulatory deadlines as a floor rather than a target, because between the moment a company becomes aware of an event and the completion of its evaluation there is still work to be done on information completion and causality judgment.

2. Legal basis

3. Expert insights

Insight 1: the core of tiered timelines is the severity judgment, and that judgment must be made the moment information is received. Which events count as a serious public health risk, death or serious injury determines which tier of timeline applies. Companies should define severity criteria and assign a responsible judge internally in advance, rather than waiting until all information has been collected before making the call. A late severity decision silently consumes the reporting window. The criteria should be written, versioned and trained so that different staff members reach the same classification for the same event.

Insight 2: the reporting clock starts on awareness, not on confirmation. There is a time gap between the moment a company becomes aware of an event and the completion of the causality evaluation, and regulatory timelines are usually counted from awareness. The approach of GRZAN is to submit an initial report based on known information first and supplement it once the evaluation is complete, instead of waiting for the evaluation to finish before reporting anything at all. This keeps the regulator informed within the regulatory window and leaves the deep causality work to the follow-up, which is how the rules are designed to be used.

Insight 3: reporting channels and content requirements must follow the specific provisions of Order No. 320/2020. A report should include the event description, device information (model, batch), circumstances of use, outcome and measures already taken. Products on the Union pathway follow Decision No. 174 instead; the two sets of requirements differ in detail and cannot be mixed. Companies running both pathways should maintain separate templates so that the applicable content list is always the correct one. Mixing the two content lists is a defect that only becomes visible when a regulator compares the submitted report against the applicable rule.

Insight 4: adverse events can trigger manufacturing site inspections. Under Decision No. 106, one of the triggers for an unplanned inspection is confirming that the causes leading to nonconforming devices leaving the factory have been eliminated. The methodological recommendations adopted by the Eurasian Economic Commission Executive Committee on April 7, 2026 likewise indicate that when a notice of an adverse event or a product complaint is received, the inspection focus should be the manufacturing site. Event handling and inspection readiness are therefore linked activities, not separate workstreams. Preparing corrective action evidence while the event is still open is the most efficient way to serve both.

Insight 5: adverse events and market sampling are two mutually corroborating lines of evidence. Order No. ҚР ДСМ-323/2020 sets out the rules for sampling products in circulation. Event investigations frequently require sampling and retesting to confirm whether a problem is batch-related; conversely, a nonconformity found through sampling may reveal events that were not previously identified. The records of the two lines must be able to reference each other, which requires a common indexing convention agreed before an event occurs. Batch numbers, model references and dates should be captured in the same fields in both records so the cross-reference works mechanically rather than by memory.

4. Practical recommendations

1. Define severity criteria and assign a responsible judge internally in advance; judge on receipt of information and start the clock immediately.
2. Submit an initial report first and supplement it after the evaluation is complete; do not wait for confirmation before reporting.
3. Prepare report content item by item under Order No. 320/2020: event description, device information, circumstances of use, outcome and measures taken.
4. For Union pathway products follow Decision No. 174 and do not mix the requirements with the national pathway.
5. Link event handling with manufacturing site inspection preparation, and prepare corrective action evidence in advance.

5. Verification checklist

• □ Severity criteria and a responsible judge have been defined in advance
• □ Reporting timelines are counted from awareness, and internal response timelines have been set by the strictest practical estimate
• □ Report content covers each item: event description, device information, circumstances of use, outcome and measures taken
• □ Reporting requirements under the national pathway (Order No. 320/2020) and the Union pathway (Decision No. 174) have been separated
• □ Event handling and manufacturing site inspection preparation have been linked
• □ Sampling and retesting records under Order No. ҚР ДСМ-323/2020 can be cross-referenced

Regulatory information verified as of October 29, 2026.

GRZAN provides registration and post-market compliance support for medical device manufacturers, importers and authorized representatives in Kazakhstan, including adverse event reporting, vigilance system setup and inspection preparation. For inquiries, contact info@grzanglobal.com.