HSA Change Notification for Registered Devices under GN-21 R7

1. Key takeaways

Any change to a registered device must be handled as a Change Notification under GN-21, Guidance on Change Notification for Registered MD. The current version is R7, effective 1 August 2026. This version clarifies the distinction between administrative changes and notifiable changes, and introduces a key scheduling constraint: no more than two change notifications may be under evaluation for a single product listing at any time. Change evaluation fees are tiered by class and nature of the change: administrative changes SGD 560; Class C technical changes SGD 1,890; Class D technical changes SGD 3,120.

• The two-in-review limit is a scheduling constraint, not an administrative detail: queued changes must be processed serially, which sets a real cadence for fast-iterating product lines.
• The cost gap between administrative and technical changes runs from 3.4 times for Class C to 5.6 times for Class D, so classifying the change correctly decides the cost.
• Software as a medical device has its own change management framework under GN-37 R1, whose Change Management Program should be prepared before market entry, not after changes occur.
• A change of registrant follows a different procedure, GN-24 R2, at SGD 880 over 40 working days, with cooperation required from both the outgoing and incoming registrants.
• Changes, adverse events and FSCA are three separate lines with different purposes, deadlines and channels; one field event can trigger all three, and none substitutes for the others.

2. Legal basis

The change notification framework is set out in GN-21 R7 with its Annex 2 of August 2026, the registrant change procedure in GN-24 R2 of July 2025, and the software change management program in GN-37 R1. The fees and timelines below come from the official HSA fees page. The table consolidates the instruments, and the second table lists the fee tiers.

Change notification fees and timelines (HSA official fees page)

3. Expert insights

Insight one: the maximum of two changes under review is a scheduling constraint, not merely an administrative detail.

The practical effect of this rule is that you cannot submit five changes at once and simply wait. If a product has more than three changes queued, they must be processed serially. For companies whose product lines iterate quickly, especially software devices, this creates a substantive rhythm constraint. Our approach is to maintain a change queue for each listing, ordered by commercial priority.

Insight two: the cost gap between administrative and technical changes is 3.4 times for Class C and 5.6 times for Class D.

Class C administrative is SGD 560 against technical at 1,890; Class D administrative is SGD 560 against technical at 3,120. Judging which category a change belongs to directly determines the cost. A misclassification either spends more money than necessary or leads to a demand for a fresh submission.

Insight three: software devices have a dedicated change management framework.

GN-37 R1 establishes the Change Management Program (CMP) for software as a medical device, including machine learning-enabled SaMD. For clients building AI/ML products, the CMP is a document to prepare before market entry, not to patch together after a change occurs, because it is a pre-approved set of change rules that allows later iterations to travel a lighter channel.

Insight four: a change of registrant is a different procedure, handled under GN-24.

The change of registrant does not fall under GN-21 but under GN-24 R2, with a fee of SGD 880 and a timeline of 40 working days, and it requires cooperation from both the original and the new registrant (see Article 34).

Insight five: changes and vigilance are separate lines, and a single event can trigger three actions.

A single field issue may simultaneously require an adverse event report (vigilance) plus a field safety corrective action (FSCA) plus a registration change notification. The three differ in purpose, deadlines and channels, and none can substitute for another. When we build systems for clients we emphasise: manage them in one controlled case record, but fulfil them separately.

4. Practical recommendations

• Maintain a change queue for each listing: constrained by the maximum of two under review, ordered by commercial priority.
• Determine the change category before submitting: the cost gap between administrative and technical changes can reach 5.6 times.
• Prepare the CMP early for software products: the change management program under GN-37 R1 should be prepared together with the registration.
• Keep registrant changes and content changes separate: GN-24 and GN-21 are two distinct procedures.
• Manage change records and vigilance records in separate ledgers: but file them in the same case file for traceability.

5. Verification checklist

• □ The category of the change has been confirmed (administrative / review-required / technical)
• □ The fee and timeline have been calculated (560 / 1,890 / 3,120 SGD)
• □ The number of change notifications under review for the listing has been confirmed as no more than two
• □ The CMP has been prepared for software products (GN-37 R1)
• □ If a change of entity is involved, the GN-24 procedure has been followed (SGD 880 / 40 working days)
• □ The three lines of change, AE and FSCA have been fulfilled separately but filed in the same case record

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