The licence stack
A Dubai telemedicine operation is not approved by one document. It is a stack of approvals that have to line up, and the stack is worth seeing whole before any application goes in, because each layer is generally assessed against the one beneath it.
- A trade licence with the correct activity. The company itself carries a healthcare activity that supports telemedicine. An entity formed with the wrong activity usually has to be amended before the authority file can move.
- DHA initial approval. The first authority gate, applied for through the Sheryan portal, which generally confirms the entity and the concept before the detailed file is assessed.
- The telemedicine licence itself. The facility level approval that lets the operation deliver remote consultations as a licensed health service rather than a software product.
- Individual professional licences. Every clinician who consults through the platform holds their own DHA licence and is credentialed under your operation.
- The medical director appointment. A licensed physician who carries clinical accountability for the whole service, named before the operation goes live.
Founders tend to plan for the third item and discover the other four late. The builds that move quickly treat the stack as one project from the first week.
The requirements that decide your timeline
Within that stack, five requirements do most of the work of deciding how long the application takes. Each one can run in parallel with the others, which is the main lever a well managed build pulls.
The entity and activity
The trade licence, the right healthcare activity and the ownership structure. Foreign founders can generally own the company outright, and this layer is the fastest when it is set up correctly the first time.
The medical director
A licensed physician accountable for clinical governance. Identifying, licensing and appointing this person early matters, because several later steps generally wait on the appointment.
The clinicians and credentialing
Every consulting clinician is individually licensed and credentialed under the operation. Credential verification and licensing run per person, so the roster is built alongside the application rather than after it.
The platform and NABIDH connected records
The consultation platform and the EMR behind it, with records connecting to NABIDH, Dubai's health information exchange, through its Go Live process. Platform choice is made early because the connection work takes time.
The policies: consent, records, clinical governance
Patient consent, record keeping, prescribing, escalation to in person care and clinical governance, written for a remote setting rather than copied from a clinic manual.
What the DHA expects to see working
Approval is generally less about paperwork promising a service and more about the service demonstrably working. Before and after go live, the operation should be able to show:
- Consultation flows. Booking, identity checks, the consultation itself and the follow up, running as designed on the licensed platform.
- Records landing on NABIDH. Consultations generating records that reach the exchange through the connected EMR, not sitting in a standalone system.
- Prescription handoff. Clinicians prescribing where clinically appropriate, licensed pharmacies dispensing, and a clean trail between the two.
- Complaint and escalation procedures. A documented route from a remote consultation to in person care when it is needed, and a working way for patients to raise concerns.
None of these are exotic. They are simply the difference between a telemedicine business and a video calling app with a doctor on it, and the authority generally looks for that difference.
How long it takes
A full telemedicine operation typically takes approximately three to six months end to end, from engagement to first consultation, subject to authority response times and the scope of the service.
The licence steps themselves are only part of that. The medical director appointment, clinician credentialing, the platform build and the NABIDH connection all run in parallel, and in a well managed build they finish together rather than queueing behind each other. That parallel running, more than any single approval, is what separates a six month build from a twelve month one.