
NPHIES connects Saudi providers and payers through one national gateway, and is the foundation for a unified health record. It validates what you send against national standards. Here is how to make sure your clinical data passes, and keeps its value along the way.
Saudi Arabia is building one of the most ambitious health data platforms in the region. NPHIES, the National Platform for Health and Insurance Exchange Services, brings eligibility checks, prior authorisations and claims between providers and payers onto a single national gateway, and is intended to support a unified health record for the people it serves.1, 2
For providers, NPHIES is now part of daily operations. Every transaction is checked against national standards before it reaches the payer. When the data behind it is incomplete, inconsistent or trapped in documents, approvals slow down, claims come back, and teams spend time on rework rather than patients.
This article is for private hospitals, clinic groups and laboratories in Saudi Arabia, and for the EMR, revenue cycle and insurance teams who work alongside them. It sets out seven ways to make clinical data ready for NPHIES.
Figure 1. Where NPHIES sits. It checks and routes; the quality of what it carries is set by each provider.
The NPHIES implementation guide describes the platform as "a centralized validating standards-based information exchange gateway" connecting providers and payers. It validates and routes transactions, but does not adjudicate them; in its own words, it acts as a "smart courier". The Council of Health Insurance (CHI) leads financial exchanges, the Ministry of Health leads clinical exchanges, and NPHIES keeps copies of exchanges to support dispute resolution and regulatory processes.1
That has a practical meaning for providers. NPHIES will reject what does not meet its standards, but it will not fix it. The structure, coding and completeness of every transaction are decided inside the provider's own systems, long before anything is sent. And because exchanges are retained, what was sent becomes part of the record that regulators and payers can review later.
The financial implementation guide, built on the FHIR R4 standard (Fast Healthcare Interoperability Resources, Release 4), covers eligibility checking, prior and advanced authorisation, claim submission, batch claims, payment reconciliation and notification, and information submission and requests.1
Each of these depends on structured data. Eligibility needs accurate patient identity and coverage details. Prior authorisation needs the diagnosis, the planned service and the clinical justification, expressed in codes the payer can evaluate. When registration details are incomplete or the justification sits in a scanned letter, the request stalls, and care can be delayed while staff chase the gap.
The guide expects coded data to use "internationally recognized or Saudi nationally recognized coding standards".1 For procedures and billable services in private insurance, that means the Saudi Billing System (SBS).
The SBS exists because the old approach did not work. A 2025 study describing its development explains that insurers had been using inconsistent in-house codes, which limited transparency and value-based financing. The team re-coded 36,299 patient records from 80 providers and three insurers against an Australian procedure classification. Three-quarters mapped to an existing code; the rest needed partial, approximate or new codes. In total, 1,774 codes were added, giving the SBS 7,947 codes.3
Figure 2. From many in-house code sets to one. Figures from Reka et al., BMC Health Services Research, 2025.
For providers, the lesson is that any system still holding old internal codes, free-text service names or outdated mappings is carrying risk into every claim. The same applies to diagnoses, laboratory tests and medicines. Mapping each to the current national standard, with clinical review where the meaning is uncertain, is the foundation for clean transactions.
Claims through NPHIES rely on a mandatory minimum data set covering diagnoses, procedures, medications and claim values.2 Payers increasingly compare what is billed with what is documented, and NPHIES retains a copy of every exchange.
Figure 3. Each line of a claim should trace back to the clinical record. The dashed line, supporting evidence, is where the gap most often appears.
The safest claims are generated from structured clinical data rather than typed separately by billing staff. When the diagnosis, the procedure and the medicines are coded once, at the point of care, the claim inherits them and the two cannot drift apart.
Prior authorisations, claims and payer information requests often need supporting evidence: laboratory results, imaging reports, referral letters or discharge summaries. NPHIES includes information submission and request transactions for exactly this purpose.1
In many facilities, that evidence lives in PDFs from reference laboratories, scans of outside reports, or documents attached to the EMR rather than recorded in it. Staff then search for the right file, attach it, and hope it answers the payer's question. Structuring the most common evidence, starting with laboratory results, makes it searchable, codable and quick to send, and lets the clinical justification be expressed as data rather than a document.
NPHIES is intended to support a unified medical record for everyone it serves. Today, as a 2025 editorial in the Saudi Journal of Health Systems Research notes, integrating EMRs across medical cities, health clusters and hospitals remains a challenge, linked to incomplete records, missing medications and duplicate visits when patients move between facilities.2
Health information exchanges across the Gulf have shown what a unified record depends on. Automated patient matching relies on national identifiers, full names and dates of birth, and missing or incorrect registration data breaks it.4 Providers who clean up duplicate records, standardise registration, and structure the clinical history they already hold will be ready to contribute to and benefit from a national record as it grows.
Saudi Arabia's Personal Data Protection Law (PDPL) came into force in September 2023 and became fully enforceable in September 2024. Health data is classed as sensitive personal data.5
Figure 4. Four PDPL points that shape how health data can be prepared and processed. Summarised from the Chambers Data Protection & Privacy 2026 guide.
Personal data may be transferred outside the Kingdom only where the receiving country or entity provides an appropriate level of protection, with safeguards and a risk assessment required for sensitive data. Accessing data remotely counts as a transfer. Breaches likely to cause harm must be reported to the regulator within 72 hours, and administrative fines can reach SAR 5 million, doubled for repeat violations. Health-sector regulations may add further restrictions.5
This matters most when outside tools or partners are used to clean, code or extract data. Many process data abroad by default, or rely on reviewers working from other countries. Before any partner touches patient data, confirm where processing happens, who can access it and from where, whether identifiers are needed at all, and how long anything is kept. Please confirm your own obligations with a legal adviser.
NPHIES is Saudi Arabia's National Platform for Health and Insurance Exchange Services. It is a centralised, standards-based gateway that validates and routes transactions such as eligibility checks, prior authorisations and claims between providers and payers, and supports clinical data exchange.
No. NPHIES validates transactions against its standards and routes them, but it does not adjudicate claims. Payers make coverage decisions.
The NPHIES financial implementation guide is based on FHIR R4 (version 4.0.1), and expects coded data to use internationally or nationally recognised coding standards.
The Saudi Billing System (SBS) is the national code set for billable services in private health insurance. It was developed to replace insurers' inconsistent in-house codes and contains 7,947 codes.
Under the PDPL, health data is sensitive personal data and may only be transferred abroad where appropriate protection exists, with safeguards and a risk assessment. Remote access from abroad counts as a transfer, and health-sector rules may add restrictions. Confirm your position with a legal adviser.
NPHIES rewards providers whose data is structured, coded and complete before it leaves the building. There are two ways we can support you.
This article is for general information and is not legal or regulatory advice. Always refer to current CHI, Ministry of Health and SDAIA requirements.
Suhina Singh is a physician, the Founder and CEO of Jonda Health, and a health data strategist working at the intersection of artificial intelligence and clinical information systems.