Short answer

HSA’s Change Management Program (CMP), introduced on 4 December 2024 with GN-37 Revision 1, lets a registered SaMD get pre-specified software changes approved up front and then implement them under its QMS without a new change notification each time. Without CMP, GN-21 applies: many software changes to Class C and D devices are Technical changes that need HSA approval before implementation, and GN-21 Revision 7 (August 2026) allows no more than two active change notifications per listing. CMP requires registration on the Singapore Medical Device Register (or a joint application), a valid ISO 13485 or MDSAP certificate, and evidence of IEC 62304 conformance.

1. The problem CMP solves

Software changes constantly. Under HSA's change notification guidance (GN-21), a change to a registered device that is not exempt must be notified, and many software changes to Class C and D devices are Technical changes that need HSA approval before implementation. GN-21 Revision 7 (August 2026) also caps the queue: no more than two change notification (CN) applications can be active for the same listing — an application that would exceed this is rejected in its entirety and the fee is not refunded.

For a SaMD company shipping frequent releases, or an ML-enabled product updated on a regular cycle, per-change approval can hold back releases. CMP is HSA's answer: agree the anticipated changes and how you will validate them up front, then implement them under your QMS. (If you also manage EU changes, compare it with the EU approach in our AI/ML SaMD change control guide.)

Before CMP

Standard CN process

  • Each non-exempt change needs its own CN
  • Max. two active CNs per listing (GN-21 R7)
  • Each CN: separate HSA review cycle
  • Each ML model change assessed via Flowchart 2.5
  • Approval targets of 45–90 working days for Review/Technical changes
  • Queue builds up during rapid iteration
With CMP

Pre-specified change pathway

  • Anticipated changes pre-approved by HSA once
  • Future updates implemented via your QMS
  • No new CN required for pre-specified changes
  • ML-enabled SaMD covered (not continuous learning)
  • Annual declaration instead of per-change submission
  • HSA monitors post-market
CMP is optional, not mandatory

HSA describes CMP as an optional regulatory pathway. Companies can continue using the standard CN process. CMP makes most sense for SaMD with frequent, well-defined update patterns — for example ML-enabled devices with a planned re-training cycle. If your releases are infrequent and changes are unpredictable, the standard CN process may be more appropriate.

2. Three documents you need to know: GL-04, GN-37, GN-21

Understanding CMP requires reading three HSA guidance documents together. Each one covers a different layer of the framework:

GL-04 Revision 4 (December 2025) — the master guideline

GL-04 is HSA's core guideline for software medical devices. Revision 4 (dated December 2025, effective 31 December 2025) adds a Change Management Program section (Section 10) that refers to GN-37 for the detail. It also reorganised the cybersecurity section — encouraging conformity with IEC 81001-5-1 and adding expectations for operating system end-of-support — expanded the requirements for machine-learning-enabled medical devices, and aligned its definitions with IMDRF terminology. If you last read GL-04 before December 2025, re-read it. Our Singapore HSA SaMD registration guide summarises the rest of GL-04 R4.

GN-37 Revision 1 (December 2024) — the CMP rulebook

GN-37 R1, Change Management Program (CMP) for SaMD, including machine-learning enabled SaMD, took effect on 4 December 2024, when HSA started the CMP pilot run. It defines eligibility, the pre-specified change concept, what a CMP application must contain, the declaration obligations and how changes to an approved CMP are handled. It covers SaMD including ML-enabled SaMD; continuous learning and generative AI are outside its scope. This is the document your regulatory team needs to read in full before preparing a CMP submission.

GN-21 Revision 7 (August 2026) — change notification rules

GN-21 is HSA's guidance on change notifications for all registered medical devices. Revision 6 (July 2025) expanded the list of changes that do not need a change notification, removed the requirement for Class A devices, and introduced Flowchart 2.5 for machine-learning-enabled medical devices. Revision 7 (August 2026, effective 1 August 2026) revised the wording on Administrative changes, updated Flowchart 6 and introduced the limit of two active CN applications per listing. GN-21 also refers registrants who want to enrol in CMP to GN-37.

3. Change categories under GN-21

Every change to a registered SaMD has to be assessed against GN-21 before implementation. The category determines whether HSA approval is needed first and whether the change could be covered by a CMP pre-specified change. Note that the outcome depends on the device class.

Category Definition & SaMD examples Process CMP eligible?
Notification (all classes) All changes not in the other categories and not exempt. Software examples in GN-21: fixing an inadvertent error without adding functions or safety risk, changing only the appearance of the user interface, addressing a cybersecurity vulnerability. For Class B, software changes that would be Technical for Class C/D (e.g. an algorithm change affecting diagnostic function, or an OS change) are also Notification changes. Implement after HSA acknowledgement Yes, if within the intended use and original indication
Technical (Class C and D) Changes that can affect safety, quality or efficacy. Software examples: an algorithm change affecting diagnostic or therapeutic function, added features or connectivity affecting those functions, an added or removed alarm that changes patient treatment, a change of operating system. HSA approval before implementation Yes, if pre-specified within the intended use and original indication
Review (Class B) A closed list for Class B: changes to indications for use, addition of models to a listing, certain changes to warnings, contraindications or adverse events, and changes to the approved method of use. HSA approval before implementation Generally not — changes to intended use, indication or method of use are ineligible
Administrative (all classes) Changes to administrative documents submitted at registration and to certain published SMDR particulars. HSA approval before implementation No — changes to published SMDR particulars are ineligible
The classification determines everything

Implementing a change that needs prior approval without that approval is non-compliance — whether or not you are enrolled in CMP. Changes linked to adverse events or field safety corrective actions need prior approval whatever their category. GN-21 provides decision flowcharts for software in general medical devices (Flowchart 2.3), IVD software (2.4) and machine-learning-enabled devices (2.5). Use them and document the outcome.

4. Machine learning-enabled devices — Flowchart 2.5

Flowchart 2.5 was added in GN-21 Revision 6 (July 2025) to classify changes to machine-learning-enabled medical devices (MLMD). Part (a) applies to all MLMD; part (b) adds questions for continuous-learning algorithms.

Changes to inputs and outputs

Adding or removing input data types while the clinical output and indication stay the same is treated as a significant software change: Technical for Class C/D, Notification for Class B. An output change that adds a new indication follows the labelling route (Technical for Class C/D, Review for Class B); if the new output also needs a new input type, a new product registration is required. Output changes that do not change the indication — for example an added parameter — are treated like other significant software changes.

Changes to the clinical workflow and risk class

Flowchart 2.5 also asks about changes to the approved clinical workflow — for example removing human review of the output — and about deployment changes. Check the flowchart for the outcome in your device class. A change that alters the device's risk class requires a new product registration.

Continuous-learning algorithms

For continuous-learning algorithms, part (b) asks whether the defined limits for allowable performance change, or the baseline performance specification, are being changed (Technical for Class C/D, Notification for Class B), and directs you to contact HSA if the inclusion or exclusion criteria for learning data change.

CMP and ML-enabled SaMD

For ML-enabled SaMD, GN-37 expects the CMP application to describe dataset selection and independence and a re-training protocol, alongside the triggers for implementing each change and pre-defined acceptance criteria. Changes such as adding or reducing input data types that produce the same clinical output can be pre-specified. Continuous learning is outside CMP, and every pre-specified change must stay within the intended use and original indication and must not introduce new risks outside your existing risk management.

5. How CMP works — Pre-Specified Changes explained

The pre-specified change is the mechanism that makes CMP work. It describes an anticipated change — not a specific version, but a defined change with its rationale and expected timing — together with how it will be verified and validated and how it will be rolled out. HSA reviews and approves the pre-specified changes as part of the CMP application. Once approved, you can implement a change that falls within them, and meets its acceptance criteria, without submitting a new CN.

1
Prepare CMP application Submit with a new product registration, or through a change notification for an existing registration (Class B: "Other Notification Changes", Class C: "Other Technical", in both cases verified by HSA before submission). GN-37 asks for: a description of each change (rationale, software version and update frequency on a best-effort basis, triggers for ML changes), a performance verification and validation protocol with pre-defined acceptance criteria (for ML: dataset selection and independence, re-training protocol), an implementation protocol (deployment, user communication, labelling, post-update corrective action plan, surveillance), a post-implementation impact analysis, a traceability table where there are several changes, your ISO 13485/MDSAP certificate and IEC 62304 evidence. No additional enrolment fee
2
HSA reviews and approves CMP HSA reviews the CMP together with the registration or CN, but decides on each separately. Approval confirms which changes are covered and on what conditions. Target turnaround of the registration/CN unchanged
3
Implement pre-specified changes via QMS When a software update falls within an approved pre-specified change and meets its acceptance criteria, implement it under your QMS following the approved implementation protocol — no new CN required. Keep the changed versions distinguishable and the implementation records available to HSA. No per-change CN submission
4
Submit declaration and implementation record Within 1 year of CMP approval, submit a declaration with the implementation records for changes made under the CMP. Further declarations follow annually. HSA uses these, together with post-market monitoring, to oversee CMP activity. Annual cycle
5
Out-of-scope changes: standard CN applies Any change outside the approved pre-specified changes follows the standard GN-21 process, and changes to the approved CMP itself are made through a CN. A well-scoped CMP application anticipates the routine changes and leaves the standard process for significant events. Standard process for out-of-scope changes

6. CMP eligibility and enrolment requirements

GN-37 sets the conditions. They reflect that HSA relies on your QMS for routine changes:

  • 1
    SaMD registered on SMDR Pre-specified changes apply to SaMD registered on the Singapore Medical Device Register. You can apply for CMP together with the initial product registration or later through a change notification for an existing registration.
  • 2
    Valid ISO 13485 or MDSAP certificate The product owner must hold a valid ISO 13485 or MDSAP certificate covering the SaMD and its development; for OEM SaMD, the OEM provides it. Conformance must be to the latest version of the standards and remain valid throughout the product lifecycle.
  • 3
    IEC 62304 software lifecycle conformance Conformance with IEC 62304 can be shown by a certificate from an accredited third party or by an in-house assessed summary report. In practice, that means your software safety classification, lifecycle records and maintenance process must be in order before you apply.
  • 4
    Change management in your QMS CMP changes are implemented under your QMS, so in practice your procedure needs to cover how changes are identified and classified against GN-21, how verification and validation are planned and executed, how records are kept, and how you decide whether a change falls inside an approved pre-specified change.
  • 5
    Well-defined pre-specified changes GN-37 asks for a rationale, (best-effort) version and frequency, triggers for ML changes and pre-defined acceptance criteria, and advises against including changes you are not sure you will implement. Vague descriptions such as "routine software improvements" give HSA nothing to approve. A usable description sets clear boundaries — for example, re-training the classification model on a defined data source for the same intended population, released only if the pre-defined performance criteria are met.

Not eligible as pre-specified changes under GN-37: changes to the intended use or indication, changes to the method of use (such as an altered review workflow), changes to device particulars published on the SMDR, and changes related to field safety corrective actions or reportable adverse events.

Is your QMS ready for CMP enrolment? CMP needs a quality system that can control pre-specified software changes. I help SaMD teams build that foundation.
See QMS implementation →

7. CMP and Malaysia — what it means for your MDA registration

Since 1 March 2026, Malaysia's MDA has fully implemented the acceptance of Singapore registrations (Class B, C and D devices on the SMDR) through its verification route — covered in our Singapore + Malaysia reliance guide. For EU MDR certified SaMD, the EU certificate on its own also qualifies for that route. CMP itself is a Singapore pathway, but it touches your Malaysian registration in two ways.

Changes are notified separately in Malaysia

MDA's verification route covers initial registration and re-registration. Changes to a device registered in Malaysia fall under MDA's own change notification requirements, and MDA's verification guidance requires that a device presented for re-registration has no unnotified changes to its design, specifications or registration information. We have not found an MDA provision that extends reliance on HSA to individual changes or to CMP-approved changes, so plan to notify MDA separately through your Authorised Representative. How MDA will categorise software changes under its new guidance, MDA/GD/0072, is covered in our Malaysia change management guide.

QMS requirements alignment

HSA's CMP requires a valid ISO 13485 or MDSAP certificate, and MDA's verification route asks for ISO 13485 or an equivalent QMS certificate (including MDSAP). The same certificate therefore serves both, provided its scope covers the SaMD.

Practical recommendation

If your SaMD has a predictable update cycle, consider including the CMP application in the initial Singapore registration rather than adding it later through a change notification — HSA reviews both together. For Malaysia, set up a separate change notification process with your Authorised Representative from the start; CMP approval does not carry over. We help EU-certified software companies set up both in our Singapore HSA and Malaysia MDA registration service.

What CMP does not change for Malaysia

CMP is a Singapore-only regulatory pathway. Changes implemented under CMP still need to be assessed against MDA's change notification requirements and, where required, notified through your Malaysian Authorised Representative. Check MDA's current change notification guidance for your device class before deploying an update in Malaysia.

Official sources & references