NPHIES for providers: eligibility, pre-authorization and claims in Saudi Arabia

Short answer: NPHIES (National Platform for Health and Insurance Exchange Services) is Saudi Arabia's central gateway for health insurance transactions between providers and insurers. Clinics use it for eligibility checks, pre-authorizations, claims and payment reconciliation, all in HL7 FHIR. Providers connect directly or through an intermediary such as Waseel. Helix supports NPHIES via Waseel.

For a Saudi clinic, NPHIES is where insured revenue lives. Every insured visit touches it at least twice: once to confirm coverage or approval, and once to claim. This guide explains the transactions, the data each one needs and the operational habits that keep claims moving.

This article is general guidance, not legal advice. Regulators update their standards, circulars and deadlines often, so always confirm the current requirement with the relevant authority or a qualified advisor before you act on it.

Who runs NPHIES

NPHIES was developed with the Council of Health Insurance (CHI, formerly CCHI), which regulates private health insurance in Saudi Arabia, together with national health bodies. It was officially launched by the Minister of Health in October 2023, after a phased rollout that began earlier. Its insurance side connects healthcare providers, insurers and third-party administrators through one validated, standards-based exchange. A clinic's system never talks to an insurer's system directly: everything goes through NPHIES.

The transactions you will use

NPHIES uses HL7 FHIR R4. The official Financial Services Implementation Guide, published on the NPHIES portal, defines each message. Your team does not need to read it, but your vendor does, and it should keep up with new versions.

What a clean NPHIES claim depends on

• Correct policy and class. In Saudi Arabia, the member's policy class drives deductibles, co-pay and approval limits. Register the patient against the right policy and class, not just the insurer name.
• Payer identifiers. Each insurer, and each TPA where one administers the plan, has its own NPHIES identifier. A missing one causes 'unknown payer' rejections.
• The pre-authorization reference on any claim that needed approval.
• Coded diagnoses from the chart, with the principal diagnosis marked.
• Price-list codes agreed with the payer for each service, alongside your internal service codes.
• Episode grouping. Services belonging to the same episode of care should carry the same episode identifier so the insurer sees them together.

Where Saudi claims usually go wrong

• Eligibility not checked, or checked against the wrong member ID.
• A service delivered before its pre-authorization came back, or outside the approved validity window.
• Diagnosis and procedure codes that do not support each other.
• Medications placed on the wrong claim type. Many payers expect pharmacy items on a separate pharmacy claim.
• Supporting documents missing when the insurer asks for them through a communication request.
• Resubmissions sent as brand-new claims instead of corrections to the original.

Pre-authorization deserves its own process. Our guide to prior authorization in the UAE and Saudi Arabia covers how to track approvals so none expire unused.

Before your first transaction: the setup list

• Your provider identifiers: your NPHIES provider ID, plus the intermediary's provider ID and API credentials if you connect through one such as Waseel.
• Separate test and live credentials. Test transactions against the staging environment first; staging credentials do not work in production.
• Payer master data: each insurer's NPHIES identifier, and the TPA's identifier where a TPA administers the plan.
• Policies and classes set up in your system with their deductibles, co-pay percentages and approval limits.
• Price lists agreed with each payer, mapped to your internal service codes.
• Clinician and department data complete, because each claim names a treating practitioner and specialty.

Daily habits that keep NPHIES claims moving

• Run eligibility for every insured patient before the visit, not after.
• Keep a live list of open pre-authorizations with their validity dates, and book services inside that window.
• Close visits with coded diagnoses the same day, so claims are not held up waiting for the chart.
• Answer insurer communication requests quickly, with the supporting documents they ask for.
• Reconcile payments against claims as soon as payment notices arrive, and chase short payments by claim.

Direct connection vs an intermediary

Providers reach NPHIES either with their own direct integration or through a licensed intermediary. Waseel is one of the best-known in the Kingdom: its Waseel Connect product connects healthcare providers to NPHIES for claims, pre-authorizations and messaging. Going through an intermediary means your clinic system talks to the intermediary's API with your own provider credentials, and the intermediary handles the NPHIES connection. When a vendor says 'NPHIES integrated', ask which route it uses. Both are legitimate. What matters is that the vendor is honest about it.

NPHIES and ZATCA: two rails, one set of numbers

NPHIES handles insurance. ZATCA handles tax invoices. Insured services appear on both, so the amounts on the claim and on the e-invoice must agree. A system that builds both from the same invoice avoids reconciliation problems at month-end. Read our ZATCA Phase 2 guide for clinics for the tax side.

How Helix handles NPHIES

Helix connects to NPHIES via Waseel, configured per branch with the provider's own Waseel and NPHIES identifiers, and separate staging and production environments. From the patient file, staff can run eligibility checks, look up CCHI beneficiary details at registration and send pre-authorizations, which Helix refreshes in the background until the insurer answers. Claims are built from the period's insurance invoices and grouped per consultation episode, with payer price-list codes and your internal codes on each item, and medications split onto their own pharmacy claim. A claims register shows payer statuses and supports correction resubmissions. Everything posts to the same ledger in billing and accounting. The full list is on our integrations page.