A clinic owner who has run a facility in Dubai and opens one in Abu Dhabi discovers quickly that the emirate is not a copy with a different skyline. The Department of Health Abu Dhabi (DoH) licenses the facility, not DHA. Clinical data flows to Malaffi, not NABIDH. Claims move through DoH's Shafafiya infrastructure. And a large share of patients, including UAE nationals on Thiqa, are covered by Daman, whose rules shape the billing workflow. A clinic platform that treats these as configuration differences works; one that treats them as a separate project does not.
This guide covers what a DoH-licensed clinic in Abu Dhabi or Al Ain needs from its software, where Abu Dhabi differs from the rest of the UAE, and how MEDAS E-Clinic handles each part. For the general selection criteria that apply everywhere in the UAE, the complete clinic software guide is the companion piece.
Where Abu Dhabi differs
| Requirement | Abu Dhabi and Al Ain | Dubai |
|---|---|---|
| Licensing authority | Department of Health Abu Dhabi (DoH, formerly HAAD) | Dubai Health Authority (DHA) |
| Health information exchange | Malaffi | NABIDH |
| Claims and transactions | DoH Shafafiya infrastructure | DHA e-claims infrastructure |
| Insurance landscape | Daman prominent; Thiqa for UAE nationals; mandatory cover for residents | Multiple insurers; mandatory cover for residents |
| Software approval needed | DoH/HAAD | DHA |
The practical consequence: if your platform is approved only by DHA and connects only to NABIDH, your Abu Dhabi branch needs a second system or a second project. Choose one that already covers both.
Malaffi: what the clinic software has to do
Malaffi is Abu Dhabi's health information exchange, connecting public and private providers so that a patient's record is available wherever they are treated in the emirate. DoH-licensed facilities are expected to participate. For the clinic, participation means the software must:
- Capture clinical data as structure, not prose. Encounters, coded diagnoses, medications from a formulary, allergies, discrete results and procedures. Free-text notes cannot be exchanged.
- Identify the patient reliably. Emirates ID at registration is the anchor that links the visit to the right record across providers.
- Send and receive. Contributing the clinic's data is half of it. The other half is letting the clinician see the patient's history from other providers, at the point of care, inside the EMR.
- Handle consent and audit. Who accessed what, when, and on what basis.
Ask every vendor two questions: at which Abu Dhabi facilities is your Malaffi connection live today, and what exactly does the facility have to provide versus what you manage. A logo on a slide is not an answer to either.
In E-Clinic: the platform is approved by DoH/HAAD for Abu Dhabi and Al Ain and supports Malaffi integration workflows, with the facility-specific integration and certification scope confirmed during scoping. Emirates ID registration, ICD-10 and CPT coding, and structured results are standard.
Billing in Abu Dhabi: Shafafiya, Daman and Thiqa
Abu Dhabi's claims workflow has its own infrastructure and its own conventions. Claims and related transactions between providers and payers move through DoH's Shafafiya platform in a defined format. Daman is a prominent insurer in the emirate and administers Thiqa, the programme covering UAE nationals, and Daman's pre-approval and coding expectations shape how a clinic bills. A platform built for Dubai and adapted for Abu Dhabi tends to show the seams here.
What to look for:
- Eligibility verification at registration for Daman, Thiqa and the other insurers your patients carry.
- Prior approval requests raised from the order, with the status visible to the desk and the doctor.
- Claims coded from the encounter and submitted in the DoH-required structure without a manual re-keying step.
- Rejections routed back as work items with the reason, not as emails.
- Reports by insurer: claim ageing, rejection reasons, days to payment.
In E-Clinic: insurance management with real-time eligibility, e-claims and approval tracking with major UAE insurers, corporate billing, and MIS reporting in the same suite. The revenue cycle guide walks through each step; the workflow is the same, with Abu Dhabi's channels configured.
Al Ain and multi-site groups
Al Ain falls under DoH, so a clinic there needs the same approvals and the same Malaffi participation as the capital, and a group with sites in both cities should run them on one platform with one patient index. If the group also has a Dubai or Northern Emirates site, the platform has to handle NABIDH or Riayati for that site without a separate deployment: one system, multiple exchanges, configured per facility licence.
In E-Clinic: approvals from DoH/HAAD, DHA and MOH/MOHAP mean one platform can serve every emirate, with multi-branch operation, per-branch configuration and consolidated reporting.
Clinical, pharmacy and diagnostics
Beyond the Abu Dhabi specifics, the clinical requirements are the same as anywhere: specialty templates the doctors will actually use, orders and results in a closed loop, e-prescribing with interaction alerts, and pharmacy and laboratory modules that share the patient record rather than exchanging files. E-Clinic's 24 modules cover these, with specialty EMR for the common polyclinic specialties, laboratory and radiology information with DICOM, and pharmacy point of sale with inventory. The UAE EMR guide covers the clinical side in depth.
Choosing a vendor for an Abu Dhabi clinic
- Confirm DoH/HAAD approval in writing, and DHA and MOHAP if you have or plan sites elsewhere.
- Ask for a live Malaffi-connected reference facility in Abu Dhabi and call it.
- Run a demo on your own patient journey with Daman or Thiqa as the payer.
- Get the proposal in components: modules, users, branches, implementation, migration, Malaffi and claims integration, hosting, support.
- Check who maintains the Malaffi connection when DoH changes a specification, and whether that is included.
- Confirm support hours and channels for Abu Dhabi, and that the team knows the Shafafiya workflow.
MEDAS is headquartered in Dubai, supports more than 500 healthcare facilities, and implements a typical clinic in four to eight weeks with 24/7 support afterwards. For an Abu Dhabi facility the team scopes Malaffi and DoH claims requirements before quoting.
Frequently asked questions
Is MEDAS E-Clinic approved by DoH Abu Dhabi?
Yes. E-Clinic is approved by DoH/HAAD for Abu Dhabi and Al Ain, alongside DHA in Dubai and MOH/MOHAP across the Northern Emirates.
Does E-Clinic integrate with Malaffi?
E-Clinic supports Malaffi integration workflows. The facility-specific integration and certification scope depends on the implementation and DoH's current requirements and is confirmed during scoping.
Can one system serve clinics in Abu Dhabi and Dubai?
Yes, if it is approved by both DoH and DHA and supports both Malaffi and NABIDH. E-Clinic is, and does, with per-branch configuration on one patient index.
How is billing different in Abu Dhabi?
Claims move through DoH's Shafafiya infrastructure rather than DHA's, and Daman, including the Thiqa programme for UAE nationals, is a prominent payer with its own approval and coding conventions. The software should handle these as configuration, not as a separate project.
See E-Clinic configured for Abu Dhabi
Bring your DoH licence details, your insurers and your specialties, and the MEDAS team will demonstrate the Malaffi and claims workflows for your facility.
Book a tailored demo