Changing clinic software in Saudi Arabia
NPHIES is mandatory here, so every vendor will tell you they support it. That is the wrong question.
Who else you are looking at
In Saudi Arabia that is usually Bonami, Cirrus, Insta HMS. All of them work with NPHIES, and several have been doing it longer than we have.
We are not going to tell you what they cannot do — we do not have current data on their products and neither does anyone writing a comparison table about ours. What is a matter of public record is where they sell: Saudi Arabia.
The question that separates them
How many countries does this vendor operate in?
Almost every clinic system serving Saudi Arabia serves Saudi Arabia and nothing else. That is fine if you are one clinic in one country, and it is a real problem the moment you are not — because the group next door running clinics in two markets is running two vendors, two contracts, two support relationships, and reconciling the numbers by hand at month end.
Drapto runs eClaimLink / DHPO, Seha / NHIC, PhilHealth eClaims 3.0 and others on one system, with the same login and one set of numbers.
What actually differs between markets
Not the clinical work — a consultation is a consultation. What differs is what gets a claim refused, and it differs completely:
- United Arab Emirates — eClaimLink / DHPO. Pre-authorisation must be submitted within ONE HOUR of the physician order.
- Saudi Arabia — NPHIES. Structural and clinical validation at submission — an ICD-10-AM code inconsistent with the stated DRG is rejected before a human reads it.
- Qatar — Seha / NHIC. Mandatory health insurance for expatriates since 2022; claims route through the national scheme rather than bilaterally.
- Philippines — PhilHealth eClaims 3.0. Older versions were switched OFF on 31 March 2026. A facility that missed it cannot bill at all.
- Indonesia — SATUSEHAT. ICD-10 WHO, not ICD-10-CM. Strict ISO 8601 with timezone. Over 1,200 hospitals flagged non-compliant.
- Brazil — TISS. Glosa codes are published by ANS, so rejections are diagnosable — but almost nobody validates before sending.
A system built for one of those does not become a system for another by adding a currency.
Five things to ask any vendor, including us
- Do you validate before submission, or only report rejections after? Reporting a rejection is bookkeeping. Preventing it is the product.
- Can I export everything, including history? A vendor who makes leaving hard is telling you what they expect the relationship to be.
- Where does my data live? Saudi Arabia requires records to be kept for 3 years. Ask where, and ask who else can read them.
- What happens when the rules change? Ask who tells you, and how quickly the software follows.
- What does it cost in year three? Ask about the renewal, not the first invoice.
We publish our prices for Saudi Arabia rather than quoting on request — see them.
We will read your last three months of rejections before you decide
The market loses 30-40% of claim value to rejections. Most clinics cannot say which codes are costing them the most.
Free rejection analysis, no commitment. You keep the report either way.
What we are not
We are not the cheapest, and in Saudi Arabia we are not the incumbent. If you have a system that submits cleanly and you can see why claims fail, changing it is a cost with no return — keep it.
The case for moving is when you cannot answer why money is being refused, or when you are running one vendor per country and reconciling by hand.
Read the mechanism. Now check your own numbers.
Bring twenty settled claims, advices only, patient details redacted. We name the clause behind each reduction and you keep the findings.