Uzbekistan Quarterly MedDRA Reporting: Aggregate Safety Obligations for Manufacturers

1. Key takeaways

Beyond individual case reporting, registration No. 3752 introduces a periodic aggregate obligation: manufacturers and registration certificate holders must compile information on all adverse events and ineffectiveness cases for their products and submit it to the competent authority on a quarterly basis, with the data coded according to MedDRA, the Medical Dictionary for Regulatory Activities. This is an independent operational requirement, not a by-product of case reporting. If a company has not separated its Uzbekistan safety data from its global case database and has not set up a separate coding routine for it, the quarterly aggregation turns into a recurring, high-cost exercise performed under time pressure every three months, typically with terminology mapping work repeated each quarter. The obligation applies to manufacturers and registration certificate holders alike, and the coding infrastructure must therefore exist before the first quarterly cycle closes, not after it.

2. Legal basis

3. Expert insights

Insight 1: The difficulty of quarterly aggregation lies not in the frequency but in coding consistency. MedDRA coding requires every case to be classified under a single uniform terminology. If the global safety database of the company uses a different version or a different terminology set, each quarterly aggregation requires terminology mapping, and this workload repeats every quarter. The practical solution is to code at the point of data entry according to MedDRA, rather than retrofitting the coding at aggregation time, because retrospective mapping across hundreds of cases is both expensive and error-prone. Documenting the coding conventions and the version in use also gives the company a defensible answer when the authority asks how each case was classified and by whom.

Insight 2: The aggregation scope includes ineffectiveness, and this item is the one most often missed. Registration No. 3752 requires the aggregation of two categories: adverse events and ineffectiveness cases. At the individual case level, the deadline for ineffectiveness is 30 days; at the aggregation level, ineffectiveness cases must likewise be included in the quarterly report. Companies that track only adverse events while ignoring ineffectiveness cases leave the most common gap in their quarterly submission, and the omission is visible to the regulator because the obligation covers both categories explicitly. Because the ineffectiveness deadline at the case level is 30 days, those cases will already exist in the case register, and the quarterly task is to include them consistently rather than to discover them.

Insight 3: The aggregation obligation runs in parallel with the individual case reporting obligation, and neither replaces the other. Individual case reporting is triggered by the deadlines of 1, 15, 60, and 30 days; quarterly aggregation is a periodic, comprehensive summary. Both must be performed: individual reporting delivers urgent information to the authority, while quarterly aggregation presents the accumulated trends. A company that treats the quarterly report as a substitute for case reporting, or vice versa, fails both obligations at once. The two obligations also serve different inspection questions: the authority uses case reports to test responsiveness, and uses the quarterly summary to test whether the company sees trends that individual reports do not show.

Insight 4: MedDRA coding capability is a screening criterion when selecting a local representative. Because the reporting obligation is carried primarily by the local legal entity named on the registration certificate, while the underlying data comes from the manufacturer, a representative who can perform MedDRA coding and aggregation directly reduces the operational burden on the manufacturer significantly. Conversely, if the representative can only forward raw information, the manufacturer must complete the coding and the aggregation itself, which means owning the entire quarterly workflow remotely. This is also the point where the cost difference between candidates becomes visible over a year, because four aggregation cycles multiplied by the coding effort per cycle is a material line in the operating budget.

4. Practical recommendations

1. Apply MedDRA coding at the point of data entry, so that terminology mapping does not have to be repeated at every quarterly aggregation cycle; coding at entry also reduces the correction work that would otherwise surface during each aggregation review.
2. Ensure the aggregation scope covers both categories, adverse events and ineffectiveness cases, without exception.
3. Maintain two parallel registers: a case reporting register timed against the 1, 15, 60, and 30-day deadlines, and a quarterly aggregation register.
4. List MedDRA coding and aggregation capability among the assessed criteria when screening and selecting a local representative.
5. Fix the MedDRA version in use and complete version alignment of historical data when the version is switched annually, since a documented version policy keeps trend analysis comparable across reporting periods.

5. Verification checklist

• □ MedDRA coding is applied at data entry, with no quarterly retrofit mapping required
• □ The quarterly aggregation scope covers both adverse events and ineffectiveness cases
• □ The case reporting register and the quarterly aggregation register have been established separately
• □ The MedDRA coding and aggregation capability of the representative has been assessed
• □ The MedDRA version has been fixed, and historical data alignment is completed at annual switching
• □ It has been confirmed that the quarterly aggregation obligation and the case reporting obligation run in parallel and neither substitutes the other

Regulatory information verified as of October 29, 2026.

GRZAN provides regulatory support to manufacturers, importers, and authorized representatives seeking medical device registration and post-market compliance in Uzbekistan, including dossier preparation, authorized representative arrangements, vigilance setup, and surveillance readiness. For inquiries, contact info@grzanglobal.com.