Shafafiya: Abu Dhabi's e-claims framework for DOH-licensed providers
What Shafafiya covers, how it differs from Malaffi and from Dubai's eClaimLink, and how finance teams keep Abu Dhabi claims clean from prior request to remittance.
Short answer: Shafafiya is the Department of Health Abu Dhabi's e-claims and transactions framework. It defines how providers and payers exchange claims, remittance advice, prior requests and authorizations and electronic prescriptions, in a standard XML format, through the Shafafiya post office. Every DOH-licensed provider that bills insurance uses it. Helix is integrated with Shafafiya for Abu Dhabi clinics.
Shafafiya means 'transparency' in Arabic, and that is the point of it: every health insurance transaction in the emirate is standardized and visible to the regulator. For a clinic's finance team, it is the rail that turns care into cash.
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.
Malaffi vs Shafafiya: the confusion to clear up first
We regularly see clinic software, and even websites, that describe 'sending the e-claim to Malaffi'. That is wrong. Malaffi is Abu Dhabi's health information exchange for clinical records. Shafafiya is where claims go. The two are linked only indirectly: Malaffi states that facilities with Daman agreements cannot submit claims until they are connected to Malaffi. Our Malaffi integration guide covers the clinical exchange.
| Malaffi | Shafafiya | |
|---|---|---|
| Purpose | Share clinical records between providers | Standardize insurance and health transactions |
| Run by | Abu Dhabi Health Data Services, for the DOH | Department of Health Abu Dhabi |
| Carries | Encounters, diagnoses, results, reports | Claims, remittance, prior requests and authorizations, eRx |
| Main users in a clinic | Clinicians and registration | Finance, billing and pharmacy |
Shafafiya vs eClaimLink
If you run branches in Dubai and Abu Dhabi, you work with two e-claims systems. They follow similar ideas (structured XML, coded diagnoses and activities, remittance with denial codes) but they are separate platforms with separate dictionaries, validation rules, credentials and circulars. A claim built for eClaimLink is not a Shafafiya claim. Your billing software needs to know which branch sits in which emirate and send each claim to the right place. See our eClaimLink and DHPO guide for Dubai.
Which platform carries what
What Shafafiya covers
The DOH's published Shafafiya dictionary lists the transaction types providers and payers exchange. The main ones for a clinic are:
- Prior Request and Prior Authorization. The provider asks the payer to approve a service before it is delivered, and the payer answers.
- Claim Submission. The claim itself, including DRG information for inpatient claims where it applies.
- Remittance Advice. The payer's response: paid, partly paid or denied, with denial codes.
- Electronic Prescription transactions, including pharmacy prior requests and claims.
- Person Register and related transactions.
The DOH also publishes XML schemas, samples, validation rules, a release schedule and a public test environment. Vendors build against those. Clinics do not need to read the schemas, but they should know that validation rules change and that the DOH announces them in notices and circulars.
Two rules finance teams should know about
- Non-insurance activity is reported too. Under a DOH circular, providers must report transactions not otherwise submitted through Shafafiya (such as self-pay, medical tourism and other non-insurance activity) as electronic claims addressed to the regulator. Cash-only does not mean invisible.
- Pharmacy detail is validated. Since December 2023, Shafafiya validation rejects pharmacy prior requests and claims that do not include the required dose and frequency information. If your clinic dispenses, your prescribing screen must capture structured dose and frequency, not a free-text instruction.
The Abu Dhabi claim cycle
- Register the patient with the right insurer, payer, plan and member details, and check coverage before the visit.
- Send a prior request for services that need approval, with coded diagnoses and the planned activities.
- Document the visit with coded diagnoses and the reason for each procedure, test or medication.
- Invoice the visit, with the patient share and net amount clearly split.
- Build and submit the claim from the visit data, with the clinician's DOH licence on each activity.
- Download remittance advice, post payments and denials against the original invoice, and work the denials.
- Correct and resubmit where allowed, and write off only with an approval trail.
Every step depends on the one before it. A missing member ID at registration becomes a rejected claim five weeks later. That is why the claim should be built from the same record the front desk and the doctor already filled, in billing and medical accounting software that shares that record.
The Abu Dhabi claim cycle
- Register and check coverageInsurer, payer, plan and member details
- Prior requestFor services that need approval
- Document with codesDiagnoses and the reason for each activity
- Invoice the visitPatient share and net amount split
- Submit the claimClinician's DOH licence on each activity
- Post remittanceWork denials, resubmit where allowed
Working denials and resubmissions
Every remittance advice is a to-do list. Each denied line carries a code that points to a cause: eligibility, authorization, coding, medical necessity, duplication or a technical error. Group denials by code each week and trace each group back to the step where it started. A cluster of authorization denials is a front-desk or booking problem. A cluster of coding denials is usually a documentation habit in one department.
When you resubmit, correct the original claim rather than creating a new one, and record why. Keep every version, so an auditor can see what changed. Only write off a balance with an approval, and make sure the write-off reaches the ledger. Our guide to reducing claim denials in the UAE goes deeper into root causes.
Who owns what in the clinic
| Role | Owns |
|---|---|
| Registration | Insurer, payer, plan, member ID and Emirates ID, checked against the card at every visit |
| Clinicians | Coded diagnoses, the reason for each activity, structured dose and frequency on prescriptions |
| Billing | Prior requests, claim submission, remittance posting and resubmissions |
| Finance lead | Denial trends by payer, write-off approvals and monthly reconciliation to the ledger |
Choosing software for Shafafiya
- Is the vendor live on Shafafiya today, and does it follow current DOH validation rules?
- Can one system handle Shafafiya for Abu Dhabi branches and eClaimLink for Dubai branches?
- Does the prescribing screen capture structured dose and frequency?
- Are remittance advice files matched automatically to invoices, with denial codes visible?
- Can finance see claim status and acceptance by payer without exporting to Excel?
- Is every change to a claim logged, with who changed what and when?
How Helix handles Shafafiya
Helix is integrated with Shafafiya for DOH-licensed branches and with eClaimLink for DHA branches, in the same system. Claims are built from the visit, so diagnoses, activities and clinician licences come from the chart and the staff profile, not from re-keying. Remittance posts to the patient's invoice and to a double-entry ledger, so finance sees what is still owed per payer. For the clinical side in Abu Dhabi, Helix is also connected to Malaffi. See all of it on our integrations page.
Is Shafafiya the same as Malaffi?
No. Shafafiya is the DOH's e-claims and transactions framework. Malaffi is Abu Dhabi's health information exchange for clinical records.
Do self-pay patients need to be reported through Shafafiya?
A DOH circular requires providers to report transactions not otherwise submitted through Shafafiya, including self-pay and medical tourism, as electronic claims to the regulator. Check the current circular for details.
Can I use my Dubai eClaimLink setup for Abu Dhabi?
No. The platforms, credentials and validation rules are separate. Your software must send each branch's claims to the correct system.
Where are the Shafafiya standards published?
On the Department of Health Abu Dhabi website, in the Shafafiya dictionary: transaction schemas, samples, validation rules and web service documentation.
Related articles
eClaimLink and DHPO: how e-claims, eRx and prior auth work in Dubai
A finance and front-office guide to Dubai's e-claims rail: what eClaimLink and DHPO are, the transaction cycle from eligibility to remittance, and how to build claims that pass the first time.
Malaffi integration for Abu Dhabi clinics: what connecting really involves
Malaffi is a licensing condition for most DOH facilities, not a nice-to-have. Here is what the connection involves: agreements, the security assessment, HL7, network access and clean patient matching.
Reducing insurance claim denials in UAE clinics: root causes and fixes
Most denials are decided long before a claim leaves the building. Here is where they start, how to trace them back, and a weekly routine that stops the same rejection coming back.