NABIDH + Pabau
DHA NABIDH connectivity for Dubai clinics — HL7 compliance without the integration project.
NABIDH is the Dubai Health Authority's health information exchange, and connecting to it is a licensing requirement for Dubai healthcare facilities. Pabau speaks NABIDH natively: patient demographics, visits and clinical data are encoded as HL7 v2.5.1 messages and delivered to the DHA platform automatically as you work.
- HL7 v2.5.1 messages generated automatically
- Patient demographics synced out of the box
- Visits, allergies, prescriptions, labs & documents opt-in
Up and running in three steps
Enter your DHA identifiers
Add your NABIDH EMR code, Sheryan facility licence ID, endpoint and application key in Pabau's Data Sync setup. Credentials are stored encrypted.
Map your practitioners and services
Assign each clinician's Sheryan ID and tag services with their DHA specialty code — Pabau validates Emirates IDs, UAE phone formats and licence IDs as you go.
Work normally — Pabau reports
Registrations, updates and check-ins generate the right HL7 messages automatically, with a full delivery log for every message sent.
Everything the integration handles
Automatic patient sync
New registrations and demographic updates are sent to NABIDH as ADT messages the moment they happen — on by default.
Full clinical message set
Opt in to visits, problems, allergies, prescriptions, lab results, document and letter submissions, and patient merges — each mapped to its DHA-specified HL7 message.
UAE validation built in
Emirates ID format, UAE phone numbers, 7-digit facility and 8-digit clinician licence IDs are validated before anything is sent.
Sheryan practitioner mapping
Each practitioner's Sheryan ID rides on their visit messages, with a clinic-wide fallback for unmapped staff.
DHA specialty coding
Tag each service with its DHA specialty so visit messages carry the correct hospital-service code.
Delivery log & retries
Every message is logged with its delivery status; failures retry automatically and are visible per message.
Compliance as a by-product of working
NABIDH reporting shouldn't be a second job. With the connector on, front-desk registration and clinical charting produce the DHA's required messages automatically — in the exact HL7 v2.5.1 format the spec demands.
- ADT demographics messages out of the box
- Visit messages fire at check-in
- Message-by-message spec mapping, viewable in setup
- Test and production environments kept safely apart
Built for how Dubai clinics actually operate
Emirates ID edge cases, resident-vs-tourist flags, VIP confidentiality markers, Arabic-speaking patient bases — the connector handles the local reality, not just the spec PDF.
- Emirates ID validation incl. newborn/emergency cases
- Resident/tourist default configurable
- VIP and restricted-access flags from client labels
- Encrypted credentials, https-only endpoints
Frequently asked questions
Is NABIDH connectivity mandatory?
The Dubai Health Authority requires licensed Dubai healthcare facilities to connect to NABIDH and report patient and clinical data. Pabau's connector is built against the DHA's NABIDH HL7 v2.5.1 specification.
What data is sent to NABIDH?
Patient demographics (registrations and updates) are sent out of the box. Visits, problems, allergies, prescriptions, lab results, documents/letters and patient merges are each opt-in message types you control.
What do I need from the DHA to connect?
Your NABIDH EMR code, your 7-digit Sheryan facility licence ID, the NABIDH endpoint URL and an application key — plus each practitioner's Sheryan clinician ID.
How do I know messages were delivered?
Pabau's sync log records every message with its delivery status, payload and any retries — so you can evidence your reporting when it matters.
See NABIDH + Pabau in action
Join thousands of clinics running bookings, records, billing and marketing on Pabau — with NABIDH connected.
