Summary
A clinic in the UAE buying an AI scribe faces questions the US-built market was not designed for. Where the patient data physically lives, how it meets the Personal Data Protection Law, and how it fits the emirate's health information exchange.
These are not preferences, they are the conditions of operating. Abu Dhabi runs Malaffi, Dubai runs Nabidh, and the federal Riayati programme connects the picture, with regulators that expect patient data handled in ways an American default does not guarantee.
So the buying order flips. Before note quality, a UAE clinic asks about residency, the PDPL and the exchange. A scribe that cannot answer those is not a candidate, however good its transcript.
Part of the DHA hub, with the framework explained, a readiness checklist and 8 guides.
Part of the DOH hub, with the framework explained, a readiness checklist and 8 guides.
See it in your clinicwai hosts your clinic's records in the UAE, under UAE rules. We set this up with your clinic.
Request a demoIn-country data residency
Health data in the UAE is expected to be handled with strong controls, and for many clinics and regulators that means processing and storing patient data in-country rather than shipping a recorded consultation to a US server by default. A scribe's answer to where the audio and transcript are processed is the first gate.
Ask for a specific answer, not a reassurance. In-region or in-country processing, stated plainly, with the retention period and who can access it. A vendor that cannot commit to residency is a vendor that cannot operate here for many buyers.
The Personal Data Protection Law
The UAE's federal Personal Data Protection Law sets out obligations for processing personal data, and health data is among the most sensitive. Consent, purpose limitation, security and cross-border transfer rules all apply, and free-zone health regulators such as those in the DIFC and ADGM add their own regimes.
The practical effect for a scribe is the same as it is anywhere serious. A named lawful basis, documented patient consent to record, a processing agreement, and a clear position on whether data ever leaves the country or trains a model. Get all of it in writing.
The health information exchanges
Abu Dhabi's Malaffi and Dubai's Nabidh connect providers into a shared patient record, and the federal Riayati programme links across the country. A documentation tool that produces a note nobody can move into that ecosystem is a dead end.
Ask how the scribe's output reaches your clinic's system and, where required, the exchange. Interoperability claims are easy to make, so ask what the product does today, in the UAE, not what is planned.
Arabic, and the bilingual consultation
Many UAE consultations move between Arabic and English, sometimes within a sentence. A scribe tuned only on American English will struggle with names, code-switching and dialect, and the note will show it.
Ask for Arabic support and test it on real bilingual consultations before you commit. wai understands more than thirty-five languages and is built for Arabic-first care, which in this market is a requirement rather than a feature.
Bring your own clinic to it. Thirty minutes, and you see it on your workflows.
Request a demoFrequently asked questions
Can a UAE clinic use a US-built AI scribe?
A UAE clinic can use a US-built AI scribe only if it meets the local conditions, which many US-built scribes were not designed for. A UAE clinic should confirm in-country or in-region data processing, compliance with the federal Personal Data Protection Law, documented patient consent to record, and a path for the note to reach the emirate's health information exchange. A scribe that ships a recorded consultation to a US server by default is a problem for many UAE buyers and regulators.
Does patient data have to stay in the UAE?
For many clinics and regulators, yes, health data is expected to be processed and stored in-country or in-region rather than sent abroad by default, and free-zone regimes in the DIFC and ADGM add their own rules. The safe approach is to require a specific, written commitment on data residency, retention and access from any scribe vendor, and to treat an inability to commit as disqualifying rather than a detail to resolve later.
Do AI scribes support Arabic?
Support varies widely, and it matters more here than almost anywhere. UAE consultations often move between Arabic and English within a single conversation, and a scribe tuned only on American English will mishandle names, code-switching and dialect. Test any candidate on real bilingual consultations before committing. wai understands more than thirty-five languages and is built for Arabic-first care, which in this market is a requirement.
What does the UAE Personal Data Protection Law require?
The UAE's federal Personal Data Protection Law sets out obligations for processing personal data, and health data is among the most sensitive. Consent, purpose limitation, security and cross-border transfer rules all apply, and free-zone health regulators such as those in the DIFC and ADGM add their own regimes.
What are Malaffi, Nabidh and Riayati?
Abu Dhabi's Malaffi and Dubai's Nabidh connect providers into a shared patient record, and the federal Riayati programme links across the country. A documentation tool that produces a note nobody can move into that ecosystem is a dead end.
Built for your jurisdiction.
wai hosts your clinic's records in the UAE, under UAE rules. We set this up with your clinic. Thirty minutes and you will see how wai handles consent and Arabic-first care.
Partner with us
See it on your own patients, then build it with us
Thirty minutes on your own patients, doctors and rules, in your market. We reply within one working day, and the clinics that partner with us early shape what we build next.
See what wai does between the visits