If you are launching or running a telehealth service in Dubai, connecting to NABIDH is not optional. It sits directly on the path to a Dubai Health Authority licence, and it shapes how you choose your clinical software. This guide explains what NABIDH is, why integration is mandatory, what your systems need to support, and the practical steps to go live.
What NABIDH is, and why it matters
NABIDH is the Dubai Health Authority's (DHA) health information exchange. Its purpose is to unify patient medical records across Dubai healthcare providers, so that an authorised clinician can see a patient's relevant history regardless of which clinic, hospital, or telehealth service created the record. For patients, that means more continuous and better informed care. For providers, it means clinical data has to be structured, standardised, and shared in a consistent way.
For a telehealth operator, this changes how you think about your software from day one. A consultation delivered over video still produces a clinical record, and that record needs to flow into NABIDH just as it would from a physical clinic.
Why integration is mandatory
Connecting to NABIDH is a regulatory requirement, not a best-practice suggestion. Every Dubai clinic must connect to NABIDH to obtain or renew its DHA licence. Telehealth operators are treated as healthcare providers in this respect, so the same rule applies. In practical terms, your NABIDH connection and your licence are linked: you cannot treat integration as a project to schedule for later if you intend to operate or stay licensed in Dubai.
Because the connection is tied to licensing, it is worth planning the integration alongside your licence application rather than after it, so the two timelines support each other.
What your systems need to support
Before you can connect, two foundations have to be in place: a valid trade licence and a capable Electronic Medical Record system.
A valid trade licence
As with any regulated business activity in Dubai, you need a valid trade licence covering your healthcare activity. This is the legal basis on which your provider entity operates.
A compliant EMR system
You need an Electronic Medical Record (EMR) system that meets NABIDH's technical expectations. Specifically, the EMR has to support NABIDH's Minimum Data Set, which defines the clinical information that must be captured and shared, and it has to support HL7 interoperability standards, which define how that information is formatted and exchanged. An EMR that cannot meet both of these cannot be connected, so this is a key consideration when selecting or reviewing your clinical software.
Make sure you have
- A valid trade licence covering your healthcare activity
- An EMR system that supports the NABIDH Minimum Data Set
- An EMR system that supports HL7 interoperability standards
- A plan for storing all patient data inside the UAE
- A relationship with a NABIDH-certified EMR vendor for onboarding
The onboarding steps
Onboarding to NABIDH is carried out through NABIDH-certified EMR vendors. A typical path runs through the following stages.
Select a certified EMR vendor
Choose an EMR vendor that is certified for NABIDH integration. The certification matters because it confirms the vendor's platform is already aligned with NABIDH's requirements, which reduces the work needed to reach a compliant connection.
Map and prepare your data
Map your clinical data to the NABIDH Minimum Data Set and prepare it for exchange. This is where you confirm that the information your telehealth workflows capture lines up with what NABIDH expects to receive.
Build the integration
Build the technical connection between your EMR and NABIDH, using the HL7 interoperability standards so that records are formatted and transmitted correctly.
Complete conformance testing
Before going live, the integration is put through conformance testing. This verifies that your data and your connection meet NABIDH's standards, and it is the checkpoint that confirms you are ready for live exchange.
Go live
Once conformance testing is passed, you can go live and begin exchanging records with NABIDH as part of your routine clinical operations.
Data residency: a requirement to plan for
One requirement that influences architecture decisions across the whole project is that all patient data must be stored inside the UAE. For a telehealth operator, whose technology stack may otherwise be cloud-based and distributed, this data residency rule should be confirmed early. It affects how you choose an EMR system, where it is hosted, and how any supporting services are arranged.
Frequently asked questions
Is NABIDH integration mandatory for telehealth operators in Dubai?
What is NABIDH?
What does a telehealth operator need before connecting to NABIDH?
How does the NABIDH onboarding process work?
Where must telehealth patient data be stored?
This guide is general information, not regulatory or legal advice. Requirements can change, so confirm current rules with the DHA, NABIDH, or your regulatory partner before acting. Related: telehealth and NABIDH integration services.