Skip to Content
العربيةBook a demo
Solutions
Platform
Integrations
Security & Delivery
Resources
Company
Book a demo

NABIDH integration for clinics, laboratories and hospitals in Dubai

NABIDH is the health information exchange of Dubai. This is which messages and standards it accepts, how identity and codes must be sent, and how Ventrecs scopes the connection for a facility.

What NABIDH is

NABIDH is the health information exchange of Dubai, run by the Dubai Health Authority. It collects, aggregates, normalises and presents clinical patient data from the organisations that provide care, so that a clinician and, through a separate portal, a patient can see a unified record.

Facilities send patient data to NABIDH from their EMR as HL7 messages or C-CDA documents.

At a glance
Where
Dubai
Operated by
Dubai Health Authority
Carries
Clinical patient data from the organisations that provide care
Standards
HL7 v2.5 messages and C-CDA v2.1 documents, per the interface documentation reviewed
Published
Interface documentation, policies and standards
NABIDH

Who needs to connect

Healthcare facilities licensed by the Dubai Health Authority that provide care.
Technology vendors that build the interface, working with the facility and the Dubai Health Authority.
Groups with facilities in both Dubai and Abu Dhabi, who connect to NABIDH and Malaffi separately.
NABIDH

What data is exchanged

Patient identityEmirates ID in the defined field, or passport or GCC number with an identifier type, and the medical record number with an assigning authority.
EncountersAdmission, discharge and transfer events, each with a unique encounter identifier.
Orders and resultsOrder messages and laboratory and radiology results and observations.
Prescriptions and dispensingPharmacy and treatment orders.
Discharge summaries and immunisationsDischarge summaries and immunisation messages (VXU).
NABIDH

What the exchange involves

Standards and messages

The interface documentation we reviewed (version 1.0, 19 July 2020) names the standards. Confirm the current version with the authority before building.

  • HL7 v2.5: ADT, ORM, ORU, RDE, MDM and VXU
  • C-CDA v2.1 documents
  • Commit acknowledgements the sending system has to read

Identity and codes

The documentation is specific, because an unmatched record is useless.

  • Emirates ID for the patient, with passport or GCC number where there is none
  • MRN sent with an assigning authority
  • ICD-10-CM, CPT and CDT, IR-DRG and the Dubai Drug Code

Privacy rules

Some rules change what a facility sends.

  • No data is sent for VIP patients
  • Tourist data is flagged
  • Opt-out is honoured on the portals while the facility still sends the data
NABIDH

How Ventrecs handles it

Events in the recordPatient movements, orders, laboratory and imaging results, prescriptions and dispensing, discharge summaries and immunisations are recorded as part of the patient record.
Patient identityEnterprise identity with a duplicate-review queue, and sensitive patients marked so release rules can respect them.
Message transportHL7 v2 transport runs in a separate integration layer, scoped per project, not inside the clinical system.
Durable outboxMessages leave through an outbox with retry, a transaction log and a reconciliation queue, so a deferred, rejected or missing response is a visible state with an owner.
How the connection is delivered

Each connection is delivered as a project: scoped with your facility and NABIDH, built as an interface adapter on the Ventrecs integration layer, tested in the operator's environment and signed off before go-live. Where the operator requires approval or certification, it is part of the project plan.

Messages are carried by Ventrecs Connect. See how an integration is delivered, from scoping to monitoring. Ventrecs Connect · The integration lifecycle

NABIDH

Typical rollout steps

The same eight stages as every Ventrecs deployment, applied to this connection. How we deliver

  1. 1
    DiscoverConfirm with the Dubai Health Authority which of your facility types must connect, and which messages or transactions apply.
  2. 2
    DesignAgree the message set, identifiers and code mappings, and name an owner for each interface.
  3. 3
    ConfigureSet up facilities, users, catalogues and the integration layer, with credentials held outside the clinical records.
  4. 4
    MigrateLoad the master data the exchange needs, such as facilities, clinicians and patient identifiers, and reconcile it.
  5. 5
    TestTest in the environment the Dubai Health Authority provides, with synthetic data, including rejected and duplicate messages.
  6. 6
    TrainTrain the teams who watch the interface and fix the rejections.
  7. 7
    Go-liveCut over in phases with on-site support, and with sign-off from the Dubai Health Authority where the operator requires it.
  8. 8
    HypercareClose monitoring in the first weeks, then hand-over to the agreed support process.
NABIDH

Sources

Operator and standards documents these statements rest on. Standards change, so work from the current version.

NABIDH

Questions we are asked

Which standards does NABIDH accept?

The Dubai Health Authority interface documentation describes HL7 v2.5 messages, namely ADT, ORM, ORU, RDE, MDM and VXU, and C-CDA v2.1 documents.

How do I identify a patient?

By Emirates ID in the defined field. Where there is none, the passport number or the GCC number is used with its identifier type, and the MRN is sent with an assigning authority.

Which code sets are used?

ICD-10-CM for diagnoses, CPT and CDT for procedures, IR-DRG, the Dubai Drug Code for medicines, and the authority's code lists for countries and nationalities.

Can Ventrecs connect us to NABIDH?

Yes. We deliver the connection as a project with your facility and the Dubai Health Authority: Ventrecs Connect carries the messages through an integration layer with retry, a transaction log and a reconciliation queue. The interface is built and tested before go-live, and the go-live plan is agreed with you.

Talk to us about your setup

Tell us about your facility and current systems. We will reply within one working day.