UAE Digital Health 2026: NABIDH, DOH, Malaffi, and Riayati Explained

In this guide, you’ll learn:
- Why UAE Digital Health Matters Right Now
- UAE Digital Health Quick Glance
- NABIDH: Dubai's Health Information Backbone
- Malaffi: Abu Dhabi's Connected Health Record
- Riayati: The National Unified Medical Record
- What's DOH Role in Abu Dhabi's Digital Health Mandate
- Side-by-Side Platform Comparison
- Emirates ID, Digital Insurance & the 2026 Shift
- What This Means for Digital Health Builders
- Compliance Checklist for Health IT Teams
The UAE has quietly built one of the most ambitious national health data ecosystems in the world. But as new regulations, platform integrations, and digital mandates take effect in 2026, the stakes for digital health teams have never been higher.
Whether you're a health startup integrating your EMR, a hospital's Head of Health IT managing compliance deadlines, or a GCC-focused insurer rethinking your verification workflows for Emirate markets; Understanding how these platforms work, who governs them, and what your obligations are is now a business-critical requirement.
| Metric | Scale |
|---|---|
| Medical records on Riayati for 9.5M patients | 1.9B |
| Facilities connected to Malaffi across Abu Dhabi | 3,000+ |
| Health providers with access to Riayati records | 90K+ |
| Clinical users on the Malaffi platform | 50,000 |
Key Insight for Builders
The UAE doesn't have one national health platform, in fact it has 3 interconnected ones, each governed by a different authority and covering a different geographic scope. Getting this right from Day 1 saves months of re-work.
UAE Digital Health Quick Overview
The UAE operates a federated healthcare governance model. This means health regulation is split between Federal-level authorities and Emirate-level bodies. For digital health, this means- you have to focus on three distinct but now interconnected health information exchange platforms.
NABIDH National Backbone for Integrated Dubai Health. Governs the exchange of clinical records across all DHA-licensed facilities in Dubai. This comes under Dubai Health Authority (DHA)
Malaffi The region's first HIE, meaning "my file" in Arabic. Connects public and private healthcare across Abu Dhabi and Al Ain. This comes under Department of Health -Abu Dhabi (DoH)
Riayati The National Unified Medical Record (NUMR). Covers Northern Emirates and acts as the federal umbrella integrating NABIDH and Malaffi. This is covered in MOHAP (Ministry of Health & Prevention)
MOHAP / DOH MOHAP governs federal-level standards. DOH governs Abu Dhabi. Both set mandatory compliance rules for any licensed health entity. This comes in Federal Regulator.
Common Misconception
Many teams assume connecting to one platform means they're covered across the UAE. This is incorrect. If you operate in multiple emirates, or serve patients across emirate boundaries, you likely need integrations with more than one platform.
Now let's understand these in detail.
NABIDH — Dubai's Health Information Backbone
NABIDH (National Backbone for Integrated Dubai Health) is the Dubai Health Authority's (DHA) mandated health information exchange. Every DHA-licensed healthcare facility in Dubai is required to integrate with it — with narrow exemptions for specific wellness and alternative medicine providers.
What NABIDH Does
- Centralises patient health records for the Emirate of Dubai.
- Enables real-time clinical data sharing: encounters, prescriptions, lab results, radiology.
- Supports patient identification via Emirates ID.
- Uses HL7 data exchange standards (FHIR-compatible in newer implementations).
- Is now integrated with Riayati (national level) via the 2023 tri-platform agreement.
NABIDH Onboarding: What to Expect
This is where most teams underestimate the timeline. NABIDH onboarding is a staged, scheduled process. It is not plug-and-play.
Build Status (Pre-certified EMRs skip this) If your EMR is already NABIDH-certified, you skip the build phase and proceed directly to System Integration Testing (SIT).
SIT Checklist API configuration, IP whitelisting, and masked message validation. This phase must be completed before live data is transmitted.
Data Monitoring Live monitoring of masked (de-identified) messages to ensure data flows correctly before full go-live.
SIT Testing & Sign-off Complete all SIT scenarios and obtain signed SIT certificate from DHA.
Cutover & Go-Live Includes RFC (Request for Change), production config, IP whitelisting in production, connectivity testing, and final go-live confirmation.
Realistic Timeline: 6–8 Weeks Post Go-Live
DHA schedules onboarding in queues. Any vendor or consultant claiming "instant NABIDH onboarding" is misleading you. Mark this into your compliance and launch planning. Active onboarding proof is typically accepted as interim compliance evidence.
Malaffi — Abu Dhabi's Connected Health Record
Launched in 2019 as the region's first Health Information Exchange, Malaffi (Arabic for "my file") is a strategic initiative of the Department of Health – Abu Dhabi (DoH). It is operated by Abu Dhabi Health Data Services (ADHDS), a public-private partnership under M42.
Malaffi is widely regarded as one of the fastest-implemented and most technically advanced HIE platforms globally connecting Abu Dhabi's entire hospital network in under three years.
| Metric | Scale |
|---|---|
| Connected healthcare facilities | 3,000+ |
| Patient records stored | 8M |
| Authorized clinical users | 50K |
| Different EMR systems connected | 90+ |
What Makes Malaffi Different
- Predictive Patient Risk Profiles: AI-powered risk scores for chronic conditions (diabetes, CKD, CHF, hypertension) and acute events (heart attack, stroke)
- Radiology Image Exchange: Not just reports — actual DICOM images shared across facilities
- Patient Health Portal: Mobile app on iOS and Android; patients directly access their own longitudinal record
- SNOMED CT at scale: First HIE in MENA to implement SNOMED CT comprehensively, improving data interoperability from 12% to 85%+ LOINC adoption for lab results by mid-2025
- Full integration with Riayati and NABIDH: since the tri-platform agreement signed at Arab Health 2023
Malaffi Onboarding Process
- System Code issuance: 4–6 weeks — this is the unique identifier for your EMR integration
- Onboarding itself: 2–3 weeks once System Code is issued
- SD-WAN requirement: Malaffi requires SD-WAN infrastructure for connectivity. Note: cloud SD-WAN supports data submission but viewing data through it is currently not supported
- Security validations: Additional security review is mandatory before go-live
For Health AI Builders
Malaffi's SNOMED CT and LOINC standardization across 3,000+ facilities means the data quality in Abu Dhabi is among the highest available for training clinical AI models in the MENA region. If your product involves population health analytics or AI diagnostics, Abu Dhabi's interoperability infrastructure is a genuine asset.
Riayati — The National Unified Medical Record
Riayati (meaning "my care") is MOHAP's national Health Information Exchange and home of the National Unified Medical Record (NUMR) program. It was launched under the directive of H.H. Sheikh Mohammed bin Rashid Al Maktoum and represents the federal umbrella that ties NABIDH, Malaffi, and Northern Emirate facilities into a single national health data layer.
Riayati's Scope
- Primary coverage includes Northern Emirates (Sharjah, Ajman, Umm Al Quwain, Ras Al Khaimah, Fujairah)
- Also integrates NABIDH (Dubai) and Malaffi (Abu Dhabi) through the national unified platform
- Connects over 3,057 healthcare facilities nationwide
- 1.9 billion medical records for 9.5 million patients, accessible by 90,000+ health providers
- Integrated with the Federal Authority for Identity and Citizenship (ICA) — patient matching via Emirates ID
- Integrated with the Alhosn national app via FHIR interface for vaccination data sharing
- Includes the eClaims "Post Office" initiative enabling seamless insurance claim exchange between facilities and insurers
How Riayati Integrates the Three Platforms
Pre-2023: Siloed Systems NABIDH, Malaffi, and Riayati operated independently. Patient records did not automatically cross emirate boundaries.
Arab Health 2023: Tri-Platform Integration Announced MOHAP, DHA, and DoH signed a formal agreement to electronically link all three platforms, creating a central national health data exchange layer.
2024–2025: Live Integration Active Records from NABIDH and Malaffi feed into Riayati's national unified record. A patient treated in Dubai can have their history accessed (with permissions) by a provider in Sharjah or Abu Dhabi.
2026: Full Emirates ID-linked verification active All platforms now use Emirates ID as the primary patient identifier, eliminating duplicate records and supporting the digital insurance verification mandate.
Riayati Onboarding for MOHAP-Licensed Facilities
- Mandatory for all MOHAP-licensed facilities including clinics in Northern Emirates
- EMR must be HL7-compliant and support national patient identifiers
- Onboarding typically takes 4–6 weeks
- Required for license renewals in Northern Emirates, non-compliance can block renewal
- Early start is strongly advised to avoid queue delays affecting your licensing timeline
License Renewal Risk
Riayati compliance is directly tied to MOHAP license renewals in the Northern Emirates. If your facility has not started the onboarding process, begin immediately. Pending onboarding (with active proof) is currently accepted as interim compliance but delays can lead to renewal complications.
What's DOH Role in Abu Dhabi's Digital Health Mandate
The Department of Health – Abu Dhabi (DoH) is the regulatory body for Abu Dhabi's entire healthcare sector. Unlike DHA (which both regulates and provides care), the DoH is purely a regulator.
They're basically overseeing licensing, quality standards, and digital health mandates for the Emirate.
What the DoH Mandates for Digital Health
- All DoH-licensed facilities must integrate with Malaffi, means no exceptions for hospitals or medical centres
- A minimum data set must be captured and transmitted from source EMR and lab systems to Malaffi HIE
- Health insurance verification in Abu Dhabi must use the Malaffi platform via Emirates ID (physical insurance cards are no longer the primary verification method in 2026)
- Unified Digital Health Licensing covering 200,000+ healthcare professionals with real-time policy verification at point of care
- Enhanced cybersecurity protocols for all entities handling patient biometric and insurance data
DoH vs. DHA: Key Differences for Builders
| Aspect | DoH (Abu Dhabi) | DHA (Dubai) |
|---|---|---|
| Primary Role | Pure regulator | Regulator + provider (runs hospitals) |
| HIE Platform | Malaffi | NABIDH |
| Coverage Area | Abu Dhabi, Al Ain | Dubai |
| Insurance Verification | Emirates ID via Malaffi | Emirates ID via NABIDH |
| AI Capabilities | Predictive risk profiles (Malaffi) | Integrated clinical data exchange |
| Data Standard | SNOMED CT + LOINC (full implementation) | HL7 / FHIR |
Side-by-Side Platform Comparison
This is the table your team needs on the wall. Use it to determine which integration(s) apply to your product or facility.
| Feature | NABIDH | Malaffi | Riayati (NUMR) |
|---|---|---|---|
| Governing Authority | Dubai Health Authority (DHA) | Department of Health – Abu Dhabi (DoH) | MOHAP (Federal) |
| Geographic Coverage | Dubai | Abu Dhabi, Al Ain | Northern Emirates + National umbrella |
| Compliance Mandatory? | Mandatory (DHA) | Mandatory (DoH) | Mandatory (MOHAP) |
| Connected Facilities | All DHA-licensed | 3,000+ | 3,057+ |
| Patient Records | Dubai population (~3.6M) | ~8M records | 1.9B records, 9.5M patients |
| Data Standard | HL7 / FHIR | SNOMED CT, LOINC, HL7/FHIR | HL7, FHIR, SNOMED CT |
| Patient Identifier | Emirates ID | Emirates ID | Emirates ID (ICA-linked) |
| AI Features | Clinical data exchange | Predictive risk profiles, population health | Population health analytics |
| Onboarding Time | 6–8 weeks post go-live | 4–6 weeks (System Code) + 2–3 weeks onboarding | 4–6 weeks |
| Insurance Integration | Yes (2026 mandate) | Yes (2026 mandate) | Yes (eClaims Office) |
| Cross-Platform Integration | Yes (via Riayati) | Yes (via Riayati) | National umbrella for all three |
| Patient-Facing Portal | Limited | Yes (mobile app, iOS & Android) | e-Portal (in development) |
Emirates ID, Digital Insurance & the 2026 Shift
In 2026, the UAE has officially moved away from physical health insurance cards. The new verification method: Emirates ID, biometrically linked to every active insurance policy. This isn't a future plan, it's live now, across Dubai (NABIDH) and Abu Dhabi (Malaffi).
How Digital Verification Works in Practice
- In Dubai: Clinics access your policy and network details via NABIDH when you present your Emirates ID or scan via UAE Pass
- In Abu Dhabi: DOH-regulated providers use Malaffi for the same function — real-time policy, co-pay rules, and benefit limits at the point of care
- In Northern Emirates: MOHAP oversees verification via the Riayati-linked national framework
- For dependents: Emirates ID or residency visa number links to the primary policyholder's plan with no separate family cards needed
| Feature | Pre-2026 (Traditional) | 2026 Digital Framework |
|---|---|---|
| Primary Verification | Physical insurance card | Emirates ID / Biometric link |
| Dependent Access | Separate physical cards | Linked via residency/visa number |
| Network Confirmation | Manual call to insurer | Real-time via NABIDH / Malaffi |
| Claim Initiation | Paper forms at clinic | Digital via insurer app or portal |
| Dispute Resolution | Phone/email, weeks of wait | Digital dispute portal (2026 framework) |
| Out-of-Pocket Visibility | Policy document only | Live display at point of care |
| Cross-Emirate Verification | Not automatic | Partial (interoperability still developing) |
Still Not Fully Interoperable
Dubai (NABIDH) and Abu Dhabi (Malaffi) operate separate verification ecosystems that are not yet fully interoperable. If your product or clinical workflow crosses emirate lines, always confirm which platform governs that specific care encounter. Cross-emirate interoperability is improving but is still in development as of 2026.
What This Means for Digital Health Builders
If you're building a digital health product, running a hospital innovation unit, or leading a government health digital initiative in the GCC, here's what these platforms mean for your day-to-day decisions:
For Health Startups (Founders / CTOs)
- Choose your target emirate early—it defines your HIE integration path.
- Use pre-certified vendors (NABIDH, Malaffi, Riayati) to save months.
- Set Emirates ID as the primary patient identifier.
- Follow HL7 FHIR; Malaffi also needs SNOMED CT coding.
- Plan 8–12 weeks per HIE onboarding, including authority queues.
For Hospital Innovation Units / Chief Digital Officers
- Multi-emirate operations require separate HIE compliance strategies.
- Data can flow across platforms, but access depends on consent and permissions.
- Leverage Malaffi's AI risk profiling beyond compliance.
- Onboarding proof works for licensing; full integration is needed for compliance.
For Health Insurance Platforms
- The 2026 mandate requires Emirates ID-linked verification.
- Integrate Riyati eClaims for Northern Emirates processing.
- Ensure systems support digital verification before denying coverage.
GCC Expansion Note
If you're a GCC-native builder expanding beyond UAE, then Saudi Arabia (Nphies), Bahrain, and Kuwait are developing their own HIE frameworks. The interoperability standards and HL7 FHIR experience you build for UAE will translate directly, but each country has its own regulatory governance. UAE remains the most mature model in the region as of 2026.
Compliance Checklist for Health IT Teams
Use this as your pre-launch and ongoing compliance reference, regardless of which emirate you operate in.
Platform Integration
Identify applicable HIEs (NABIDH, Malaffi, Riayati)
Identify applicable HIEs (NABIDH, Malaffi, Riayati).
Use certified EMR vendors
Use certified EMR vendors.
Start onboarding early, allow 4–8 weeks per platform
Start onboarding early, allow 4–8 weeks per platform.
Secure onboarding proof for interim compliance
Secure onboarding proof for interim compliance.
Complete SIT and get authority approval
Complete SIT and get authority approval.
Technical Standards
Support HL7 and FHIR APIs
Support HL7 and FHIR APIs.
Malaffi requires SNOMED CT and LOINC coding
Malaffi requires SNOMED CT and LOINC coding.
Use Emirates ID as primary identifier
Use Emirates ID as primary identifier.
Set up SD-WAN (Malaffi) and secure PHI with encryption and IP whitelisting
Set up SD-WAN (Malaffi) and secure PHI with encryption and IP whitelisting.
Insurance & Patient Identity
Map Emirates ID to all patient and policy records
Map Emirates ID to all patient and policy records.
Enable UAE Pass for patient apps
Enable UAE Pass for patient apps.
Align with emirate-specific verification platform
Align with emirate-specific verification platform.
Integrate Riayati eClaims for Northern Emirates
Integrate Riayati eClaims for Northern Emirates.
Governance & Compliance
Track DHA, DoH, MOHAP updates
Track DHA, DoH, MOHAP updates.
Align license renewals with HIE milestones
Align license renewals with HIE milestones.
Meet UAE Central Bank 2026 cybersecurity standards
Meet UAE Central Bank 2026 cybersecurity standards.
Train staff on digital ID workflows
Train staff on digital ID workflows.
Conclusion
As understood, UAE's digital health ecosystem isn't complex by accident, it's designed that way to balance federal oversight with emirate-level control. But in 2026, complexity is no longer an excuse for delay.
If you're building, scaling, or operating in this space, the rules are clear: pick your emirate early, align with the right HIE, and build your systems around Emirates ID, HL7 FHIR, and compliance-first workflows.
It's about building products and workflows that are ready for the future of healthcare across the GCC.
Frequently Asked Questions
Not Sure Where Your Platform Stands?
Get a free compliance audit of your digital health product from Sanowork experts. No commitment required · 45-minute session with a GCC health IT specialist