Hospital AI Lab Practical information on medical AI for UAE hospitals

Updated:

Templates: generative AI policy and 20 vendor questions

“We don’t know where to start writing” is a common problem for hospitals. Here are four drafts: press the button, copy, and replace “__” with your own details.

Checked: November 15, 2026 · For: hospital administration and IT

Before you use these
These are the author’s drafts, not legal advice and not a version that is ready to copy as is. Adapt them to the size, systems and contracts of your hospital, and show them to counsel or your compliance office before they become documents.

Contents

Related pages: Roadmap, Patient data checklist, Checklist: AI vendors and documents.

1. Generative AI use policy

A page you can hand to staff. Replace "__" with your hospital’s details.

GENERATIVE AI USE POLICY, "__" HOSPITAL (DRAFT)

1. Purpose
   Sets rules for staff of "__" when they use generative AI tools (chatbots, summarising tools, translation tools).

2. What must NOT be entered
   - Patient names, Emirates ID numbers, medical record numbers, dates of birth, addresses, phone numbers, or the content of patient records.
   - Images or recordings that could identify a patient.
   - Contracts, or restricted financial and personnel data.
   Exception: a tool that "__" has approved in writing for that data type (see clause 3).

3. Approved tools and permitted data
   Only tools on the approved list kept by "__" (owner: __). For each approved tool the list states which data types may be entered, following our data classification, and states where the tool stores and processes data (inside the UAE unless DoH has authorised otherwise). Using an unapproved tool for work is not allowed.

4. Review of output
   A person is responsible for every AI-generated text used in work. Generative AI can state fictitious content as fact, so check facts, numbers and names against the source before use.
   AI output is never entered in a patient record until the responsible clinician has reviewed and approved it. Where AI-generated content is shown to others, label it as AI-generated.

5. Reporting
   If patient information was entered into an unapproved tool, report it the same day to __ (name, phone __). Do not try to delete it yourself first.

6. Training
   Staff who use AI tools are trained on this policy, including the data input restrictions and how to report an incident, and are re-trained after significant updates. Owner: __. Review date: __.

Basis of the template

  • The data input rules follow the Abu Dhabi Data Access Standard (no storage, replication or transfer of healthcare data outside the UAE without explicit DoH authorisation, section 3.2.1.2) and the DoH AI policy (boundaries on access to and sharing of patient information, section 7.2).
  • Human review of output follows both AI policies, which describe AI as supportive technology where a human makes the final decision.
  • The rest is the author’s proposal.

2. Twenty questions for a vendor

Print it and take it to the vendor presentation. Write the answers down.

TWENTY QUESTIONS FOR AN AI VENDOR (DRAFT)
Write the answers down and attach them to the contract.

Status and rules
1. Which emirate's rules do you design for (Abu Dhabi DoH, Dubai DHA, or both), and which policy documents do you say you meet?
2. Do you treat this product as a medical device? Which registration do you hold, and may we see it?
3. What is the intended use statement, and does our planned use match it?
4. Which functions are AI-enabled, and what type of algorithm is used?
5. How was the solution validated, on which data sets, and has a competent third party validated it independently?
6. What are the limits of the data and the algorithm, and what outcomes should we expect?

Performance and updates
7. How will we be told before an update reaches our wards, and can we delay it?
8. How is an update rolled back, and who tells our staff?
9. Which real-world performance figures do you monitor after go-live, and will you share them with us so we can compare them with your validation results?
10. What does the tool do when its service or hardware fails (graceful degradation), and what is our fallback?

Patient data
11. Where is our data stored and processed, including logs and backups? Does anything leave the UAE, and with whose authorisation?
12. Do you use our data to train or improve your models? If so, is it anonymised or de-identified, and on what consent basis?
13. Which sub-processors (cloud, model providers) touch our data, and where are they located?
14. How and how fast do you tell us of a breach, and who answers at night?
15. How is data erased when the contract ends, including logs, backups and sub-processors?

Security and operations
16. Will you give us your MDS2 security disclosure, and how do patches, security alerts and recalls reach us?
17. Who can override the tool's decisions, and how can an affected person appeal?
18. Which decisions affecting patients will the output feed into, and does a clinician make the final decision?
19. What does the exit plan look like, including return or erasure of data?
20. What is your support commitment and escalation path for safety issues?

Basis of the template

  • Questions 4–6 and 17–18: the Dubai policy’s disclosure and validation duties (DHA/HISHD/PP-09, sections 4.2.3, 4.3.2 and 4.3.3).
  • Questions 9–10: DHA/HISHD/PP-09, section 4.6.11, and the DoH AI policy’s graceful degradation (section 7.1.2).
  • Questions 11–13 and 15: Data Access Standard section 3.2.1.2 and Analytics and Reporting Standard section 3.2.6.
  • Question 16: DoH device cybersecurity guideline, section 3.6.
  • The other questions are the author’s proposals, not legal requirements.

3. Text for patients

A short example of how to tell a patient that the hospital uses an AI tool. Match it to your actual practice.

TEXT FOR PATIENTS: OUR USE OF AN AI TOOL (EXAMPLE)

"__" hospital uses an AI tool for __ (for example: drafting discharge summaries, which a clinician then checks).
The tool does not make the final decision about your treatment. A member of our staff reviews what it produces.
We tell you which of your information the tool uses and why. You can ask us about it and about alternatives.
Questions: __ (name or office, phone, email).

Basis of the template

  • The DoH AI policy asks end-users to educate everyone involved, including patients (section 7.2); the Digital Products Governance Standard asks patient-facing products for a privacy notice and records of consent (section 3.2.6).
  • The wording is the author’s example, not required language.

4. Incident record

Turn the procedure into one fillable page and keep it where people will find it at night and on weekends.

AI / DATA / DEVICE INCIDENT RECORD (DRAFT)

Date and time discovered: __   Discovered by: __   Reported to: __
What happened (one sentence, no patient names): __
Systems, devices and data involved (type of data, approximate number of individuals): __
Kind of incident (tick): AI tool error or safety issue __   Medical device event __   Connected-device cyber incident __   Data breach __

Containment done: __   By: __   Time: __
Reporting clocks (check the current text of each document; keep the rows that apply):
  - Connected medical device cyber incident: report to the Abu Dhabi Healthcare Cybersecurity Emergency Response Team immediately upon discovery. Reported on: __
  - Death, serious injury or malfunction involving a device: as soon as possible and not later than 5 days from awareness (follow-up within 15 days). Via Malaffi where you have access. Reported on: __
  - Breach of data in the Abu Dhabi health information exchange: affected patients notified without undue delay and within 60 days of discovery; DoH notified by the exchange side within 5 business days of determining it occurred. Done on: __
  - Known or suspected AI incident or implementation issue affecting patient safety: report to DoH (Abu Dhabi) or DHA Health Regulation Sector (Dubai). Reported on: __
Affected individuals notified: who sends: __   Method: __   Sent on: __
Vendor involved: __   (contact: __, 24-hour line: __)

Recorded: __ (who contacted whom, and when).

Basis of the template

  • The clocks come from the DoH device cybersecurity guideline (sections 3.5 and 3.6), the medical device reporting standard (section 3.1), the HIE policy (section 4.3.17) and the two AI policies. Check each document for later revisions; this page does not state the federal laws’ own breach rules, which were not read.

Sources and date checked

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.