An AI receptionist is two products, and one of them cannot leave

Short answer. Federal Law No. 2 of 2019 defines health information as processed health data that carries meaning, "whether visual, audio or legible". Audio is named. Article 13 bars storing, processing, generating or transforming it outside the country when the service was provided inside it. The only exception is a health authority resolution issued in coordination with the ministry. Ministerial Decision No. 51 of 2021 lists ten such cases, and none of them describes a vendor's answering service on foreign servers. So an AI receptionist splits in two, and one question does the splitting: did it hear why the patient called?

Every proposal you will read prices one product. The law sees two. One half answers "are you open on Sunday", holds nothing the law cares about, and can run anywhere. Its twin hears a symptom, creates health information in the statute's own words, and from that second has to stay in the country.

Nobody selling you an AI receptionist in Dubai is going to raise this. Booking appointments is the question every shortlist already asks. Put this one beside it, in writing: where does the audio land the moment a caller says the word pain?

Is a phone call health information?

Once the caller says why they rang, yes. The definition does not leave room to argue, because it names the format.

"Health Information: The health data which had been processed and became with a meaning, whether visual, audio or legible, and characterised by the health feature, whether related to the health or insurance establishments or authorities or to the beneficiary from the health services."

Three words in that sentence decide your procurement. Audio counts. Meaning counts, so a raw waveform nobody has interpreted sits further from the definition than a transcript does. And the beneficiary of the health service is named. A doctor's note about the problem is in scope; so is the patient's own account of it.

Now read Article 13's four verbs against a vendor, one at a time, because two of them bite and two do not.

Processing is the one people reach for first, and it is the weakest. The law defines it narrowly.

"Process: Information creation, introduction, amendment, update or deletion electronically."

No storage in that definition, and no transmission. So "they process it abroad" is a thinner argument than it sounds, and a vendor's lawyer will say so.

The two that bite are storing and generating. Audio parked on a foreign server is stored there, even in transit. A transcript produced by a model abroad is generated there, and generating is in the article by name. That second one is why asking where the recording lives is not enough on its own: the audio can reside in Dubai while a model elsewhere reads it, and the transcript is still made outside the country.

Nor can a vendor argue that a phone line is not the kind of system the law was written for. The statute's definition of information and communication technology is wide. It covers technological and electronic tools, systems or other means that allow all types of information and data to be processed. The processing it names includes storing, recovering, publishing and exchanging. A speech model on a phone number is squarely inside that.

The boundary sits inside the conversation. "Do you open on Sunday" produces no health information about anybody. "My daughter has had a fever since Tuesday" produces it before the agent has said a word.

What does Article 13 actually forbid?

Leaving the country, by default. Only a regulator can lift that, in coordination with the ministry.

"It is not permissible to store, process, generate or transform the health data and information outside State, which are related to the health services provided inside State, except in the case where a resolution is issued from the Health Authority in coordination with the Ministry."

One translation note, because it changes how the sentence reads. The official English on the government's legislation portal says transform. Most law firm commentary writes transfer. I am quoting the official text and flagging the difference instead of choosing for you; either way, storing and processing are both listed on their own.

Two things in that sentence are easy to miss. The trigger is where the service was provided, not who the patient is, so a tourist treated in Dubai is covered exactly like a resident. And the duty lands on you. The law governs the use of information technology in health fields, and your clinic is the one using it. A vendor's compliance page is not a defence; the licence is yours.

The executive regulations arrived as Cabinet Resolution No. 32 of 2020, issued on 22 April 2020, and they sit on top of the same article.

Does any exception cover a vendor abroad?

Ten exist, and your answering service is not among them.

Ministerial Decision No. 51 of 2021, issued on 28 April 2021, sets out the cases. A note on sourcing: the decision's operative text sits on the health ministry's legislation portal, which would not answer when I tried to pull it, so the table below follows the enumeration in a Latham & Watkins client alert of 29 August 2021, cross-read against an Al Tamimi summary that groups the same material into eight headings.

Read the conditions column of that alert and a pattern appears. Nearly every case requires written approval from the person receiving the service, or anonymisation, and most require encryption. Five of the ten also require that a copy of the information stay inside the country. Case 6 is the only one the decision leaves without stated conditions, which is worth a second of thought: a blood pressure cuff syncing to a foreign app gets a clear path, and a phone call about a fever does not.

Two of them get misread as a way in. Insurance requires the insurer and the claims company to operate here, the patient to consent, the data to be anonymised and not transferred in full. Case 9, remote medical services, gives the clinician access for a determined duration and sends a report only to the named physician, again with written consent. Neither is a standing pipe to a vendor.

Case 8 is the one worth reading slowly, because it is the only door not tied to a named purpose. Who opens it decides everything: an Emirate-level health authority approves, which means the approver is a regulator. Not the clinic, and certainly not the vendor. Article 13 says the same about its own exception, where the resolution comes from the health authority in coordination with the ministry. Nobody's compliance page substitutes for either.

Three conditions ride on case 8, and two of them appear in the decision's own text. A copy of the information stays inside the country. The data must not be confidential for reasons of public security, public interest or public health. And its disclosure must not reveal the patient's medical secret unless there is written consent.

Read that last one against a phone ringing. The caller has not consented to anything yet. They have not filled in a form, they have not met you, and they are already describing a symptom. Written consent before the handset is picked up does not exist, which is why case 8 fits a planned transfer of a known record and not an inbound call.

Which half of your calls carries it?

The half where the caller got as far as saying why, which is fewer calls than you would guess.

The fourth row is the one that ruins a tidy architecture. You do not control whether somebody volunteers a reason. A caller who opens with "it's about my back" has created health information before any menu or routing rule has run. You cannot design that away. The question is where the audio already sits when they do.

Our piece on what a front desk costs gives you the number to compare against, about AED 27 for an hour the desk is covered. That number tells you whether a system is worth buying. It says nothing about where the recording lives, and the two questions have to be answered separately. The wider version of this problem, which law covers which of your data, is in which data has to stay.

What to ask before you sign

Four questions, all of them answered in writing, and none of them technical.

1. Where does the audio sit? Name the country. "In the cloud" and "on AWS" are not answers; a region is.
2. Where is the transcript produced? Speech recognition is processing, and processing is in the article by name. The audio can rest in Dubai while a model abroad reads it.
3. What survives the booking? If the appointment is in your calendar, ask what the vendor still holds an hour later, and for how long.
4. How fast can you delete it? In days, in a contract, with somebody responsible for doing it.

Then one design decision that removes most of the problem before it starts. An agent that never asks why the patient is calling creates far less health information than one that triages. You lose something real: a system that cannot hear urgency cannot sort it, and sorting is what a good receptionist does best. That is a trade to make deliberately, with your clinical lead in the room, and it is the same trade as the presence split in the piece on what a front desk costs.

This is not legal advice and I am not your lawyer. I quoted the provisions above so you can take them to one. That hour costs less when you arrive with citations instead of a question.

On a clinic project we split the call types before anybody shortlists software, because that split decides which half of the market you are allowed to buy from at all.