The classification decision drives everything downstream. It is also routinely deferred until after procurement, which is the worst possible moment to discover the answer.
Classification turns on intended purpose, not on the technology. If a tool is intended for diagnosis, prevention, monitoring, treatment or alleviation of disease, it will generally meet the definition of a medical device and fall under the Health Products Act 2007 in Singapore, with HSA registration requirements following. Administrative, scheduling and documentation tools generally do not. AIHGle 2.0 added worked examples distinguishing the two, because the boundary has caused persistent confusion since 2021.
The most common misconception is that classification follows from what the system is built on. It does not. Two tools using the same underlying model can land on opposite sides of the line depending entirely on what they claim to do.
A large language model summarising a consultation for the medical record is doing documentation. The same model flagging that a described symptom pattern warrants urgent referral is doing something closer to triage. The technology is identical. The intended purpose is not.
AIHGle 2.0 added worked examples specifically because that third category generated most of the confusion after the 2021 guidelines.
Intended purpose is established partly through how a product is described. A vendor whose website promises the tool will detect deterioration earlier than clinicians has made a claim, whatever the contract's disclaimer section says. Institutions have been surprised to find that their own internal communications about a tool contributed to how its purpose would be read.
The failure pattern is consistent: classification gets treated as a compliance formality to be resolved after the purchasing decision, by whoever owns regulatory. By then the budget is committed and the answer is unwelcome, which creates pressure to reach the convenient conclusion.
Ask it during evaluation instead, and make the vendor state their position in writing. "Do you consider this a medical device in Singapore, and on what basis" is a fair question with a short answer. A vendor who has sold into this market has taken a view. A vendor who becomes vague is either inexperienced or hoping you will not ask again.
The related question worth asking: if you configure or extend the tool, does that change its intended purpose? Institutions that build workflows on top of a purchased system can move it across the line without realising they have become a manufacturer.