NABIDH health information exchange
We support NABIDH connectivity through Care and keep acknowledgements, so your team can review the response within the facility’s agreed clinical exchange scope.
Set by Dubai Health Authority
What this is
NABIDH is the Dubai Health Authority health information exchange. A facility connects to it through onboarding with the Authority; this page describes what Care provides on the facility’s side.
What is built
- Care includes a NABIDH connector for clinical exchange, built on FHIR R4.
- Each outbound message is recorded in an exchange log with its status, attempts and the response received.
- A failed exchange keeps its error text for the team to review.
- Clinical information is drawn from the relevant Care patient and encounter context.
- Until a facility’s live connection is configured, the connector runs in a test mode that records the message and a synthetic acknowledgement without sending anything.
What a technical reviewer can inspect
Your team can examine the information in a representative exchange and the response recorded against it. The evidence relates to that transaction and the agreed site scope. It does not show that every record is accepted, that every required dataset is present or that the facility has completed external onboarding, and a test-mode acknowledgement is not evidence of a live connection.
Illustrative example: one exchange message and a failed one
This example uses synthetic data.
A synthetic patient, Layla Haddad, is seen in a clinic encounter. Care builds the exchange message from the encounter and records it with its status. When NABIDH responds, the response is kept against the entry. In a second synthetic case the response reports an error, so the entry keeps the error text. The facility decides who reviews failed entries, who corrects the clinical record and how the outcome is recorded.
What the facility arranges
- The health data exchange pack, where licensed, and the facility’s licensing.
- Onboarding with the Dubai Health Authority, including credentials and endpoints.
- The message profile and clinical fields required for the facility’s services.
- Testing with representative records, and agreed handling of responses needing attention.
Boundaries
Product support is distinct from the operational status of a particular facility’s connection. Keep NABIDH clinical exchange separate from Dubai insurance transactions through eClaimLink and DHPO, which have their own plan and workflow scope. No universal interface coverage, automated submission dashboard or guaranteed acceptance rate is claimed.
Official source: nabidh.ae
What we claim, precisely
The system holds the evidence; the facility's accountable person attests. Nothing here asserts that a facility is compliant.
Common questions
-
Care includes a NABIDH connector in its health data exchange scope. A facility still needs its regulatory pack, licensing, onboarding and live connection arrangements before its deployment can be treated as activated.
-
No. This page describes clinical information exchange. Insurance transactions through eClaimLink and DHPO have their own workflow and plan scope, which should be reviewed separately.
-
Care’s NABIDH connector is built on FHIR R4. The message profile and clinical fields for a facility are agreed with the Dubai Health Authority during onboarding, and the receiving specification governs.
-
The described exchange workflow retains acknowledgements. Inspect the relevant response during the demonstration and agree how the facility will review and act on anything needing attention.
Not answered here? Contact the team
NXH Flow