NABIDH — the Network and Analysis Backbone for Integrated Dubai Health — is the Dubai Health Authority's (DHA) official Health Information Exchange (HIE) platform. Launched as part of Dubai's Digital Health Strategy, NABIDH creates a single, unified longitudinal clinical record for every patient in Dubai by connecting all licensed healthcare facilities to a central secure data backbone.
When a patient visits any DHA-licensed facility — a GP clinic in Jumeirah, a specialist hospital in Dubai Healthcare City, or a pharmacy in Deira — their clinical data flows in real time into NABIDH. The next provider that patient visits can immediately access their full medication history, allergies, lab results, and prior diagnoses, reducing duplicate testing, medication errors, and fragmented care across the emirate.
NABIDH is not optional. It is a regulatory requirement enforced by the DHA as a condition of maintaining any healthcare facility license in Dubai. The DHA conducts technical audits to verify active, compliant NABIDH connectivity for every licensed facility.
NABIDH compliance is mandatory for every DHA-licensed healthcare entity in Dubai, regardless of size, specialty, or patient volume.
All inpatient and outpatient encounters, surgical procedures, discharge summaries, and medication administrations must be transmitted to NABIDH in real time for every patient episode.
Every patient consultation — whether with a GP, dermatologist, cardiologist, dentist, or any other specialty — generates clinical events that must be shared via NABIDH. This obligation applies to solo-practitioner clinics and multi-specialty polyclinics alike.
All dispensed medications must be reported to NABIDH, enabling cross-pharmacy drug interaction checking and a complete medication record for each patient across Dubai's pharmacy network.
All finalised laboratory results — CBC, lipid panels, HbA1c, microbiology cultures, and all other investigations — must be transmitted to NABIDH and linked to the patient's Emirates ID as the primary identifier.
Structured radiology report conclusions must be shared via NABIDH. Imaging files (DICOM) follow the DHA imaging integration pathway, separate from the core NABIDH clinical data exchange.
NABIDH applies specifically to DHA-regulated facilities in Dubai. Abu Dhabi facilities regulated by DOH connect to the Malaffi HIE platform. Facilities in other emirates fall under MOH regulation with its own data sharing requirements. Multi-emirate facility groups must comply with each regulator separately.
The DHA specifies a defined set of clinical data elements that must be transmitted for each patient encounter. Facilities are required to share all of the following categories in a structured, coded format:
NABIDH uses the internationally standardised HL7 FHIR R4 (Fast Healthcare Interoperability Resources, Release 4) framework. This is the same standard adopted by the US ONC 21st Century Cures Act and NHS England's interoperability programme.
Each clinical data category maps to a specific FHIR resource type: Patient for demographics, Condition for diagnoses, MedicationRequest for prescriptions, Observation for lab results and vitals, Procedure for clinical procedures, AllergyIntolerance for allergies, and DiagnosticReport for packaged lab panels and radiology reports.
NABIDH uses a push notification model. When a qualifying clinical event is finalised in your HMS — a clinician signs off a diagnosis, a prescription is issued, a lab result is verified — the system must push the corresponding FHIR bundle to the DHA NABIDH endpoint within minutes. End-of-day batch uploads do not meet the DHA real-time requirement.
NABIDH connectivity requires DHA-issued API credentials (client ID and client secret), OAuth 2.0 bearer token authentication for each API call, and TLS 1.2 or higher encrypted transport for all transmissions. All data must be facility-authenticated — no anonymous or shared-credential connections are permitted.
DHA provides a dedicated NABIDH sandbox environment for pre-go-live testing. Facilities and their HMS vendors must demonstrate that all required FHIR resource types are correctly populated, Emirates ID linkage is accurate, and real-time transmission is functioning before DHA grants access to the production NABIDH environment.
Follow these five steps to achieve and maintain full NABIDH compliance for your Dubai healthcare facility.
Confirm with your HMS vendor that they have completed DHA's NABIDH conformance testing process and hold a current integration approval letter from DHA. Request this documentation in writing. Do not accept verbal assurances — vendor staff may not be aware of the current status of their own DHA certification, particularly if the system has been updated since original approval.
Submit your facility's NABIDH onboarding application through the DHA digital health portal. You will need your DHA facility license number, the name and contact details of your designated IT lead, and the name and DHA registration details of your HMS vendor. DHA assigns a unique facility identifier that is embedded in all NABIDH transmissions from your facility.
Work with your HMS vendor to complete all required data mapping: ICD-10-CM codes for your most commonly used diagnoses, your drug formulary mapped to the DHA-approved drug database, laboratory test codes, and clinician DHA license numbers configured for every provider account in the system. This phase typically takes 2–4 weeks for a typical clinic.
Run your configured HMS against the DHA NABIDH sandbox environment. Test every clinical event type systematically: patient registration with Emirates ID, diagnosis coding, prescription generation, lab result upload, allergy recording, and vital sign entry. Validate that DHA's sandbox confirms receipt of complete, correctly structured FHIR bundles for every event type before proceeding to go-live.
After DHA grants production environment access, activate NABIDH transmission in your live system. Monitor transmission logs daily — every failed or rejected message must be reviewed and resolved within 24 hours. Conduct a quarterly audit of NABIDH transmission success rates. Re-validate whenever your HMS is upgraded or when DHA publishes updates to the NABIDH API specification.
The following obstacles arise in the majority of NABIDH implementations. Awareness of them in advance significantly reduces go-live delays and post-launch compliance gaps.
NABIDH uses Emirates ID as the primary patient identifier. If reception staff are not capturing Emirates ID at every registration — common in busy walk-in clinics — NABIDH records cannot be correctly linked. Update your intake process and make Emirates ID a mandatory field in patient registration before going live.
Clinicians accustomed to typing free-text diagnoses will generate NABIDH transmission failures because the platform requires ICD-10-CM coded entries. Clinical staff training on using the coded diagnosis picker in the HMS is essential before go-live.
If your formulary includes drugs not yet mapped to the DHA-approved drug database, prescriptions for those drugs will fail NABIDH validation. A pre-go-live drug mapping review — typically 300–600 items for a general clinic — should be completed and validated before activating NABIDH transmission.
Every prescription and clinical note transmitted to NABIDH must include the treating or prescribing clinician's DHA license number. If your HMS user accounts were set up without storing DHA license numbers — or if visiting or locum clinicians are not correctly configured — transmissions will be rejected at the DHA endpoint.
Older HMS systems were built around end-of-day batch processing. NABIDH requires near-real-time transmission when a clinical event is finalised. A batch architecture fundamentally violates the DHA real-time requirement and cannot be remedied by configuration alone — it requires a system that was built with event-driven real-time transmission from the ground up.
Facilities that go live and do not actively monitor NABIDH transmission logs accumulate rejected records silently. A compliant HMS must provide a real-time dashboard showing per-encounter transmission status, rejection reasons, and outstanding failed records that require resolution. Without this visibility, compliance gaps grow undetected until a DHA audit.
MedicoPlus is built with NABIDH compliance as a core architectural requirement — not a bolt-on module. Every clinical workflow in MedicoPlus is designed around NABIDH's technical and data requirements from the ground up.
NABIDH (Network and Analysis Backbone for Integrated Dubai Health) is the Dubai Health Authority's unified Health Information Exchange platform. It creates a single longitudinal patient record for every patient in Dubai by aggregating clinical data from all DHA-licensed facilities in real time. When a patient visits any DHA-licensed provider, that provider can access the patient's complete prior clinical history from all other Dubai providers — diagnoses, medications, allergies, lab results, and procedures — through NABIDH.
Yes, without exception. NABIDH integration is a mandatory condition of holding any DHA healthcare facility license in Dubai. There are no size exemptions — a one-doctor GP clinic has the same NABIDH obligation as a 600-bed hospital. DHA enforces this through technical compliance audits and during license renewal reviews. Facilities found non-compliant face penalties that can include formal warnings, financial fines, operational suspension, or license non-renewal.
NABIDH requires patient demographics (Emirates ID mandatory), ICD-10-CM coded diagnoses, medications and prescriptions with generic drug name and dose, laboratory test results, clinical procedures, documented allergies and adverse reactions, vital signs, referrals, and discharge summaries for inpatient episodes. All data must be structured and coded — unstructured free text is rejected by the NABIDH platform.
Clinic software connects via the DHA-certified HL7 FHIR R4 REST API. The HMS packages each clinical data element into a corresponding FHIR resource (Patient, Condition, MedicationRequest, Observation, etc.) and transmits the bundle to the DHA NABIDH API endpoint using OAuth 2.0 bearer token authentication over TLS-encrypted HTTPS. The transmission must occur in real time when the clinical event is finalised — not in batches. A NABIDH-ready HMS handles all of this automatically with no manual steps required from clinical or administrative staff.
Book a free demo — no commitment, no sales pressure. We will walk you through live NABIDH compliance in the system.
Book a Free Demo +971 50 386 9500 WhatsApp Us
