Emirate-Wide Health Information Exchange
Malaffi aggregates records from SEHA, Cleveland Clinic Abu Dhabi, Mediclinic and other DOH-licensed providers into one longitudinal patient record.
Trusted by startups and global leaders
The Malaffi Landscape
Malaffi — "my file" in Arabic — is Abu Dhabi's mandated HIE: one shared patient record across the Emirate.
DOH-Mandated for All Licensed Facilities
The Abu Dhabi DOH requires every licensed facility to connect and share clinical data — enforced through licensing, not optional.
FHIR-Based, Single Integration Point
One standardized HL7 FHIR integration with Malaffi gives aggregated data across the whole network — not a separate interface per hospital.
What Malaffi Integration Involves — From the DOH Mandate to Real-Time Submission
We build Malaffi integration for Abu Dhabi — FHIR interfaces, Emirates ID matching, terminology mapping and the submission patterns the DOH requires.
The DOH requires every licensed facility — hospitals, clinics, labs, pharmacies — to connect to Malaffi.
Systems must implement FHIR interfaces conformant to Malaffi's specs across encounters, diagnoses, medications and lab results.
The Emirates ID is Malaffi's primary patient identifier — captured at registration and sent in every submission.
Submitted data must use approved vocabularies — ICD-10, LOINC and the Abu Dhabi DOH formulary.
Malaffi supports real-time submission for urgent events and batch for less urgent data.
The Gap Between Connecting to Malaffi and Passing DOH Validation
Malaffi is well-specified, but conformant integration is still hard — and where most deployments struggle.
Conformance to Malaffi FHIR Profiles
Base FHIR isn't enough — submissions must match Malaffi's profiles per domain, and sandbox validation often takes several cycles before production.
Emirates ID Identity Matching
Records attach to a Malaffi profile via the Emirates ID — capture it correctly at registration and handle visitor IDs to avoid rejected or misattributed data.
Terminology Mapping to DOH Standards
Local codes must map to ICD-10, LOINC and the Abu Dhabi DOH formulary before submission — mapping that preserves clinical meaning across both code systems.
Submission Completeness at Production Scale
The DOH monitors completeness via submission dashboards — choose real-time versus batch per category and sustain quality under live load.
The Malaffi Integration Process
A structured path from DOH registration to live submission, each stage delivering what passes Malaffi validation.
-
DOH Registration & Agreement
DOH Registration & Agreement
Register with the Abu Dhabi DOH and sign the data-sharing agreements governing submission, access, and consent.
-
Technical Onboarding With Malaffi
Technical Onboarding With Malaffi
Malaffi provides developer portal access, the FHIR implementation guide, and sandbox credentials.
-
FHIR Interface Development
FHIR Interface Development
Build FHIR submissions for each clinical domain — demographics, encounters, diagnoses, medications — per Malaffi's profiles.
-
Testing & Validation
Testing & Validation
Test against the Malaffi sandbox across all domains; resolve the conformance issues Malaffi flags before production.
-
Go-Live & Compliance Monitoring
Go-Live & Compliance Monitoring
Once validated, the integration submits live data to production while the DOH monitors compliance through dashboards.
Who This Is For
We build Malaffi integration for the organisations Abu Dhabi's healthcare data ecosystem runs on.
Hospitals & Health Systems
FHIR submission infrastructure meeting DOH specs under production load for SEHA and Mediclinic.
Health IT Vendors
We make your EHR, LIS, RIS, or pharmacy product Malaffi-conformant for DOH-licensed Abu Dhabi facilities.
Digital Health Companies
One Malaffi integration gives a consent-based longitudinal record across the Emirate.
Diagnostic & Pharmacy Providers
Domain-specific FHIR submissions and terminology mapping so DOH-licensed labs and pharmacies stay compliant.
Malaffi Standards & Requirements — Implemented to the DOH Specification
We implement Malaffi's FHIR profiles, identifiers, and vocabularies with the security a conformant DOH deployment needs.
FHIR
Malaffi FHIR Profiles
Data exchange conformant to Malaffi's FHIR profiles and data model.
Identity
Emirates ID Matching
Patient records attach to Malaffi profiles via Emirates ID.
Terminology
Code Systems & Mapping
Local codes mapped to standard vocabularies Malaffi requires.
Data Domains
Clinical Data Coverage
Full range of clinical data Malaffi aggregates per encounter.
Submission
Real-Time & Batch Patterns
Submission pattern per data category, chosen by clinical urgency.
Mandate
DOH Regulatory Drivers
DOH mandate that makes Malaffi connectivity non-optional.
The Malaffi Connectivity Stack We Build With
FHIR servers, Emirates ID matching, and UAE-resident cloud — matched to Malaffi and DOH specs.
H
HL7 FHIR
H
HAPI FHIR
M
Malaffi FHIR Profiles
H
HL7 v2
B
Bulk Data Access
I
ICD-10
L
LOINC
S
SNOMED-CT
D
DOH Drug Formulary
E
Emirates ID Matching
M
Master Patient Index
O
OAuth 2.0
C
Consent Management
R
Role-Based Access
A
AWS UAE Region
A
Azure UAE
G
G42 Cloud
I
In-Country Hosting
M
Monitoring & Alerting
In Abu Dhabi, Clinical Software Connects to Malaffi. We Make Sure Yours Does.
FHIR submission, Emirates ID matching, DOH terminology mapping and the validation cycles Malaffi requires — built in and carried through sandbox, DOH validation and go-live.
Book a Malaffi Consult
Award-Winning AI Development & Consulting
100 Fastest Growth Companies
Global Spring Winner
Top App Development Company
AWS Partner Network
Google Cloud Partner
Highly Rated on Trustpilot
Verified Agency
Top App Development Company
ASSOCHAM Member
Frequently Asked Questions
[ 1 ]
How is Malaffi different from NABIDH?
Malaffi is Abu Dhabi's DOH-mandated HIE; NABIDH is Dubai's, mandated by the DHA. Separate specs and onboarding mean facilities in both Emirates must comply with each.
[ 2 ]
Can patients access their own Malaffi records?
Yes. UAE residents can access their Malaffi health summary through DOH apps and government digital services, part of Abu Dhabi's push to give patients control of their health data.
[ 3 ]
What happens to a facility's DOH license if it does not connect to Malaffi?
The DOH treats Malaffi connectivity as mandatory in Abu Dhabi. Non-compliant facilities face warnings, notices and licensing impacts — treat Malaffi integration as a baseline requirement.
Global presence
