The data line

In production, patient data is processed only inside the UAE. This demo runs on synthetic data, which is why it can run on Google Cloud in Doha and call a global model endpoint.

Inside the UAE: patient data allowed

Clinic EMR
Claims Engine on a UAE cloud region
K2 Horizon, self-hosted on vLLM
RPA runners on UAE VMs
Audit logs and backups, including DR

Outside the UAE: no patient data, ever

RPA developers: build on synthetic data only
Gemini 4 Argon (global): public documents, code, synthetic data
This demo: synthetic data on Google Cloud me-central1 (Doha)

Why production stays in the UAE

Federal Law No. 2 of 2019, Article 13

The UAE's law on ICT in health fields: health data and information about health services provided in the UAE may not be stored, processed, generated or transferred outside the country, except in cases set by the health authorities.

DoH Abu Dhabi Responsible AI Standard

Requires governance over AI used in healthcare, including where development and support access to systems happens. Our reading: production access stays inside the UAE.

ADHICS and DHA data rules

Healthcare information security standards for Abu Dhabi and Dubai: access control, audit logging and incident handling.

What this demo is

Every encounter, member ID, clinic, clinician and payer is synthetic or fictional.
The model behind this demo is Gemini 4 Argon. The interface is switchable: production uses K2 Horizon on vLLM in a UAE region.
The mock TPA portal and RPA bot are fictional. Nothing is sent to a real insurer or to eClaimLink.
A billing coordinator approves every submission. The engine is administrative support, not a medical device.

Sources: Al Tamimi: Dubai claims directive, DoH Responsible AI Standard, Federal Law No. 2 of 2019.