What moves
Pre-approval requests with the patient, policy, diagnosis and activity details from the file; claims and resubmissions; and the responses, rejections and remittance advice that come back.
eClaimLink, through the DHPO, is the claims platform Dubai clinics use with their insurers and TPAs. Capra connects to it as one of the systems a Dubai clinic runs: pre-approval requests and claims are prepared from the booking and the patient file, responses and remittance come back to the same record, and your insurance coordinator works from queues rather than a separate portal. 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.
Pre-approval requests with the patient, policy, diagnosis and activity details from the file; claims and resubmissions; and the responses, rejections and remittance advice that come back.
Out from Capra when a pre-approval or claim is submitted from the queue, and back as each response arrives, so the status sits on the booking and the patient file where reception and doctors can see it.
Submissions go when your coordinator sends them or in the batches you set, responses update the queue as they arrive, and every exchange is logged in the audit trail.
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 eClaimLink / DHPO, 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.
eClaimLink / DHPO 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. eClaimLink / DHPO is one of the systems Capra connects to for Dubai clinics, alongside your insurers and TPAs. The connection is scoped on your onboarding call, built and tested with your data, and switched on with every exchange logged.
Insurance details and the pre-approval status sit on the booking, your insurance coordinator works from a pre-approval queue, requests are prepared from the patient file and submitted through the connection, and responses update the booking so reception and the doctor can see them.
Rejected claims land in a resubmission queue with the reason attached, are corrected on the record and resubmitted through the same connection, with each attempt logged.
No. Your payers' own requirements stay exactly as they are; Capra keeps the status visible and the paperwork in one place, and prepares submissions from the details already on the file.
Capra connects to Shafafiya for Abu Dhabi claims in the same way, and a group with branches in both emirates runs them from one account.
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 eClaimLink 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