Automating DHA eClaims and TPA Portals in the UAE — A Complete Guide

Healthcare providers in the UAE face an insurance submission landscape that's more complex than almost anywhere else in the world. Between DHA eClaims for Dubai, HAAD/DoH for Abu Dhabi, and six major TPAs each with their own portals and rules — a single clinic can be managing submissions across 8 different systems daily.

Most clinics handle this with a team of insurance coordinators staring at screens, copying data between systems, checking claim statuses manually, and following up by phone. It works — barely — and it costs far more than it should.

The UAE Insurance Landscape

Before diving into automation, it's worth mapping the ecosystem clearly:

Regulatory Bodies

DHA (Dubai Health Authority) governs insurance in Dubai through the eClaims portal. All providers with DHA licenses must submit and follow up through this system.

DoH (Department of Health Abu Dhabi) operates HAAD eClaims for Abu Dhabi-licensed providers. Different portal, different submission rules, different adjudication logic.

Major TPAs

The six major TPAs in the UAE each operate their own portal with unique interfaces, file formats, and adjudication timelines: NextCare, NAS, Neuron Health, AlMadallah, Sukoon, and GlobeMed.

What Automation Looks Like in Practice

DHA eClaims Automation

The DHA eClaims portal is the most standardized of the UAE systems. It accepts HAAD XML format submissions and has a relatively stable interface for RPA automation. Key automation points include: claim submission with ICD-10/CPT coding validation, status polling and rejection handling, resubmission workflows for technical rejections, and EOB reconciliation.

The main complexity is the coding validation layer. DHA has specific rules around which CPT codes require prior approval, which diagnoses require supporting documentation, and how bundled services should be submitted. An automation system that doesn't embed this rules logic will generate the same rejections your manual team does.

NextCare Portal Automation

NextCare is the largest TPA by volume in the UAE. Their portal has undergone several UI changes in the past two years, which has broken naive RPA implementations. Our NextCare automation uses a combination of API integration (where available) and resilient RPA that handles UI changes gracefully.

Key automation workflows: eligibility verification, claim submission with attachment handling, status checking, and query response submission for pending claims.

NAS and Neuron

NAS operates one of the more sophisticated portals — they have a provider API for high-volume submitters that's far more reliable than portal RPA. Neuron Health has a clean interface but requires specific XML formatting for certain claim types.

Implementation Approach

We recommend a phased implementation: start with the TPA that handles the highest claim volume, automate submission and status checking first, then expand to resubmission and query handling. Full automation across all TPAs typically takes 6–8 weeks depending on EHR integration complexity.

The critical success factor is data quality at the source. Automation amplifies whatever comes out of your clinical documentation — if diagnoses are consistently coded wrong, the automation will submit them wrong consistently. A coding audit before implementation prevents downstream issues.