Short answer

Software with an EU MDR certificate usually registers with Singapore’s HSA through the abridged route: EU Notified Body certificates are among HSA’s recognised reference approvals, and the ASEAN CSDT dossier is built from your MDR technical documentation plus Singapore-specific declarations and a local registrant. HSA’s target turnaround is 100, 160 and 220 working days for Class B, C and D (full route: 160, 220 and 310), excluding the time you take to answer queries. GL-04 Revision 4, effective 31 December 2025, sets HSA’s expectations for the software lifecycle and for machine-learning-enabled devices, including dataset documentation and model-drift monitoring.

Why Singapore matters for SaMD companies

Singapore is often the first Asian market for SaMD companies already certified under EU MDR (and, for the UK, UKCA). HSA lists EU Notified Body certificates among its recognised reference approvals, and its dossier format — the ASEAN Common Submission Dossier Template (CSDT) — can be built from MDR technical documentation. There is no ASEAN-wide mutual recognition of HSA approvals, but specific reliance routes now exist: Malaysia's MDA accepts Singapore registrations through its verification route, and the Philippine FDA offers abridged processing for devices approved by an ASEAN regulator.

Singapore has also been active on AI. GL-04 Revision 4 covers machine-learning-enabled medical devices in detail, and version 2.0 of Singapore's Artificial Intelligence in Healthcare Guidelines (AIHGle 2.0), published in March 2026, complements HSA's software device framework.

GL-04 Revision 4 (December 2025) — what it covers

GL-04 is HSA's Regulatory Guidelines for Software Medical Devices — A Life Cycle Approach. Revision 4 (dated December 2025, effective 31 December 2025) extends the title to including Machine Learning-Enabled Medical Devices; HSA describes it as a one-stop reference for the software lifecycle. The points below matter most for SaMD teams.

Machine learning-enabled medical devices (MLMD)

GL-04 R4 sets out what HSA expects for MLMD before and after registration, including:

  • Dataset documentation — source and size of the training data, labelling, curation and cleaning steps, no overlap between training and validation data, and a test dataset and data-collection protocol that address bias and representativeness of the local population
  • Performance and monitoring — test protocols against the performance specification, a risk assessment covering overfitting, unintended bias, degradation and model drift, and real-world performance monitoring after launch
  • Continuous learning controls — for models that learn after deployment: a defined learning process, quality checks on new data, built-in validation, anomaly detection with rollback to a previous version, version control and traceability from real-world data to model version
  • Transparency for users — information that the device contains machine learning, the ML function with its inputs and outputs, the clinical workflow and any human intervention, known risks and limitations, and the exclusion criteria used in training and validation

Change management

GL-04 R4 adds a section on the Change Management Program (CMP), aligned with GN-37 Revision 1, which has applied since 4 December 2024. The change categories themselves are defined in GN-21, HSA's change notification guidance, now at Revision 7 (August 2026):

  • Technical changes (Class C and D): changes that can affect safety, quality or efficacy — for software, for example an algorithm change affecting diagnostic or therapeutic function, added features or connectivity affecting those functions, or a change of operating system. HSA approval is required before implementation.
  • Review changes (Class B): a closed list — for example changes to indications for use, added models, certain changes to warnings, contraindications or adverse events, and changes to the approved method of use. HSA approval is required before implementation; most other Class B software changes are Notification changes.
  • Administrative changes: changes to administrative documents and certain published SMDR particulars. HSA approval is required before implementation.
  • Notification changes: all other changes that are not exempted — for software, for example a bug fix that adds no function or risk, a change to the appearance of the user interface, or a fix for a cybersecurity vulnerability. Implementation can start once HSA acknowledges the submission.

GN-21 includes a dedicated decision flowchart for machine-learning-enabled devices (Flowchart 2.5, added in Revision 6, July 2025). Since Revision 7, no more than two change notification applications may be active for the same listing, and changes linked to adverse events or field safety corrective actions need prior approval whatever their category. For pre-approved software changes, see our guide to HSA's Change Management Program.

Cybersecurity and operating system end-of-support

GL-04 R4 reorganised its cybersecurity section. It encourages conformity with IEC 81001-5-1 and adds explicit expectations for operating system end-of-support: manufacturers must communicate with users in good time before support ends, labelling must state the OS requirements, devices already on an unsupported OS need mitigations or a migration plan, and software on an unsupported OS whose cybersecurity risks cannot be adequately mitigated will not be permitted for supply in Singapore. In August 2026 HSA also published GL-10 Revision 1, a best-practices guide on medical device cybersecurity.

How EU MDR documentation maps to HSA requirements

For companies with existing EU MDR certification, most of the evidence already exists; the work is selecting, restructuring and filling Singapore-specific gaps:

  • Technical documentation: EU MDR Annex II documentation generally covers the essential information HSA requires. The device description, risk management file (ISO 14971), software documentation (IEC 62304) and usability engineering documentation (IEC 62366) form the core. HSA's dossier format is the ASEAN CSDT (guidance GN-17); GL-04 also refers to the IMDRF Table of Contents format.
  • Clinical evidence: your EU MDR clinical evaluation is the starting point. For ML-enabled devices, GL-04 expects clinical validation data that are independent of training and tuning data, and attention to how representative the data are of the local population.
  • QMS: your ISO 13485 certificate serves as QMS evidence. HSA's manufacturer's licence concerns local entities that design, program, test and maintain software in Singapore (GL-04, Table 5); local importers and wholesalers need HSA dealer licences.
  • Cybersecurity: documentation built on MDCG 2019-16 is a good starting point; check it against GL-04 R4 Section 8, especially operating system end-of-support.
Preparing an HSA registration? I help software teams apply GL-04 R4, choose the evaluation route and prepare the CSDT from their existing EU documentation, working with your local registrant.
Request a free call →

The HSA registration process for SaMD

  1. Determine device classification under HSA's Class A–D framework (GN-13; for clinical decision support software, GL-07). Class A devices are exempt from product registration and are notified to HSA instead.
  2. Establish a Singapore registrant — a Singapore company that applies for and holds the registration on behalf of the product owner (your subsidiary, a distributor or an independent registrant). Importing and wholesale supply require HSA dealer licences in addition; GL-04 notes that a local entity providing cloud-based access to software needs a wholesaler's licence.
  3. Choose the evaluation route — with an EU Notified Body certificate for the same labelled use, a Class B–D device normally qualifies for the abridged route. Expedited routes (Class C and D) and immediate routes (Class B, and standalone medical mobile applications in Class B and C) have additional conditions, such as approval from two reference agencies or marketing history.
  4. Prepare the CSDT dossier following GN-17, with the letter of authorisation and declaration templates annexed to GN-15.
  5. Submit via SHARE, HSA's online submission system.
  6. Respond to HSA queries — HSA's target turnaround times exclude the time you take to answer (abridged route: 100, 160 and 220 working days for Class B, C and D). Slow or incomplete responses extend the elapsed time.
  7. Maintain the registration — pay the annual retention fee to keep the SMDR listing, report adverse events (GN-05) and field safety corrective actions (GN-10), and submit change notifications under GN-21.

We support EU-certified software companies through these steps in our Singapore HSA and Malaysia MDA registration service.

Singapore–Malaysia regulatory reliance: HSA and Malaysia's MDA signed an MoU on 22 August 2025 and piloted a reliance programme from 1 September 2025 to 28 February 2026; MDA moved to full implementation from 1 March 2026. Devices on the SMDR can use MDA's verification route, and HSA offers an abridged review for devices registered with MDA. An EU MDR certificate on its own also qualifies for MDA's verification route. Details in our Singapore–Malaysia reliance guide.
Official sources & references