Change Management: How the Three Change Notification Categories Are Divided

1. Key takeaways

A registered device can be changed, but not silently. Every change to a registered medical device must be handled through a Change Notification (CN) under MDA/GD/0020. The governing principle is simple and unforgiving: a change that has not been approved may not be implemented, and may not be carried into a renewal. The MDA’s guidance states the point directly — a renewal application and a CN cannot be submitted at the same time.

Changes are sorted into three classes by their effect on safety and performance, and the class determines whether the company may act on its own notification or must wait for an approval. Because the classification decides the commercial timetable, it is worth resolving before engineering release rather than after.

• Major change: affects intended use, risk classification or comparable fundamentals — re-registration is required.
• Change requiring prior approval: may be implemented only after the MDA has approved it.
• General change: may be implemented once the information has been submitted, on a notification basis.
• Scenario allocation: the comparison table in MDA/GD/0020 governs which class a specific change falls into.
• Renewal interaction: where a CN is open, the renewal route sits under the completed CN application; the change must be approved first or the renewal information will not match the MDA record.
• Automated renewal: the route requires that there is no in-progress or pending CN or COO.
• Fees: the Fifth Schedule applies as published at the time; the Class A change application fee is RM500 from 2026, subject to the MDA’s current publication.

2. Legal basis

The CN system sits between the registration and the post-market obligations. A registration certificate records a specific configuration of a device, and a change alters that configuration; the CN process is the mechanism by which the record is kept true. MDA/GD/0020, Change Notification for Registered Medical Device, sets out the classes and the scenarios. MDA/GL/08 (June 2023, third edition), section 4.1, addresses the interaction with renewal: a CN and a renewal may not run in parallel, and the change must be approved before the renewal proceeds. The Automated Re-Registration Guide carries the same logic into the automated route, whose frequently asked questions Q6 and Q8 confirm the eligibility condition.

The practical effect of this layering is that the three instruments answer three different questions. GD/0020 answers what kind of change this is. GL/08 answers what may be filed at the same time. The automated guide answers whether the fastest renewal route is available at all.

3. Expert insights

Insight 1: the real risk is not the CN, it is the change that bypasses it.

Companies rarely decide to ignore the CN process. What happens instead is that an engineering change is released to production under a routine internal approval, and the regulatory question is asked afterwards, if at all. By the time the device is on the market in its new configuration, the registration record no longer describes the product. That divergence is the finding an inspector is looking for, and it cannot be cured retrospectively by filing a CN, because the unapproved configuration has already been distributed.

Insight 2: classification is a threshold question, not a documentation question.

The three classes are not administrative conveniences; they describe three different legal positions. A major change removes the basis of the existing registration, so a new registration is the only route. A change requiring prior approval leaves the registration intact but suspends the right to implement. A general change preserves both, provided the submission is made. The sequence to apply is therefore: does the change affect the intended use or risk classification, then does it affect EPSP conformity, then consult the GD/0020 comparison table. Companies that start at the table without the first two steps tend to find a row that appears to fit and stop reading.

Insight 3: the renewal interface is where the timing damage shows up.

Where a CN is open, the renewal action is attached to the completed CN application rather than standing alone. Two consequences follow. First, a change that is still under review delays the renewal, which is why a change programme should be sequenced against the certificate expiry calendar and not against the engineering calendar. Second, a renewal cannot be used as a container for unapproved changes: the declared configuration and the MDA’s approved record must agree, and a mismatch is exactly the inconsistency the review is designed to detect.

Insight 4: the automated renewal route rewards a clean file, and punishes a neglected one.

The automated route requires that there is no in-progress or pending CN or COO. That condition is a statement about housekeeping as much as about compliance. A company that files CNs promptly, closes them and keeps its records aligned will qualify; a company that has left several notifications open will not, and will fall back to the standard review at the moment it wants speed. The operational lesson is that CN discipline is a renewal strategy, not merely a change-control obligation.

Insight 5: fees should be budgeted per event, not per year.

Charges follow the Fifth Schedule as published at the time, and the Class A change application fee is RM500 from 2026, subject to confirmation in the MDA’s current publication. Because the fee attaches to the notification rather than to the calendar, a change programme with several triggers carries several charges. Budgeting on the basis of the published schedule, and re-checking it before submission, avoids the common surprise of a fee change discovered at the payment step.

Insight 6: make the CN question part of the engineering release, not a later review.

The cheapest control is a gate. Every engineering change order should pass a documented question — does this trigger a CN, and if so which class — before production is released. Remedying a missed notification costs either a re-registration or an interruption in supply, both far more expensive than the gate.

4. Practical recommendations

• Put a CN gate on the engineering change order. No production release without a recorded classification decision and a named approver.
• Apply the tests in order. Intended use and risk classification first, EPSP conformity second, the GD/0020 comparison table third.
• Map every certificate against its expiry date. Sequence planned changes so that no CN is open during the renewal window.
• Do not file a CN and a renewal together. Section 4.1 of GL/08 prohibits parallel submission; plan for one to finish before the other starts.
• Keep the automated route available. Close CNs promptly and clear any COO issues so that the eligibility condition continues to be met.
• Confirm the fee before every submission. Check the current Fifth Schedule rather than a figure carried over from a previous project.
• Record the rationale for each classification. A short written justification, retained with the change record, is the evidence that the decision was made rather than assumed.

5. Verification checklist

• □ MDA/GD/0020 Change Notification for Registered Medical Device reviewed in its current version
• □ MDA/GL/08 (June 2023, third edition) section 4.1 confirmed — CN and renewal not parallel, change approved first
• □ MDA Automated Re-Registration Guide FAQ Q6 and Q8 (July 2026) reviewed
• □ Three classes and their implementation rules written into the change procedure
• □ Trigger list covers design, materials, site, labelling, sterilisation, software and suppliers
• □ Certificate expiry calendar cross-checked against planned changes
• □ Fifth Schedule fee checked before submission, including the Class A change application fee

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across Southeast Asia, including Malaysia. Our team prepares dossiers to ASEAN CSDT structure, manages submissions and deficiency responses with the MDA, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com