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

How to Backload Historical Records to NABIDH

If DHA asks your facility to send its past patient records to NABIDH before you go live, Pabau can do it for you as a backload. It always starts with a dry run: every record in your chosen date range is checked and counted, nothing is sent, and you get a report to review. Only when you’re happy do you send it, in the order DHA asks for.

NOTE: This guide is for clinics in Dubai with a NABIDH connection, and you need access to the Data Hub. You only need a backload when DHA asks for one, usually when a facility is (re)onboarding to NABIDH. Set up your connection and mapping first (Part 2 and Part 3 of the NABIDH guide series).

Step 1: Open the Backload Card

  1. Go to Data Hub → Data Sync, click Manage on your NABIDH connection, and stay on 1. Settings. Scroll down to the Backload to NABIDH card.
  2. Click Start dry run.

The Backload to NABIDH card on the Settings tab with the Start dry run button marked

Every backload begins with a dry run

Step 2: Choose What to Check

  1. Set the From and To dates. Both dates are included.
  2. Under Record types, tick what to include: Visits, Prescriptions, Lab results, Documents and Problems. Everything except lab results is ticked to begin with.
  3. Optionally, enter At most N records of each type. Use a small sample while you’re in DHA’s test phase; leave it empty to include everything.
  4. Leave When a key detail is missing unticked unless DHA has agreed to it. Send nationality as Unknown (UNK) and Send country as Other (001) include patients who would otherwise be left out for a missing nationality or country.
  5. Click Start dry run.

The Start a backload dry run form with the dates, record types, record limit, missing-detail options and Start dry run marked

Choose the date range and record types

The dry run works through your records in the background. While it runs, the card shows Dry run in progress with the counts so far, and you can click Stop dry run at any time. Nothing is sent to NABIDH during a dry run.

Step 3: Review the Dry Run Report

When the card shows Dry run complete, read the report:

  1. The DHA count table shows how many valid messages of each type would be sent: the numbers DHA asks you to report.
  2. By record type breaks each kind of record down into Considered, Will send, Left out, Failed checks and Not applicable.

The dry run report with the DHA count table and the By record type table marked

The report shows exactly what would be sent

Below the tables, Patients left out lists how many records were left out for each missing detail. DHA asks for patients missing a first name, last name, date of birth, nationality, country, Emirates ID or mobile number to be left out, and one record can be missing more than one. VIP patients are always left out.

NOTE: While the connection isn’t on Production, or when a Backload endpoint URL is set in the connection settings, the report says identities are masked: patient details are hidden and documents are replaced with a dummy PDF. That’s what DHA expects during its backload test phase.

Step 4: Send the Backload

  1. Click Download report (CSV) to keep a copy of the report.
  2. Not ready to send? Click Discard to throw the dry run away. Nothing is sent.
  3. Click Send backload when you’re ready.

The bottom of the dry run report with Download report (CSV), Discard and Send backload marked

Download, discard or send

A confirmation opens before anything leaves Pabau:

  1. Messages to send shows how many messages will go.
  2. The note underneath says where they will go. On Test, they go to the Backload endpoint URL in the connection settings, or to your regular test endpoint if none is set. On Production, they’re real patient records going to the live NABIDH platform and can’t be taken back.
  3. Click Send backload to start, or Cancel.

The Send the backload to NABIDH confirmation with the message count, destination note and Send backload button marked

Check the count and destination before you confirm

IMPORTANT: The connection must be active to send. If it’s paused, the card asks you to resume it first. Records are checked again as they’re sent, so the final numbers can differ slightly from the dry run.

Step 5: Follow the Backload

The card shows Sending and which record type is going out (Now sending: Visits, for example). Visits go first, then the other record types, one type at a time. Each message also appears in the connection’s Logs like any other NABIDH delivery, with DHA’s reply.

  • Click Stop backload to stop. Messages already queued are still sent; the rest aren’t. To send them later, start again with a new dry run.
  • When it finishes, the card sums up how many messages were sent and how many failed. Click Start a new dry run to run another backload.

What's next?


Was this guide helpful? Let us know by voting below - your feedback helps us write clearer articles.

For more guides, browse the related articles below or use the search bar at the top of the page. You can also watch our video learning series, the Pabau Academy, or visit the Support page for additional help.