Private Medtech and the HSA AI-SaMD Sandbox: It Isn't for You — Here's the Path That Is

If you're a founder or small medtech team building Class A or B AI Software as a Medical Device (AI-SaMD) for the Singapore market, you've probably seen the news about HSA's proposed AI-SaMD sandbox from February 2026. Some commentary has framed it as a new lower-friction route for AI medical software generally.

It isn't — at least not as currently proposed. As covered in our companion post on what the consultation actually says, the proposed sandbox is scoped to AI-SaMDs developed by selected public healthcare entities for use in public healthcare. Public feedback during the consultation included requests to expand participation beyond the public healthcare sector, which confirms broader participation is not the current proposed scope.

For a private medtech founder, the practical conclusion is short: the sandbox is not your route. The standard HSA medical-device framework applies — classification first, then the applicable licensing, listing, or registration route. This post walks through what that actually means.

What Standard HSA Registration Looks Like for AI-SaMD

Singapore regulates medical devices — including AI-SaMD — under the existing Health Products Act. The registration framework uses four risk classes (A, B, C, D), and the route depends on your class plus whether you have prior approvals from recognized authorities.

For Class A and Class B AI-SaMD specifically, the headline picture:

• Class A generally does not require product registration with HSA. You still need to comply with general safety requirements and post-market obligations. (See our HSA registration overview for the full classification framework.)
• Class B requires registration. The route depends on prior approvals — devices with recognized reference-authority approvals (FDA, EU, TGA, etc.) may qualify for abridged evaluation, and in some cases immediate or expedited review, depending on class and approval profile.

For Class B registration, foreign manufacturers typically need a Singapore-based Authorized Representative (AR) structure — they handle the registration submission and carry post-market surveillance responsibilities. For Class A supply that doesn't go through product registration, confirm the dealer-licence structure that will import or distribute the device locally.

Three Planning Themes That Still Matter

Three planning themes still matter for private AI-SaMD teams even though the sandbox is not their route:

1. ISO 13485 quality management

ISO 13485 is the medical-device QMS standard HSA expects for registered devices, and the practical standard most serious medtech teams should build toward regardless of class. The proposed sandbox itself uses ISO 13485 self-attestation as one of its core ongoing conditions, which is consistent with how HSA already treats the standard for registered devices.

For Class B registration, that means a working QMS that produces design records, risk files, supplier controls, change control, and CAPA evidence on demand. For an exempt Class A position, ISO 13485 isn't a registration mandate, but confirm the actual compliance baseline before assuming a lighter setup is enough.

2. ISO 14971 risk management

ISO 14971 is the risk-management framework expected in a registration dossier and for ongoing registered-device compliance. In practice for AI-SaMD this often means extra attention to data drift, training-data bias, and intended-use boundary conditions on top of the standard hazard analysis — but those are practitioner-level commentary on how teams operationalize ISO 14971, not separate regulator language.

3. Classification clarity

Misclassification — particularly between Class A and Class B — is one of the more common preventable mistakes. The class drives whether you need registration, what evaluation route applies, and what post-market obligations attach. Get this wrong at the start and the rework cost compounds.

What Changes Because of the WHO ML4 Designation

On 10 March 2026, HSA became the first national regulatory authority in the world to attain WHO Maturity Level 4 for medical devices regulatory systems, allowing it to serve as a global reference authority.

For private medtech entering Singapore, the practical read of the press release is narrower than some commentary suggests: HSA's regulatory direction is worth tracking closely. Beyond that, the cited press release does not predict specific timeline shifts or evidence-portability outcomes, and we won't either.

Practical Next Steps for a Private Class A/B AI-SaMD Team

1. Confirm your class. Class A vs B vs C is the gate. The regMD classifier returns this for Singapore plus all other jurisdictions regMD covers in one pass.
2. Map your full HSA route. If Class B, identify whether you qualify for an abridged or expedited evaluation based on prior reference-authority approvals.
3. Line up your Singapore market-access structure. For Class B registration, that's an Authorized Representative — selection affects timeline and post-market workload. For exempt Class A supply, confirm the dealer-licence and importer setup that fits your distribution model.
4. Plan ISO 13485 + ISO 14971 to your route. If you're on a Class B registration path, stand them up early — they sit at the centre of the dossier. If you expect an exempt Class A position, confirm your actual compliance baseline before assuming a lighter setup is enough.
5. Watch the sandbox conversion. If HSA later expands the sandbox beyond public healthcare entities, that becomes a different conversation. Track HSA publications.

Where regMD Fits

regMD is a regulatory intelligence platform for medical devices. For private medtech teams working on Singapore HSA registration:

• Classification: the free classifier returns Singapore class plus how the same device classifies across regMD's 14 jurisdictions in one pass.
• Pathway mapping: the pathway finder maps HSA registration routes including evaluation-route selection based on prior approvals.
• ISO 13485 + 14971 grounding: the standards guides cover the QMS and risk-management scope you'll need.
• Regulatory change monitoring: the alerts engine flags HSA updates, including any future expansion of the proposed sandbox.

Sources: Baker McKenzie commentary on HSA's AI-SaMD consultation findings (Feb 2026) · HSA WHO ML4 announcement, 10 March 2026 · regMD: Singapore HSA AI-SaMD Sandbox — What the Consultation Actually Says · regMD: Medical Device Registration in Singapore HSA

This post is for general guidance only and does not constitute regulatory advice, legal advice, or a substitute for professional consultation. Requirements may change, and you should verify all decisions against official HSA materials and qualified counsel before relying on this information.