Hospital Management System in UAE: DHA, DOH, MOHAP and NABIDH Guide

A hospital management system in UAE has to do much more than register patients and print bills. It must connect to the health information exchange for your emirate, submit insurance claims electronically in the formats your regulator expects, code diagnoses and procedures correctly, work in Arabic and English, apply VAT properly and keep patient data in line with UAE health data rules.

Get those right and the system becomes the backbone of a well-run facility. Get them wrong and you face rejected claims, failed exchange submissions and compliance findings that take months to fix.

This guide is for owners, medical directors, administrators and IT managers of hospitals, day-surgery centres, polyclinics and clinics in Dubai, Abu Dhabi and the northern emirates. It explains the regulatory landscape, the integrations you need, the features to insist on and the questions to ask vendors. Regulations change, so always confirm current requirements with your regulator.

The UAE healthcare regulatory landscape

Healthcare in the UAE is regulated at both emirate and federal level. Which body licenses you determines many of your software requirements.

Each regulator sets its own licensing rules, data standards, insurance and claims processes and audit expectations. A hospital management system that works well in Dubai may need additional work before it is ready for Abu Dhabi, and vice versa. If you operate across emirates, plan for each regulator's requirements from the start.

Health information exchange: NABIDH, Malaffi and Riayati

The UAE has invested heavily in health information exchanges that let a patient's records follow them between providers.

• NABIDH is Dubai's health information exchange, run by DHA. Licensed facilities in Dubai are expected to connect and share defined clinical and administrative data.
• Malaffi is Abu Dhabi's health information exchange, run under DOH. Facilities licensed in Abu Dhabi connect to share and access patient records.
• Riayati is the national unified medical record platform used by facilities under MOHAP and Emirates Health Services, mainly in the northern emirates.

These exchanges typically use HL7-based messaging for events such as registrations, visits, admissions, discharges, orders and results. Connection usually involves technical onboarding and conformance testing before go-live, and ongoing monitoring of message quality afterwards.

For your HMS, this means:

• Patient demographics, including Emirates ID, must be captured accurately and consistently.
• Clinical events must generate the right messages at the right time.
• Errors and rejections from the exchange must be visible and fixable by your team.
• Coding must follow the standards the exchange and regulator expect.

Our guide to HL7 and FHIR integration explains the underlying standards, and our healthcare integration page covers how these connections are typically built.

Insurance and electronic claims

Health insurance has long been mandatory for residents in Dubai and Abu Dhabi, and since January 2025 employer-provided cover has also been mandatory for private-sector employees and domestic workers in the northern emirates. As a result, most UAE facilities handle a high volume of insured patients, and claims are submitted electronically.

• In Dubai, prior authorisations and claims run through DHA's electronic claims platform, eClaimLink.
• In Abu Dhabi, they run through DOH's Shafafiya platform.
• Other emirates have their own processes, and many insurers and TPAs also have their own portals.

A hospital management system in UAE should handle:

1. Eligibility checks and capture of insurance card and Emirates ID at registration.
2. Prior authorisation requests and responses, linked to the visit or admission.
3. Accurate coding using ICD-10-CM for diagnoses, CPT for procedures and the regulator's drug and service codes.
4. Claim generation and submission in the required format.
5. Remittance processing and reconciliation against claims.
6. Rejection management, with reasons, resubmission and reporting by payer.

Claim rejections are one of the biggest sources of revenue leakage for UAE providers. Software that validates codes and required fields before submission prevents many of them.

Arabic and bilingual support

UAE facilities serve Emiratis, Arabic-speaking expatriates and a large non-Arabic-speaking population. Your system should support:

• Patient names and demographics in Arabic and English.
• Right-to-left layouts for Arabic screens and documents.
• Bilingual prescriptions, consent forms, discharge summaries and invoices.
• SMS and WhatsApp messages in the patient's preferred language.
• Arabic search that handles different spellings and transliterations.

Bilingual support is more than translated labels. Check printed documents carefully, especially mixed Arabic and English layouts.

VAT and billing in the UAE

The UAE applies VAT at a standard rate of 5%. In healthcare, certain preventive and basic healthcare services and some medicines and medical equipment can be zero-rated, while other services and products are standard-rated. The correct treatment depends on the service, so your billing must apply VAT line by line and produce compliant tax invoices.

Check that the system can:

• Configure VAT treatment per service, item and package.
• Split patient share and insurer share correctly, with VAT on each where applicable.
• Produce tax invoices and credit notes in the required format.
• Report VAT for your returns.

The UAE is also introducing electronic invoicing in phases, so ask vendors about their plans to support it. Always confirm VAT treatment for specific services with your tax advisor.

Data protection and data residency

UAE health data is subject to specific rules. Federal Law No. 2 of 2019 on the use of information and communication technology in health fields sets requirements for health data, including that it is generally stored and processed within the UAE unless an exception applies. Emirate regulators add their own standards; for example, DOH applies the Abu Dhabi Healthcare Information and Cyber Security Standard (ADHICS) to Abu Dhabi facilities.

For your HMS, that typically means:

• Hosting patient data in UAE data centres, whether in a cloud region in the UAE or on-premise.
• Role-based access, audit trails and strong authentication.
• Encryption in transit and at rest.
• Documented backup, recovery and incident response processes.
• Clear contracts on who can access data, including vendor support staff outside the UAE.

Core modules for UAE hospitals and clinics

The core of a hospital management system in UAE is similar to anywhere else, with local requirements layered on top.

• Registration with Emirates ID and insurance capture.
• Appointments, queues and online booking.
• OPD and EMR with specialty templates and coded diagnoses.
• IPD, nursing, bed management and OT for hospitals and day-surgery centres.
• Pharmacy with local drug codes and controlled drug handling.
• Lab and radiology with result flow and exchange messaging.
• Billing, insurance, e-claims and VAT.
• Exchange integration with NABIDH, Malaffi or Riayati.
• Dashboards for occupancy, revenue, claims and rejections.

For a detailed breakdown, see our hospital management system modules list.

Questions to ask HMS vendors in the UAE

1. Which emirates and regulators do your current UAE clients operate under?
2. Is your system connected to NABIDH, Malaffi or Riayati today, and can we see it working?
3. How do you handle prior authorisations, claims, remittances and rejections for our emirate?
4. Which code sets do you support, and how are code updates applied?
5. How complete is your Arabic support, including printed documents?
6. How do you handle VAT treatment per service and package?
7. Where will our data be hosted, and who can access it?
8. What are your support hours in UAE time, and is on-site support available?
9. How do you handle regulatory changes, and are they included in support fees?
10. How do we export all our data if we leave?

Our guide on how to choose hospital management software includes a demo checklist you can adapt for UAE scenarios.

Multi-emirate groups and growing networks

Many UAE healthcare groups start with one clinic in Dubai and later add facilities in Abu Dhabi, Sharjah or other emirates. Each new emirate can bring a different regulator, exchange, claims platform and set of codes. If expansion is likely, ask vendors early:

• Can one installation serve facilities licensed under different regulators?
• Can price lists, payer contracts and code sets be managed per facility?
• Can one patient record be shared across the group while each facility reports to its own exchange?
• Can management see consolidated dashboards across emirates?

Choosing a system that can grow across emirates is much cheaper than running two or three disconnected systems later and trying to reconcile them.

Product, local vendor or custom build?

UAE facilities typically choose between established products already integrated with their regulator's systems, local implementation partners who configure and support products, and custom-built systems designed around a facility's workflows.

Products with existing exchange and e-claims integrations reduce regulatory risk, which matters a lot. Custom builds make sense for groups with unusual workflows, multi-emirate operations or a strong preference for owning their platform, provided the partner has real integration experience and allows time for conformance testing.

Algon Solutions builds hospital management systems and healthcare software for clients in India, the UAE and the USA, working around each facility's existing workflows. For UAE projects, regulator integration and testing are planned into the schedule from the start rather than left to the end.

Implementation timeline considerations

UAE projects often take longer than buyers expect because of regulatory steps. Plan for:

• Mapping your workflows and payer mix.
• Configuring codes, price lists, payer contracts and VAT rules.
• Building and testing exchange and e-claims integrations.
• Conformance testing with the exchange or regulator.
• Staff training in both languages where needed.
• A parallel run before full cut-over.

Starting integration and testing early is the single most effective way to avoid delays.

Conclusion

A hospital management system in UAE must handle your regulator's rules, connect to NABIDH, Malaffi or Riayati, manage electronic claims with accurate coding, work in Arabic and English, apply VAT correctly and keep patient data in line with UAE health data law. Start with your emirate and payer mix, test real scenarios and insist on seeing integrations working.

If you are planning a new facility or replacing your current system in the UAE, talk to our team about your requirements.