Updated:
Is hospital AI software a medical device in Singapore? What HSA says
How HSA’s software guidelines decide what counts as a medical device and which class it falls in. A plain reading for administrators and nurse leaders before they sign a proposal.
When a vendor says its AI tool is “registered with HSA”, or that it needs no registration at all, an administrator has no easy way to judge. The Health Sciences Authority (HSA) publishes two documents that answer most of the first questions: GL-04, its life-cycle guidelines for software medical devices, and GL-07, which explains how software is classified by risk.
What counts as a software medical device
GL-04 (revision 4, effective 31 December 2025) applies to software whose intended use meets the definition of a medical device under the Health Products Act 2007. That includes software meant for medical purposes such as investigating, detecting, diagnosing, monitoring, treating or managing a medical condition, disease, anatomy or physiological process. It covers software embedded in a device and software that runs on general computing platforms, including standalone mobile applications, which are often called software as a medical device (SaMD).
The key word is “intended use”. GL-07 quotes the regulations: it is the objective purpose reflected in the specifications, instructions and information the product owner provides. Two products with the same model can differ in status because of what the manufacturer says they are for.
How the class is decided
GL-07 (revision 2, July 2025) follows an international framework. It asks two questions. How significant is the software’s information for care: does it treat or diagnose, drive clinical management, or only inform it? And how serious is the patient’s situation: critical, serious or non-serious?
In its table, software that treats or diagnoses in a critical or serious situation is Class C. Software that only informs clinical management in a serious or non-serious situation is Class A. A footnote moves some software up to Class B: software meant to analyse or monitor a vital physiological process, or anatomical structure images, to drive clinical management. GL-07 gives an example of Class A: software that lets healthcare professionals predict the risk of migraine from patient inputs such as sleep and stress.
GL-04 adds that Class B, C and D software medical devices require product registration. Software of every class, including Class A, must be safe and perform as intended throughout its life cycle.
Decision support is not automatically exempt
GL-07 also has a section on clinical decision support software. It sets out how such software qualifies as a regulated medical device or not. A vendor’s claim that its tool is “only decision support” is therefore something to test against that section, not a reason to stop asking.
Three questions for the vendor
- Do you treat this product as a medical device in Singapore, and on what intended use is that based?
- If so, which class is it, and what are its HSA registration details?
- Does our planned use match the intended use you state?
Ask for the answers in writing and attach them to the contract. Registration does not replace the hospital’s own testing: the Ministry of Health’s AI guidelines say the hospital usually validates a tool in its own workflows.
Key takeaways
- Software whose intended use meets the medical device definition falls under HSA’s guidelines, whether embedded or standalone.
- The class follows the significance of the information and the seriousness of the situation; Class B, C and D software needs product registration.
- Decision support software is not automatically outside the rules.
- Ask for status, class and registration details in writing. This is general information, not legal advice.
Sources: HSA, GL-04-R4 Regulatory Guidelines for Software Medical Devices, HSA, GL-07-R2 Risk classification of SaMD and qualification of CDSS, Ministry of Health, AIHGle 2.0. Read on 14 November 2026.