Digital Health

NPHIES Readiness: What Saudi Arabia's National e-Claims Platform Means for Private Providers

What NPHIES means for private providers in Saudi Arabia: eligibility, pre-authorisation and claims on one platform, SBS coding and practical readiness steps.

By Dr. Neeraj Puranik· 12 August 2026· 7 min read

NPHIES, the National Platform for Health Information Exchange Services, has changed how private providers in Saudi Arabia work with insurers. Governed by the Council of Health Insurance (CHI), it is the national platform through which licensed providers, insurers and TPAs exchange eligibility checks, pre-authorisation requests, claims and payment information. For a private clinic or hospital, NPHIES readiness is no longer an IT project. It is a condition of getting paid.

I have spent 18+ years in revenue cycle management and insurance networking, and the pattern I see with NPHIES is consistent. Providers that treat it as a software integration struggle. Providers that treat it as a change to their entire revenue cycle, from front desk to finance, adapt far better.

What NPHIES actually does

At its core, NPHIES standardises the electronic transactions between providers and payers. The main ones that affect a provider's daily operations are:

  • Eligibility: confirming a patient's coverage and benefits before service.
  • Pre-authorisation: requesting and receiving approval from the insurer before delivering services that require it.
  • Claims: submitting claims electronically and receiving adjudication responses.
  • Payment information: receiving notices that reconcile what was paid against what was billed.

Because these transactions sit on one platform and follow shared standards, inconsistencies that once went unnoticed are now visible. An eligibility check, an authorisation and a claim for the same encounter can be compared directly.

Why it matters for private providers

NPHIES sits inside a wider transformation. Under Vision 2030 and the Health Sector Transformation Program, the Ministry of Health (MOH) is moving towards the role of regulator, government care delivery is being organised into health clusters under the Health Holding Company, and private sector participation is expanding. Insurance and standardised digital exchange are central to how that system is financed and monitored.

For private providers, this has three practical consequences:

  1. Transparency increases. Payers and the regulator see standardised data on what you bill and how often.
  2. Data quality becomes a revenue issue. Errors in codes, member details or authorisation references lead directly to rejections.
  3. Process discipline becomes a competitive advantage. Providers that submit clean, well-supported transactions are easier for payers to work with.

Coding: the Saudi Billing System

NPHIES claims use Saudi coding standards. CHI's Saudi Billing System (SBS) and its coding standards are based on the Australian classifications, ICD-10-AM for diagnoses and ACHI for procedures, with Saudi-specific additions. This matters if your coding team trained in the UAE or elsewhere on ICD-10-CM and CPT. The logic, code structure and coding standards are different, and assuming they transfer directly is a common source of rejections.

CHI has updated SBS over time, so confirm that your system, your code lists and your coders' training reflect the current version.

A practical NPHIES readiness checklist

Technology

  • Your hospital or clinic management system is integrated with NPHIES through a supported solution and handles eligibility, pre-authorisation and claims, not only claim submission.
  • Master data, including your service catalogue, price lists and clinician records, is mapped to the codes and formats the platform expects.
  • You have a process for monitoring failed transactions and technical errors every day.

People

  • Front-desk staff run eligibility on the platform for every insured visit and know what to do when coverage is unclear.
  • Clinicians understand which services require pre-authorisation and what documentation the request needs.
  • Coders are trained in SBS, ICD-10-AM and ACHI, with regular audits.
  • Your finance team can reconcile payment information against claims by payer.

Process

  • The codes in the pre-authorisation request match the codes on the final claim.
  • Contract terms and tariffs for each payer are loaded and checked after every renewal.
  • Rejections are classified by root cause and fed back to the department responsible.
  • Leadership reviews a small set of measures monthly: clean-claim rate, rejection reasons, authorisation turnaround and days in receivables.

Common problems I see

  • Integration without process change. The system connects, but staff keep old habits, so the same errors now reach the payer faster.
  • Coding carried over from another market. Coders who are strong in CPT still need proper SBS training.
  • Authorisations treated as a formality. Requests go out with minimal clinical justification and come back rejected or partially approved.
  • No owner for rejected transactions. Technical errors and rejections pile up in a queue nobody checks.
  • Vendor dependency. The facility cannot tell whether a problem sits in its own data, its software or the payer response.

What good looks like

A well-prepared provider can answer a few questions immediately. What share of claims pass first time? What are the top three rejection reasons this month, and which department owns each? How long do pre-authorisations take by payer? Which contracts are due for renegotiation? If those answers take a week to assemble, the organisation is not yet ready, whatever the integration status says.

Readiness is also not a one-time milestone. Payers update their rules, CHI updates standards, and your own service lines change. Build a quarterly review into your calendar: check a sample of claims end to end, confirm that code lists and contracts are current, and retrain staff where the rejection data shows new gaps.

How Tulazai Health helps Saudi providers

We work with private clinics, medical centres and hospitals on the operational side of NPHIES: readiness assessments, workflow redesign for eligibility and pre-authorisation, coding and documentation improvement, contract loading, rejection analysis and management reporting. We coordinate with your software vendor, but our focus is the process and the people, because that is where most revenue is won or lost.

If you are a private provider in Saudi Arabia preparing for NPHIES, or already connected but losing revenue to rejections, book a discovery call with Tulazai Health. We will assess where you stand and give you a clear, prioritised readiness plan.

Complimentary 30-minute call

Talk it through with Dr. Neeraj.

Tell us where your facility is today and where you want it to be. You leave the call with a clear next step.