Skip to content
Live12+ production solutions40+ clients deployeddirect + partner
Glossary · Healthcare & Clinical

What is NPHIES?

The Council of Health Insurance (CCHI) national platform for health information exchange in Saudi Arabia — the FHIR R4 spec for eligibility, pre-authorisation, claims and clinical-data exchange.

Also known as

National Platform for Health Information Exchange ServicesNPHIES Saudi ArabiaKSA NPHIESCCHI NPHIES
Definition

NPHIES — explained.

NPHIES (National Platform for Health Information Exchange Services) is the Saudi Arabia Council of Health Insurance (CCHI) national platform for health-data exchange between providers (hospitals, clinics, pharmacies), payers (insurance companies, government health programmes) and regulators. It operates on the FHIR R4 specification — meaning every transaction is a FHIR resource (Patient, Encounter, Coverage, EligibilityRequest, EligibilityResponse, Claim, ClaimResponse, ServiceRequest, MedicationRequest). NPHIES covers four primary transaction types: **eligibility** (real-time check of a patient's insurance coverage), **pre-authorisation** (request for advance approval of a procedure or medication), **claims submission + adjudication** (post-service billing), and **clinical-data exchange** (referrals, lab results, discharge summaries). For any clinic management or hospital information system selling into KSA in 2026, NPHIES integration is a hard procurement requirement — operators cannot transact with the regulated insurance market without it. Beyond KSA, similar national FHIR-based platforms exist or are being deployed across the GCC (UAE federal + emirate-level equivalents, Kuwait's national health information network, Oman's national e-health platform) — NPHIES is the model. Integration is typically a 4-8 week per-message-type engagement with CCHI certification testing.

Why it matters

Why operators care about nphies.

NPHIES integration is the gate between a KSA hospital information system pilot and a multi-site rollout. Without it, an operator cannot submit claims to the regulated insurance market — meaning revenue cycle breaks. CCHI procurement explicitly references vendor-NPHIES-certification as a shortlisting criterion. Beyond KSA, the FHIR R4 pattern transfers directly to UAE + Kuwait + Oman national-platform integrations.

What to look for in a vendor

Buyer's checklist

  • CCHI-certified NPHIES integration in production
  • All four transaction types supported (eligibility, pre-auth, claims, clinical exchange)
  • FHIR R4 native (not v3 retrofit)
  • Real-time eligibility check at the appointment-booking step
  • Claim denial reason capture + reconciliation back to the encounter
  • Audit log of every NPHIES transaction for CCHI inspection
Solutions where nphies applies

Zeour solutions that operate on this layer.

MediCare Clinic

medicare · clinic · management · system

Zeour MediCare — the multilingual on-premise clinic and EMR management system for small-to-mid healthcare practices. Covers patients (records, allergies, conditions, medications, body diagrams), appointments + visits with SOAP notes, prescriptions with drug-interaction checks, lab orders + samples + results, billing + payments + invoicing, inventory, expenses, referrals, medical certificates, refill requests, patient communications, telemedicine (WebRTC), an AI clinical assistant (OpenAI-powered with 7 modes), a patient self-service portal, and a full role-based access model across Admin, Doctor, Reception, and Lab Tech roles. Engineered multilingual — (with full RTL) as the production baseline, extensible to any locale — and runs locally on a single server.

See the solution
Industries where this matters

Verticals where nphies is operationally critical.

Related terms

Adjacent definitions to read next.

FHIR

Healthcare & Clinical

The REST + JSON healthcare data standard from HL7 — replaces the pipe-delimited HL7 v2 for new national programmes and patient-facing apps.

HL7

Healthcare & Clinical

The pipe-delimited messaging standard that lab analysers, radiology systems, EMRs, and admission systems use to exchange clinical data — still the lingua franca of hospital integration.

Electronic Medical Record

Healthcare & Clinical

The longitudinal digital record of a patient — demographics, encounters, problems, allergies, medications, vitals, results, attachments — owned by the clinic or hospital.

Clinic Management System

Healthcare & Clinical

The single platform that runs a clinic or hospital — EMR, appointments, billing, lab, radiology, pharmacy, patient portal, telemedicine and (in 2026) a bounded AI clinical assistant.

E-Prescription

Healthcare & Clinical

The fully-digital workflow from clinician prescription writing → drug-interaction check → national prescription network submission → pharmacy dispensing → patient pickup — with audit at every step.

PDPL

Compliance & Data

Personal Data Protection Law — the data-protection regime in Saudi Arabia (and equivalents in the UAE and several Gulf states).

Sovereign Deployment

Sovereign Deployment

Software that runs entirely inside the operator's perimeter — their hardware, their network, their backups, their keys — with no third-party dependency for continued operation.

AI Clinical Assistant

Healthcare & Clinical

A side-pane AI in the EMR that summarises history, drafts notes from voice, suggests differential diagnoses, and flags drug interactions.

Want to discuss nphies for your operation?

Talk to a Zeour engineer.

A 30-minute scoping call to walk your operational profile against where nphies actually sits in your stack, then a fixed-fee Discovery price by the end of the call.