eClaimLink and DHPO: how e-claims, eRx and prior auth work in Dubai

Short answer: eClaimLink is Dubai's e-claims standard: the data dictionary, code sets and validation rules for health insurance transactions. DHPO (Dubai Health Post Office) is the gateway that carries those transactions between providers and payers: prior authorization requests, claims, eRx and remittance advice. Every insured visit in a Dubai clinic runs through it. Helix is integrated with eClaimLink and DHPO.

Clinic owners often hear about eClaimLink only when cash flow slows down. By then, the problem usually started weeks earlier at the front desk or in the chart. This guide follows one insured visit from start to finish and shows where each piece of data comes from.

This article is general guidance, not legal advice. Regulators update their standards, circulars and deadlines often, so always confirm the current requirement with the relevant authority or a qualified advisor before you act on it.

eClaimLink vs DHPO vs NABIDH

People use eClaimLink and DHPO interchangeably, and that is mostly fine in conversation. Mixing them up with NABIDH is not: NABIDH is a clinical exchange, covered in our NABIDH integration guide.

The transaction cycle, step by step

1. Registration and eligibility. The front desk records the patient's insurer, payer (TPA), network, policy and member ID, and confirms coverage with the payer before the visit.
2. Prior request (when required). For services the payer must approve in advance, the clinic sends a prior request with diagnosis codes, the requested activities and the clinician. The payer answers with an approval, partial approval or rejection.
3. Consultation and documentation. The doctor documents the visit and records coded diagnoses. This is where most future denials are made or avoided.
4. eRx. In Dubai, prescriptions go electronically to the eRx hub in DHPO, where insurers can give coverage feedback. The pharmacy later retrieves the prescription electronically at dispensing.
5. Claim submission. After the visit, the clinic builds the claim in the eClaimLink format (encounter, diagnoses, one activity per billed service with its code, quantity, net amount and clinician licence) and uploads it through DHPO.
6. Remittance advice. The payer returns a remittance advice showing what was paid, partly paid or denied, with denial codes.
7. Resubmission. Denied or partly paid claims can be corrected and resubmitted with a resubmission type and comment, within the limits set by the regulator.

Dubai's insurance regulator publishes policy directives and standards notices that set timelines for submission, resubmission, remittance and payment. They are updated from time to time, so your finance team should keep the current documents on file rather than rely on memory.

What a clean claim needs

• At least one coded diagnosis that supports every activity on the claim.
• The right code for each activity, using the code set the payer and eClaimLink expect for that service type.
• The treating clinician's DHA licence number on each activity. A new doctor without a licence number on their profile is a common source of rejections.
• Correct payer, receiver and member details from registration, matching the insurance card.
• The prior authorization reference where one was required.
• Amounts that match the invoice: gross, patient share and net.

None of these are exotic. They fail because the data is typed in three different systems by three different people. When the claim is built from the same record the doctor charted in and the front desk registered, most of them take care of themselves. That is the core argument for billing and medical accounting on the same record as care.

Where denials usually start

For a deeper look at root causes and how to measure them, read our guide to reducing claim denials in the UAE. For the approval step specifically, see prior authorization in the UAE and Saudi Arabia.

Metrics finance should track monthly

• First-pass acceptance by payer: the share of claims accepted without resubmission.
• Denial reasons, grouped by code and by the step where the error started (front desk, chart or billing).
• Days from visit to submission, because late claims risk falling outside submission windows.
• Days from submission to remittance, by payer.
• Open resubmissions and their age.

None of these need a special tool if claims, remittance and invoices live in one system. They become hard when claims are exported to a separate portal and remittance is reconciled in a spreadsheet.

Questions to ask any billing system

• Does it build the claim directly from the visit, or does someone re-key it?
• Does it check for diagnosis, clinician licence and file size before submission, and tell me what to fix?
• Can I see every claim's status in one place: pending, submitted, accepted, rejected?
• Are remittance advice and denial codes posted back against the original invoice and into the ledger?
• Can I correct and resubmit a claim without starting over?
• Can I see acceptance rates by payer?

How Helix handles eClaimLink

Helix is integrated with eClaimLink and DHPO for claims, eRx, prior authorization and remittance. Visits with an invoice and no claim appear in a staging list. One click builds the claim from the chart, pulling coded diagnoses and each clinician's licence number. A pre-submission review checks for diagnoses, licences and batch size, and a claim quality panel lists what to fix before anything is sent. Once a visit is claimed, its invoice is stamped so it cannot be claimed twice. Remittance and denial codes come back to the same record and the same ledger. The full picture is on our integrations page.