Guide

NPHIES for clinics: what it is and how a claim flows from booking to payment

NPHIES is Saudi Arabia's national platform through which healthcare providers, insurers and third-party administrators exchange insurance transactions electronically: eligibility checks, prior authorizations, claims and payment notices. A clinic's claim passes five stops: eligibility at booking or arrival, prior authorization when needed, the claim after the service, the insurer's decision, and the payment notice.

Last reviewed:

In this guide

This guide walks through each stop, what a clinic needs before it starts, and where the clinic system fits. To see how this runs inside the system, see revenue cycle and NPHIES integration.

What is NPHIES and who runs it?

According to the NPHIES "About" page, the platform is a digital gateway that organises the exchange of health transactions between parties in the sector. It was delivered under the leadership of the Council of Health Insurance (CHI), with the National Health Information Center, and with the supervision and support of the Ministry of Health. Its target users are healthcare providers, health insurers and claims management companies (TPAs).

CHI's own "who we are" page lists among its duties accrediting and qualifying healthcare providers to serve insured beneficiaries, and overseeing the operation of NPHIES.

A note for readers: since 4 March 2024, health insurance responsibilities have moved to the Insurance Authority, including health insurance complaints and enquiries. Some rules and documents may therefore sit on the Authority's site rather than CHI's.

Who has to use NPHIES? A facility that treats privately insured patients exchanges its transactions with insurers through the platform. The platform's provisions and activation notices are published in the NPHIES digital library.

How does a claim move from booking to payment?

The services below come from the NPHIES services page, in the order they happen in a clinic day.

1. Eligibility (at booking or arrival)

Reception checks that the patient's policy is valid and covers services at this specific facility, and can request the policy details. This step prevents the most expensive surprise: a patient treated, then found to have an expired policy or a clinic outside their network.

2. Prior authorization (before the service, when needed)

Some services need the insurer's approval first. The clinic sends the request, the insurer or TPA reviews it and decides, and the clinic informs the patient when needed. There is also a reverse service: the insurer can push an authorization to the provider without a request, for specific cases.

What needs approval depends on the policy, the insurer and the contract. Do not build a general rule from one insurer's behaviour.

3. Communication (supporting documents)

If the insurer needs more information to complete an authorization or a claim, both sides exchange documents through the communication service: radiology reports, lab results, prescriptions and notes.

4. Claim (after the service)

The clinic submits the claim on the patient's behalf. The insurer or TPA reviews it and decides, and the decision comes back to the clinic. A status inquiry service lets the clinic check an authorization or claim before the final response.

5. Payment

When an insurer issues a payment covering one or more claims, it notifies the clinic, and the clinic sends back an acknowledgement of receipt. This is where reconciliation starts: which claims were paid in full, which partly, and which not at all.

If a claim is rejected or partly paid, read NPHIES claim rejection reasons.

What does a clinic need before it starts?

Licence and accreditation. A facility licence from the competent health authority, CHI accreditation to serve insured beneficiaries, then contracts with insurers.

Registration on the platform. The NPHIES registration page has separate routes for healthcare providers, insurers and health technology companies.

Standard coding. This is the point small clinics most often neglect. According to the Saudi Billing System (SBS) V3.0 Coding Standards, the Saudi Billing System includes:

  • ICD-10-AM for diagnoses. Saudi Arabia mandated the 10th edition of ICD-10-AM/ACHI/ACS from 1 January 2020.
  • SBS procedure codes, a Saudi modification of ACHI 10th edition that adds chapters for laboratory, emergency, rehabilitation, transport and service codes. Each code keeps ACHI's 7 digits plus a 2-digit extension.
  • SBS Coding Standards, used with the Australian Coding Standards (ACS).
  • SFDA GTIN codes for medicines and GMDN for medical devices and consumables.

The version currently published on CHI's clinical classification page is SBS V3, with its electronic code list and V2-to-V3 maps. The page does not state an effective date for V3, so ask your vendor and your insurers which version they accept. The NPHIES guidebook also lists ICD-10-AM 10th edition for diagnoses and SBS for procedures and outpatient services, and HL7 FHIR as the exchange standard.

A conformant system. The SBS V3 information systems implementation guidelines require systems to validate each code, its effective dates, and its fit with the patient's age and sex. They also state that vendors must pass a conformance test for each SBS version, and that systems not conformant by the version's implementation date will not be able to access NPHIES. Ask your vendor directly.

How long does each step take?

NPHIES publishes quarterly performance reports in its digital library. For example, the summary of the Q1 2025 report states that average eligibility response time was 2.6 seconds.

Response times for prior authorization, the deadline to submit a claim after the service, and payment terms are set by the policy, the regulations and the clinic's contract with each insurer. Write these terms into each insurer's file and track them weekly.

Where does the clinic system fit?

The simple principle: everything sent to NPHIES should come from the clinic's daily work, not be re-keyed into another portal.

  • Reception: eligibility from the booking screen, with the response saved on the visit.
  • Doctor: diagnosis in ICD-10-AM and procedure in SBS during the consultation, not days later.
  • Insurance desk: prior authorization from the same visit, and a block on services whose approval has not arrived.
  • Claims: the claim built from the visit, documents attached, status tracked.
  • Finance: payment notices matched to claims, then the insurer invoice issued through e-invoicing. See ZATCA e-invoicing for clinics.

How Nixpend helps

In Nixpend, insurance eligibility, prior approvals and claims are exchanged with NPHIES from inside the platform, from the same visit that reception and the doctor recorded. The system combines clinic management (HIS) and finance (ERP), so a claim reaches ZATCA e-invoicing (Fatoora) and the accounts without re-entry. The interface is in Arabic and English and runs in the browser. Isnad, our revenue cycle management product on NPHIES, is in early access. See revenue cycle and NPHIES integration or book a demo.

FAQ

What is NPHIES in one line?

The national platform for exchanging health insurance transactions between providers, insurers and TPAs, delivered under the leadership of CHI.

Which codes does a claim need?

ICD-10-AM (10th edition) for diagnoses and Saudi Billing System (SBS) codes for procedures and services, plus GTIN for medicines and GMDN for devices.

Does every service need prior authorization?

No. It depends on the patient's policy, the insurer and the contract.

Can any clinic software connect to NPHIES?

Systems must pass a conformance test for each SBS version, and non-conformant systems lose access to NPHIES from the implementation date. Ask the vendor.

Where are the official documents?

In the NPHIES digital library on nphies.sa and on CHI's clinical classification page.

See Nixpend on a day like yours

A 30-minute walk through the platform, on a scenario close to your day: from the booking to the claim and the journal entry.