NPHIES Integration for Saudi Clinics: A Practical Guide
NPHIES is Saudi Arabia's national platform for exchanging health insurance information between healthcare providers and insurers. It runs eligibility checks, pre-authorization requests and claims through a shared messaging standard, so a clinic's software needs to send and receive those messages in the format NPHIES defines, typically through its insurer or a connected system.
Written by the Medoc HMS team · Last updated 14 October 2026 · Last reviewed 14 October 2026
NPHIES touches billing more than clinical care, which is exactly why it is confusing for a clinic owner: the people who need to understand it are often not the people who read technical implementation guides. This article explains what NPHIES actually does, in plain terms, and what it means for your clinic's software.
What is NPHIES?
NPHIES (National Platform for Health Insurance Exchange Services) is Saudi Arabia's national platform for exchanging health insurance information between healthcare providers (referred to as HCPs in the platform's documentation) and health insurance companies (HICs) or their third-party administrators. The platform's own implementation guide describes it validating and routing requests between a provider and the correct insurer.
The platform is commonly associated with Saudi Arabia's Council of Health Insurance (CHI) as the regulatory body for health insurance in the Kingdom. We were not able to independently verify CHI's current role from chi.gov.sa directly during research for this guide; confirm current governance and requirements with CHI before relying on this point.
Which clinics does NPHIES apply to?
NPHIES applies to the exchange between healthcare providers and health insurance companies for insured patients in Saudi Arabia. Its implementation guide is written for providers submitting eligibility checks, pre-authorization requests and claims to insurers through the platform, across institutional (hospital), professional (outpatient physician), pharmacy, dental and vision service categories.
Whether NPHIES participation is mandatory for a specific facility type, and on what timeline, is a regulatory question for CHI. This guide describes how the platform works for providers who use it; it does not state a universal compliance deadline, because that was not something this guide's research could confirm from a primary source.
What does NPHIES require from your clinical software?
NPHIES is built on HL7 FHIR R4 messaging. The platform's own implementation guide specifies that a provider's system exchanges structured FHIR resources, not free-text forms, for each workflow.
| Workflow | What it does | What software needs to handle |
|---|---|---|
| Eligibility | Real-time check of a patient's insurance coverage before a visit | Send a coverage eligibility request and read the response, including whether pre-authorization is required |
| Pre-authorization | Approval for a service before it is delivered, across institutional, professional, pharmacy, dental and vision categories | Build a FHIR message bundle with the patient, provider, insurer and service details, then handle the authorization reference returned in the response |
| Claims | Submission for payment after care is delivered, referencing any prior authorization | Submit claims that reference the correct prior-authorization number and encounter details, and process the adjudication response |
The implementation guide also sets rules for specific situations: a provider can request changes to an existing authorization by referencing it directly and preserving line-item details, a cancellation must happen before the authorization period expires, and a referral between providers is recorded using a transfer flag so the second provider can claim against the original approval.
How does a clinic connect or register?
Connecting to NPHIES is a software and insurer relationship, not a one-time form. A clinic's practice management or billing system needs to generate and consume the FHIR messages NPHIES expects for eligibility, pre-authorization and claims, and the clinic needs an active relationship with the insurers it bills through the platform.
NPHIES's own documentation notes that the platform may not always respond within a set time window, and advises providers not to rely solely on it for timely decisions, using insurer portals or help desks as a backup. That is a useful operational detail for a clinic's billing team to know before go-live.
For the registration and credentialing steps specific to your facility and insurers, confirm the current process directly with CHI and the insurers you work with, since this guide's research could not independently confirm a single standard registration path from a primary regulatory source.
What happens if a clinic is not compliant?
This guide does not state specific consequences for a clinic that has not integrated with NPHIES, because that was not confirmed from a primary source during research. In practice, a clinic that cannot submit eligibility checks, pre-authorizations or claims through NPHIES would need to manage those processes through insurer portals or manually, which is an operational cost worth weighing even before any formal requirement applies to your facility. Confirm your specific obligations with CHI.
How Medoc HMS supports NPHIES readiness
Medoc HMS supports HL7 FHIR as an interoperability standard, the same message format NPHIES uses for eligibility, pre-authorization and claims exchange. The platform records the patient, encounter, diagnosis and billing details a FHIR-based exchange depends on.
Medoc HMS does not connect your facility to NPHIES automatically. That connection is arranged through the Council of Health Insurance and your insurers, using the credentials and registration process they require. What Medoc HMS provides is the structured record layer that exchange depends on. Talk to us about your current billing and insurer workflow.
Frequently asked questions
Is Medoc HMS NPHIES certified?
This guide did not confirm a formal vendor-certification scheme for NPHIES from a primary source, so no such claim is made. Medoc HMS supports the HL7 FHIR standard NPHIES is built on, as a capability, not a certification.
What is the difference between eligibility, pre-authorization and claims on NPHIES?
Eligibility is a real-time check of a patient's coverage before a visit. Pre-authorization is approval for a specific service before it is delivered. Claims are submitted for payment after care, and reference the relevant pre-authorization where one was required.
Does NPHIES guarantee a real-time response?
No. NPHIES's own documentation says responses may be real-time, queued or partial, and advises providers to have a backup through insurer portals or help desks rather than relying solely on the platform for timely decisions.
Is NPHIES integration mandatory for my clinic?
This depends on your facility type and the Council of Health Insurance's current requirements. This guide does not state a universal mandate, because that was not confirmed from a primary source. Confirm directly with CHI.