DHPO and eClaimLink
We support DHPO and eClaimLink claims workflows through Care billing and approvals, with facility setup and receiving responses reviewed for the agreed transaction scope.
Subject type: claims transaction gateway. DHPO and eClaimLink carry insurance claim transactions in the UAE. This page is about a technical route, not a regulator or an accreditation programme.
What is built
- Care Billing provides the charge and billing context.
- Claims and approvals builds the claim as XML and submits it through the gateway’s web service.
- Remittance advice can be downloaded from the gateway and read against the claim.
- Until a facility has gateway credentials, a test mode records a placeholder acknowledgement. It is not a gateway response.
Transmission, acceptance and payment
These are three different things. Transmission means the claim reached the gateway. Acceptance means the payer’s rules accepted it. Payment means the payer paid. Care records what the gateway returns. A software workflow does not establish acceptance, payment or the correctness of a clinical code, and each transaction type and facility setup stays explicit. Connection status is maintained with the UAE market page.
Setup prerequisites
- The facility’s gateway credentials and the payer identifiers it submits to.
- Agreed code sets for diagnoses, procedures and drugs.
- The schema checks that apply to the route. For Dubai these are confirmed during onboarding.
- A test of representative claims with the gateway before live use.
Illustrative example: a claim and its response
This example uses synthetic data. A synthetic consultation for a patient, Fatima Al Zaabi, is billed in Care. Care builds the claim from the bill and the signed encounter, submits it and stores the gateway’s response with the claim. If the response reports an error, the returned message is kept with the claim for the billing team to review. Later, the remittance advice is downloaded and read against the claim. The example shows how Care records each step. It does not show payment or a live connection.
Official source
eClaimLink. The gateway operator publishes its own transaction requirements. No guaranteed acceptance, payment, denial prediction or universal transaction coverage is claimed.
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
-
No. The payer or receiving service assesses the transaction under its requirements. Your team must review the response and the supporting record; transmission alone does not establish approval or payment.
-
Claim submission and remittance download are built. Any other transaction type, such as eligibility or prior authorisation through the gateway, is scoped separately for your deployment.
-
Gateway credentials, the payer identifiers it submits to, agreed code sets and a test of representative claims with the gateway. In test mode Care records a placeholder acknowledgement, which is not a gateway response.
Not answered here? Contact the team
NXH Flow