Qualysec
Blog

NABIDH Compliance in Dubai: Healthcare Data Security and Penetration Testing

Investigate compliance with NABIDH Dubai standards, data security in healthcare organizations& other means to protect patient information.

Published on November 16, 2026
Read Time: 21 min
CONNECT WITH US

Summarize this blog post with

Consider a multi-speciality clinic in Dubai completing its EMR migration by March and executing its go-live rollout. Then connectivity tests start failing. Duplicate patient identifiers and failing ADT returns by the dozen from a decade of walk-in registrations.

Moreover, the integration engine records all patient information in a debug file that no one secures! The go-live slips off a wave. The date of the licence remains unchanged.

A quick rundown. Facilities in Dubai must obtain a licence from NABIDH and the Dubai Health Authority’s health information exchange. Beyond connectivity, compliance is about policies that set security requirements, consent rules, audit responsibilities, and a 48-hour incident clock and expects penetration testing prior to onboarding.

The second one is unexpected. Since “the EMR vendor handles it” is the only way to comply with NABIDH Dubai regulations, the security requirements that go along with the facilities’ interfaces are allotted virtually nothing. The vendor is not responsible for managing it. The policies require proof from your facility, your Information Security Officer and your suppliers.

This guide explains what NABIDH is and who needs to connect, the journey from EMR to go-live, the policy set, the 17 security domains, who’s responsible for what, a worked example of the interfaces you test and run, the two breach clocks, where NABIDH fits into Dubai’s other rules, and a compliance plan that will pass an audit.

What NABIDH Is and Who Must Connect

Commence with the product itself, as a significant portion of the frustration with NABIDH arises from its confusion with adjacent items.

NABIDH is Dubai Health Authority’s health information exchange. It is based on HL7 messages and IHE profiles received from EMRs of individual facilities, creating one longitudinal record per patient in public and private facilities in Dubai. If you are licensed by DHA, then NABIDH connectivity is part of your facility licence.

The licensing link is straightforward. The Manual for Licensing Health Facility, v1.2 (Effective 30 September 2026), states that an EMR that meets the NABIDH Minimum Data Set becomes a condition of licence activation (section 7.2.4). Additionally, organizations must approve an email message sent through the tested NABIDH connectivity before enabling the licence (7.2.6.10). The hospital standards reiterate this requirement. The Standards for Speciality Hospitals, ST-70 (effective 30 June 2026) have the following requirements: Registration with NABIDH and active integration (15.1, 15.2).

Over the years, the rollout has continued. According to  Zavis’ sourced integration guide, onboarding was a licence condition from 31 December 2021, outpatient clinics from 30 June 2023 and laboratory integration from 31 December 2023 with go-lives since October 2020. You should check the DHA circular to make sure the dates are correct before setting deadlines to get around them. The dates come from a vendor guide.

This is because the UAE has three exchanges: Malaffi in Abu Dhabi, Riayati (Federal Level) and a Dubai Security called NABIDH. Malaffi is run by a different company with different rules, and no advice can be applied to them.

The final takeaway is that NABIDH is not an IT project but a project about rules.

NABIDH Integration: The Path from EMR to Go-Live

The integration path is short on paper, and in reality it takes months; it is good to know all the stations in advance.

The facility will prove itself to be a facility capable of sending clean, complete, correctly coded messages. The NABIDH integration process starts with a readiness assessment on the developer portal, proceeds to a connectivity test and culminates in a go-live wave. The quality of your patient data will dictate the number of rejections you will receive. The following steps are based on the EMR Transition Guideline and the Zavis guide; please check the details against the DHA’s current onboarding pack.

Key Steps in the NABIDH Integration Process

  1. Conduct a readiness test. Discuss documentation practices, patient identifier hygiene, coding standards, clinician Sheryan IDs and named change champions with clinicians prior to any interaction with the portal.
  2. Choose or verify the EMR. Look at its NABIDH history, not what it can do. Validating an EMR for other locations saves you trips.
  3. Verify that you have signed the DHA onboarding agreement. At this point, the section 4 policy will actually start to have legal force behind it.
  4. Check the connection on the developer portal. NABIDH checks the structure, completeness, codes sets and duplicates of the message. There will be many rejections and fixes. First passes are rare.
  5. Go live during a predetermined wave. Waves are batched, so failing a test is a weeks delay, not days.
  6. Post go-live monitoring. The portal dashboards will show your error rates. Accepted messages will return CA acknowledgements, while rejected messages will return CE or CR.

The technical baseline consists of the Technical and Operational Standards (v1.0): HL7 ADT, MDM, ORM, ORU, RDE and VXU message families and IHE profiles, including ATNA for audit trails, BPPC for privacy consents, PDQ and PIX for patient identity, and XDS and XUA for document sharing and user assertions. Code sets include the following groups of codes: ICD-10-CM, CPT-4, LOINC, SNOMED CT and Dubai Drug Code (Check in NABIDH interoperability documents). If you are changing your EMRs at a later stage, please inform NABIDH at least one month in advance and schedule the transition period as per the EMR Transition Guideline.

In this case, both are true at the same time. A clean NABIDH integration is mostly data quality activities, and the same interfaces you create will be the targets on which the security standards will make you defend your data.

The final takeway is to consider rejection rounds and view your interfaces as security assets from the outset.

The NABIDH Policy Set Every Facility Signs Up To

The onboarding agreement is a rollup of policy documents that you are agreeing to sign, so the prudent first move is to read them all.

Policy or standard Version and date What it governs
Information Security Standards v1.0, September 2020 17 security control domains in three tiers
Incident Management and Breach Notification Policy v1.0, September 2020 Incident reporting, investigation and notification duties
Consent and Access Control 2020, plus ST-09, effective 2 April 2025 Consent mechanics, access rules, break-the-glass
Authentication and Authorization Policy 2020 Who may connect, and how identity is asserted
Audit Policy 2020 Audit trails and log review
Identity Management Policy 2020 Patient and user identity
Data Management and Quality Policy 2020 Data quality, primary and secondary use
Subject of Care Rights 2020 Patient rights over their record
Technical and Operational Standards 2020 Message families, IHE profiles, operations

Observe the two generations. The NABIDH dates were published in 2022 and continue to apply. It is replaced by newer DHA instruments: ST-09 (Standards for Health Information Consent and Access Control), effective from 2 April 2025, and PP-13 (Policy for Health Data and Information Sharing), from 10 November 2024. ST-09 does not say it replaces the 2020 consent policy, so refer to both and show where they apply, rather than assume one layer ‘wins’.

The consent mechanics, which are in ST-09, are more specific than most facilities expect:

  • There is no separate consent for uploading PHI to NABIDH (8.17), but the general consent form of the facility should have a NABIDH sharing clause (8.18).
  • Patients do not opt in at your front desk (9.9); further, they opt out via a DHA process.
  • Break-the-glass access is only available for emergencies, and the system logs and audits it (17.1 to 17.8). Organizations must restrict access to PHI to users within the UAE and require all users to authenticate through two-factor authentication (17.1).
  • Access reviews happen at least once a year, and reviews of privileged accounts happen every three months. After 40 days of inactivity, the system turns off accounts (10.17, 16.4–16.6).

PP-13 deals with these and introduces data sharing agreements, DPIAs, logs of the sharing for six years and a breach clock of its own.

The final takeaway: Print the list, assign an owner to each item, and mark the location of your controls against each requirement.

NABIDH Data Security: The 17 Domains and Three Tiers

Security under NABIDH is not a single checklist; it is a multi-layered system with a level for each layer.

The Information Security Standards, v1.0, includes 17 control domains, grouped into three levels: Essential, Intermediary and Enhanced. All organisations must be at the Essential level before they can join (see section 5). 2.1 PHI in all its forms 3.2 Apply to NABIDH integrated providers and beyond. 2.1 The HISS framework requires risk management. 2.1 Dubai Law No. 26 of 2.1 classifies health information as at least “shared-sensitive.” 2.1 Section 2.1 organises the next set of 17 domains for reading.

Area Domains
Governance Information security organisation; policies; audit and compliance
People and assets Human resource security; asset management; supplier relationships
Facilities and operations Physical and environmental; communications; operations
Access and identity Access control; cryptography
Systems System acquisition, development and maintenance; electronic biomedical devices; cloud computing; mobile device working
Response Incident management; business continuity

The tiers stack up. The Essential tier serves as the introductory ground level: “At this tier, organizations must conduct penetration (vulnerability) testing and disaster recovery testing to meet Audit and Compliance requirements (6.1.12).” The intermediary tier adds additional controls, such as vulnerability scans as defined in Incident Management (6.1.10).

Enhanced goes a step further and requires penetration testing and vulnerability assessments for access control (6.1.8). Security requirements are also part of the acceptance testing of new systems (6.1.9) and the standards give you the right to audit suppliers (6.1.6, 6.1.14).

Re-read those citations as they settle a common argument. But penetration testing is essential and should be done before handing over the new hard drive.

There is no frequency in any of the NABIDH documents. Regular, that is, in the standards, and you’ll have to fill in the interval, record it and keep the reports. There is no “NABIDH Pentest Mandate Annually” in the documents.

There are two planning implications: NABIDH data security is layered, so a small clinic’s floor is not the target of a hospital. You need to start at your tier level, not at a generic level. Because the standards apply to PHI regardless of location, NABIDH data security requirements apply to the data in the EMR, the integration engine, the debug logs and the cloud account that supports them.

The summary: know what tier you are in, compare yourself to the controls, keep a record of your testing period, and if you are asked, show it to an auditor.

Who Does What: Facility Duties Under the Platform Policies

The policies do not pertain to “the facility” as a whole, but rather emphasise specific roles, each of which entails responsibilities that individuals must assume. The structure builds three named pillars of roles.The Information Security Officer (or designee) of the facility audits and monitors security measures and reviews suspicious activity on a monthly basis (Incident Policy 3.3.5) and reports suspicious activities to NABIDH (Incident Policy 3.3.7). The Information Security Standards require organizations to formally assign roles for vulnerability monitoring, assessment, and coordination (6.1.7). ST-09 also expects system owners to manage access control and decide who can access specific information.

There is a list under ST-09 for access to hygiene. Users sign user and confidentiality agreements (10.3) and receive training first (5.11) before they gain access. You base access on ‘need to know’ (10.3) and ‘least privilege’ (5.11), assign roles to the clinician’s Sheryan licence code, and revoke access on termination (13.1). This information is all verified, not exclusive.

And audit responsibilities are related at the same time. The Audit Policy and ATNA profile both require the creation of audit trails and the review of logs. ST-09 also requires that records of consent and audit logs be available to the patients and DHA inspectors (16.13).

Of course, facilities most frequently miss the supplier angle. Your EMR vendor and your integration partner are inside your compliance boundary, not outside it. Agreements should contain audit rights (ISS 6.1.6), and PP-13 requires “sufficient guarantees” of security for any person handling shared health data (4.19).

The conclusion is that NABIDH compliance has identified owners, and the one who says “the vendor does it” isn’t one of them.

Healthcare API Security Testing on NABIDH-Style Interfaces

Nowadays, your connectivity interfaces are the most important access points to your PHI; test them as such.

Most patient data flows through an HL7 feed, an FHIR endpoint, the integration engine, and the developer-portal connection with minimal human supervision. Healthcare API security testing verifies that the connectivity test never runs: Broken authentication on listening interfaces, PHI echoed in acknowledgements and logs, and messages were received from senders who shouldn’t reach you. The connectivity test asks, “Does the message follow the correct format?” The security test asks, “Who sent the message, what information did the system expose, and what data did it record?”

Map the tests to the documents, and the list almost writes itself:

  • Authentication on all listening interfaces, as per the Authentication and Authorisation Policy and the IHE XUA profile.
  • Conduct access audits as per ATNA/Audit Policy.
  • ACK and error messages, debug logs and exports, and PHI leak.
  • – Movement between roles and buildings as per ST-09.
  • Encryption on the wire, as required by PP-13 4.19.6.
  • Test environments will be synthetic data only, not live PHI (PP-13 4.18.1).

That last point deserves repeating, because healthcare API security testing done with production patient records creates the exact breach it is meant to prevent. Build a mock, feed it invented patients, and keep the real interfaces for authorised, scheduled work.

This final point deserves emphasis: when organizations test healthcare API security using actual patient records, they risk causing the very data breach they aim to prevent. Create a mock, supply it with made- up patients, and leave the actual interfaces for authorised and scheduled work.

Code example: three checks on a mock HL7 listener

This is a mini, runnable version of the concept. The script models the receiving side of an integration engine in two builds (enabled and disabled) and does three checks: the listener refuses an unauthenticated sender, and CE and CR acknowledgements do not contain patient The error text includes demographics, and there is an audit record for each message, whether accepted or rejected.

The listener it tests (hl7_listener.py, in the download) has an insecure and a secure profile. The screenshot shows its receive() method, where the three controls live.

The run output, unedited:

The insecure build fails all three checks, while the secure build passes all three – that’s the whole argument, in thirteen lines of output. The limits matter: in this case a mock listener with synthetic data, written to demonstrate the method. To test real NABIDH connections, written authorisation, non-production environment and DHA compliant data handling is required. 

The lesson: whether or not people have run your interfaces today, they fail or succeed these 3 tests.

NABIDH Cybersecurity Dubai: Incidents, Breaches and the 48-Hour Clock

If anything goes wrong, the question is no longer, “Are we safe?” but rather, “How quickly can we convince ourselves of what happened?”

The Incident Management and Breach Notification Policy, v1.0, establishes the timelines of the platform, and they are tight. When teams look for NABIDH cybersecurity requirements in Dubai, they typically are after just this table: 

Step Duty Timeline Section
The facility reports an incident. Facility ISO notifies NABIDH. Within 48 hours of discovery 3.3.7
Significant incidents Sent to the common reporting point, Nabidh@dha.gov.ae Per policy 3.2.8
NABIDH acknowledges Acknowledgement of a reportable event Within 48 hours or two business days 3.2.15
NABIDH notifies DHA. Confirmed breach escalation Within 48 hours 3.2.26
NABIDH notifies the facility. Confirmed breach affecting it Within 48 hours or two business days 3.2.28
Public notification By the facility, where required Within 30 days of discovery 3.2.29
Large breaches Typically over 500 people with continuing risk to DHA Per policy 3.2.31
Root cause analysis Completed and documented Within 30 days 3.2.19
Mitigation of a confirmed breach Completed Within 180 days 3.2.21
Investigation reports Retained At least 25 years 3.2.27c

Now the twist: there is a second clock running in parallel. Breach reports to PP-13 are required to be submitted to the UAE Information Office and DHA’s data compliance mailbox (datacompliance@dha.gov.ae) within 24 to 48 hours (4.23.4(d)). The two clocks are in separate documents and do not refer to each other, so use both in a single playbook, not averaged. If they have a CERT in India, and they leave behind a copy of the CERT playbook, the UAE regime is independent.

The numbers 25 years and 30 days differ from the other numbers when building. The investigation report may not be supporting the logs 25 years after 90 days have passed. Realistically, the NABIDH cybersecurity responsibilities in Dubai are largely time- and proof-orientated: detection that gets the job done, a reporting system that has been determined ahead of time, and logs that pass muster. 

What are some ways to have two clocks running together? In our opinion, the best practice (neither of the documents has a rule in that regard) is to give all first notices in 24 hours. That meets the more demanding PP-13 and is within the NABIDH 48 hours. Prewrite two notice forms with recipients identified for them to concentrate on the facts and not the formatting.

Lesson learned: Have two copies of the incident playbook, one for each alarm, and practise them before the incident.

Where NABIDH Sits Among Dubai’s Other Rules

NABIDH is one of the layers in a stack, where each layer imposes you into various obligations with auditors and lawyers.

Instrument Who it binds What it adds
NABIDH policies (2020) DHA-licensed facilities on the platform Platform security tiers, consent, audit, incident clocks
PP-13 and ST-09 All DHA-regulated entities and PHI users Sharing agreements, DPIAs, consent mechanics, and the 24 to 48-hour clock
Federal Law No. 2 of 2019 UAE-wide Health data localisation and 25-year record retention, with Cabinet Decision 51 of 2021 exemptions
Dubai Law No. 26 of 2015 Dubai Data classification: health data rated as at least shared-sensitive
DESC ISR Dubai government entities The emirate’s government security regulation
ADHICS Abu Dhabi only The contrast case: it does not govern Dubai facilities.

The table reading is more difficult than the practical reading. Dubai’s regulatory framework includes two NABIDH policies, PP-13 and ST-09, alongside federal laws that private clinics must follow.The DESC ISR gear will be stored in a facility owned by DHA. If you are an Abu Dhabi hospital reading this page, read the equivalents ADHICS and Malaffi also. 

Our DHA rule guide contains a larger policy stack and a providers guide for some of the duties you have outside of the platform and the licensing manual. 

The key takeaway is that NABIDH serves as the platform layer, and organizations must continue to comply with data protection rules after transmitting messages to the interface.

A NABIDH Compliance Plan That Survives an Audit

The following plan documents every step, and good intentions won’t cut it to survive audits.

  1. Check the status of your licence and find the NABIDH connectivity approval email (Manual 7.2.6.10). 
  2. Assign the named roles: Organizations must establish the designated roles of Information Security Officer, system owners, and vulnerability monitoring and coordination personnel (ISS 6.1.7).
  3. At the basic level, compare the 17 domains and record all gaps, including their owners and deadlines. 
  4. Fix the consent paperwork: the NABIDH clause in your general consent, opt-out routing through DHA, and a written break-the-glass procedure (ST-09 8.18, 9.9, 17.1).
  5. Harden the interfaces: authentication, encryption and audit trails on every listener, including the integration engine.
  6. Test: penetration testing of the EMR, APIs and integration engine before onboarding, after major changes, and at your documented interval.
  7. Clean the test environments: synthetic data only, per PP-13 4.18.1.
  8. Write the incident playbook with both clocks: 48 hours to NABIDH and 24 to 48 hours under PP-13, plus the 30-day public notice.
  9. Review access on schedule: yearly for standard accounts and quarterly for privileged ones, and keep the six-year sharing logs and 25-year investigation records straight.
  10. Re-run the baseline before licence renewal and after any EMR switch.

If it is of any value, from a note of my testing work. Most commonly here is the integration engine next to the exchange, and the capability to log in full HL7 into files that no one secures and that anyone can read. The exchange is audited, the middleware is passed over and the middleware has everything.

The lesson learned: The evidence is more important than the intent, and the auditor wants the evidence, the report, and the retest.

How Qualysec Supports NABIDH-Connected Facilities

Qualysec is a penetration testing expert company, and the NABIDH relationship is direct, the controls that the company expects are the same type that would be tested by a penetration test.

The team validates EMRs, patient portals, mobile applications, HL7 and FHIR interfaces, and cloud configurations and correlates the test results to NABIDH Information Security Standards domains for your gap register and test report to find common ground. Testing runs in non-production environments with synthetic data, in line with PP-13 4.18.1. After each fix, we conduct retests to validate it and produce an attestation letter documenting the closure, the evidence trail that Section 10 has been looking for.What you will NOT hear is a claim of DHA accreditation, DHA NABIDH or DHA DESC since DHA does not certify security testing vendors and does not approve EMR connectivity. 

Case study: testing a connected medical device

Medical device manufacturer, vTitan, engaged Qualysec to test its Accuflow Uro medical device, and mobile application, against FDA Cybersecurity Guidelines from December 2024 to February 2025. Their verified Clutch review states that the engagement involved the device and app, and that the team reported results, corrected issues, and re-tested. NABIDH and DHA did not contract this project. The shape still transfers, and that is a regulated health product: it sends data across an interface, and the team verifies closure through retesting, not through an email.

Prepare for Your Next Cybersecurity Audit with Qualysec

Choose a partner that helps you identify and fix real security risks before attackers do. We are here to help.

Talk to an Expert→

Talk to a Cybersecurity Expert

Conclusion and Next Steps

Through its link between your licence, EMR and security posture, NABIDH is the solution for you. The foundation of the platform’s policies in 2020 were the Essential tier, the named testing obligation, the designated officers and the 48 hour reporting duty. The newer DHA instruments, ST-09 and PP-13, take that floor up via consent mechanics, sharing agreements and a second breach clock. None of it pays for purpose. It’s all about evidence. Retests and logs, baselines, and they still exist when asked.

This week you are to pull your NABIDH Dubai onboarding evidence and your previous interface security test report. One is missing or out of date; it is the space you will fill before the renewal date closes.

Frequently Asked Questions

1. Is NABIDH mandatory for clinics in Dubai?

Yes, for DHA registered premises. The licensing manual makes an EMR compliant with the NABIDH Minimum Data Set (7.2.4) and the approval email for tested connectivity (7.2.6.10) conditions of the licence. This obligation is reiterated in the hospital standards: ST-70 to be registered and integrated (15.1, 15.2). In summary, there is a close relationship between Dubai licence and Dubai platform, and if the connectivity approval is not granted, it can cause delay in the process of obtaining a Dubai platform.

2. What security level must a facility reach before NABIDH onboarding?

The NABIDH Information Security Standards (section 5) is at least at the minimum level. That tier includes 17 control domains and already includes penetration (vulnerability) testing and disaster recovery testing (6.1.12) in Audit and Compliance. The standards stipulate that all be under risk management with the HISS framework (3.1), while the Intermediate and Enhanced levels add to the control. There is no set frequency for testing; determine and record your own.

3. How fast must a NABIDH security incident be reported?

The Information Security Officer shall report to NABIDH within 48 hours after it is discovered (3.3.7). The UAE Information Office and DHA’s data compliance mailbox should be notified of any breach separately within 24-48 hours (4.23.4(d)). If a public notification is required it shall be made no later than 30 days after discovery (3.2.29). Use both these timings, not average, as they’re from two different documents.

4. Do patients have to consent before their data goes to NABIDH?

There is no need for a second consent. As stated in ST-09, there is no need to upload any additional form (8.17) for PHI in NABIDH, but the facility must have NABIDH sharing clause (8.18) in their general consent. The clinic front desk will not know patients want to get out unless they go through the DHA opt-out process (9.9). Emergency break-the-glass access is for treatment purposes and is only used by treating doctors and is logged and reviewed (17.1 to 17.8).

Pabitra Kumar Sahoo

About Pabitra Kumar Sahoo

Pabitra Kumar Sahoo is the Co-Founder and Chief Operating Officer (COO) at Qualysec. With a deep commitment to elevating global cybersecurity standards, he directs corporate operations and service strategy, helping enterprises mitigate compliance debt and defend their digital infrastructure through elite, human-led penetration testing.

Leave a Comment.

Your email address will not be published. Required fields are marked *

Related Blogs

Subscribe to Newsletter

Get the latest cybersecurity insights, compliance tips, and vulnerability reports delivered directly to your inbox.