NABIDH Guide Part 2: Connect Pabau to NABIDH
This guide walks through creating the NABIDH connection in Pabau — from opening the connector catalogue to a successful connection test. It takes about ten minutes once you have your DHA onboarding details to hand.
This article is part of the NABIDH guide series:
- Part 1: What is NABIDH and how Pabau connects to it
- Part 2: Connect Pabau to NABIDH (you are here)
- Part 3: Map your data for NABIDH
- Part 4: Choose which events are sent to NABIDH
- Part 5: Test, monitor and troubleshoot NABIDH deliveries
IMPORTANT: You need three details from your DHA NABIDH onboarding pack before you start: your EMR code, your 7-digit Sheryan facility ID, and your application key, plus the NABIDH endpoint URL for the environment you are connecting to. If you do not have these yet, complete DHA onboarding first.
Step 1: Open The Data Sync Hub
- In Pabau, go to Data Hub and open the Data Sync tab.
- Click Add connector in the top-right corner.
- Find NABIDH (Dubai Health Authority) in the catalogue and click Set up.
Step 2: Enter Your Configuration
The setup wizard has three numbered steps. The first, 1. Configuration, identifies your clinic to NABIDH:
- Connection name — how the connection is labelled inside Pabau. The default is fine.
- Environment — Dummy (developer sink), Test or Production. Dummy targets a developer sink for previewing messages; Test and Production target DHA NABIDH endpoints.
- Endpoint URL — where messages are delivered. Test and Production require an https NABIDH URL; non-NABIDH endpoints (e.g. webhook.site) are only allowed while the environment is Dummy.
- EMR code — the EMR code NABIDH assigned to your system. It is sent as the HL7 sending facility (MSH.4).
- Sheryan facility ID — your 7-digit DHA Sheryan facility licence number. It is sent as the event facility (EVN.7) and the patient-ID assigning facility (PID.3).
- Assume Dubai resident by default — how patients without a resident/tourist marker are reported to NABIDH (PID.31). Leave on Yes if most of your patients are Dubai residents; Part 3 shows how to record the flag per patient.
NOTE: Start against the Test environment if the DHA has given you test credentials, verify a few deliveries end to end, then switch the connection to Production from the Settings tab. The environment and endpoint can be changed at any time.
Step 3: Add Your Application Key
On 2. Credentials, paste your NABIDH application key. It is required for the Test and Production environments and optional while the environment is Dummy.
Credentials are stored encrypted and are never displayed again once saved — to change the key later you simply paste a new value over it in the Settings tab.
Step 4: Review And Create The Connection
The 3. Review step summarises everything before anything is created:
Note the Enabled by default line: only Add patient (ADT^A28) and Update patient (ADT^A31) are switched on when the connection is created. Visits, allergies, problems, prescriptions, lab results and documents are all off until you enable them (covered in Part 4). Click Create connection to finish.
IMPORTANT: The connection is Active as soon as it is created — with the default triggers on, new patient registrations and updates start syncing to the configured endpoint straight away. If you are not ready for that, click Pause on the connection until your mapping is complete.
Step 5: Test The Connection
After creation the connection opens on its 1. Settings tab. Your configuration fields are all editable here, and this is also where you verify the connection:
- Check the environment, endpoint, EMR code and Sheryan facility ID are correct.
- Click Test connection in the Connection settings card.
- Wait for the result — you will see either "Connection test passed" or "Connection test failed" with detail, and the last tested time is remembered.
TIP: A green connection test also saves any staged changes to the settings fields — it is the quickest way to confirm and persist edits in one go.
Next: before real patient data can flow cleanly, map your Pabau fields to NABIDH's requirements in Part 3: Map your data for NABIDH.