Post-Registration Changes and Renewal Documents: Article 6.3.3

1. Key takeaways

Article 6.3.3 of RTS 11.03.02:21 governs post-registration changes and renewal through 4 items (a to d). Item a) sets the precondition: the registration must be valid and the annual fee paid. Item b) requires the change or renewal application to be filed as the authority requires. Item c) requires supporting documents covering changes made by the manufacturer to the documents in the registration file, and any design or characteristic change affecting the performance of the device, whether directly or indirectly, which covers 2 kinds of action, and which must occur during the validity period of the registration. Item d) requires every change made after registration to be incorporated into the file when renewal is applied for.

The article is short, but item c) is drafted widely enough to capture events that companies do not usually describe as changes at all. The operative question is not whether the product has become a different product, but whether anything in the registration file has moved, or whether performance has been affected even at second hand. Once that reframing is accepted, the change-management workload in this market looks considerably larger than most manufacturers initially plan for. It also explains why a company can hold an unbroken chain of valid registrations and still be found deficient, because the deficiency lies not in the registrations themselves but in the gap between what was filed and what is actually being manufactured.

2. Legal basis

The four items of Article 6.3.3 and the two change fee lines are set out below.

3. Expert insights

Insight 1: The reach of item c) is far wider than the phrase design change suggests. The text covers changes made by the manufacturer to the documents contained in the registration file, or any design or characteristic change affecting the performance of the device directly or indirectly. The two alternatives extend the obligation in two directions at once: towards manufacturer-side document changes even where the product itself is untouched, and towards changes that affect performance only indirectly. A change of raw material supplier, an adjustment to the sterilisation method or a software version update may therefore each trigger a filing obligation, even though none of them produces a new device in the ordinary commercial sense.

Insight 2: Item d) turns change reporting into a general ledger that is settled at renewal. The article states that all changes occurring after the registration was granted must appear in the file when renewal is applied for. This is the mirror image of filing changes one at a time during the term: batching is permitted in practice, but at renewal the authority reads the whole account, and a change that was never reported has nowhere to hide. The consolidation requirement therefore converts an intermittent administrative task into a continuous record-keeping obligation.

Insight 3: Change fees are priced per filing, while registration fees are priced per code, and the two logics must not be confused. Section 3.2.1 of the tariff charges a basic fee of USD 48.00 for a change of code or model name or description, plus USD 0.60 for each affected code or model; Section 3.2.3 charges a flat USD 48.00 for other post-registration changes. A renaming covering 50 models therefore costs 48.00 plus 50 multiplied by 0.60, which is USD 78.00, and is not recalculated against the registration bracket table. Budgeting a change as though it were a re-registration overstates the cost; budgeting it as a single flat fee understates it.

Insight 4: The precondition in item a) turns arrears into a global block. Once the annual fee is unpaid the registration is suspended, and in that state even a change cannot be filed. A company wishing to replace its professional responsible or to correct a model description must first clear the annual fee; the change application is not a route around the suspension. Treating the annual fee as a cost that can be deferred until something else needs doing is the most expensive misjudgement available in this system, because it freezes every other procedure at the same time.

4. Practical recommendations

• Build a change assessment list covering file document changes, changes with a direct effect on performance and changes with an indirect effect, and bring all three within the filing scope.
• Archive each change as it happens, and produce a complete change ledger when renewal is filed.
• Confirm that the annual fee is paid before any change is filed, so that Article 6.3.3 a) does not block it.
• Calculate change fees as the basic fee plus USD 0.60 per affected model, and keep them distinct from the registration bracket fee.
• Assess software version updates, supplier changes and sterilisation adjustments against the change criteria before implementing them.
• Write the response time for change filings into the service agreement with the local licence-holding partner.

5. Verification checklist

• □ Change assessment list established, including indirect effects
• □ Each change archived as it occurs
• □ Annual fee confirmed as paid before filing a change
• □ Change fee calculated as basic fee plus model count
• □ Software, supplier and sterilisation changes assessed against the criteria
• □ Change response time written into the service agreement

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for the Salvadoran market. Our team manages Ministry of Health (MINSAL) sanitary registration applications, prepares Spanish-language dossiers, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com