Skip to content
Get Support
  • There are no suggestions because the search field is empty.

NABIDH Guide Part 3: Map Your Data for NABIDH

NABIDH expects a handful of details that Pabau does not store natively — an Emirates ID, a nationality, a DHA specialty for each service, a Sheryan licence number for each practitioner. This guide covers the one-off mapping that connects those dots. Do this before enabling visit or clinical triggers; it is what stands between you and validation failures.

This article is part of the NABIDH guide series:

How the Mapping tab works

Open your NABIDH connection (Data Hub > Data Sync > Manage) and go to 3. Mapping. Unlike other connectors, the NABIDH mapping is fixed by the DHA NABIDH HL7 v2.5.1 specification — you cannot re-route standard fields, and that is deliberate. Standard fields (name, date of birth, contact details and so on) are applied automatically. What you can edit are the rows marked Custom: NABIDH fields that Pabau fills from your client custom fields.

Each section shows a completion bar. The groups you see depend on which triggers are enabled — with only patient sync on, you will see the Message envelope, Client, Client next of kin, Client insurance, and Consent & VIP flags groups.

Step 1: Bind The Client Custom Fields

Expand the Client group. Rows marked Custom need a Pabau client custom field selected in the left-hand dropdown. The full set the connector can use:

  • Emirates ID (text) — sent as PID.19. Required for every Dubai-resident patient.
  • Middle name (text) — PID.5.3.
  • Marital status (dropdown) — PID.16.
  • Religion (dropdown) — PID.17.
  • Nationality (dropdown) — PID.28.
  • Resident / tourist flag (dropdown: Resident / Tourist / Visitor / Non-resident) — PID.31.
  • Insurance plan ID (text) — IN1.2.
  • Insurance payer code (DHA) (text) — IN1.3.
  • Insurance plan expiry (date) — IN1.13.
  • NABIDH consent to share (yes/no) — ZSC.1.

If a field does not exist in your account yet, use Create new field directly from the mapping row — it creates the client custom field and binds it in one go. Fields whose names match the list above are suggested automatically.

NOTE: Accounts that signed up from the UAE have these ten client custom fields created automatically. Established accounts adding NABIDH later create them once here — after that they appear on every client card like any other custom field.

IMPORTANT: Emirates ID is the single most important binding. NABIDH requires it for every patient reported as a Dubai resident (a 784-prefixed, 15-digit number). A resident patient without one fails validation and their messages are not sent. Tourists are exempt — they are sent with the standard placeholder ID automatically.

The VIP / restricted flag (ZSC.2) works differently — it is driven by a client label rather than a custom field: pick the label on the mapping row and any client carrying it is flagged to NABIDH.

Step 2: Set The NABIDH Specialty On Your Services

Every visit message must carry a DHA hospital service code (the NAB008 code set, sent as PV1.10). Pabau reads it from the service the appointment was booked for:

  1. Go to Setup > Services and edit a service.
  2. On the General tab, directly under Service code, you will find the NABIDH specialty dropdown (it appears once a NABIDH connection exists).
  3. Pick the specialty that matches the service — e.g. DER — Dermatology or LAS — Laser Hair Removal. The selection saves immediately.

NOTE: Set the specialty on every service that patients book appointments for. A visit whose service has no NABIDH specialty fails validation until one is set.

Step 3: Record Your Practitioners’ Sheryan Licence Numbers

Visit messages also identify the attending clinician by their individual 8-digit DHA Sheryan licence (PV1.7). These live on the connection's 1. Settings tab, in the Your team card:

  1. Open Staff Sheryan provider IDs. If the team field does not exist yet, click Set up team field — this creates a "Sheryan provider ID" team custom field (it also appears on each team member's Personal Details page).
  2. Enter each practitioner's 8-digit licence number and click Save IDs.
  3. Set a practice-wide fallback licence for anyone without their own number, and click Save fallback.

At delivery time Pabau uses the booked practitioner's own number first and falls back to the practice-wide one; if neither exists, the visit fails validation.

Step 4: Check Your Diagnostic Codeset

If you plan to sync client problems, NABIDH expects ICD-10 problem codes. If your account's default diagnostic codeset is something else, the Client problems mapping group shows a banner with a one-click Set ICD-10 as default fix. Problems recorded without an ICD-10 code are still sent, as free text.

Step 5: Save Your Mapping

Mapping edits are staged, not applied instantly — the header shows an Unsaved changes pill. Go to 4. Review and press Save in the top right to publish them. Closing the connection without saving discards the staged changes after a confirmation prompt.

TIP: With mapping done, decide exactly which events flow to NABIDH in Part 4: Choose which events are sent to NABIDH.