Short answer

MDA/GD/0072 (first edition, May 2026) is Malaysia’s new guidance on changes to registered medical devices. It is published but not yet in force: it takes effect when MDA launches MeDC@St 3.0, and until then MDA/GD/0020 (fourth edition, November 2022) applies. GD/0072 sorts changes into significant changes, which need MDA approval before implementation, and non-significant changes, which need a notification, an optional notification or only a record in your QMS. Its Flowchart D covers software: changes to an approved PCCP, algorithm changes, new clinical features, alarm changes and operating system platform changes are significant (D1–D7), and a new software version identifier needs a notification (D8). Changes made within a PCCP approved at registration need no submission. A significant change costs RM 50 to RM 1,500 depending on class; a notification costs RM 30.

Status: published, not yet in force

MDA has announced the publication of MDA/GD/0072 Change Management for Registered Medical Devices, first edition, and states that it will replace MDA/GD/0020 Change Notification for Registered Medical Device. The announcement is explicit that the new document is not yet implemented: it takes effect only after the official launch of the next version of MDA’s online system, MeDC@St 3.0 (the announcement calls it MedCAST 3.0). Until then, GD/0020 remains applicable and in force. MDA’s guidance document list dates GD/0072 15 May 2026.

What to do today: keep submitting changes under MDA/GD/0020 until MDA announces that GD/0072 applies. MDA had not announced a date in the sources we checked on 14 November 2026. Use the months before the switch to map your release types to the new categories.

GD/0072 applies to all devices registered under Act 737. It covers three kinds of submission through the Change Management module in MeDC@St: changes to a registered device, updates arising from reportable incidents and field corrective actions, and updates to registration information before re-registration (section 2). Its definitions of significant and non-significant change come from the Global Harmonization Working Party guidance on change management (GHWP/WG2-WG1-WG3/F001:2024), so the logic will look familiar if you know the GHWP or HSA approach.

Four ways a change is handled

A significant change is one that “could reasonably be expected to affect” the safety, performance or effectiveness of the device, or its conformity with the Essential Principles (section 3.13). A non-significant change has little or no potential to do so (section 3.9). Table 2 of the guidance turns this into four reporting pathways:

Reporting pathways under MDA/GD/0072
CategoryBefore you implementWhat you submit
Significant changeMDA evaluation and approval; the changed device may only be placed on the market after approvalChange Management application in MeDC@St with the supporting documents listed in Annex B
Non-significant change, notification requiredImplement immediately once the complete notification is submittedNotification in MeDC@St with supporting documents
Non-significant change, notification optionalImplement; submission is voluntaryOptional notification, for example to update information held in MeDC@St
Non-significant change, no notificationImplementNothing to MDA; documented assessment and evidence in your QMS or technical documentation

Some changes leave the change management system altogether and need a new registration (section 5.6): a fundamental change such as a completely new intended purpose, a change of risk class, an added device that is not a permissible variant under the grouping rules, or an added device with a different proprietary name that cannot be listed with the registered ones.

Whatever the category, the manufacturer or its Authorised Representative must assess every change and keep the assessment (section 5.4). For a foreign manufacturer that means your change control procedure has to produce a Malaysian decision for each release, and your Authorised Representative submits it.

Flowchart D: software changes step by step

Annex B contains seven decision flowcharts. Flowchart D (Figure B.4) is the one for software, and Table B.4 gives examples and the supporting documents for each outcome. The questions are asked in order, and the first “yes” decides the category:

MDA/GD/0072 Flowchart D for software changes
StepQuestion (paraphrased)OutcomeExamples in Table B.4
D1Is it a change to a PCCP approved with the initial registration?SignificantChanges to the change description, protocol or impact assessment of the PCCP
D2Does the change affect the control of the device and may it alter its diagnostic or therapeutic function, including new indications?SignificantInsulin pump software that doses on readings from a compatible CGM; extending the user group to paediatric patients
D3Is it a manufacturer-initiated change to the algorithm that affects the diagnostic or therapeutic function?SignificantLung nodule software that detects smaller nodules; changed QC interpretation or cut-off calculation in an IVD
D4Does it add features or applications that clinically affect the diagnostic or therapeutic function, or change how data is read so diagnosis or treatment may differ?SignificantA pulse oximeter that also reports blood CO; wireless connection of an insulin pump to glucose monitors
D5Does it add or remove alarms where the user’s response may affect treatment?SignificantAn early-warning alarm for atrial fibrillation in an ECG system
D6Does it affect safety or performance in a way that may alter diagnosis or treatment?SignificantChanged sensitivity or specificity of an IVD; better accuracy of a reported value
D7Does it change the operating system platform, or move to an OS version that is not backward compatible?SignificantMoving from Linux to Windows, or from Windows to iOS
D8Does a version update change or add a software identifier?Non-significant, notification requiredSW 1.1 to SW 1.1.1 or SW 1.2, with no impact on safety or performance
D9Is it another software change you want to record in MeDC@St?Non-significant, notification optionalAny update to registered information you choose to submit
—None of the aboveNon-significant, no notificationDocumented in the QMS and technical documentation

For a significant software change (D2–D7), Table B.4 lists the supporting documents: software validation report, risk management report, labelling, clinical evaluation report, change approvals from recognised countries. D6 adds pre-clinical study reports such as validation and usability. For D8, MDA asks for the list of configurations and the labelling. Where a document cannot be provided, a justification is required.

D1 reads differently in the table. The D1 box in the flowchart asks about a change “that falls within the scope of” an approved PCCP. Table B.4 makes the intent clear: D1 covers changes to the approved PCCP, while software changes carried out under a PCCP approved at initial registration are listed as non-significant with no submission. Section 8 says the same.

“Change approval documents from recognised countries” appear in every significant software row. If your notified body or another reference regulator has already approved the same change, that approval is part of the Malaysian file, so keep it with the change record.

Software changes that need no submission

Table B.4 also lists software changes that are non-significant and need no notification. For SaMD the most useful are:

  • Simple bug fixes, such as correcting display errors, and code changes that correct wording or minor logic errors without altering the core detection or measurement algorithm
  • Non-diagnostic features such as printing, report format or improved image clarity
  • Cybersecurity improvements, for example encrypting configuration files, adding passcodes for remote access, adding timeouts or restricting user access
  • Adding, changing or removing operating system versions within the same platform
  • GUI changes to colours or menu locations, and added user languages, without effect on intended use or performance
  • Changes in how the software is distributed or stored, such as downloads instead of physical media
  • Adjustments to machine learning datasets that do not change the labelled product design specifications
  • New connections to barcode readers, handheld devices or other devices, and disabling functions that do not interact with others

Two points need care. First, the flowchart asks the D8 question before it reaches “no notification”. Our reading is that a release which changes the software version identifier registered with MDA still needs a D8 notification, even when its content would otherwise need nothing; what changes is the size of the submission (list of configurations and labelling rather than validation and clinical evidence). Second, the dataset example is narrow: retraining that changes performance against the labelled specifications points to D3 or D6, which are significant.

PCCP for SaMD

Section 8 introduces the predetermined change control plan to Malaysian regulation. A PCCP sets out the pre-specified elements of a SaMD that may be modified after it is on the market, with the method, data requirements and verification and validation that keep it compliant. Once MDA has reviewed and approved it as part of the registration, it is part of the regulatory decision for the device. From there:

  • Software changes made within the approved PCCP are non-significant and need no submission (Table B.4).
  • Any change to the approved PCCP itself goes through a Change Management application as a significant change (D1). MDA then checks that the revised plan still supports safe and effective performance, stays within the approved framework and controls any new risks or methods.

Two limits matter in practice. GD/0072 describes the PCCP as part of the initial registration application and does not describe adding one to an existing registration. And it states that the comprehensive requirements for PCCPs will be set out in a separate guidance document on SaMD, which had not been published when we checked. If you are preparing a Malaysian registration for an AI-enabled SaMD with planned model updates, ask your Authorised Representative to confirm with MDA how a PCCP is submitted today. The documentation you prepared for an FDA PCCP or an HSA Change Management Program is a reasonable starting point.

What changes compared with MDA/GD/0020

MDA/GD/0020 compared with MDA/GD/0072
TopicMDA/GD/0020 (in force today)MDA/GD/0072 (after MeDC@St 3.0)
CategoriesCategory 1 (new registration), Category 2 (MDA endorsement before implementation), Category 3 (implement on submission of complete documents)Significant; non-significant with notification required, optional or not needed; new registration
Version-only software changes (bug fix to specification, non-medical peripherals, UI appearance)Category 3 with a software validation report and a detailed summary of software changes; may be batched in six-monthly submissionsD8 notification with the list of configurations and labelling if the identifier changes; otherwise a QMS record
Software changes that alter diagnosis or treatmentCategory 2 with risk analysis, software validation report and summary of changesSignificant (D2–D7) with validation, risk management, labelling, clinical evaluation and recognised-country approvals
Pre-approved changesNo mechanismPCCP approved at registration; changes within it need no submission
Review time30 working days for a single submission, 60 for combined or multiple submissions10 working days for a single type of significant change, up to 45 for multiple types or applications; none for notifications
FeesPaid before endorsement or acknowledgementSame amounts, paid after approval or acknowledgement

For most SaMD teams the change is positive: routine releases get lighter, cybersecurity fixes need no submission, and significant changes have a shorter target review time. The cost is a stricter documentation set for significant changes, which now explicitly includes a clinical evaluation report.

Fees, review times and bundling

MDA/GD/0072 change management fees
Device classSignificant change (RM)Non-significant change (RM)
Class A5030
Class B50030
Class C1,00030
Class D1,50030
Device containing a medicinal product2,50030

Fees are charged per registration certificate and per change type: a single application with one significant and one non-significant change for a Class B device costs RM 530, and the same pair of changes across three Class B certificates costs RM 1,590 (Table 4). Payment is made after MDA approves the significant change or acknowledges the non-significant one.

Review times run from submission of a complete application (Table 5): 10 working days for a single type of significant change on one certificate, and up to 45 working days for multiple types of change or multiple applications. Non-significant changes have no review time because they can be implemented on submission.

Several changes to one certificate can be bundled into one application (section 6.1). Bundling across several certificates is allowed only for the same administrative-type change applied identically, such as a change of manufacturer name or address, site, QMS information, brand name or labelling information (section 6.2). Changes resulting from a field corrective action, including those linked to open reportable adverse events, may be implemented immediately without prior MDA approval (section 12).

Updates before re-registration

Registration lasts five years, and GD/0072 ties re-registration to up-to-date information. Before you apply for re-registration, you update the registered information through the Change Management module as a non-significant change with notification (section 7). For Class B, C and D devices that means the Declaration of Conformity, QMS information, post-market surveillance information, the clinical evaluation report, the risk management report, and the CAB report and certificate; for Class A the first three. Re-registration cannot proceed until these are updated. For SaMD with frequent releases, plan this update well before the re-registration window opens.

Malaysia, EU and Singapore compared

Software change control in Malaysia, the EU and Singapore
TopicMalaysia (MDA/GD/0072)EU MDRSingapore (GN-21 R7, GN-37)
Who decidesManufacturer or AR applies Flowchart D; MDA approves significant changesManufacturer under its notified body’s change procedure; NB approval where a change could affect safety and performance (Annex IX, section 4.10)Manufacturer applies the GN-21 flowcharts; HSA approves Technical, Review and Administrative changes
Algorithm change affecting diagnosisSignificant (D3), MDA approval firstUsually needs NB approvalTechnical change for Class C and D, approval first
Cybersecurity fixNo submissionUsually not significant; documentedNotification change
Version-only bug fixD8 notification if the registered identifier changesUsually not significant; documentedNotification change
Pre-approved changesPCCP approved at registration; detailed requirements still to comeNo equivalent in the MDR today; the AI Act recognises pre-determined changes for high-risk AI devices from 2 August 2028Optional Change Management Program (GN-37)
Review time10 or up to 45 working daysSet by your notified bodyApproval targets of 45–90 working days for Review and Technical changes

The EU and Singapore columns summarise our AI/ML SaMD change control guide and our Singapore CMP guide. Malaysia’s verification route lets an EU MDR certificate support the initial registration, but we have not found a provision that extends this reliance to individual changes: changes are assessed and submitted in Malaysia separately.

What to do now

  1. Keep using MDA/GD/0020 for changes until MDA announces that GD/0072 applies, and watch MDA’s announcements on MeDC@St 3.0.
  2. Add a Malaysia column to your change assessment record, next to your notified body and HSA decisions, and map your usual release types to D1–D9.
  3. Agree with your Malaysian Authorised Representative who prepares and submits notifications, how quickly, and which documents you supply for each release (list of configurations, labelling, validation report).
  4. Keep notified body and other regulators’ change approvals with the change record; they are listed supporting documents for significant changes.
  5. If you plan to register an AI-enabled SaMD in Malaysia, decide early whether you want a PCCP and confirm the current submission route with MDA through your Authorised Representative.
  6. Put the re-registration update (DoC, QMS and PMS information, CER, risk management report, CAB documents) into your regulatory calendar.

The registration route itself is covered in our Malaysia MDA registration guide, the Authorised Representative’s licence and GDPMD in the GDPMD guide, and labelling in the Malaysia labelling guide. TrustedTraceMed does not act as an Authorised Representative in Malaysia; our Malaysia and Singapore registration support covers the route, the dossier and change control together with the partner you appoint.

Sources