Patient mobility is baked into how the UAE’s healthcare system actually functions. Someone insured and registered in Abu Dhabi might need a specialist consultation in Sharjah. A resident of Ajman might be referred to a tertiary facility in Abu Dhabi for a procedure their local clinic can’t perform. In a country where three separate regulatory authorities — Dubai’s DHA, Abu Dhabi’s DOH, and the federal Ministry of Health and Prevention (MOHAP) covering the Northern Emirates — each run their own health information exchange, the real question for hospital administrators and clinic owners isn’t whether these referrals happen. It’s whether the patient’s data follows them as smoothly as the patient does.
This blog breaks down how that actually works in practice — what Malaffi and Riayati are individually, how they’re technically connected, and what a referral between Abu Dhabi and the Northern Emirates looks like from registration through to claims.
The three-system landscape, briefly
The UAE’s health data architecture runs on three parallel but increasingly interconnected exchanges. NABIDH is Dubai’s exchange, run by the Dubai Health Authority. Malaffi is Abu Dhabi’s exchange, operated by Abu Dhabi Health Data Services (ADHDS), an M42 company, under the Department of Health, Abu Dhabi. Riayati is the federal exchange under MOHAP, serving facilities across the Northern Emirates — Sharjah, Ajman, Umm Al Quwain, Ras Al Khaimah, and Fujairah.
Each of these exists at serious scale. Malaffi connects more than 3,072 healthcare facilities across Abu Dhabi, supports 53,476 authorised users, and as of August 2025 had aggregated 3.5 billion clinical records representing 12.7 million unique patient profiles. Riayati, on the federal side, connects more than 3,000 healthcare facilities, including public and private hospitals, clinics, day care centres, and diagnostic centres across the Northern Emirates. A significant share of that Northern Emirates data flows in through Emirates Health Services’ own EMR, known as Wareed, which alone provides more than 50% of health data in the Northern Emirates through 17 hospitals and over 80 health centres.
How Malaffi and Riayati are actually connected
Here’s the part that matters most for a cross-emirate referral: Malaffi and Riayati aren’t two isolated silos that happen to sit next to each other. They’ve been deliberately integrated, in phases, specifically to solve the problem of a patient’s record not following them across emirate lines.
The Department of Health — Abu Dhabi and MOHAP completed a dedicated phase of integration between Malaffi and Riayati, explicitly described as facilitating “access to patient records across Abu Dhabi and other emirates”. The practical result: Malaffi clinical users can now access patient records from healthcare facilities in the Northern Emirates through Riayati, the UAE’s federal HIE. The next phase of this rollout was designed to extend the same access in the other direction — giving Malaffi users visibility into Dubai-originated records as well, moving toward what the DOH has described as complete access to patient records “regardless of where they received care within the UAE”.
This matters because it tells you where the real technical work in a cross-emirate referral actually happens: not in a one-off data transfer triggered by the referral itself, but in standing, federated connections between the exchanges that make the patient’s record visible to an authorised clinician the moment they search for it — as long as consent and access controls are properly in place.
What a Dubai-to-Northern-Emirates or Abu Dhabi-to-Northern-Emirates referral looks like in practice
Walk through a realistic scenario: a patient registered and insured under a Northern Emirates provider, say, in Sharjah, is referred to a specialist or tertiary facility in Abu Dhabi for a procedure unavailable locally.
- Patient identification. The Emirates ID functions as the primary patient identifier across all three exchanges, which is what allows a provider in a different emirate to confidently match the incoming patient to their existing record rather than creating a duplicate one.
- Record retrieval. Once the patient is matched, the receiving facility’s clinical team — through a properly connected clinic management system or hospital management system — can query the patient’s history, including demographics, prior encounters, diagnoses, medications, allergies, and lab results, through the Malaffi-Riayati integration layer, without the patient needing to physically carry prior records or repeat their history from memory.
- Imaging and diagnostics. This extends to radiology as well. Malaffi’s centralised Philips Image Exchange Solution gives connected facilities secure access to more than four million X-rays, CT scans, MRIs, and ultrasound images across 67 healthcare facilities in Abu Dhabi — specifically designed to reduce duplicate imaging and the burden on patients of carrying physical copies of diagnostic studies between providers. For a referred patient, this is often the single biggest practical benefit — a scan done in Ajman doesn’t need to be repeated in Abu Dhabi simply because the receiving hospital can’t see it.
- Treatment and documentation. The Abu Dhabi facility treats the patient and documents the encounter in its own system, which — because the facility is DOH-licensed — is contractually and technically required to push that data back into Malaffi. That update then becomes visible to the originating Northern Emirates provider through the same federated access, closing the loop on the patient’s record.
- Claims and reimbursement. On the financial side, Riayati runs its own e-Claims Post Office — a dedicated data exchange system that facilitates the secure exchange of health insurance claims between healthcare providers and payers operating in the Northern Emirates. For a referred patient whose insurance is anchored in the Northern Emirates but who was treated in Abu Dhabi, this is the layer responsible for making sure the claim correctly reaches the right payer and the right pre-authorisation and billing workflow, rather than getting stuck between two separate claims systems.
Why this is harder than it sounds, operationally
On paper, this sounds like a clean, automatic handoff. In practice, three things make cross-emirate referrals genuinely difficult for providers to get right without the correct underlying technology.
Technical compliance differs by authority, even if the underlying standards are shared. Clinics and hospitals connecting to Riayati must be HL7-compliant and capable of supporting national patient identifiers, while Malaffi requires FHIR interfaces conformant to its own published technical specifications across encounters, diagnoses, medications, and lab results. A provider’s clinic management software has to speak both dialects correctly, not just generically “support FHIR.”
Mandatory connection doesn’t mean automatic connection. Connecting to Malaffi is mandatory for every DOH-licensed facility in Abu Dhabi, with narrow exemptions for military, police, aviation medical, and university facilities. Similarly, MOHAP-licensed clinics in the Northern Emirates must integrate with Riayati. But “mandatory” is a licensing requirement, not a guarantee of smooth data flow — a facility’s hospital management system still has to be properly built and configured to meet each exchange’s specific submission requirements for that data to actually appear when a referring or receiving clinician searches for it.
Multi-location groups feel this most acutely. A healthcare group running facilities in Abu Dhabi, the Northern Emirates, and potentially Dubai is effectively operating under three licensing authorities and three technical specifications simultaneously. Each site needs its own clinic management software correctly connected to the right exchange, while leadership still needs one coherent view of the patient and the group’s own operational data across all of them.
What the right software actually needs to do
For a provider operating across Abu Dhabi and the Northern Emirates, the practical requirement isn’t just “be connected to Malaffi” or “be connected to Riayati” as a compliance checkbox. It’s a platform — whether deployed as a clinic management system for a single-specialty outpatient practice or a full hospital management system for a multi-department facility — that is built to:
- Match patients reliably across exchanges using the Emirates ID as the common identifier
- Submit and retrieve structured FHIR and HL7-compliant data correctly to both Malaffi and Riayati’s distinct technical specifications
- Surface a referred patient’s prior encounters, medications, labs, and imaging to the receiving clinician without manual lookup across separate portals
- Route insurance eligibility, pre-authorisation, and claims correctly through the right payer workflow, whether that’s Riayati’s e-Claims Post Office for the Northern Emirates or Abu Dhabi’s own payer ecosystem
This is where a lot of generic hospital management system deployments fall short — they treat NABIDH, Malaffi, and Riayati compliance as three separate bolt-on integrations rather than a single, coherent exchange layer the platform was designed around from the outset.
Where Lifetrenz fits
This is the layer Lifetrenz’s UAE platform is built to operate at. Rather than treating Malaffi and Riayati connectivity as two separate integration projects, the platform is designed to recognise where a patient is actually registered, route clinical data and claims to the correct authority, and keep the patient’s record consistent regardless of which emirate the care was delivered in, whether a facility is running it as a standalone clinic management system or as the backbone hospital management system for a multi-site group spanning Abu Dhabi and the Northern Emirates.
For a patient, a cross-emirate referral should feel seamless — the same care, with no extra paperwork, no repeated history, no duplicate scans. Getting there depends entirely on whether the technology layer behind the scenes was actually built for that reality, or just connected to it after the fact.
Final words
Referrals between Abu Dhabi and the Northern Emirates work because Malaffi and Riayati have been deliberately integrated at the platform level, not because each individual referral triggers a one-off data exchange. With Malaffi now aggregating 3.5 billion clinical records across 12.7 million unique patient profiles and Riayati connecting over 3,000 facilities across the Northern Emirates, the infrastructure for this kind of patient mobility already exists at national scale. What determines whether an individual provider benefits from it is whether their own systems, from patient identification through to claims, were genuinely built to work across both exchanges, not just connected to each in isolation.
