Clinical costing fails on data plumbing, not on methodology.
The Abu Dhabi Clinical Costing Standard tells you what to produce. Getting there means pulling clean data out of your EHR, general ledger, payroll, rostering, pharmacy and theatre systems, then allocating it defensibly. That plumbing is the work, and it is what we build.

The Abu Dhabi Clinical Costing Standard
The standard is issued by the Department of Health under reference DoH/ST/FPS/ADCC/V2/2025, published in January 2026 and effective from February 2026.
Who it applies to
- DoH-licensed healthcare providers, including hospitals, specialist day case and day surgery centres, long-term care and rehabilitation, standalone specialist services such as dialysis, IVF and dental, primary care centres and clinics.
- DoH-licensed providers of dental services.
- DoH-authorised health payers, and health insurance products and schemes as applicable.
It is owned by Healthcare Payers and Finance Affairs, with document control in the DoH Strategy Sector, and it carries a one-year revision period. Submission requirements and timing reach providers through DoH circulars, so confirm the current cycle with the Department rather than with a vendor blog.
Cost centre structure, overhead allocation and step-down
The standard is built on cost centres. Almost every costing project that stalls stalls here, because the finance structure and the clinical structure were never designed to reconcile.
What has to hold together
- A cost centre structure that maps to how care is actually delivered, not to how the general ledger happened to grow.
- Direct costs traced to the cost centre that incurred them, with people, time, consumables, equipment and rooms separated rather than bundled.
- Overhead allocation with a stated basis, so an auditor can see why a number landed where it did.
- Step-down allocation applied consistently, with the sequence documented.
- Patient-level cost that reconciles upward to the department and downward to the encounter.
Where your current structure cannot support this, we fix the structure. A costing model built on cost centres that do not reflect reality produces numbers nobody will defend.

Getting the data out of your systems
Costing needs operational data that lives in systems that were never built to hand it over.
What we connect
- EHR and EMR encounters, so activity ties to the patient and the episode.
- The general ledger and trial balance, so costs reconcile to the accounts.
- Payroll and rostering, so clinical time is costed against who actually worked.
- Pharmacy dispensing, so drugs and consumables land on the right encounter.
- Theatre and procedure logs, so the most expensive minutes are costed properly.
- Radiology and laboratory systems, so diagnostics stop being an undifferentiated overhead.
- Fixed asset registers and materials management, for equipment and supply cost.
Most providers already have this data. It is in formats and systems that will not speak to each other, which is why costing becomes a spreadsheet exercise someone repeats by hand every cycle.
Submission and the evidence behind it
A submission is a claim about your costs. What makes it survive scrutiny is the trail underneath it.
What the platform keeps
- The source of every figure, traceable from the submitted number back to the transaction.
- The allocation basis applied, and the version of the model that produced the result.
- A record of changes, so a restated figure can be explained rather than defended from memory.
- Reconciliation to the general ledger, run before submission rather than after a query.
- Prior cycles, retained and comparable, so year-on-year movement has an explanation.
The standard names a DoH contact for clinical costing. Our job is to make sure that when a question arrives, the answer is a query rather than a project.
What we build
We build the costing platform and the integrations around it, and we run the migration from whatever you do today.
A typical engagement
- Review your current cost centre structure against the standard, and say plainly where it does not hold.
- Build the connectors to your EHR, ledger, payroll, pharmacy and theatre systems.
- Implement the allocation model, with the basis for each step recorded in the system rather than in someone's notes.
- Reconcile a full historical cycle against your existing figures, and explain every difference.
- Hand over a platform your finance team runs, with the submission as a report rather than a quarter-end scramble.
It deploys on your own infrastructure. Costing data is commercially sensitive and sits under the same residency and access rules as the rest of your patient-linked data, which is why we do not ask you to send it anywhere.
Read more
All articlesDIFC Regulation 10: what full enforcement means for your AI systems
Not new law. Introduced in September 2023, enforced from January 2026. The four obligations, who they fall on, and why no vendor can sell you the certificate.
The UAE's Federal Authority for AI and Data: what actually changes
A Cabinet-level regulator consolidating three bodies. What it covers, what it does not change today, and the artefacts worth building before the rules settle.
UAE PDPL and AI: what the 2027 deadline actually requires
Everyone quotes 1 January 2027. Far fewer can say what it rests on. How the PDPL applies to AI systems, which articles matter, and what to fix first.
Bring AI inside your walls.
Talk to us about a private, compliance-ready deployment for your organization.