Dubai's health information exchange
Connecting a Dubai facility to NABIDH
Every healthcare facility in Dubai connects to NABIDH, the National Backbone for Integrated Dubai Health, and answers to the Dubai Health Authority for the security of that connection. You and your EMR vendor build and run the integration. We map the security and privacy requirements around it to one control set and keep the evidence ready for your next review.
Get ready for your NABIDH review
The security and privacy side of your NABIDH connection
DHA requires Dubai healthcare facilities to connect to NABIDH.
The Dubai Health Authority requires every healthcare facility in Dubai to connect to NABIDH, the National Backbone for Integrated Dubai Health. NABIDH is a unified health information exchange that lets patient data move between Dubai facilities, which puts a live link between your systems and a shared record. You and your EMR vendor build that link. How it is secured, who can query it and whether each query leaves a trail is the part we assess and keep evidence for.
One control set for the security and privacy side of your NABIDH connection.
What the NABIDH connection involves
NABIDH requires real-time bidirectional data exchange between your EMR/EHR and the central platform. Patient demographics, clinical encounters, lab results, medications, imaging reports, all must flow automatically. You and your EMR vendor build and run that connection. We assess its security: how it authenticates, how its credentials are managed, what is encrypted in transit, and who inside your organization can query the exchange.
Your EMR vendor builds the link; we assess how it is secured.
NABIDH's data standards and formats
NABIDH mandates specific data formats, coding systems (ICD-10, SNOMED CT, LOINC), and structural requirements. Data that doesn't meet these standards gets rejected. Mapping and validating the data is work for your EMR vendor and integration team. We record which standards apply to your facility and keep the evidence of how they were checked.
Your EMR vendor maps the codes; we keep the evidence of how they were checked.
Patient consent before sharing
NABIDH requires explicit patient consent before sharing health information across facilities. You must capture consent, manage opt-outs, respect patient preferences, and enforce restrictions in real-time. Consent capture runs in your registration and EMR workflow. We assess whether the consent and opt-out procedures exist and are followed, and keep the records that show it.
Consent runs in your workflow; we check the procedure and keep the records.
Secure Patient Data in Transit and at Rest
NABIDH expects strong security: encryption in transit and at rest, access controls, audit trails, and breach detection. DHA looks at your security posture during its reviews. We assess those controls against the requirement, track the gaps to closure and keep the documentation DHA reviewers expect for your NABIDH connection. The controls themselves run in your systems.
Encryption, access control and audit trails, assessed and documented.
Prepare for NABIDH certification testing
DHA requires formal certification testing before you're authorized to go live with NABIDH. They test data accuracy, format compliance, security controls, and error handling. Your EMR vendor runs the technical tests. We prepare the security side: the controls, the documentation and the evidence the testers ask for.
The security documentation testers ask for, ready before the test.
Keep the evidence current after go-live
The connection keeps running after go-live, and DHA's expectations on uptime, data quality and security continue with it. Our read-only agent re-checks the security controls around the connection and we keep the evidence current between reviews. It changes nothing in your systems.
Read-only checks, with the evidence kept current between reviews.
Why Healthcare Facilities Choose This Path
What facilities get when the NABIDH security requirements are mapped to one control set.
Facilities using our platform:
Security Requirements Mapped
The NABIDH security and privacy requirements that apply to your facility, each mapped to a control with a named owner.
Ready for Testing
The security documentation DHA testers ask for, assembled before the test instead of during it.
Evidence Kept Current
Each control has an owner and current evidence, so a DHA reviewer asking for proof gets a document the same day.
Know the Data Standards
A record of which coding and format standards apply to your facility, for your EMR vendor to build against.
Protect Patient Privacy
Consent and opt-out procedures assessed and documented, alongside the encryption and access controls around the link.
Focus on Patient Care
Your clinical staff are not pulled into assembling security evidence before each review.
Built for Dubai healthcare cybersecurity and NABIDH connection readiness.
Meet Every NABIDH Integration Requirement
NABIDH's specifications are wide. We cover the security and privacy side.
DHA's NABIDH specifications cover technical integration, data standards, security controls, consent management, and operational requirements. Each facility type faces specific obligations. The integration itself is built and run by you and your EMR vendor. We map the security, access and consent requirements to one control set, assess whether the controls exist, and keep the evidence DHA reviewers expect.
We keep the security and privacy evidence for your NABIDH connection ready for review.
NABIDH Integration Requirements
What NABIDH asks of a connected facility