Telehealth UAE
GuideChecked 4 November 2026, 4 minute read

Telehealth platform and data rules in Dubai

A consumer app can launch with whatever stack is quickest. A telehealth service in Dubai cannot. Here are the technical rules to give your developers or vendor on day one.

Published by HealthcareSetup UAE, with Pharmareg UAE
Both are brands of PharmaReg ME L.L.C-FZ.
We sell telehealth builds and regulatory services, so we have a commercial interest in this topic. Checked against the sources listed at the end of this guide on 4 November 2026.
Patient deviceWeb or appConsent loggedIdentity checkedTelehealth platformDHA approvedHIPAA and ISO 27001Encrypted channelsHealth recordEvery encounter in writingPhone calls includedName and licence of staffNABIDHDubai's health informationexchange. Your recordsystem integrates with itClaimseClaimLink where insuredDHIC-approved ICDand CPT codesHeld in the UAE, and kept for at least 25 years from the last encounterCloud provider certified by Dubai Electronic Security Centre. Data centres at least Tier 3. No storage, development or transfer abroad except where the law allows.
Our drawing of the requirements in clauses 7.6, 7.9, 11 and 13 of DHA's Standards for Telehealth Services, version 4. Your own architecture may differ.
Hosting01 / 07

Keep the data in the UAE

The standard sets these rules for platforms:

  • All data centres must be at least Tier 3 certified.
  • All data must sit on a server at a cloud service provider certified by the Dubai Electronic Security Centre (DESC), in the UAE.
  • Platforms must hold HIPAA and ISO 27001 compliance certification.
  • Some conditions may call for more, such as HITRUST or SOC 2 with HIPAA alignment.

Storing, developing or transferring health data outside the UAE is not permitted, except in the cases in Article 2 of Ministerial Decision 51 of 2021. The word "developing" matters. If your developers, analytics tools, support desk or AI services sit abroad, check how they touch patient data before you sign with them.

Infrastructure02 / 07

Build for uninterrupted care

Facilities providing telehealth must make sure they have:

  • Integrated IT with uninterrupted connectivity and enough bandwidth
  • Uninterrupted or backup power
  • Secure UAE-based servers with data backup
  • Secure, private and soundproof workspaces, with access limited to authorised staff
  • Another way to reach the patient if the main channel fails
  • Devices compatible with UAE technical and safety requirements, in good condition and maintained to the manufacturer's specifications

The soundproof workspace applies wherever your clinicians consult from. It is worth asking how that works for anyone who plans to consult from home, and getting DHA's view if that is your model.

Records03 / 07

Write every encounter down

Your record system has to integrate with NABIDH, Dubai's health information exchange. All telehealth encounters must be turned into written documentation, including telephone consultations. For each one, the physician records at least:

  • The type of service and the technology or platform used
  • The name, licence number and role of every professional involved
  • Date, time and the location of the care sites
  • Confirmation of consent, and that privacy and security requirements were met
  • Presenting complaint, signs, symptoms and observations
  • Diagnosis, clinical decisions, treatment plan and therapies
  • Relevant electronic communications, prescriptions, test results and instructions

Telehealth information must be kept securely for at least 25 years from the last health encounter, or as DHA specifies. Build storage costs and export formats around that, because DHA can also ask for your data in a required format.

Pharmareg UAE has a separate guide to NABIDH integration for telehealth.

Consent04 / 07

Treat data consent as a feature

Consent has to be built into the workflow and stored in the record. Electronic consent is acceptable if it meets the same requirements as manual consent, identifies the patient and can be audited. Consent for treatment must be documented at each encounter.

Your product also needs consent for audio recording, monitoring, storing data and passing it to another provider. Any active or passive tracking in the service needs consent too, which may affect analytics tools and advertising pixels.

If you record video for quality or training, DHA expects a documented purpose, a named responsible person, security measures, written consent, a retention period and a breach plan.

AI05 / 07

Keep a physician over any AI

Version 4 of the standard addresses AI directly:

  • Providers using AI, including ambient AI, are subject to specific requirements and DHA's AI policy.
  • Patient consent is required if ambient AI supports encounter documentation.
  • The DHA-licensed physician must review any AI-generated content before it becomes part of the permanent record.
  • AI-enabled tools must follow documented clinical validation, ethical disclosure and patient consent.
  • Data must stay on secure UAE-based infrastructure unless the law permits otherwise.

Check where any AI model actually runs. Many popular services process data outside the UAE, which brings you back to the hosting rule.

Devices06 / 07

Check monitoring kit before you buy

Remote patient monitoring must use DHA-approved platforms and MOHAP-approved medical devices. A DHA-licensed physician leads it, and decides who is eligible after an in-person assessment or a teleconsultation. Devices must be tested with the patient before use, and faults reported to MOHAP.

When buying, the standard asks you to consider safety alerts, accuracy, infection control, ease of use, durability and data security, including authentication and the ability to fix weaknesses in the device.

Vendors07 / 07

Questions for any vendor

These questions are our view of what to ask, based on the rules above:

  1. Is the platform DHA approved, and for which use?
  2. Which DESC-certified provider and data centre hold our data, and can you show the certificates?
  3. Do you hold HIPAA and ISO 27001 certification, and who issued it?
  4. Does anyone outside the UAE, including your support and development teams, access patient data?
  5. Has your record system completed NABIDH integration, and how do we get our data out?
  6. Which AI tools are in the product, where do they run, and can we switch them off?
  7. What is your escalation matrix and backup plan when the service fails during a consultation?

HealthcareSetup UAE can take the technology decisions as part of its telemedicine business setup.

Questions

Common questions

Can telehealth patient data be hosted outside the UAE?

Generally no. DHA's standard says it is not permitted to store, develop or transfer health data outside the country, except in the cases in Article 2 of Ministerial Decision 51 of 2021. Check any exception with DHA.

How long must telehealth records be kept?

At least 25 years from the date of the last health encounter, or as otherwise specified by DHA, according to the standard.

Do phone consultations need to be recorded in the patient file?

They must be written up. The standard says all telephonic consultations must be reduced to writing in the patient's electronic record.

Can we use AI to write consultation notes?

The standard allows ambient AI with patient consent, provided the treating physician reviews the content before it enters the permanent record, and the tool follows DHA's AI requirements.

Who can build or check our platform?

HealthcareSetup UAE builds telehealth businesses including their systems, and Pharmareg UAE handles NABIDH and DHA licensing. Both are brands of the same company and publish this guide.

Build the telehealth business

HealthcareSetup UAE

The licence, clinical team, platform, records and supply chain, run as one project and handed over ready to trade.

healthcaresetup.ae ↗
Handle the regulatory work

Pharmareg UAE

Regulatory affairs in the UAE: DHA telehealth licensing, NABIDH, accreditation support, and pharmaceutical and medical device registration.

pharmareguae.com ↗
Sources
WhatsApp us