Skip to content
faceela

Your busiest month and your worst month can be the same month.

A UAE clinic is two businesses wearing one coat. One of them sees patients. The other one files claims, chases denials, watches a submission deadline and waits forty-five days to find out how much of last month it is actually going to keep. Most clinic software is built for the first business and leaves the second one to a spreadsheet and a determined person.

Recognise any of this

Where the money goes before anyone calls it a problem

If more than two of these are true this week, the cost is already larger than the system you would replace.

  1. 01

    Coding is checked against today's code list rather than against the date of the visit.

    The Dubai Drug Code is republished about twice a week and codes are deactivated in it. A claim carrying one is unpayable, and you learn that in a remittance advice weeks later — by which time the twenty-one-day resubmission window is part of the arithmetic.

  2. 02

    The submission deadline and the resubmission count live in someone's head.

    The cycle allows two resubmissions and one submission date per service month. A missed fifteenth is a late-submission penalty at 0.03% a day; a third resubmission is not a claim with a problem, it is revenue already written off by a person who still thinks it is coming.

  3. 03

    VAT is set on the customer or the invoice instead of on the line.

    Healthcare is zero-rated for preventive and basic treatment by a licensed provider, and standard-rated for cosmetic and elective work and for non-residents. The mixed visit is the normal visit, and getting it wrong at invoice level either overcharges the patient or quietly costs you input VAT recovery. Nothing about it looks like an error.

  4. 04

    Denials are worked in a spreadsheet rebuilt from the remittance file each month.

    The denials that get worked are the large ones. The small ones expire, and the pattern behind them — one clinician, one code, one payer rule — is never visible because nobody ever groups them.

  5. 05

    Late payment by the payer is treated as a fact of life rather than as a receivable.

    The remittance deadlines run both ways: the payer owes 0.03% a day when it pays late, exactly as you owe it when you file late. Almost no clinic in the country bills that side. It is real money and it is sitting in the same regulation everybody quotes at you.

  6. 06

    The health information exchange connection is treated as an IT project.

    NABIDH, Malaffi and Riayati connectivity is a licence condition, not an integration nicety. Discovering an incomplete minimum data set during a renewal is a different conversation from discovering it during a build.

What we build

The system that removes those, specifically

Not a feature list. Each of these exists because one of the problems above cost somebody real money.

  • The visit as one record, end to end

    Booking, arrival, vitals, the clinical note, the diagnosis, the procedure, the prescription and the invoice on a single chain — so a line a payer questions can be traced back to the thing that justified charging it.

  • Coding validated against the service date

    ICD-10-CM, CPT, HCPCS, CDT and the drug code list checked as they were on the day of the visit, not as they are today. The code sets are loaded from your own regulator licence; a system that ships them to you has a licensing problem it is about to hand over.

  • The claim cycle as a state machine

    Submission before the deadline read in local time, remittance parsed back in, denials rolled onto the claim that carried them, resubmission inside the window and of the right type — and a count that stops you rather than warns you.

  • Healthcare VAT resolved per line

    Zero-rated treatment and standard-rated cosmetic work on the same invoice, correctly, with the input-recovery consequence of the zero-rated-versus-exempt distinction handled where it belongs rather than at the customer record.

  • Patient share and payer share as two documents that agree

    The patient pays at the desk and the payer pays on its own timetable. Splitting that at the point of invoicing is what makes the receivables ledger mean something afterwards.

  • The regulator as a record, not a constant

    DHA, DoH, MOHAP and DHCC differ in code lists, enumerations, denial codes and deadlines. A group with branches in two emirates needs that as configuration; anything hardcoded is a product with an expiry date on it.

  • Clinical records that cannot be quietly rewritten

    Twenty-five years of retention on the record and five on the access log means a correction has to be a new document that references the original and carries a reason — including when the write comes from an automation rather than a person.

Already built

CLINX

We did not build the capabilities above one clinic at a time. CLINX is our clinic suite on Odoo 19 — twenty-one modules, no Enterprise dependency anywhere in it — and it turns them from recorded into enforced: a code withdrawn before the visit date is refused at build time rather than declined by a payer six weeks later, a third resubmission simply does not send, a Dubai facility cannot file into Abu Dhabi, and the penalty the payer owes you for remitting late appears as a receivable instead of as a complaint.

See CLINX

Questions

What people in this industry ask us first

Can we not just buy a clinic app from the Odoo store?

For patients, appointments, notes and an invoice — yes, and several of them are competent. What none of them does is get you paid in this country: the claim cycle, the per-line VAT, the regulator differences between emirates and the denial workbench are the part that decides your margin, and they are the part those apps stop before.

We have branches in Dubai and Abu Dhabi.

Then the difference between the two regulators is your main technical problem, not a footnote. Different code lists, different activity-type enumerations, different denial codes, different endpoints. It has to be configuration held on the facility, and a facility licensed in one emirate should be refused when it tries to file into the other.

Where can the system be hosted?

Inside the UAE. Federal Law 2 of 2019 on the use of ICT in health fields prohibits storing or processing UAE health data outside the country without express regulator approval, which rules out the usual European and American cloud regions for the production database. Any vendor who has not raised it before quoting has not read it.

Does this replace our lab or radiology system?

No, and you should be suspicious of anyone who says it does. This is the operational and financial side of the clinic — the visit, the claim, the money, the record — talking to the specialist systems around it. One product that is also a LIS, a RIS and a QMS is a roadmap being described in the present tense.

Healthcare and clinics

Start with a diagnosis, not a demo

Two weeks. We walk your floor and your books, and you get the list of where money is leaving the business with a cost against each item. The list is yours whether or not you work with us afterwards.

Monday to Friday, 9:00 AM – 6:00 PM (GST)

Prefer we call you?

Leave your WhatsApp number and we will reach out.

We reply on WhatsApp first. Include your country code.

No newsletter, no reselling your number. We use it to reply to you — see our privacy policy.

WhatsApp us