Nabd in the UAE

Hospital information system for the UAE

Nabd runs its clinical, operational and financial modules in Arabic and English today and exports insurance transactions in the XML formats used in Abu Dhabi and Dubai. Live regulator connections, the health information exchanges and dirham amounts are on the roadmap — here is the honest status of each.

Key facts

Interface language
Arabic (right-to-left) and English, per user
Currency
EGP today; UAE dirham (AED) and UAE VAT are planned
Insurance (Abu Dhabi / Dubai)
Shafafiya and eClaimLink XML export for upload; no live calls
Health information exchange
Malaffi and NABIDH are planned
Deployment
On the hospital’s own server or a dedicated server in the UAE; no shared SaaS
Data residency
Data stays on the hospital’s server inside the UAE

UAE regulations and integrations

"Export" means Nabd writes the regulator’s file format for upload; it does not call the regulator’s web services. "Planned" items are on the roadmap and not available yet.

  • Shafafiya (DOH Abu Dhabi)

    File export

    Prior.Request and Claim.Submission XML files for pre-authorisations and claims, ready for upload. A live web-service adapter needs the facility’s Shafafiya credentials.

  • eClaimLink / DHPO (DHA Dubai)

    File export

    The same XML transactions for upload to DHPO. Live calls are not made today; they need the regulator’s web-service credentials.

  • Malaffi (Abu Dhabi HIE)

    Planned

    Planned as a country plugin on top of the FHIR R4 layer.

  • NABIDH (Dubai HIE)

    Planned

    Planned as a country plugin on top of the FHIR R4 layer.

  • UAE e-invoicing

    Planned

    Planned in the UAE country pack, in line with the national e-invoicing timeline.

  • UAE dirham and UAE VAT

    Planned

    Amounts in the product are in Egyptian pounds today; dirham amounts and UAE VAT are planned.

  • Riayati

    Not covered today

    Not part of the product and not on the current roadmap.

What works in a UAE hospital today

One medical record per patient, clinics and queues, emergency with ESI triage, inpatient wards with the bed board and nursing station, operating theatres, laboratory with critical results and read-back, radiology, blood bank, pharmacy and stores with batch and expiry control, billing with patient and payer shares, and double-entry accounting — in Arabic and English. See the hospital information system, pharmacy and inventory and laboratory.

Insurance in Abu Dhabi and Dubai

Abu Dhabi’s Shafafiya and Dubai’s eClaimLink both use XML transactions. Nabd builds the Prior.Request and Claim.Submission files from the same approvals and invoices staff already record, and keeps a log of every file produced. Today these are files for upload, not live web-service calls; connecting live needs the facility’s DOH or DHA licence and the regulator’s web-service credentials, and then a connector on Nabd’s payer layer. Approvals, rejections, resubmissions and the payer ledger work the same way as in any Nabd deployment — see billing, insurance and claims.

Health information exchanges

Malaffi in Abu Dhabi and NABIDH in Dubai are planned as country plugins on top of Nabd’s FHIR R4 layer. Today Nabd offers a read-only FHIR R4 API that authorised systems can use to read patients, encounters, results, medications and coverages, with every read audited. Sending data to the exchanges is not available yet.

Health data stays in the UAE

Federal Law No. 2 of 2019 on the use of information and communications technology in health fields generally requires health data to be stored and processed inside the UAE, with limited exceptions. Nabd is installed for one hospital on its own server or a dedicated server in the UAE, so patient data does not leave the country through us: the licence check sends five technical values only, never patient data. Confirm the exact requirements for your emirate with your counsel or regulator. See on-premise or cloud for hospital data.

The UAE country pack

Dirham amounts with UAE VAT, e-invoicing and the exchange plugins are grouped in a UAE country pack on our roadmap. In discovery we separate clearly what Nabd does today from what would be built for your hospital, and put both in the written scope.

This page is not legal advice. Regulatory status as of November 2026; confirm your obligations with your counsel and DOH, DHA or the relevant regulator.

Frequently asked questions

Can Nabd submit claims to Shafafiya or eClaimLink directly?

Not today. Nabd exports Prior.Request and Claim.Submission XML files for upload. A live web-service connection needs the facility’s regulator credentials and is added on the payer-connector layer.

Is Nabd connected to Malaffi or NABIDH?

No. Both exchanges are planned as country plugins. Nabd offers a read-only FHIR R4 API today.

Can invoices be in UAE dirhams?

Amounts are in Egyptian pounds today. Dirham amounts and UAE VAT are planned in the UAE country pack.

Does Nabd work with Riayati?

No. Riayati is not part of the product and is not on the current roadmap.

Where is the data hosted?

On the hospital’s own server or a dedicated server in the UAE. Nabd is not a shared SaaS and no patient data is sent to Flexcode Systems.

Discuss a UAE deployment

See the modules on fictional data and the exact status of each UAE integration.