Updated:
Machine-learning medical devices in Singapore: what HSA expects from vendors
HSA’s software guidelines set extra expectations for machine-learning devices: a quality system, model documentation and instructions for use. A buyer’s reading for administrators.
A vendor brochure usually says what a model can do. HSA’s guidelines say what a vendor of a machine-learning-enabled medical device has to put in writing. Reading that list helps a hospital decide what to ask for in a proposal. The document is GL-04 (revision 4, effective 31 December 2025), section 9.
A quality system around the whole model life
HSA says that all activities for designing, developing, training, validating, retraining and deploying a machine-learning-enabled medical device must be managed under a quality management system based on ISO 13485. This covers retraining too, so a vendor that retrains its model should be able to show how that step is controlled.
What the registration file describes
For pre-market registration, the guidelines list additional information. It includes the intended use and indication for use, a description of the ML feature and its clinical association with the condition, the model’s inputs and outputs, the clinical workflow during deployment, and how the model was trained. A vendor should describe the model used, show that it suits the intended purpose, and explain its limitations and how shortcomings are mitigated.
What the instructions for use must tell you
In addition to ordinary labelling, the guidelines say users must be told:
- that the device contains machine learning, and what the ML function does, including its inputs and outputs;
- how to install, use, calibrate, validate locally and monitor performance on an ongoing basis;
- which hardware and software versions it works with;
- the clinical workflow of the device, including any human intervention;
- the risks and limitations of the ML function, and any exclusion criteria in the training and validation data.
Those items map neatly onto questions a hospital can ask: where was it validated, and on whom; what does our local validation need to look like; and where must a human step in?
After go-live
The guidelines say companies must monitor the real-world performance of all registered machine-learning-enabled devices after deployment, and that developers and distributors should set up processes with implementers and users to ensure traceability. For devices that continue to learn, the guidelines add controls on the learning process, rollback and traceability.
Key takeaways
- Retraining and deployment of an ML-enabled device sit inside an ISO 13485-based quality system.
- Registration and the instructions for use should describe the model, its inputs and outputs, the workflow, its limits and the training data exclusions.
- Vendors must monitor real-world performance after deployment; hospitals are part of that loop.
- Ask for these in writing. This is general information, not legal advice.
Sources: HSA, GL-04-R4 Regulatory Guidelines for Software Medical Devices (sections 9.1 to 9.3). Read on 14 November 2026.