Changing clinic software in Philippines

PhilHealth eClaims 3.0 is mandatory here, so every vendor will tell you they support it. That is the wrong question.

Who else you are looking at

In Philippines that is usually certified HITPs and local HIS vendors. All of them work with PhilHealth eClaims 3.0, 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: the Philippines.

The question that separates them

How many countries does this vendor operate in?

Almost every clinic system serving Philippines serves Philippines 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, NPHIES, Seha / NHIC 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

  1. Do you validate before submission, or only report rejections after? Reporting a rejection is bookkeeping. Preventing it is the product.
  2. Can I export everything, including history? A vendor who makes leaving hard is telling you what they expect the relationship to be.
  3. Where does my data live? Philippines requires records to be kept for 3 years. Ask where, and ask who else can read them.
  4. What happens when the rules change? Ask who tells you, and how quickly the software follows.
  5. What does it cost in year three? Ask about the renewal, not the first invoice.

We publish our prices for Philippines rather than quoting on request — see them.

We do the eClaims 3.0 migration. You do not pay until you are billing again

Older versions were switched off on 31 March 2026. A facility that missed it cannot submit at all.

Migration at no charge. Billing starts the month after your first successful claim.

Start

What we are not

We are not the cheapest, and in Philippines 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.