Updated:
Checklist: AI vendors and documents
When a vendor offers AI software, three questions come up together: which emirate’s rules bind us, what must the vendor show, and what changes when the tool is updated. This page puts them in one place, each with its basis.
In short: Abu Dhabi hospitals follow DoH’s AI policy and, since August 2026, its digital products standard; Dubai hospitals follow the DHA policy, which asks for a detailed vendor disclosure and independent third-party validation; and device security and incident clocks come from DoH’s reporting standard and cybersecurity guideline.
- This is not an official checklist. It is the author’s list built from the documents cited; each item gives its basis.
- The documents cited do not decide whether a particular product is a medical device. That depends on its intended use and the vendor’s registration; ask the vendor in writing.
- Items marked “author’s recommendation” are not requirements.
A. Which rules apply to this hospital?
Abu Dhabi and Dubai have separate AI policies. Start by writing down which one binds you.
| No. | What to check | Basis |
|---|---|---|
| 1 | You have recorded which regulator licenses the facility (DoH in Abu Dhabi, DHA in Dubai) and therefore which AI policy applies. A group with hospitals in both emirates keeps one checklist for each. | DoH AI policy (Policy/AI/0.9), section 4; DHA policy DHA/HISHD/PP-09, sections 1 and 2 |
| 2 | You have checked the DHA policy’s current version: its control table lists a revision date of 1 July 2026, so a newer text may exist. | DHA/HISHD/PP-09, control table |
| 3 | The vendor has said in writing whether it treats the product as a medical device and which registration it holds. You have asked your regulatory team about the Ministry of Health and Prevention’s requirements, which this site has not read. | Author’s recommendation |
B. Digital product status and risk tier (Abu Dhabi)
Since August 2026 the Digital Products Governance Standard treats AI-powered software as a digital product with named owners.
| No. | What to check | Basis |
|---|---|---|
| 4 | The product has a named Digital Product Owner and a Digital Product Architect (or equivalents), and a feasibility study and risk assessment were done before it started. | DoH/ST/DHS/DPGS/V1/26, sections 3.2.3.2 and 3.2.4.1 |
| 5 | The risk tier is recorded in a risk register with an owner: very high risk is prohibited, high risk needs conformity assessments before and after deployment, medium risk needs governance and risk reporting, low risk needs monitoring. | DoH/ST/DHS/DPGS/V1/26, sections 3.2.8.2.1 and 3.2.8.2.2 |
| 6 | A new medical device, or an existing one with cybersecurity considerations, is evaluated by DoH’s Health Technology Assessment department before implementation. | DoH device cybersecurity guideline, section 3.6 |
C. What the vendor must show
The Dubai policy has the most specific disclosure list. Abu Dhabi’s policy asks for certification and validation statements.
| No. | What to check | Basis |
|---|---|---|
| 7 | The vendor’s disclosure covers which functions are AI-enabled, how the solution was validated, the data sets used, expected outcomes, the professional’s role in the final decision, the type of algorithm, the limits of the data and algorithms, and how it is integrated into care. | DHA/HISHD/PP-09, section 4.3.2 |
| 8 | Independent validation by a competent third party exists, or the governance group has recorded why it accepts the risk. | DHA/HISHD/PP-09, section 4.3.3 (the policy requires it); the recorded decision is the author’s recommendation |
| 9 | For Abu Dhabi, the tool shows certification of the software and of major upgrades from recognised agencies, compliance with ADSSSA regulations, and auditable validation statements. | DoH AI policy, section 7.1.2 |
| 10 | Designated users can override or reverse the tool’s significant decisions, and the tool has a way to appeal them. | DHA/HISHD/PP-09, section 4.2.3 |
D. Security, updates and incidents
Updates change a tool after you approved it. Ask how they reach you before signing.
| No. | What to check | Basis |
|---|---|---|
| 11 | For connected devices and software you hold the vendor’s MDS2 security disclosure and know how patches, security alerts and recalls are communicated. | DoH device cybersecurity guideline, section 3.6 |
| 12 | The device is in an inventory with its software and firmware version, operating system and network configuration. | DoH device cybersecurity guideline, section 3.4 |
| 13 | The incident card lists the clocks: deaths, serious injuries and malfunctions as soon as possible and within five days; follow-up within 15 days; other reports within 90 days; connected-device cyber incidents immediately to the Abu Dhabi Healthcare Cybersecurity Emergency Response Team. | DoH/ST/HLS/SMDR/V2/26, section 3.1; DoH device cybersecurity guideline, sections 3.5 and 3.6 |
E. What the hospital does itself
A vendor’s paperwork does not replace the hospital’s own governance.
| No. | What to check | Basis |
|---|---|---|
| 14 | The hospital has clear governance on AI use, has stated where AI enters the process and the role of the physician or practitioner, and audits AI functionality regularly. | DoH AI policy, section 7.2 |
| 15 | Real-world results are compared with the vendor’s validation results and significant gaps trigger further inspection. Someone is named to report incidents to DoH or DHA. | DHA/HISHD/PP-09, sections 4.6.11 and 4.8.1; DoH AI policy, sections 9.2 and 9.3 |
Next
Frequently asked questions
- Does a vendor’s validation mean the tool is right for our hospital?
- No. Both policies treat AI as supportive technology: a human makes the final decision. The Dubai policy asks that actual outcomes in clinical practice be compared with those from training and validation, with significant gaps leading to further inspection.
- A vendor says its product is not a medical device. What do we do?
- Ask for the reasoning in writing and take it to your regulatory team. This site has not read the Ministry of Health and Prevention’s device rules, so it cannot say how a product is classified. The Abu Dhabi digital products standard still treats AI-powered software as a digital product with an owner, an architect and a risk tier.
- Which deadlines apply if an AI-enabled device has a serious event?
- Under DoH’s medical device reporting standard (effective October 2026), deaths, serious injuries and malfunctions are reported as soon as possible and not later than five days from awareness, with follow-up reports within 15 days. Other reports are due within 90 days. Facilities with access to Malaffi use it as the primary route.
Sources and date checked
- Abu Dhabi DoH — Policy on Use of Artificial Intelligence (AI) in the Healthcare Sector of the Emirate of Abu Dhabi (Policy/AI/0.9, version 0.9, 30 April 2018) (opens in a new tab)
- Dubai Health Authority — Artificial Intelligence in the Healthcare (policy DHA/HISHD/PP-09, issue date 1 July 2021) (opens in a new tab)
- Abu Dhabi DoH — Digital Products Governance Standard (DoH/ST/DHS/DPGS/V1/26, published March 2026, effective August 2026) (opens in a new tab)
- Abu Dhabi DoH — Standard on Medical Device Reporting (MDR) (DoH/ST/HLS/SMDR/V2/26, published July 2026, effective October 2026) (opens in a new tab)
- Abu Dhabi DoH — Medical Device Cybersecurity in Healthcare Facilities Guideline (DOH/GL/0000002397/24, published November 2026, effective January 2027) (opens in a new tab)
Sources checked November 15, 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.