Hospital AI Lab Practical information on medical AI for Singapore hospitals

Updated:

Digital health and AI roadmap

“What does our hospital have to do, and by when?” The more AI news there is, the harder that is to answer. This page collects dates that appear in the text of rules and official publications, with sections and links to the sources.

Checked: November 14, 2026 · For: hospital administration and nursing leadership

In short: HSA’s life-cycle guidelines for software medical devices (GL-04, revision 4 effective 31 December 2025) treat Class B, C and D software as needing product registration and set extra expectations for machine-learning devices; GL-07 explains how risk class follows the significance of the software’s information and the patient’s situation; the Ministry of Health’s AIHGle 2.0 (March 2026) tells hospitals to run AI under governance, risk assessment, testing, training and monitoring; and the PDPC’s breach guide sets a 30-day assessment and a 3-day notification clock.

How to read this page
Each item was written after the text of the document was opened and read. We do not add dates that circulate only in summaries. What applies to a particular hospital depends on its status and structure, so check the text and ask counsel or your compliance officer.

What has already happened

  1. March 2026
    MOH guidance for healthcare AI MOH and HSA publish AIHGle 2.0 for AI in healthcare Version 2.0 is dated March 2026 on its cover. It splits responsibilities between developers, deployers (healthcare organisations) and users (healthcare professionals), and adds chapters on continuous-learning AI, generative AI and direct-to-consumer AI. For deployers it sets out governance, risk assessment, pre-deployment testing, staff training, monitoring, adverse-event response, end of life and patient communication.
  2. February 2026
    HSA and software as a medical device MOH and HSA launch the AI-MD Exemption Sandbox AIHGle 2.0 (case study 5) says the sandbox, launched in February 2026, lets selected public healthcare entities deploy low-to-moderately-low-risk AI medical devices across multiple institutions without full licensing and registration requirements. It is not a route for private hospitals in general.
  3. December 31, 2025
    HSA and software as a medical device GL-04 revision 4 takes effect The revision history of GL-04 lists revision 4 with the effective date 31 December 2025. The document covers quality management, pre-market registration, change notification, post-market duties, cybersecurity and machine-learning-enabled medical devices, and says Class B, C and D software medical devices require product registration.
  4. July 21, 2025
    HSA and software as a medical device GL-07 revision 2 takes effect GL-07 revision 2 lists 21 July 2025 as its date. The classification table puts software that treats or diagnoses in a critical or serious situation in Class C, and an asterisk says software that analyses vital physiological processes or anatomical structure images to drive clinical management is Class B.
  5. December 4, 2024
    HSA and software as a medical device HSA issues GN-37 on an optional Change Management Program for SaMD, including machine-learning enabled SaMD GN-37 revision 1 (4 December 2024) describes a new pathway built into HSA’s existing registration and change notification processes. It lets a manufacturer have “pre-specified changes” approved in advance. The guidance says the program is optional, and its scope note excludes continuous learning and generative AI.
  6. March 1, 2024
    HSA and software as a medical device GL-04 revision 3 takes effect The revision history of GL-04 lists revision 3 with the effective date 1 March 2024.
  7. April 29, 2022
    HSA and software as a medical device HSA publishes GL-07 on risk classification of SaMD and on clinical decision support software GL-07 lists April 29, 2022 as its first release. It follows the IMDRF framework: the risk class depends on how significant the software’s information is for care (treat or diagnose, drive, or inform clinical management) and on the state of the patient’s situation (critical, serious or non-serious). GL-04 revision 2 carries the same date.
  8. March 15, 2021
    Personal data protection The PDPC revises its guide on managing and notifying data breaches The revised guide says an organisation that has credible grounds to believe a data breach has occurred must assess within 30 calendar days whether it is notifiable, and must notify the PDPC within 3 calendar days once it determines that the breach is notifiable. A breach that involves the personal data of 500 or more individuals is of “significant scale” and must be notified even if no prescribed data is involved.
  9. April 30, 2020
    HSA and software as a medical device HSA issues its first life-cycle guidelines for software medical devices (GL-04) The revision history of GL-04 lists the first release as 30 April 2020. The guidelines apply to software whose intended use meets the definition of a medical device under the Health Products Act 2007, and later revisions added machine-learning-specific requirements.

Upcoming dates

We found no upcoming dates confirmed by a primary source, so this section is intentionally empty.

New HSA guidance documents on medical devices and software appear automatically in the HSA calendar.

Pages that complement this one

Frequently asked questions

Is AI software that a hospital buys regulated as a medical device in Singapore?
It can be. HSA’s guidelines apply to software whose intended use meets the definition of a medical device under the Health Products Act 2007, which includes software intended to investigate, detect, diagnose, monitor, treat or manage a condition. GL-04-R4 says Class B, C and D software medical devices require product registration. Whether a given product is a device depends on its intended use, so ask the vendor for its HSA status in writing.
Who is responsible for an AI tool inside the hospital?
AIHGle 2.0 splits responsibilities between developers, deployers (healthcare organisations) and users (healthcare professionals). For deployers it recommends an internal governance platform, a registry of every deployed AI solution with its risk classification, pre-deployment testing, staff training, monitoring and an adverse-event process.
How fast must a hospital report a personal data breach?
The PDPC’s guide (revised 15 March 2021) says an organisation must assess within 30 calendar days whether a breach is notifiable and, once it decides that it is, notify the PDPC within 3 calendar days. A breach involving 500 or more individuals is of significant scale.
Are there confirmed upcoming deadlines for hospitals?
This page lists only dates that appear in the text of an official document that we read. We found no future compliance date in those documents, so the upcoming section is intentionally empty. HSA and MOH say their guidelines are reviewed and updated periodically.

Sources and date checked

Sources checked November 14, 2026. Rules and procedures change, so rely on the current text on the official source page.

The material on this site is general information for education. It does not replace diagnosis or medical advice for a specific patient, and it is not legal advice or a purchasing recommendation. For rules and policy, rely on the primary official sources.