Updated:
Checklist: device status and AI vendors
When a vendor offers AI software, three questions come up together: is it a regulated medical device, what changes when the model is updated, and what happens to the data it touches. This page puts them in one place, each with its basis.
In short: software whose intended use meets the definition of a medical device falls under HSA’s guidelines; Class B, C and D software medical devices require product registration (GL-04-R4); machine-learning devices carry extra documentation and monitoring expectations; and the hospital’s own governance, testing and incident process still applies under the Ministry of Health’s AIHGle 2.0.
- This is not an official checklist. It is the author’s list built from the documents cited; each item gives its basis.
- The documents cited do not decide whether a particular product is a medical device. That depends on its intended use and the vendor’s licence; ask the vendor in writing.
- Items marked “author’s recommendation” are not legal requirements.
A. Is the product a medical device?
HSA’s guidelines apply to software whose intended use meets the definition of a medical device under the Health Products Act 2007.
| No. | What to check | Basis |
|---|---|---|
| 1 | The vendor has given a written answer on whether it treats the product as a medical device in Singapore, and why. | GL-04-R4, section 1.3 |
| 2 | You have read the intended use the vendor relies on (the objective purpose reflected in its specifications, instructions and information) and compared it with how your staff will actually use the tool. | GL-07-R2, definitions; Author’s recommendation |
| 3 | If the product gives clinical decision support, you know that GL-07 sets out how such software qualifies as a regulated medical device or not, and you have asked the vendor which side it says it falls on. | GL-07-R2, section 3 |
B. Class and registration
GL-07 takes the IMDRF approach: the class follows how significant the software’s information is for care and how serious the patient’s situation is.
| No. | What to check | Basis |
|---|---|---|
| 4 | The vendor states the risk class and the reasoning (significance of the information: treat or diagnose, drive, or inform; situation: critical, serious or non-serious). | GL-07-R2, risk classification framework and table |
| 5 | If the product is Class B, C or D software, it is registered with HSA; you have asked for the registration details and checked them against HSA’s register. (The checking step is the author’s recommendation.) | GL-04-R4, Table 5 note |
| 6 | The local company that supplies the software holds the dealer’s licences and quality system GL-04 describes for its supply scenario. | GL-04-R4, section 4 and Table 5 |
C. Machine learning and updates
These items apply when the product uses machine learning to achieve its medical purpose.
| No. | What to check | Basis |
|---|---|---|
| 7 | The vendor’s documentation says that the device contains machine learning, what the ML function does (its inputs and outputs) and the clinical workflow including any human intervention. | GL-04-R4, section 9.1 |
| 8 | The documentation states the risks and limitations of the ML function and any exclusion criteria in the training and validation data. | GL-04-R4, section 9.1 |
| 9 | If the model keeps learning after deployment, the vendor can show its safety mechanism for detecting anomalies and rolling back to a previous version, and its version control. | GL-04-R4, section 9.2 |
| 10 | You know how model or software changes are handled: HSA requires change notification for any change to a registered ML-enabled device, and a manufacturer may use the optional Change Management Program for pre-specified changes. | GL-04-R4, section 9.4; GN-37-R1, section 1 |
| 11 | The vendor monitors the real-world performance of the device after deployment and has a route for your feedback and incidents. | GL-04-R4, section 9.3 |
D. What the hospital does itself
Registration with HSA does not replace the hospital’s own governance. AIHGle 2.0 sets out the deployer’s part.
| No. | What to check | Basis |
|---|---|---|
| 12 | The AI solution is entered in the hospital’s registry of deployed AI solutions with its risk classification. | AIHGle 2.0, section 6.1.1(b) |
| 13 | The hospital has tested the tool in its own workflows before going live, with a pilot phase for higher-risk solutions. | AIHGle 2.0, section 6.3.1 |
| 14 | Healthcare professionals stay in charge: the tool does not make clinical decisions independently without a human making the final decision. | AIHGle 2.0, section 6.2.1 and Table 4 |
| 15 | Adverse events from the use of a medical device are reported to HSA, in addition to internal reporting. | AIHGle 2.0, section 6.7.1 and footnote 25 |
Next
Frequently asked questions
- Does HSA registration mean the tool is right for our hospital?
- No. AIHGle 2.0 says the implementing organisation usually tests and validates the tool in its own context and clinical workflows, unlike the developer’s own validation, and that it should at minimum ensure patients and professionals maintain current care standards.
- A vendor says its product is not a medical device. What do we do?
- Ask for the reasoning in writing, tied to the intended use. GL-07 explains how clinical decision support software does or does not qualify as a medical device. Do not assume a exemption: the AI-MD Exemption Sandbox that AIHGle 2.0 describes is for selected public healthcare entities and low-to-moderately-low-risk AI medical devices.
- Does every change to the AI model need HSA’s approval?
- GL-04-R4 says a change notification is required for any change to a registered machine-learning-enabled device, and the category of change (technical, review or notification) follows GN-21. HSA’s optional Change Management Program lets a manufacturer have anticipated “pre-specified changes” approved in advance.
Sources and date checked
- HSA — GL-04-R4 Regulatory Guidelines for Software Medical Devices including Machine Learning-Enabled Medical Devices: A Life Cycle Approach (Revision 4, December 2025) (opens in a new tab)
- HSA — GL-07-R2 Guidelines on Risk Classification of Software as a Medical Device (SaMD) and Qualification of Clinical Decision Support Software (CDSS) (Revision 2, July 2025) (opens in a new tab)
- HSA — GN-37-R1 Guidance on Change Management Program (CMP) for SaMD, including machine-learning enabled SaMD (December 2024) (opens in a new tab)
- Ministry of Health and HSA — Artificial Intelligence in Healthcare Guidelines (AIHGle), Version 2.0, published March 2026 (opens in a new tab)
Sources checked November 14, 2026. Rules and procedures change, so rely on the current text on the official source page.
The material on this site is general information for education. It does not replace diagnosis or medical advice for a specific patient, and it is not legal advice or a purchasing recommendation. For rules and policy, rely on the primary official sources.