Hospital AI Lab Practical information on medical AI for Singapore hospitals

Updated:

Hospital AI governance in Singapore: what AIHGle 2.0 asks before go-live

The Ministry of Health’s AI in Healthcare Guidelines 2.0 give hospitals a list of things to set up before AI reaches patients. Five of them, in plain language.

The Ministry of Health and HSA published version 2.0 of the Artificial Intelligence in Healthcare Guidelines (AIHGle) in March 2026. It splits responsibilities between developers, deployers and users. A hospital is a deployer, and the chapter written for deployers reads like a project checklist for administrators and nurse leaders. It is guidance, not a statute.

1. A governance platform and a registry

The guidelines say organisations should set up internal governance platforms to oversee all healthcare AI solutions through their life cycle. The platform assesses and approves solutions (including that they are fit for purpose and perform at least as well as current standard processes), keeps a registry of every deployed solution with its risk classification, gives guidance on safe deployment, and ensures deployments meet cybersecurity and data protection requirements. It recommends three distinct functions: a governance platform, a unit for day-to-day implementation and monitoring, and a unit that audits compliance.

2. A risk assessment tied to human oversight

Hospitals should assess the potential harm to a patient and how probable it is. The guidelines give an illustrative table separating human-in-the-loop, human-over-the-loop and human-out-of-the-loop, for clinical and clinical-operations uses. For clinical use, they say deployers should not deploy AI that makes clinical decisions independently without a human making the final decision.

3. Testing in your own workflows

Testing and validation is usually done by the implementing organisation, in its own clinical context. For higher-risk solutions the guidelines suggest a pilot phase with a smaller patient population. They mention the AI Verify testing framework, and say hospitals should also measure clinical outcomes, at minimum ensuring that professionals and patients benefit from or maintain current care standards.

4. Training and change management

Training should cover roles, workflow integration, contingency plans, limitations, output interpretation, patient communication, data input restrictions and incident reporting, and staff should be re-trained after significant updates. The guidelines also suggest user champions, as a case study from one public healthcare group shows.

5. Monitoring and a way out

Monitoring should check that performance is at least equivalent to current practice and track indicators such as model drift, with feedback channels and reporting timelines. For adverse events, the guidelines call for detection, response, investigation and reporting, including contingency plans that can shut the AI down and switch to a protocol without it. Before changing provider or decommissioning, an exit management plan should be agreed with the developer.

Key takeaways

  • Set up a governance platform and a registry of AI solutions with risk classification.
  • Tie the deployment model to human oversight; keep a human making final clinical decisions.
  • Test in your own workflows, pilot higher-risk tools, and plan training, monitoring and exit.
  • Read the full guidelines and the deployers’ toolkit on the Ministry of Health’s page. This is general information, not legal advice.

Sources: Ministry of Health and HSA, AIHGle 2.0 (sections 6.1 to 6.8), Ministry of Health, AIHGle 2.0 page. Read on 14 November 2026.

This article is part of a series

All series

← Blog