Updated:
AIHGle 2.0 after go-live: training, monitoring, off switch
Singapore's AI in Healthcare Guidelines 2.0 ask hospitals to train staff, monitor AI and plan a way to switch it off. Who reports what to whom.
An AI tool is switched on, the vendor leaves, and the ward carries on. Weeks later a nurse notices the alerts look odd. Who does she tell, and what happens to the patient in the meantime? Singapore’s Ministry of Health and the Health Sciences Authority (HSA) address exactly this stage in version 2.0 of the Artificial Intelligence in Healthcare Guidelines (AIHGle 2.0), published in March 2026. This post covers only what the guidelines say about the period after go-live, in plain words. They are guidelines, not a statute, and we read only the guidelines document itself.
Training that goes beyond “how to click”
Section 6.5.2 says staff training should comprehensively cover a long list of topics. It includes roles and responsibilities, relevant professional standards and regulatory requirements, workflow integration, contingency plans, specific use cases, the limits of the AI solution, how to interpret its output, patient communication, data input restrictions (including data security and classification), spotting abnormal behaviour and incident reporting. It also says organisations should re-train staff when there are significant updates to the AI solution or to clinical workflows. It suggests several ways to train: self-paced online courses, hands-on demonstrations and knowledge-sharing sessions led by experienced colleagues, and structured seminars or programmes.
Monitoring that someone owns
Section 6.6.1 asks organisations to set up a process to monitor the AI solution’s performance, both ad hoc and regularly, to keep it safe, effective and robust while it is in use. Section 6.6.2 says periodic evaluation should at minimum show that the tool is as good as or better than current practice for patient safety or welfare, and should check the accuracy and reproducibility of its decisions. User feedback channels should be set up and communicated, and feedback should reach organisational leadership, relevant authorities and the developers or technical teams. The guidelines list features of a feedback loop: roles and responsibilities, reporting timelines, indicators such as model drift and a response matrix.
When something goes wrong
Section 6.7.1 asks organisations to set up a process to detect, respond to, investigate and report adverse events or other device issues from using the AI solution. Three points stand out:
- Contingency plans should include shutting down the AI solution and switching to a contingency protocol, for example one where the AI is not involved, so the impact on the patient is minimised, while working with developers on interim and permanent fixes.
- Reporting: organisations should set up internal reporting and abide by existing frameworks. Data-related incidents go to the Personal Data Protection Commission (PDPC), adverse events from medical devices to HSA, and critical cybersecurity incidents to the Cyber Security Agency of Singapore (CSA). A footnote adds that other AI-related cybersecurity incidents may be reported to SingCERT.
- Investigation: because the root cause may not be obvious, events should be documented and investigated, and the AI developer may be involved where appropriate.
What a ward or department can prepare
These steps are our suggestions drawn from the guidelines, not requirements stated in them.
- Write a one-page “when the AI looks wrong” card. It should say who to call, how to switch to the non-AI process and how to log the event.
- Rehearse the off switch. Check that the non-AI protocol still works on a normal shift, not only on paper.
- Name the owner of monitoring. Decide who reviews performance indicators and where user feedback goes.
- Schedule re-training whenever the vendor ships a significant update.
Key takeaways
- AIHGle 2.0 asks for broad staff training, re-training after significant updates, and periodic monitoring against the performance of current practice.
- It asks hospitals to plan for adverse events, including shutting down the AI and switching to a protocol without it, and to report through PDPC, HSA and CSA as applicable.
- Turn the guidelines into a one-page card and a rehearsed fallback. This is general information, not legal advice.
Sources: Ministry of Health and HSA, AIHGle 2.0 (March 2026), sections 6.5.2, 6.6.1, 6.6.2 and 6.7.1 with footnotes 24 to 26. Read on 16 November 2026.
This site’s content is for general information, research, and education. It does not replace medical diagnosis or advice for any specific patient, and it is not legal advice.