<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/in/rss-styles.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hospital AI Lab</title><description>Columns on the practical side of medical AI in the UAE: Abu Dhabi DoH and Dubai DHA policies, patient data rules, device security and what hospital teams should ask vendors.</description><link>https://hospital-ai-lab.com/in/</link><language>en</language><atom:link href="https://hospital-ai-lab.com/in/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Mon, 16 Nov 2026 00:00:00 GMT</lastBuildDate><item><title>Dubai AI policy: what hospitals must do once AI is live</title><link>https://hospital-ai-lab.com/in/blog/2026-11-16-dubai-dha-ai-policy-end-user-duties-override-report-audit/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-16-dubai-dha-ai-policy-end-user-duties-override-report-audit/</guid><description>Dubai&apos;s AI policy sets duties for end users: designated overrides, incident reports to DHA and independent audits. What the text says, in plain words.</description><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;A radiology tool is live, an alert looks wrong at 3 a.m., and the charge nurse asks who is allowed to overrule it and who must be told. Dubai’s health regulator answers these questions in its AI policy, in a section aimed at “end users” such as hospitals and clinics. This post reads only that policy document, the Dubai Health Authority (DHA) policy “Artificial Intelligence in the Healthcare” (reference DHA/HISHD/PP-09). It is general information, not legal advice, and other Dubai or federal rules may apply too.&lt;/p&gt;
&lt;h2 id=&quot;who-the-policy-speaks-to&quot;&gt;Who the policy speaks to&lt;/h2&gt;
&lt;p&gt;The document lists duties for several groups. Section 4.8 is headed “End users of AI solutions in the Emirate of Dubai must”, and it is the part most relevant to a hospital that has bought an AI tool. The policy’s header shows an issue date of 1 July 2021 and an effective date of 1 October 2021. It also shows a revision date of 1 July 2026, so check with DHA whether a newer version exists before relying on this summary.&lt;/p&gt;
&lt;h2 id=&quot;overrides-and-appeals&quot;&gt;Overrides and appeals&lt;/h2&gt;
&lt;p&gt;Two design requirements matter for daily work. Section 4.4.2 says AI solutions that may directly affect people’s lives in a significant way must be designed with utmost care, and must be able to be overridden, or their decisions reversed, by designated end users. Section 4.2.3 says AI solutions must have built-in appeals procedures so that users can challenge significant decisions. In practice, “designated” suggests the hospital should decide in advance who holds the override, rather than leaving it to whoever is on shift.&lt;/p&gt;
&lt;h2 id=&quot;watching-the-tool-in-real-use&quot;&gt;Watching the tool in real use&lt;/h2&gt;
&lt;p&gt;Section 4.6.11 says the performance of an AI tool must be monitored in clinical practice, and that actual outcomes must be compared with those obtained in training and validation. Any significant discrepancy must call for further inspection. Section 4.6.13 adds that the tool must be equipped with “graceful degradation” mechanisms, meaning automatic alerts and gradual operation cessation. These sit in the part of the policy addressed to the tool, so ask the vendor to show you how each one works.&lt;/p&gt;
&lt;h2 id=&quot;what-end-users-must-do&quot;&gt;What end users must do&lt;/h2&gt;
&lt;p&gt;Under section 4.8, end users must:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;report to DHA’s Health Regulation Sector all known or suspected incidents or deficiencies related to AI solutions used in their facility (4.8.1), and any implementation issues that could affect patient safety (4.8.2);&lt;/li&gt;
&lt;li&gt;give clear guidelines and boundaries on access to and sharing of patient information (4.8.3);&lt;/li&gt;
&lt;li&gt;make sure everyone involved, including patients, receives education on AI and its effective use (4.8.4);&lt;/li&gt;
&lt;li&gt;conduct regular audits of AI functionality by an independent third party, reporting to DHA as needed (4.8.5);&lt;/li&gt;
&lt;li&gt;submit end-user feedback to DHA and to the manufacturing company (4.8.6).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The policy gives no deadline for incident reports in the sections we read. Do not borrow a number from another emirate or country.&lt;/p&gt;
&lt;h2 id=&quot;a-one-page-checklist-for-a-ward&quot;&gt;A one-page checklist for a ward&lt;/h2&gt;
&lt;p&gt;These are our suggestions drawn from the policy, not requirements it states.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Name the person who may override the AI, and write down how.&lt;/li&gt;
&lt;li&gt;Put a “who do we tell” line on the unit card: your internal safety lead, who then decides on the report to DHA.&lt;/li&gt;
&lt;li&gt;Schedule an independent audit and note who pays for it.&lt;/li&gt;
&lt;li&gt;Keep a short record of staff and patient education on the tool.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Dubai’s AI policy expects designated end users to be able to override or reverse significant AI decisions, with built-in appeals (sections 4.4.2 and 4.2.3).&lt;/li&gt;
&lt;li&gt;End users must report AI incidents and patient-safety issues to DHA, arrange regular independent audits and educate staff and patients (section 4.8).&lt;/li&gt;
&lt;li&gt;The policy’s revision date was 1 July 2026, so check the current version with DHA. This is general information, not legal advice.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Source: &lt;a href=&quot;https://www.dha.gov.ae/uploads/082022/Artificial%20Intelligence%20Policy20228457.pdf&quot;&gt;Dubai Health Authority, Artificial Intelligence in the Healthcare, DHA/HISHD/PP-09&lt;/a&gt;, sections 4.2.3, 4.4.2, 4.6.11, 4.6.13 and 4.8. Read on 16 November 2026.&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>AI Tools</category></item><item><title>Abu Dhabi’s AI policy for hospitals: six principles, one checklist</title><link>https://hospital-ai-lab.com/in/blog/2026-11-15-abu-dhabi-doh-ai-policy-six-principles-hospital-checklist/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-15-abu-dhabi-doh-ai-policy-six-principles-hospital-checklist/</guid><description>Is your hospital in Abu Dhabi using AI without a written position? The Department of Health’s policy lists six principles and what end users must do. Here is what it asks, in plain language.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;If your hospital is licensed by the Abu Dhabi Department of Health (DoH) and uses AI in any form, one short document applies to you: the Policy on Use of Artificial Intelligence (AI) in the Healthcare Sector of the Emirate of Abu Dhabi. It is version 0.9, dated 30 April 2018, and its effective date is the date of publication. It is only a few pages long, but it sets the tone for how AI is expected to be run. The sections below give the parts an administrator or nurse leader can act on.&lt;/p&gt;
&lt;h2 id=&quot;who-it-covers&quot;&gt;Who it covers&lt;/h2&gt;
&lt;p&gt;The policy applies to DoH-licensed healthcare providers, UAE-based pharmaceutical manufacturers, healthcare insurers, licensed researchers involved in human research, and every local, national or locally based international end user that uses Abu Dhabi population or patient clinical and non-clinical data in AI work, directly or indirectly. In plain terms: if your tool uses Abu Dhabi patient data, the policy is in the room, whoever built the tool.&lt;/p&gt;
&lt;h2 id=&quot;the-six-guiding-principles&quot;&gt;The six guiding principles&lt;/h2&gt;
&lt;p&gt;The policy names six principles: transparency (AI software should be verifiable and explainable), user assistance or supportive technology, safety and security, privacy, ethics (human dignity and autonomy), and accountability of researchers and developers to users. The second one matters most day to day. The policy defines supportive technology as technology that assists a human decision and does not replace it, so a human makes the final decision and is responsible for the action taken. A discharge-summary drafter, a risk score or a scheduling tool is a helper, not the person in charge.&lt;/p&gt;
&lt;h2 id=&quot;what-it-asks-of-the-hospital&quot;&gt;What it asks of the hospital&lt;/h2&gt;
&lt;p&gt;Healthcare end users other than patients should:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;have clear governance on AI use;&lt;/li&gt;
&lt;li&gt;state where AI enters the process and what the role of the physician or practitioner is;&lt;/li&gt;
&lt;li&gt;set boundaries on access to and sharing of patient information;&lt;/li&gt;
&lt;li&gt;educate everyone involved, including patients;&lt;/li&gt;
&lt;li&gt;audit AI functionality regularly and report to DoH as needed; and&lt;/li&gt;
&lt;li&gt;comply with national and DoH rules on e-health, health information exchange, data protection and information security.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;They must also report all known or suspected AI incidents or deficiencies, and any implementation issue that could affect patient safety.&lt;/p&gt;
&lt;h2 id=&quot;what-it-asks-of-the-tool&quot;&gt;What it asks of the tool&lt;/h2&gt;
&lt;p&gt;For AI tools, the minimum requirements include certification of the software and of upgraded major versions from recognised international agencies, compliance with ADSSSA regulations, and auditable validation statements. Tools should have “graceful degradation”, meaning automatic alerts and gradual cessation if hardware or software malfunctions, and should go through repeated improvement cycles based on end-user feedback sent to the DoH Drug and Medical Products Regulation Department and the manufacturer. They should be subject to audits and comply with DoH’s Health Information Exchange policy.&lt;/p&gt;
&lt;h2 id=&quot;a-one-page-checklist-to-build-from-it&quot;&gt;A one-page checklist to build from it&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Name who owns AI governance in your hospital.&lt;/li&gt;
&lt;li&gt;List each AI tool, where it enters the process and who makes the final decision.&lt;/li&gt;
&lt;li&gt;Ask each vendor for its certification and validation statements, in writing.&lt;/li&gt;
&lt;li&gt;Ask what the tool does when it fails (graceful degradation).&lt;/li&gt;
&lt;li&gt;Decide who reports incidents to DoH, and by what route.&lt;/li&gt;
&lt;li&gt;Plan patient information and staff training.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Abu Dhabi’s AI policy applies to any DoH-licensed provider that uses Abu Dhabi patient data in AI work.&lt;/li&gt;
&lt;li&gt;Its central idea: AI supports a human decision, and a human stays responsible.&lt;/li&gt;
&lt;li&gt;Hospitals are asked for governance, clear roles, data boundaries, education, audits and incident reporting; tools are asked for certification, validation statements and graceful degradation.&lt;/li&gt;
&lt;li&gt;This is general information, not legal advice. Read the policy itself and ask your compliance officer before acting.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://www.doh.gov.ae/-/media/E9C1470A575146B18015DEBE57E47F8D.ashx&quot;&gt;Abu Dhabi Department of Health, Policy on Use of Artificial Intelligence (AI) in the Healthcare Sector of the Emirate of Abu Dhabi, Policy/AI/0.9&lt;/a&gt; (sections 2, 4, 5.3, 7, 9). Read on 15 November 2026.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>AI Tools</category></item><item><title>Using patient records to train AI: what Abu Dhabi’s standard requires</title><link>https://hospital-ai-lab.com/in/blog/2026-11-15-doh-analytics-standard-secondary-use-patient-data-ai-consent/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-15-doh-analytics-standard-secondary-use-patient-data-ai-consent/</guid><description>Before a vendor or research team trains a model on your hospital’s records, read this. Abu Dhabi’s 2026 analytics standard sets consent, anonymisation and re-identification rules.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;“We only use your data to improve the model.” Vendors say it often. In Abu Dhabi, the Department of Health’s Analytics and Reporting Standard (published April 2026, effective May 2026) gives hospital teams a rulebook for exactly that situation, which it calls secondary use: using patient data for a purpose other than the care it was collected for.&lt;/p&gt;
&lt;h2 id=&quot;the-default-anonymised-or-de-identified&quot;&gt;The default: anonymised or de-identified&lt;/h2&gt;
&lt;p&gt;Patient data used for secondary purposes must be anonymised or de-identified unless the patient explicitly permits otherwise or the law requires it. That puts the burden on the project, not on the patient. If a vendor wants identifiable data, ask on what basis: explicit permission or a legal requirement.&lt;/p&gt;
&lt;h2 id=&quot;consent-that-means-something&quot;&gt;Consent that means something&lt;/h2&gt;
&lt;p&gt;The standard requires explicit informed consent before secondary use. Patients may withdraw consent at any time without any effect on their care. For a hospital, that means the consent process and the withdrawal route need an owner, and staff at registration should know what to say when a patient asks.&lt;/p&gt;
&lt;h2 id=&quot;things-that-are-prohibited&quot;&gt;Things that are prohibited&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Using secondary use to deny or limit insurance, employment or other essential services.&lt;/li&gt;
&lt;li&gt;Using personally identifiable data for commercial gain without explicit consent.&lt;/li&gt;
&lt;li&gt;Trying to re-identify anonymised data.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The standard also asks data science and AI teams to embed ethical data use at every stage of the AI system lifecycle.&lt;/p&gt;
&lt;h2 id=&quot;questions-for-a-vendor-or-research-partner&quot;&gt;Questions for a vendor or research partner&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Is the data anonymised or de-identified before it leaves our systems? By whom and how?&lt;/li&gt;
&lt;li&gt;If it is not, what explicit permission or legal requirement do you rely on?&lt;/li&gt;
&lt;li&gt;Will our data be used to train or improve a model that you also sell to others?&lt;/li&gt;
&lt;li&gt;How do we honour a patient’s withdrawal?&lt;/li&gt;
&lt;li&gt;What stops anyone from re-identifying the data?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Where the data is stored matters too: see our post on the Data Access Standard.&lt;/p&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Secondary use of patient data: anonymised or de-identified by default; explicit informed consent required.&lt;/li&gt;
&lt;li&gt;Withdrawal at any time, with no effect on care; re-identification and use to deny essential services are prohibited.&lt;/li&gt;
&lt;li&gt;Put a named owner on consent and withdrawal. This is general information, not legal advice; the federal laws were not read for this post.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://www.doh.gov.ae/-/media/Feature/Resources/Standards/2026/070426Analytics-and-Reporting-Standard.ashx&quot;&gt;Abu Dhabi Department of Health, Analytics and Reporting Standard, DoH/ST/DDGO/AR/V1/2026&lt;/a&gt; (sections 3.2.6.2 and 3.2.6.3). Read on 15 November 2026.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>Column</category></item><item><title>Four risk tiers for hospital AI in Abu Dhabi: where does your tool sit?</title><link>https://hospital-ai-lab.com/in/blog/2026-11-15-doh-digital-products-standard-four-risk-tiers-hospital-ai/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-15-doh-digital-products-standard-four-risk-tiers-hospital-ai/</guid><description>Since August 2026 an Abu Dhabi standard sorts digital products, AI included, into risk tiers and asks for named owners. What a hospital needs before a project starts.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;A new standard from the Abu Dhabi Department of Health (DoH) changes how AI projects begin. The Digital Products Governance Standard (reference DoH/ST/DHS/DPGS/V1/26) was published in March 2026 and takes effect in August 2026. It does not mention AI as an afterthought: its definition of digital products includes systems, applications, collaborative platforms, electronic health records, telemedicine and wearable devices powered by technologies such as robotics, IoT, 5G, blockchain, artificial intelligence, augmented reality and virtual reality. It applies to all DoH stakeholders that develop and manage digital products.&lt;/p&gt;
&lt;h2 id=&quot;two-named-people-one-assessment&quot;&gt;Two named people, one assessment&lt;/h2&gt;
&lt;p&gt;Each digital product needs at least a Digital Product Owner and a Digital Product Architect, or equivalents. They may be dedicated roles or added to existing duties. Before any digital product starts, a feasibility study and risk assessment must be done. Products that DoH requires to be reviewed follow the DoH ADHTAC approval and the web and mobile application approval.&lt;/p&gt;
&lt;p&gt;For an administrator this is practical: when a department proposes an AI tool, ask who the owner and architect are, and where the feasibility study and risk assessment are.&lt;/p&gt;
&lt;h2 id=&quot;the-four-tiers&quot;&gt;The four tiers&lt;/h2&gt;
&lt;p&gt;The standard sorts products by risk:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Very high risk:&lt;/strong&gt; prohibited from deployment.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;High risk:&lt;/strong&gt; conformity assessments before and after deployment, in coordination with the DoH Data and Digital Governance Office.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Medium risk:&lt;/strong&gt; governance policies, standards and risk reporting.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Low and very low risk:&lt;/strong&gt; exempt from formal risk reporting, but their controls must be monitored for effectiveness.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Risk assessments must be documented in a risk register with defined ownership. The standard does not say which tier a given product falls in; that comes from the assessment, so record how your hospital reached its answer.&lt;/p&gt;
&lt;h2 id=&quot;privacy-for-patient-facing-products&quot;&gt;Privacy for patient-facing products&lt;/h2&gt;
&lt;p&gt;A patient-facing product needs a privacy policy, a privacy notice shown at registration or before download with affirmative consent such as an “I Agree” box, a separate affirmative consent for sharing data for a specific purpose that names the recipients and purposes, published procedures for security incidents and breaches, instructions to opt out or withdraw consent, and records of consents. Products developed by or owned by DoH, or marked for government use, must integrate UAE Pass for authentication.&lt;/p&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The standard covers AI-powered digital products in Abu Dhabi and applies from August 2026.&lt;/li&gt;
&lt;li&gt;Name an owner and an architect, and do a feasibility study and risk assessment before the project starts.&lt;/li&gt;
&lt;li&gt;Know the four tiers; keep a risk register with owners.&lt;/li&gt;
&lt;li&gt;This is general information, not legal advice. Confirm applicability with your compliance team.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://www.doh.gov.ae/-/media/Feature/Resources/Standards/2026/24032026--Digital-Products-Governance-Standard.ashx&quot;&gt;Abu Dhabi Department of Health, Digital Products Governance Standard, DoH/ST/DHS/DPGS/V1/26&lt;/a&gt; (cover page and sections 2.6, 3.2.3.2, 3.2.4.1, 3.2.6, 3.2.8.2). Read on 15 November 2026.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>AI Tools</category></item><item><title>Dubai hospital buying AI? What the vendor must disclose and who validates it</title><link>https://hospital-ai-lab.com/in/blog/2026-11-15-dubai-dha-ai-policy-vendor-disclosure-independent-validation/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-15-dubai-dha-ai-policy-vendor-disclosure-independent-validation/</guid><description>A Dubai Health Authority policy lists what an AI vendor must tell you and asks for independent validation. Here is the list, so you can put it in your next proposal review.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;When a vendor presents an AI product to a Dubai hospital, the questions that matter are rarely on the slides. The Dubai Health Authority (DHA) policy “Artificial Intelligence in the Healthcare” (reference DHA/HISHD/PP-09) turns many of them into a list. Its control table gives an issue date of 1 July 2021, an effective date of 1 October 2021 and a revision date of 1 July 2026, so check DHA for a newer version before you rely on this summary.&lt;/p&gt;
&lt;h2 id=&quot;who-it-covers&quot;&gt;Who it covers&lt;/h2&gt;
&lt;p&gt;The policy applies to DHA-licensed facilities and professionals that use AI, to national and locally based international AI developers that use Dubai data, and to UAE-based pharmaceutical manufacturers, health insurers, public health entities and researchers using AI in Dubai.&lt;/p&gt;
&lt;h2 id=&quot;what-a-vendor-must-disclose&quot;&gt;What a vendor must disclose&lt;/h2&gt;
&lt;p&gt;The policy says the disclosure about an AI solution must cover:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;which functions are AI-enabled;&lt;/li&gt;
&lt;li&gt;how the solution was validated;&lt;/li&gt;
&lt;li&gt;which data sets were or must be used;&lt;/li&gt;
&lt;li&gt;the expected outcomes;&lt;/li&gt;
&lt;li&gt;the healthcare professional’s role in the final decision;&lt;/li&gt;
&lt;li&gt;the type of algorithm;&lt;/li&gt;
&lt;li&gt;the ethical examination of how data is used;&lt;/li&gt;
&lt;li&gt;how performance must be validated;&lt;/li&gt;
&lt;li&gt;how the solution is integrated into care; and&lt;/li&gt;
&lt;li&gt;the limits of the data and algorithms.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can turn that list straight into a vendor questionnaire. A vendor who cannot answer “what are the limits of your data?” in writing has told you something useful.&lt;/p&gt;
&lt;h2 id=&quot;independent-validation&quot;&gt;Independent validation&lt;/h2&gt;
&lt;p&gt;All AI solutions for healthcare must also go through independent validation by a competent third party. A vendor’s own validation study is the start of the conversation, not the end of it.&lt;/p&gt;
&lt;h2 id=&quot;oversight-after-go-live&quot;&gt;Oversight after go-live&lt;/h2&gt;
&lt;p&gt;AI solutions with a significant effect on people’s lives must be designed so that designated end users can override them or reverse their decisions, and they must have built-in appeals procedures. Performance must be monitored in clinical practice and actual outcomes compared with those from training and validation; significant gaps lead to further inspection. End users must report incidents and patient-safety issues to DHA’s Health Regulation Sector and have AI functionality audited regularly by an independent third party.&lt;/p&gt;
&lt;h2 id=&quot;what-a-nurse-leader-can-ask&quot;&gt;What a nurse leader can ask&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Who can override this tool on the ward, and how?&lt;/li&gt;
&lt;li&gt;What will we compare real results against?&lt;/li&gt;
&lt;li&gt;Who do staff tell when something looks wrong?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Dubai’s policy gives you a disclosure list to hold vendors to, plus independent third-party validation.&lt;/li&gt;
&lt;li&gt;Overrides, appeals, monitoring against validation results and incident reporting are part of the expected set-up.&lt;/li&gt;
&lt;li&gt;Check DHA for a version newer than the one dated 2021, and ask your compliance team how it fits with other Dubai rules.&lt;/li&gt;
&lt;li&gt;This is general information, not legal advice.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://www.dha.gov.ae/uploads/082022/Artificial%20Intelligence%20Policy20228457.pdf&quot;&gt;Dubai Health Authority, Artificial Intelligence in the Healthcare, DHA/HISHD/PP-09&lt;/a&gt; (cover page and sections 1, 2, 4.2.3, 4.3.2, 4.3.3, 4.4.2, 4.6.11, 4.8.1, 4.8.2, 4.8.5). Read on 15 November 2026.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>AI Tools</category></item><item><title>Connected devices and AI: questions DoH’s new security guideline lets you ask</title><link>https://hospital-ai-lab.com/in/blog/2026-11-15-doh-medical-device-cybersecurity-guideline-ai-vendor-questions/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-15-doh-medical-device-cybersecurity-guideline-ai-vendor-questions/</guid><description>Abu Dhabi’s medical device cybersecurity guideline names what vendors must provide and where to report an attack. Questions for your next vendor meeting and an incident card.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;On the wards, many devices now run software and sit on the hospital network. The Department of Health (DoH) in Abu Dhabi published its Medical Device Cybersecurity in Healthcare Facilities Guideline (reference DOH/GL/0000002397/24) in November 2026. It takes effect in January 2027 and lists October 2029 as its revision date.&lt;/p&gt;
&lt;h2 id=&quot;what-it-covers-and-who-it-applies-to&quot;&gt;What it covers and who it applies to&lt;/h2&gt;
&lt;p&gt;The guideline covers standalone medical device software, for example diagnostic or therapeutic applications, and software embedded in hardware such as MRI machines, infusion pumps and ventilators. It applies to implantable, mobile, software-only and network-connected devices. It applies to healthcare facilities, providers, IT departments, biomedical and clinical engineers, distributors and vendors, and manufacturers.&lt;/p&gt;
&lt;h2 id=&quot;what-vendors-are-asked-to-provide&quot;&gt;What vendors are asked to provide&lt;/h2&gt;
&lt;p&gt;Manufacturers, distributors and vendors are required to integrate security-by-design, conduct pre- and post-market cybersecurity risk assessments, provide transparent documentation including Manufacturer Disclosure Statements for Medical Device Security (MDS2), deliver timely updates and patches, keep clear channels for security alerts and recalls, and secure the supply chain.&lt;/p&gt;
&lt;p&gt;So, in a vendor meeting, ask:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Can we have your MDS2 for this product and version?&lt;/li&gt;
&lt;li&gt;How are patches delivered, and how fast after a vulnerability is found?&lt;/li&gt;
&lt;li&gt;Where do security alerts and recalls reach us?&lt;/li&gt;
&lt;li&gt;How do you secure your own supply chain?&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;what-hospitals-are-asked-to-do&quot;&gt;What hospitals are asked to do&lt;/h2&gt;
&lt;p&gt;The guideline asks hospitals to keep an inventory of all medical devices with software and firmware versions, operating system, IP and MAC addresses and network configuration; assess threats and vulnerabilities with the STRIDE method; segment networks; apply software updates and patches promptly; keep backup and recovery plans; run incident response plans with drills; and handle decommissioning securely, including data wiping or physical destruction.&lt;/p&gt;
&lt;h2 id=&quot;reporting&quot;&gt;Reporting&lt;/h2&gt;
&lt;p&gt;For any cybersecurity information or incident involving the Internet of Medical Things, including vulnerabilities or breaches, a healthcare entity must report to the Abu Dhabi Healthcare Cybersecurity Emergency Response Team (ADHCCERT) immediately upon discovery and without delay. Adverse events related to medical devices, including those linked to software or patch updates, go without delay to the DoH Pharmacovigilance team under the medical device reporting standard.&lt;/p&gt;
&lt;p&gt;Any new medical device, or an existing one with cybersecurity considerations, intended for use in Abu Dhabi healthcare facilities must be evaluated by DoH’s Health Technology Assessment department before implementation.&lt;/p&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The guideline takes effect in January 2027; ask AI and device vendors for their MDS2 and patch and recall process now.&lt;/li&gt;
&lt;li&gt;Keep a device inventory with software versions; report connected-device cyber incidents to ADHCCERT immediately.&lt;/li&gt;
&lt;li&gt;New devices need a DoH Health Technology Assessment evaluation before implementation.&lt;/li&gt;
&lt;li&gt;This is general information, not legal advice.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://www.doh.gov.ae/-/media/Feature/Resources/Standards/2026/Medical-Device-Cybersecurity-in-healthcare-facilities-Guideline301026.ashx&quot;&gt;Abu Dhabi Department of Health, Medical Device Cybersecurity in Healthcare Facilities Guideline, DOH/GL/0000002397/24&lt;/a&gt; (cover page and sections 1.1, 3.4, 3.5, 3.6). Read on 15 November 2026.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>News</category></item><item><title>Malaffi consent and the 60-day breach notice, in plain English</title><link>https://hospital-ai-lab.com/in/blog/2026-11-15-malaffi-health-information-exchange-consent-60-day-breach-notice/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-15-malaffi-health-information-exchange-consent-60-day-breach-notice/</guid><description>Does your AI tool read or write data through Abu Dhabi’s health information exchange? Two clauses in the exchange policy decide what consent and breach deadlines you work to.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;AI tools that read from or write to Abu Dhabi’s health information exchange, known as Malaffi, inherit its rules. The Department of Health (DoH) set them in its Policy on the Abu Dhabi Health Information Exchange (reference DOH/POL/STR/HIE/1.1/2020, version 1.1), effective 16 April 2020. Two parts matter most to administrators and nurse leaders: consent and breaches.&lt;/p&gt;
&lt;h2 id=&quot;consent&quot;&gt;Consent&lt;/h2&gt;
&lt;p&gt;DoH requires healthcare facilities to seek patient consent for sharing patient data through the exchange. Facilities are to build this into their standard consent forms and to tell patients that sharing relevant health information with the exchange is part of their treatment. Where consent is unavailable for any reason, for example for legacy data, DoH requires and authorises facilities to share and receive the data as set out in DoH’s instructions.&lt;/p&gt;
&lt;p&gt;For an AI project this means: if your tool uses exchange data, check how consent was obtained and on what basis, and do not assume that agreement to share for treatment also covers other purposes. (Secondary use has its own standard; see our post on the Analytics and Reporting Standard.)&lt;/p&gt;
&lt;h2 id=&quot;breaches-two-clocks&quot;&gt;Breaches: two clocks&lt;/h2&gt;
&lt;p&gt;The breach clause sets two deadlines:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Affected patients must be notified without undue delay and in no event later than 60 days from discovery.&lt;/li&gt;
&lt;li&gt;The clause on the exchange’s duties says DoH must be notified as soon as reasonably practicable after a breach is determined, and in any event within 5 business days.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The same clause has the exchange develop internal breach procedures, investigate root causes and set preventive plans, and it holds the exchange responsible for unauthorised disclosure by its own staff.&lt;/p&gt;
&lt;h2 id=&quot;what-to-put-in-your-own-contract&quot;&gt;What to put in your own contract&lt;/h2&gt;
&lt;p&gt;When an AI vendor connects to the exchange or to your records that feed it:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Ask how quickly the vendor will tell you of any breach, so that you can meet the 60-day patient notice and any other clock that applies to you.&lt;/li&gt;
&lt;li&gt;Ask who talks to patients and who talks to DoH.&lt;/li&gt;
&lt;li&gt;Ask for the breach procedure in writing.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exchange consent is sought from patients; legacy data may be shared as DoH instructs.&lt;/li&gt;
&lt;li&gt;Breach clocks in the exchange policy: patients within 60 days of discovery; DoH within 5 business days of determining a breach occurred.&lt;/li&gt;
&lt;li&gt;Put the clocks in vendor contracts and on your incident card. This is general information, not legal advice; the federal laws were not read for this post.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://www.doh.gov.ae/-/media/A78104416DF2440E89AC90FB75F11055.ashx&quot;&gt;Abu Dhabi Department of Health, Policy on the Abu Dhabi Health Information Exchange, DOH/POL/STR/HIE/1.1/2020&lt;/a&gt; (sections 4.2.1.2, 4.2.2 and 4.3.17). Read on 15 November 2026.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>AI Tools</category></item><item><title>AI device incident in Abu Dhabi: the 5, 15 and 90 day reporting clocks</title><link>https://hospital-ai-lab.com/in/blog/2026-11-15-medical-device-software-incident-5-15-90-day-clock-abu-dhabi/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-15-medical-device-software-incident-5-15-90-day-clock-abu-dhabi/</guid><description>Who must report a serious event involving a medical device or its software, how fast, and through which channel? The DoH reporting standard, version 2, in plain language.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;When software that counts as part of a medical device misbehaves, the hospital’s first question is “who do we tell, and by when?” In Abu Dhabi the answer sits in the Department of Health’s Standard on Medical Device Reporting (MDR), version 2, published in July 2026 and effective October 2026.&lt;/p&gt;
&lt;h2 id=&quot;the-three-clocks&quot;&gt;The three clocks&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Five days.&lt;/strong&gt; For deaths, serious injuries and malfunctions, and events that need remedial action to prevent an unreasonable risk of substantial harm to public health, the standard says report as soon as possible from the date of awareness and not later than five days. Reporting may start as an initial report if follow-up reports come within 15 days.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fifteen days.&lt;/strong&gt; Manufacturers and others who place devices on the market must submit, within 15 days after receipt, required information on deaths, serious injuries and malfunctions that was not available when the initial report was filed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ninety days.&lt;/strong&gt; Other reports, such as use errors, product quality issues and therapeutic failures, are due within 90 days of receiving the related reports, when the reporting is in the form of complete reports.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;who-reports&quot;&gt;Who reports&lt;/h2&gt;
&lt;p&gt;Healthcare facilities and professionals, and manufacturers, marketing authorisation holders, importers, authorised agents, distributors and anyone who places a device on the market.&lt;/p&gt;
&lt;h2 id=&quot;which-channel&quot;&gt;Which channel&lt;/h2&gt;
&lt;p&gt;Facilities and professionals with access to the Malaffi platform must use it as the primary method. Those without access, or during downtime, use the online fillable PDF form.&lt;/p&gt;
&lt;h2 id=&quot;a-practical-card-for-the-nurses-station&quot;&gt;A practical card for the nurses’ station&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Something harmful or dangerous happened with a device or its software: tell the person named on your incident card at once.&lt;/li&gt;
&lt;li&gt;That person reports to DoH as soon as possible, and no later than five days from awareness.&lt;/li&gt;
&lt;li&gt;Keep the vendor in the loop; they have their own duties.&lt;/li&gt;
&lt;li&gt;Lower-severity issues such as use errors go into the 90-day route.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Connected-device cyber incidents have a separate, faster route; see our post on the DoH cybersecurity guideline.&lt;/p&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Serious device events: report as soon as possible and not later than five days; follow-ups within 15 days; other reports within 90 days.&lt;/li&gt;
&lt;li&gt;Use Malaffi as the primary route if you have access.&lt;/li&gt;
&lt;li&gt;Put the clocks on one incident card. This is general information, not legal advice.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://www.doh.gov.ae/-/media/Feature/Resources/Standards/18826-Medical-Device-Reporting-Standard-MDR.ashx&quot;&gt;Abu Dhabi Department of Health, Standard on Medical Device Reporting (MDR), DoH/ST/HLS/SMDR/V2/26&lt;/a&gt; (cover page and sections 3.1, 3.2.3, 3.3.1). Read on 15 November 2026.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>AI Tools</category></item><item><title>Can our hospital send patient data to an AI cloud outside the UAE?</title><link>https://hospital-ai-lab.com/in/blog/2026-11-15-uae-health-data-stay-in-country-doh-data-access-standard-ai-cloud/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-15-uae-health-data-stay-in-country-doh-data-access-standard-ai-cloud/</guid><description>In Abu Dhabi the short answer is: not without DoH’s authorisation. What the Data Access Standard says about storage, remote access and cloud providers, and what to ask a vendor.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Many AI tools run in a cloud somewhere. For an Abu Dhabi hospital, where that somewhere is can decide whether the tool may be used at all. Two Department of Health (DoH) standards answer the question: the Data Access Standard (published January 2026) and the Data Sharing, Integration and Interoperability Standard (published December 2025, effective April 2026).&lt;/p&gt;
&lt;h2 id=&quot;what-the-data-access-standard-says&quot;&gt;What the Data Access Standard says&lt;/h2&gt;
&lt;p&gt;The standard says no storage, replication or transfer of healthcare data outside the UAE may occur without explicit DoH authorisation. Remote access from outside the UAE is permitted only in exceptional circumstances with prior written approval from DoH. Entities that use external or cloud providers must keep data residency within the UAE, with contractual and technical safeguards against unauthorised cross-border transfer or access. The standard takes effect six months from the date of publishing.&lt;/p&gt;
&lt;h2 id=&quot;what-the-sharing-standard-adds&quot;&gt;What the sharing standard adds&lt;/h2&gt;
&lt;p&gt;The data sharing standard says that data labelled under the data classification standard must not be transferred, stored, shared, processed or disseminated outside the UAE unless DoH issues a valid and specific exemption.&lt;/p&gt;
&lt;h2 id=&quot;what-this-means-when-a-vendor-pitches-you&quot;&gt;What this means when a vendor pitches you&lt;/h2&gt;
&lt;p&gt;“Our model runs on a global cloud” is not an answer. Ask for these in writing:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Where is our data stored, including logs and backups?&lt;/li&gt;
&lt;li&gt;Where is it processed, including by any sub-processor?&lt;/li&gt;
&lt;li&gt;Does anyone outside the UAE have remote access, for support or otherwise? On whose written approval?&lt;/li&gt;
&lt;li&gt;Which contract clauses and technical measures stop unauthorised cross-border transfer?&lt;/li&gt;
&lt;li&gt;If an exemption is needed, who requests it, and has DoH granted it?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Staff who use free consumer chatbots are a separate risk: a hospital policy should say which tools are approved and which data may never be typed into any other tool. That is the author’s recommendation, not a quotation from the standard.&lt;/p&gt;
&lt;h2 id=&quot;what-we-did-not-read&quot;&gt;What we did not read&lt;/h2&gt;
&lt;p&gt;This summary rests on the DoH documents. We could not read the federal laws themselves, because the federal legislation portal refused automated requests, so we do not say what federal law adds. For Dubai facilities, ask DHA and your counsel which rules apply.&lt;/p&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Abu Dhabi: no storage, replication or transfer of healthcare data outside the UAE without explicit DoH authorisation.&lt;/li&gt;
&lt;li&gt;Remote access from abroad needs prior written DoH approval and is only for exceptional circumstances.&lt;/li&gt;
&lt;li&gt;Cloud contracts must keep data residency in the UAE with contractual and technical safeguards.&lt;/li&gt;
&lt;li&gt;This is general information, not legal advice.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://www.doh.gov.ae/-/media/Feature/Resources/Standards/2026/11126_Data_Access_Standard.ashx&quot;&gt;Abu Dhabi Department of Health, Data Access Standard&lt;/a&gt; (section 3.2.1.2), &lt;a href=&quot;https://www.doh.gov.ae/-/media/Feature/Resources/Standards/2026/Data-Sharing-Integration-and-Interoperability-Standard.ashx&quot;&gt;Data Sharing, Integration and Interoperability Standard&lt;/a&gt; (section 2.1.8). Read on 15 November 2026.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>AI Tools</category></item></channel></rss>