Hospital Management Software UAE 2026: 6 Picks and NABIDH Rules

Hospital management software in the UAE costs AED 17,000 to 127,500 for a ready HMS configured for a clinic or small hospital, and AED 24,500 to 245,000 for a custom build, the two bands on our published UAE price list (excluding VAT, converted from our GBP list at GBP 1 = AED 4.90 on 11 October 2026). The price is only half the decision. Every DHA-licensed facility in Dubai must connect its hospital management software to NABIDH, every DOH-licensed facility in Abu Dhabi to Malaffi, and every facility bills insurers through eClaimLink or Shafafiya rather than directly. Patient data stays in the UAE under Federal Law No. 2 of 2019. This guide covers all of it with prices, named regulators and the questions to ask before you sign.

I am Ashish, founder of Codingclave. We have built software from Lucknow, India since 2017, 200 plus projects, and the HMS and clinic products in this guide are our own code, built for Indian facilities. I do not sell Epic or Oracle Health, so I have no reason to flatter or bury them.

How much does hospital management software cost in the UAE in 2026?

The honest answer has three tiers, and the sites that rank for this query mostly skip the numbers. SoftwareSuggest's UAE hospital management list, read 5 October 2026, holds 26 products; of the 20 on its first page, 16 say "available on request" and the only hospital product with a number is Halemind at INR 7,500 a year, which tells you how many of the listed vendors are Indian products sold into the UAE without UAE pricing. Capterra's hospital management category ranks by rating and review count and shows no UAE prices either.

Tier	What you get	Price (AED)	Timeline	Source
Ready HMS, UAE configuration	Patient records and EMR, OPD and IPD, appointments, pharmacy, lab, billing, role-based access; Emirates ID fields, AED VAT invoices and Arabic-English print layouts added as set-up work, confirmed in writing	17,000 - 127,500 one time	6 - 12 weeks	Our UAE price list, clinic and healthcare software row
Custom build, hospital grade	Everything above designed around your workflow, plus LIS and RIS integration; the NABIDH or Malaffi connection and eClaimLink or Shafafiya claim files are outside the band and need a named integrator	24,500 - 245,000	6 - 16 weeks on the list, longer once HIE and claims work is in scope	Custom software row on the same list
Enterprise EMR	Epic, Oracle Health (Cerner), InterSystems TrakCare	Not published; multi-year contract quoted per hospital	12 - 30 months	Vendor quotations only

Two notes on the first row. In India the same product lists at INR 49,999 one time or INR 4,999 a month as SaaS on our product page; the UAE band is wider because the product was built for India, and Emirates ID and UAE insurance fields, AED VAT invoices and Arabic-English print layouts are set-up or custom work on top of it, confirmed in writing. A clinic with one to five doctors usually needs the lighter clinic management software, not a full HMS, which brings the price toward the bottom of the band.

What the AED numbers do not include, and what you should get in writing from any vendor:

• Hosting. The health-data rules below decide where it can sit, the cloud provider bills it, and imaging storage is what pushes it up; get the hosting location and the monthly figure in writing before you sign.
• A maintenance retainer for when the six months of free bug fixes after launch end. We quote it with the build.
• Regulator and payer fees, if any, which you pay to DHA, DOH or the payer, not to the software vendor.
• Third-party services the software depends on: WhatsApp Business API conversations for reminders, SMS, a payment gateway for co-pays.

For where a build lands inside the custom band, see our software development cost in Dubai guide. For a clinic group also buying accounting and HR modules, the ERP price for UAE small business post gives the three-year totals.

Which hospital management software is actually used in the UAE?

Six picks, by tier, with what I could verify in October 2026 and what I could not.

Pick	Tier	Where it fits	What I verified	What to ask
Epic	Enterprise EMR	Large hospital groups and academic centres	Epic's public customer page lists US and Canadian systems, no UAE names	Which UAE implementation partner, and the five-year total
Oracle Health (Cerner)	Enterprise EMR	Large public and private networks	Oracle's UAE health page refused my request; no UAE customer names verified	Same, plus the Malaffi or NABIDH connector they will use
InterSystems TrakCare	Enterprise HIS	Mid to large hospitals	Site did not load for me; no customer claims made here	Reference sites in the same emirate
eHospital Systems (Adroit)	Mid-market HIS	Small to mid hospitals	4.9/5 from 73 reviews on Capterra's hospital management list, read 5 October 2026; vendor site blocked my request	Whether it is on Malaffi's connected EMR list and has an eClaimLink schema
MocDoc HMS	Mid-market HIS	Small hospitals, labs, polyclinics	4.9/5 from 44 reviews on the same Capterra list; mocdoc.com names 16 countries including India, Oman, Bahrain and Saudi Arabia, not the UAE; pricing on request	UAE references and the exchange connector
Codingclave HMS	Ready product, configurable	Clinics and smaller hospitals	Our own product, built for India: OPD, IPD, pharmacy, lab, billing, role-based access; UAE fields, VAT invoices and Arabic are set-up work; no NABIDH or Malaffi connection claimed; AED 17,000 - 127,500 on our UAE list, excluding VAT	Everything below, and ask for a guided demo, which shows the Indian configuration

The previous version of this page named two more "local" vendors I could not find evidence for in 2026, so they are gone.

The questions in the last column matter more than the names. The UAE market is full of good Indian hospital software sold through a Dubai reseller, and the software is often fine. The gap is usually the integration layer: is the exchange connection done and tested, who owns the claim schema updates when DHA changes a code list, and what happens when the reseller relationship ends. Get the answers in the contract.

What do DHA, DOH and MOHAP each require from your HMS?

The UAE has three health regulators, and the one that licensed your facility decides your exchange, your claims platform and your inspector.

Regulator	Emirate	Health information exchange	Claims and payer platform	Licensing portal
Dubai Health Authority (DHA)	Dubai	NABIDH	eClaimLink (DHA)	Sheryan
Department of Health Abu Dhabi (DOH)	Abu Dhabi	Malaffi, operated by Abu Dhabi Health Data Services (M42)	Shafafiya (DOH)	DOH licensing
Ministry of Health and Prevention (MOHAP), with Emirates Health Services (EHS) running public facilities	Sharjah, Ajman, Umm Al Quwain, Ras Al Khaimah, Fujairah	Riayati	Payer-specific and the federal basic scheme	MOHAP licensing

The u.ae "Healthcare providers" page, updated 1 October 2026, lists SEHA for Abu Dhabi, DHA for Dubai, MOHAP federally and EHS across the emirates as the entities that run and regulate facilities. Free zones add a layer: Dubai Healthcare City has its own regulator, and a facility there still ends up on NABIDH for exchange purposes. Confirm the licensing path with the free zone before you buy software that assumes DHA forms.

Across all three, the software has to do the same core things: identify patients by Emirates ID, code diagnoses in ICD-10 and procedures in CPT, keep medication data in the regulator's drug code, record consent, log every access to a record, and produce the exchange messages and claim files in the published schema. The differences are in the schema details and the onboarding steps, which is why "UAE compliant" on a brochure means little until you ask which emirate.

NABIDH, Malaffi and Riayati: which exchange does your facility connect to?

Your facility connects to the exchange of the regulator that licensed it. A group with hospitals in Dubai and Abu Dhabi connects to both, and the national layer, Riayati, is where MOHAP-licensed facilities connect and where the emirate exchanges meet.

Exchange	Regulator and operator	Who must connect	What is published and verified
NABIDH	DHA, Dubai	DHA-licensed facilities	DHA publishes the NABIDH policies on dha.gov.ae covering data sharing, consent, access and privacy. I could not reload DHA's pages for counts while writing, so I quote none
Malaffi	DOH Abu Dhabi, operated by Abu Dhabi Health Data Services (M42)	Hospitals, clinics, medical, dental, primary care and one-day surgery centres, school clinics, diagnostic centres, dialysis, IVF centres, mobile health units, pharmacies, home care, telemedicine	3,144 connected of 3,147 signed facilities, 56,192 end users, 100% of hospitals connected; recognised by SNOMED International for clinical data standardisation in a release dated 12 November 2025 (snomed.org) and shown as a Global Reference Site on malaffi.ae; ISO/IEC 27001 and EHNAC accredited; 12 disease registries completed 21 July 2026 (malaffi.ae)
Riayati	MOHAP with EHS	MOHAP-licensed facilities in the five northern emirates	MOHAP's Riayati pages did not load from my location on 5 October 2026, so I state scope only

Malaffi is the one that spells out consequences in plain words. Its "facilities required to connect" page says the deadline for active-licence facilities has closed, that facilities not connected will not be able to renew their DOH licence, and that facilities with Daman agreements cannot submit claims until connected. New facilities on a preliminary licence are told to contact Malaffi at least two months before applying for an active licence. I treat NABIDH the same way for Dubai: it is a licensing dependency, and the software contract should say who does the connection work and by when.

What the connection work actually involves, from the facility's side:

1. Register the facility and the EMR vendor with the exchange and get test credentials.
2. Map the HMS data model to the exchange's message set: patient demographics with Emirates ID, encounters, diagnoses in ICD-10, procedures, medications, allergies, lab and radiology results.
3. Send the required message types from a test environment and pass the exchange's validation.
4. Implement the consent and access rules in the policies, including the audit log of who viewed what.
5. Go live with monitoring, because a message type that silently fails will surface months later at an audit.

Malaffi's SNOMED recognition tells you where the standards are going: coded clinical content, not free text. If your HMS stores diagnoses as typed notes, the exchange connection becomes a data-cleaning project first.

How do insurance claims work: eClaimLink in Dubai and Shafafiya in Abu Dhabi?

Health insurance is mandatory in Dubai and Abu Dhabi, and since 1 January 2025 private-sector employers in the other five emirates must buy a basic package priced at AED 320 a year for workers aged 1 to 64 (u.ae, "Getting a health insurance", updated 8 September 2026). Dubai's own law was phased in between 31 October 2014 and 30 June 2016 (Wikipedia's DHA article). The practical result is that almost every patient who walks in has a payer, and your HMS lives or dies on claims.

Claims do not go to each insurer in its own format. They go through the regulator's platform:

• eClaimLink is DHA's claims system. Its site publishes the coding standards DHA mandates for providers and payers: the Dubai Drug Code (DDC), the CPT list and the HCPCS list, as the eClaimLink Standard Data Sets, with a Provider Quick Guide and Payer User Guide. Your HMS must produce claim files that validate against the current schema and keep these code tables current.
• Shafafiya is DOH's equivalent for Abu Dhabi. Its portal holds the data dictionary and the standards for encounters, episodes, claims, activities and observations, and the Shafafiya Post Office moves the files between providers and payers as web-service transactions. DOH states that all Abu Dhabi healthcare entities are required to monitor the standards update page, which in software terms means somebody owns schema changes.

The payers behind the platforms include Daman and its Thiqa programme for Abu Dhabi nationals, Sukoon (the renamed Oman Insurance), ADNIC, Dubai's Enaya scheme for government employees, and third-party administrators such as NAS that adjudicate on behalf of insurers. A note on a mistake in the earlier version of this page: NAS is a TPA, not the ambulance service, and I have corrected it.

The claim workflow your software needs as first-class features, not as an export button:

1. Eligibility check at registration against the payer's response, with the policy network and co-pay captured.
2. Prior authorisation for procedures and admissions that need it, with the approval reference stored on the encounter.
3. Coding of the encounter in ICD-10, CPT and the regulator's drug code, by the clinician or coder, with validation before submission.
4. Claim file generation in the platform's schema and submission in the batch cycle.
5. Remittance import, reconciliation against the submitted claim, and posting of the paid, short-paid and rejected amounts.
6. Rejection management with reason codes, correction and resubmission inside the payer's time window.

In my view, step 5 is where most hospital software falls over. Many systems can submit; far fewer can import the remittance and tell the finance team, per claim, what was paid and why the rest was not. Ask every vendor to show remittance reconciliation on a demo, not a slide.

Where can you host hospital data in the UAE?

Federal Law No. 2 of 2019 on the use of ICT in health fields is the rule that matters. Article 13 prohibits storing, processing, generating or transferring health information outside the UAE unless the health authority of the emirate authorises it in coordination with the Ministry, and Ministerial Decision No. 51 of 2021 sets out the permitted exceptions (DLA Piper's UAE data protection guide). The Personal Data Protection Law, Federal Decree-Law 45 of 2021, keeps the existing health data rules intact rather than replacing them. UAE law firms also summarise the ICT law as setting a long minimum retention period for health records; confirm the current figure with counsel, because it changes how you size storage and design deletion.

So the default is UAE-region hosting, and the choice is which one:

Option	What is verified	Fit
Microsoft Azure UAE North	Dubai, three availability zones (Microsoft's region list, updated 23 September 2026)	The safe default for a hospital workload in 2026
Microsoft Azure UAE Central	Abu Dhabi, restricted-access region paired with UAE North	Disaster recovery for Abu Dhabi facilities, by request
AWS Middle East (UAE), me-central-1	AWS's infrastructure page lists 39 regions and says nothing about status; Wikipedia's AWS article states the UAE and Bahrain regions were damaged in March 2026 during the Iran war and listed unavailable from 1 March 2026	Check the AWS Health Dashboard before you commit; I would not plan a new hospital deployment on it without that check
On-premise or UAE private cloud	Your own servers in the facility or a UAE data centre	Imaging-heavy hospitals and facilities with poor connectivity; you own backups and patching
Hybrid	Clinical database in the UAE region, analytics and non-identifying reports wherever convenient	Groups with a data team; the de-identification has to be real

What to put in the contract with any vendor, us included: production database and files in a UAE region unless the regulator has authorised otherwise, no real patient data in development or staging, encryption at rest and in transit, a signed data processing agreement, and an access log the facility can export. The exchange and claims platforms sit inside the UAE anyway, so a UAE region also keeps latency sane. The contracting side is in why Dubai businesses outsource software to India: code can be written anywhere, data cannot live anywhere.

Which modules does a UAE hospital actually need?

The module list looks like every other country's until you read the right-hand column.

Module	What it must do in the UAE	Why
Registration and EMR	Emirates ID as the identifier, passport fallback for visitors, Arabic and English names, insurance card capture at the desk	Exchange messages and claims both key on Emirates ID
OPD and appointments	Doctor schedules, queue, WhatsApp or SMS reminders in Arabic and English, telemedicine encounters flagged for the exchange	No-shows are one of the biggest avoidable revenue losses for a clinic
IPD and bed management	Admission, transfers, discharge summary in the exchange format	Discharge data is a mandatory exchange message
Pharmacy	Regulator drug code on every item, batch and expiry, controlled-drug register	eClaimLink mandates the Dubai Drug Code on pharmacy claims
Laboratory and radiology	Orders and results with coded tests, DICOM links for imaging, results pushed to the exchange	Results are exchange messages, not just PDFs
Billing	AED, per-item VAT treatment because healthcare is not uniformly zero-rated, split between payer and patient share	The FTA treats some services differently; the invoice has to show it
Insurance and claims	The six-step workflow above, with schema validation and remittance reconciliation	This is the cash flow
HR and credentialing	Staff licence numbers and expiry per regulator	Inspectors check that the person who signed the note is licensed
Audit and consent	Who viewed which record, when, and the patient's consent status	Required by the exchange policies and the ICT law
Reporting	Regulator statistics, payer ageing, department P&L	Finance will ask for the claims ageing on day one

Our HMS covers registration and EMR, OPD and IPD, pharmacy, lab, billing, role-based access and MIS reports out of the box. It was built for India, so AED VAT invoices, Emirates ID fields, UAE insurance claims and Arabic layouts are set-up or custom work, confirmed in writing in the quote, as is radiology integration. The NABIDH or Malaffi connection and the eClaimLink or Shafafiya claim files are not part of the product, so agree in writing who delivers them.

What does a UAE HMS implementation look like, week by week?

For a ready product configured for a clinic or small hospital, the six to twelve weeks on our UAE price list break down like this; a small clinic with no exchange backlog finishes at the short end. A custom hospital build stretches each block, and the exchange and claims work becomes the critical path.

Weeks	Work	Who is on the critical path
1 - 2	Workflow walkthrough on video, department by department; master data collected: doctors, services, price lists, payer contracts, drug formulary	The facility: one decision-maker and the master data
2 - 4	Configuration: Emirates ID fields, VAT codes, Arabic-English print layouts, roles; regulator registration for the exchange and the claims platform started	Us for configuration; the facility for the regulator paperwork
4 - 8	Exchange connection and claims schema tested in the sandbox by the integrator the contract names; data migration from the old system or spreadsheets	Us for the migration; the named integrator, plus the exchange's testing turnaround
8 - 10	Staff training by role; parallel run on live registrations; remittance reconciliation tested on the first real cycle	The facility's super-users
10 - 12	Go-live, hypercare, first month-end close with claims ageing	Both

Three things decide whether you finish on time. First, the regulator paperwork must start in week 2, not week 8; Malaffi's own guidance of at least two months before the licence application is a fair proxy for every exchange. Second, master data: a price list that still has three versions in Excel will add weeks. Third, parallel running: run the old and new systems on live registrations for at least two weeks, because the first rejected claim batch teaches you more than any UAT script. Migration from an existing HMS with years of records is priced in the quote, and the figure depends on how clean the old database is.

Should you buy a ready HMS, a SaaS clinic tool, or build custom?

Buy a ready, configurable HMS when you run a clinic, polyclinic or smaller hospital, want to go live in weeks, and your workflows are standard enough that configuration covers them. This is most facilities, and it is the AED 17,000 to 127,500 band.

Build custom when the workflow is the business: IVF centres, dialysis chains, cosmetic surgery groups, home care operators with field staff, or a group that needs one platform across emirates with different exchanges. Expect the AED 24,500 to 245,000 custom band on our list for the software, with the exchange connections and claims schemas priced on top by whoever delivers them, and plan a maintenance retainer for when the six months of free bug fixes end.

Choose an enterprise EMR when you have hundreds of beds, a CIO, a capital budget approved over several years and the implementation partner already in the room. Epic and Oracle Health earn their price at that scale and lose it below it.

Choose SaaS clinic software when you are one to five doctors and your biggest problems are appointments, reminders and a clean invoice. Our clinic management software has a live demo you can click through before talking to anyone; it shows the Indian set-up, so VAT invoices, Arabic and where the data is hosted are agreed in writing for a UAE clinic.

Whatever you choose, price it over five years: licence or build, hosting, retainer, the exchange and claims work, and the cost of the staff hours the system saves or wastes. A cheap system that cannot import remittances costs a finance clerk's salary every year. The patient-facing website is a separate, smaller purchase; our UAE hospital and clinic website guide covers the doctor directory, Arabic pages and the DHA ST-21 wording rules.

What our healthcare work has taught us

Codingclave has been building software from Lucknow, India since 2017, founder-led, with 200 plus delivered projects, a 4.9 star Google rating from 76 reviews and Top Rated status on Upwork. Our HMS and clinic products are our own code, built in India with ABHA and ABDM readiness, India's national digital health programme, so designing software around a national health-data standard is not new to us.

Three things from our healthcare and Arabic work that I would pass on to anyone buying in the UAE:

1. The exchange connection is a project, not a checkbox. Every facility underestimates the master data cleanup that coded exchange messages demand. Start it in week one.
2. Remittance reconciliation is the module nobody demos and everybody needs. Ask to see a real remittance file imported and matched against claims before you sign.
3. Arabic is a design decision, not a translation. Right-to-left layouts, Arabic names alongside English on every printed document, and Arabic WhatsApp templates for reminders change the build from day one. Our AI and WhatsApp chatbot page covers what a clinic bot should answer, in Arabic and English.

What I will not claim: a NABIDH or Malaffi connection, or a certification badge from a regulator. If your facility needs the exchange connection, the contract should name who builds and certifies it, and that is a question to put to every vendor on the list above. If you want a vendor with a long list of named UAE hospital references, the enterprise tier is where you will find it, at the enterprise price.

For the broader picture of building healthcare software, including compliance design and where the hours go, see our healthcare software development guide.

Next step: a scope and an AED quote

Send us five things and Ashish or the team replies during our hours, Monday to Saturday 8:30am to 5:30pm Gulf time, with a written scope, an AED price band that becomes a fixed price once the scope is agreed, and a realistic timeline: the emirate and licence type, the number of doctors or beds, the departments you run (pharmacy, lab, imaging, IPD), the payers you contract with, and the system you use today. Message WhatsApp +91 92771 84741, email hello@codingclave.com, or send the brief through our free AED quote form. If a guided demo of the HMS helps first, book it on the product page. If the brief tells us an enterprise EMR is the right answer for you, we will say so in the same reply. Invoices are in AED, paid by bank transfer to our AED account in three stages (40% at the start, 40% at a mid-project milestone, 20% at launch), and you own the code and IP on final payment. Prices exclude VAT; we are not UAE VAT-registered, so a VAT-registered facility usually accounts for it under the reverse charge, which your tax adviser should confirm.