NABIDH integration: a practical guide for Dubai clinics

Short answer: NABIDH integration means your clinic's EMR sends patient and encounter data to the Dubai Health Authority's health information exchange in the HL7 format DHA specifies, and can show clinicians the shared record. The clinic owns the licence, the onboarding forms and data quality. The vendor owns the messages. Helix is connected to NABIDH out of the box.

Most NABIDH problems we see are not technical. They are data problems: missing Emirates IDs, free-text diagnoses, doctors without licence numbers on their user profile. This guide explains the process and, more usefully, where it tends to go wrong.

This article is general guidance, not legal advice. Regulators update their standards, circulars and deadlines often, so always confirm the current requirement with the relevant authority or a qualified advisor before you act on it.

What NABIDH is

NABIDH stands for National Backbone for Integrated Dubai Health. It is the DHA's health information exchange (HIE), connecting public and private healthcare facilities in Dubai so that trusted health information can be shared securely. When a patient who was seen at a hospital last month walks into your clinic, a connected clinician can see relevant history instead of relying on memory or paper.

NABIDH is also linked to Malaffi in Abu Dhabi and Riayati, the national record run by MOHAP, so data can follow a patient between emirates. If you run branches outside Dubai, read our emirate-by-emirate compliance map.

Who needs to connect

DHA ties NABIDH participation to facility licensing. Vendor and consultant guides consistently report that new applicants and existing facilities at renewal are expected to have a working connection, and that onboarding has been rolled out by facility category. Because the policy is updated over time, check the current DHA NABIDH policies and standards for your facility type rather than relying on an older circular or a vendor's summary.

The standards behind it

• DHA interoperability and data exchange standards. The policy document that defines what must be shared and how.
• The NABIDH HL7 v2.5.1 inbound specification. It describes the onboarding process, message structures, segments, data types and code tables. Facilities must use the latest version.
• Patient identification. Emirates ID is the main identifier for residents, with passport details used for visitors. Clean IDs are the difference between a merged record and a duplicate.
• Coding. Diagnoses in ICD-10, plus the other code sets DHA specifies for procedures, labs and medications.
• Consent. DHA's policies define how patient consent and opt-out work. Your front desk needs to know the rules.

Who does what: clinic vs vendor

The onboarding path, step by step

1. Confirm your EMR is already live on NABIDH. Ask which message types it sends (patient registration and updates, encounters, diagnoses, results, and so on) and how many facilities use it today. A vendor that is still building the interface will delay you.
2. Register and submit your facility details through the NABIDH onboarding process with your DHA licence information and the EMR you use.
3. Configure the facility in your EMR: facility identifiers, department and specialty mappings, and clinician licence numbers.
4. Clean the data you will send. Fill missing Emirates IDs for active patients, replace free-text diagnoses with ICD-10 codes, and fix duplicate patient files.
5. Run integration testing against DHA's test environment. Expect a few rounds of fixes, mostly on mappings and mandatory fields.
6. Go live and monitor. Someone on your team should own the failed-message queue and review it weekly.

Five things that break NABIDH after go-live

• Walk-ins registered without ID. A busy front desk creates a file with just a name and phone number. Every encounter for that patient then fails or lands on a partial record.
• Free-text diagnoses. If the chart allows a diagnosis to be typed instead of coded, the message is weaker, or rejected.
• New doctors without licence numbers on their user profile. Their encounters go out incomplete.
• Specialty charts that export as 'other'. If a specialty form is not mapped, every visit looks generic to the exchange. We found and fixed exactly this for urology in our own product, which is why we check mappings per specialty.
• Duplicate files. Two files for one patient means two partial histories. Merge them, and make the merge keep the audit trail.

A weekly NABIDH routine for practice managers

A connection that worked on go-live day can degrade quietly. A short weekly routine keeps it healthy:

1. Review failed or rejected messages and fix the underlying record, not just the message.
2. Check new patient files from the week for missing Emirates IDs and complete them.
3. Confirm that every new clinician has a DHA licence number on their profile before their first clinic.
4. Look for visits closed without a coded diagnosis and ask the doctor to complete them.
5. Search for likely duplicates (same name and date of birth) and merge them.

Ten to fifteen minutes a week is usually enough for a single clinic. For a group, give each branch its own owner and share one summary.

How NABIDH connects to the rest of your workflow

NABIDH is clinical. Insurance claims in Dubai go through eClaimLink and DHPO, which is a separate platform with its own rules. The same data quality work helps both: coded diagnoses and clinician licences on every activity reduce claim rejections too. Our eClaimLink and DHPO guide explains the claims side.

The easiest way to keep both clean is to capture everything once, in the chart. When the doctor documents in a specialty EMR with coded fields, the same diagnosis flows to NABIDH, to the invoice and to the claim.

How Helix handles NABIDH

Helix is connected to NABIDH over HL7. Registration captures Emirates ID from the card reader, diagnoses are coded in the chart's ICD-10 picker, and clinician licence numbers live on staff profiles, so messages go out complete. Each of our specialty charts is mapped to the right NABIDH specialty value. The Verto AI scribe can also suggest ICD-10 codes from the consultation, which the doctor confirms. See the full list of live connections on our integrations page.