Malaffi & Nabidh HIE Integration:
Complete Guide for UAE Hospitals
Abu Dhabi has Malaffi. Dubai has Nabidh. Every licensed UAE hospital must connect to one or both. Here's what the integration actually involves — technically, operationally, and compliantly.
Every hospital licensed in the UAE — whether in Abu Dhabi, Dubai, or operating across both emirates — must integrate with the emirate's Health Information Exchange (HIE). Malaffi serves Abu Dhabi. Nabidh serves Dubai. Together, they form the backbone of the UAE's national health data infrastructure, enabling patient records to follow patients across any facility in real time.
For hospital administrators and IT teams, the question is rarely whether to integrate — it is mandatory. The question is how: what do the integrations actually require, what does the technical work look like, and how do you choose an HMS that handles both without doubling your implementation burden?
This guide answers all of that, drawing on careup.ai's direct experience integrating with both Malaffi and Nabidh across UAE hospital deployments.
What is Malaffi?
Malaffi — Arabic for "my file" — is Abu Dhabi's Health Information Exchange, launched in 2019 by the Department of Health Abu Dhabi (DOH). It is one of the first operational HIE platforms in the Middle East and among the most technically sophisticated health data exchange networks in the world.
Malaffi aggregates patient health records from every DOH-licensed facility in Abu Dhabi into a unified longitudinal health record accessible to authorised clinicians across the emirate. A patient who visits a clinic in Khalifa City and then presents at Sheikh Khalifa Medical City will have their full medical history available to the treating team — instantly, without any manual record transfer.
- ✓Covers 100% of Abu Dhabi's licensed healthcare facilities
- ✓Over 3 million patient records in the network
- ✓Real-time bidirectional data exchange using HL7 FHIR R4
- ✓Integrated with DOH's Shafafiya licensing and regulatory platform
- ✓Supports Arabic and English clinical documentation
- ✓Patient consent managed under UAE's opt-out model
What is Nabidh?
Nabidh — Arabic for "pulse" — is Dubai's equivalent Health Information Exchange, operated by the Dubai Health Authority (DHA). Launched in the same year as Malaffi, Nabidh enables health data sharing across all DHA-licensed facilities in Dubai, including private hospitals, clinics, pharmacies, and diagnostic centres.
Nabidh is particularly significant for private healthcare providers in Dubai, where the majority of hospitals and specialist clinics operate. It connects facilities ranging from large multi-specialty hospitals like Mediclinic City Hospital to single-specialty day surgery centres.
- ✓Mandatory for all DHA-licensed healthcare facilities in Dubai
- ✓Covers 1,500+ licensed healthcare facilities across Dubai
- ✓Bidirectional FHIR R4 integration with DHA systems
- ✓Linked to Dubai's Salama insurance claims platform
- ✓Supports the Dubai Electronic Medical Record (EMR) initiative
- ✓Integrated with Dubai Pharmacy Programme for medication tracking
Malaffi vs Nabidh: Key Differences
If you operate in one emirate, you need one HIE. If you operate across both, you need both — and your HMS must handle them simultaneously.
| Feature | Malaffi (Abu Dhabi) | Nabidh (Dubai) |
|---|---|---|
| Full name | Malaffi Health Information Exchange | Nabidh Health Information Exchange |
| Jurisdiction | Abu Dhabi Emirate | Dubai Emirate |
| Regulatory body | Department of Health Abu Dhabi (DOH) | Dubai Health Authority (DHA) |
| Launch year | 2019 | 2019 |
| Technical standard | HL7 FHIR R4 | HL7 FHIR R4 / CDA |
| Data shared | Patient demographics, diagnoses, medications, lab results, radiology, allergies | Patient records, diagnoses, procedures, prescriptions, imaging |
| Mandatory for | All DOH-licensed healthcare facilities in Abu Dhabi | All DHA-licensed healthcare facilities in Dubai |
| Patient identifier | Emirates ID + UMRN | Emirates ID + UMRN |
| Consent model | Opt-out (patient consent assumed unless withdrawn) | Opt-out with patient notification |
FHIR R4: The Technical Backbone
Both Malaffi and Nabidh use HL7 FHIR R4 (Fast Healthcare Interoperability Resources) as their data exchange standard. FHIR is a globally recognised healthcare data standard that enables structured, machine-readable health data to be exchanged between systems via REST APIs.
For your HMS to integrate with either HIE, it must be capable of producing and consuming valid FHIR R4 resources. The key FHIR resources required by both Malaffi and Nabidh are:
Critically, both HIEs require a Unified Medical Record Number (UMRN) and Emirates ID linkage at the patient level. Every patient registered in your HMS must be matched to their Emirates ID to enable cross-facility record lookup.
The Integration Process: Step by Step
Whether connecting to Malaffi, Nabidh, or both, the integration process follows a structured onboarding pathway defined by the respective HIE authority.
Facility Registration
Register your facility with the relevant HIE authority — DOH for Malaffi, DHA for Nabidh. You will receive a facility ID and integration credentials.
Technical Onboarding
Your HMS vendor submits integration documentation, architecture diagrams, and sample FHIR payloads to the HIE technical team for review.
Sandbox Testing
Integration is tested end-to-end in the HIE sandbox environment. Mandatory test scenarios must pass before production access is granted.
Go-Live Approval
Upon passing all sandbox tests, the HIE authority issues go-live approval and production API credentials are activated.
Ongoing Compliance
Post go-live, facilities must maintain integration uptime SLAs, respond to HIE version updates, and submit to periodic compliance audits.
Typical timelines: Malaffi integration takes 8–12 weeks from registration to go-live for a new facility. Nabidh integration is similar at 6–10 weeks. For facilities needing both, careup.ai runs parallel workstreams to reduce total time to approximately 10–14 weeks.
What Happens if You Are Not Integrated?
Non-integration with Malaffi or Nabidh is not a technical gap — it is a regulatory violation. DOH and DHA have both made HIE connectivity a licensing requirement for healthcare facilities.
- ⚠ DOH can suspend or revoke facility licences for non-compliance with Malaffi integration requirements
- ⚠ DHA can impose fines and suspend DHA-licensed facilities not connected to Nabidh
- ⚠ Insurance claims via the Unified Insurance Claim Form (UICF) require HIE connectivity for submission
- ⚠ Patients have a right to access their unified health record — facilities not on the HIE cannot contribute to this
- ⚠ Joint Commission International (JCI) accreditation surveys increasingly assess HIE compliance
How careup.ai Handles Both Malaffi and Nabidh
careup.ai is integrated with both Malaffi and Nabidh, making it one of the few HMS platforms in the market with dual UAE HIE connectivity built into the core product — not as an add-on.
- ✓ Native FHIR R4 engine — all clinical data is structured in FHIR format at the point of entry, not converted at export
- ✓ Emirates ID lookup and UMRN linkage at patient registration — no manual mapping required
- ✓ Automatic HIE routing — Abu Dhabi patients sync to Malaffi; Dubai patients sync to Nabidh; multi-emirate patients sync to both
- ✓ Real-time patient record pull from Malaffi/Nabidh at point of care — clinicians see full patient history without leaving the HMS
- ✓ Malaffi and Nabidh audit trail — every data submission, pull, and access event is logged with user, timestamp, and reason
- ✓ Consent management — opt-out handling per DOH and DHA requirements with patient notification workflows
- ✓ Version management — careup.ai tracks HIE API version updates and applies changes without facility downtime
For multi-emirate hospital groups — operating facilities in both Abu Dhabi and Dubai — careup.ai's single-platform architecture means one HMS deployment covers both HIEs, with emirate-specific compliance configuration managed centrally from a unified admin console.
Selecting an HMS for UAE HIE Compliance: 5 Questions to Ask
Q1: Is FHIR R4 native or retrofitted?
Native FHIR means clinical data is structured at the source. Retrofitted FHIR means a conversion layer is applied at export — which introduces mapping errors and maintenance complexity.
Q2: Has the vendor completed Malaffi/Nabidh onboarding for other UAE facilities?
Prior integration experience dramatically reduces your go-live risk. Ask for reference hospitals in the UAE and speak to their IT teams.
Q3: How are Emirates ID and UMRN handled at registration?
Patient matching is the most failure-prone aspect of HIE integration. The HMS should perform Emirates ID verification and UMRN lookup automatically at registration.
Q4: What happens when the HIE API is unavailable?
Your HMS should queue failed submissions and retry automatically. Clinical operations should never depend on HIE availability — the system must degrade gracefully.
Q5: How are HIE API version updates managed?
Malaffi and Nabidh release API updates periodically. Your HMS vendor should manage these updates centrally — you should not need to coordinate a technical project every time the HIE API changes.
Conclusion
Malaffi and Nabidh are not optional IT projects — they are the operating licence conditions for every UAE hospital. The question for hospital administrators is not whether to integrate, but how to do it efficiently, without disrupting clinical operations, and with a technology partner who has done it before.
careup.ai brings dual Malaffi and Nabidh connectivity to UAE hospitals out of the box, backed by native FHIR R4 architecture, Emirates ID-linked patient matching, and a dedicated UAE compliance team. Whether you are opening a new facility, switching from a legacy HMS, or expanding from one emirate to two, careup.ai eliminates the HIE integration burden.
Ready to Connect to Malaffi & Nabidh?
careup.ai handles the full integration — from FHIR mapping to go-live. Talk to our UAE team today.