What moves
Patient demographics with Emirates ID, encounters, diagnoses, prescriptions, results and documents, in the message set agreed for your clinic, taken from the fields your doctors already complete on the file.
NABIDH is the health information exchange Dubai clinics connect their patient records to. Capra connects to NABIDH as one of the systems a Dubai clinic runs: patient and visit information recorded on the file is sent to the exchange in the message set agreed on your onboarding call, results and lookups come back to the file where applicable, and every exchange is logged. The connection is scoped and built with you during onboarding.
The three things every connection should spell out: what moves, in which direction, and how quickly you can see it.
Patient demographics with Emirates ID, encounters, diagnoses, prescriptions, results and documents, in the message set agreed for your clinic, taken from the fields your doctors already complete on the file.
From the patient file to NABIDH as visits are recorded, and from NABIDH back to the file for the lookups and results the exchange returns, so doctors see the wider record without leaving Capra.
Messages go as visits are completed, queued and retried if the exchange is unavailable, and every message is logged in the audit trail with its status.
Built for you during onboarding, with one named lead from the scoping call to go-live and human support in UK and UAE hours afterwards.
Your onboarding lead maps what your clinic sends to and receives from NABIDH, which fields on the record feed it, and who sees the results.
We build the connection, test it with you against sample records and walk through what moved before anything goes live.
The connection goes live with every exchange logged and visible in your audit trail, and your onboarding lead stays your contact in UK and UAE hours.
NABIDH is named here as a system Capra connects to. Like every record, accounting, claims and exchange connection, it is scoped and built with you during onboarding rather than left for the clinic to work out.
See every integrationDefence in depth, from the first message to the last record. This is how we operate, not a badge.
Connections use current TLS with HSTS, and stored data is encrypted with keys managed by our cloud provider.
Permissions come from defined roles, privileged access needs multi-factor authentication, and rights are reviewed regularly.
Security-relevant events are recorded, retained and reviewed so unusual activity can be investigated quickly.
Critical data is backed up regularly and protected like production, with processes to restore service after a disruption.
UK clinics are hosted in the UK by default; deployment in other regions, including the UAE, is available on request with the same protections.
Capra connects to the record, calendar, accounting, messaging and claims systems you already run; integrations are built with you during onboarding.
Yes. NABIDH is one of the systems Capra connects to for Dubai clinics. The connection is scoped on your onboarding call, built and tested with your data by Capra's own team, and switched on with every message logged in your audit trail.
Your clinic's identifiers and the message set agreed on the scoping call; your onboarding lead handles the technical build and testing with you. Doctors keep working on the patient file as before; the connection takes what they record.
Consent status is recorded on each patient file and the connection respects it, so a patient who has not consented to sharing is not shared. Consent changes are logged like every other change to the file.
The same approach, different systems: Capra connects to Malaffi for Abu Dhabi clinics and to Riayati for the Northern Emirates. A group with branches in several emirates runs them from one account, each branch connected to its own exchange.
Deployment in the region is available on request, with the same encryption, role-based access, backup and audit practices described on our security page.
Data moves over encrypted connections, access to the connection follows roles, and every exchange is written to the audit trail, like every other part of the platform. The practices behind that, from encryption to backups, are described in full on our security page.
Capra keeps working on its own data and queues what needs to be sent. When NABIDH is reachable again, the queued updates are delivered and logged, and your team can see in the audit trail exactly what moved and when.
Explore more
Book a personalized demo and we'll show you exactly how Capra fits your practice, with your channels, your calendars, and your workflows.
Just have a question? Send us a message