See what our clients say about working with Bonami Software across 200+ projects for 18+ industries. EXPLORE NOW!
We don't just build software. We deliver results. EXPLORE NOW!
See why businesses choose Bonami Software for reliable, scalable solutions. EXPLORE NOW!
We turn ideas into scalable products with proven delivery across 18+ industries. EXPLORE NOW!
See what our clients say about working with Bonami Software across 200+ projects for 18+ industries. EXPLORE NOW!
We don't just build software. We deliver results. EXPLORE NOW!
See why businesses choose Bonami Software for reliable, scalable solutions. EXPLORE NOW!
We turn ideas into scalable products with proven delivery across 18+ industries. EXPLORE NOW!

NPHIES Integration for Saudi Healthcare

We integrate NPHIES into clinical software — HL7 FHIR R4, National ID and Iqama matching, claims and prior authorization, and the conformance package for production.

BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart
Turing
BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart
Turing

Book Your Free Demo

See it working on your own workflows. We reply within 24 hours.

  • Your idea is 100% protected by our NDA
BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart
Turing
BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart
Turing

Trusted by startups and global leaders

BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart
Turing
BrowserStack
Persistent
Yatra
Kellton
Jade Global
Optum
PokerBaazi
Walmart
Turing

What NPHIES Integration Covers

Operated by the Ministry of Health and built on HL7 FHIR R4, NPHIES is the national hub for electronic claims, prior authorization, and clinical data exchange. Connectivity follows the MoH's published NPHIES FHIR Implementation Guides.

Electronic Claims Submission

Providers submit FHIR-based claim resources and insurers return adjudication decisions through the same platform. Claims integration is essential for billing, with the Council of Cooperative Health Insurance (CCHI) overseeing payer participation.

Prior Authorization

NPHIES handles electronic prior authorization for procedures, medications, and services requiring insurer approval — replacing manual, paper-based workflows. Health information systems must implement these workflows to function in the Saudi insurance environment.

Patient Health Record Exchange

NPHIES exchanges clinical records between connected facilities, building toward a unified national health record — encounter summaries, ICD-10-CM diagnoses, medications, and LOINC lab results. The MoH defines specific FHIR profiles for each data category that connected systems must conform to.

National Patient Identifier

NPHIES uses Saudi national identifiers as the primary patient identifier — National ID for citizens, Iqama number for residents. Systems must capture and transmit the correct identifier, since matching failures cause data to be rejected or attributed to the wrong record.

Drug & Formulary Integration

NPHIES incorporates a national drug database and formulary with standardized medication codes for claims, prescriptions, and records. Systems must map local medication data to these codes, maintained by the Saudi Food and Drug Authority.

FHIR Conformance & Certification

NPHIES is built on HL7 FHIR R4 with Saudi-specific profiles and workflows defined in the MoH Implementation Guides. Before production access, systems undergo conformance testing validating the required profiles and transaction types across claims, prior authorization, and clinical data.

NPHIES Connectivity Is a Ministry of Health Requirement for Every Saudi Healthcare Facility

Hover to explore the regulations, technical standards, and onboarding steps that define NPHIES integration.

The NPHIES Integration Process

A structured path from Ministry of Health registration to live production — each step with the technical deliverables that determine whether a system passes NPHIES conformance.

STEP 1 — Ministry of Health Registration

Facilities and system vendors register through the Ministry of Health's digital health portal — submitting facility and system information, completing technical documentation, and signing the data sharing and participation agreements that govern NPHIES connectivity.

STEP 2 — Implementation Guide Review

The team reviews the NPHIES FHIR Implementation Guides published by the Ministry of Health — the authoritative specifications for each scenario: claims, prior authorization, clinical data exchange, and patient identity. They must be followed precisely.

STEP 3 — Development in the NPHIES Sandbox

Development and initial testing occur in the NPHIES sandbox, a controlled environment with synthetic data. Teams validate their FHIR implementations across each transaction type before moving to production testing.

Why NPHIES Integration Is Essential for the Saudi Market

NPHIES is the foundation of Saudi Arabia's digital health ecosystem — a universal requirement for any system deployed in the Kingdom. Click through to see what is at stake.

Book a NPHIES Integration Consultation
Universal
NPHIES is mandatory across all government and private facilities. Vendors without it cannot sell health information systems in the Kingdom.
Largest Market
Saudi Arabia has the largest healthcare market in the Middle East. NPHIES connectivity is the entry requirement for participating in it.
Vision 2030
NPHIES is the data infrastructure behind Vision 2030's digital health reform — the platform every Saudi-market product must align with.
Claims Gateway
All claims between Saudi providers and insurers flow through NPHIES. Integration is essential for reimbursement and insurer participation.
National Data
NPHIES connects analytics and population health tools to structured national health data — the Kingdom's unified health record.
FHIR Foundation
Built on HL7 FHIR R4, NPHIES requires Saudi-specific profiles and code systems — existing FHIR builds cannot be reused unchanged.

The NPHIES Requirements That Drive System Design and Conformance

Each NPHIES integration area maps to specific design decisions and onboarding deliverables — not configuration choices, but commitments made before a system can pass Ministry of Health conformance.

Claims

Electronic Claims Submission

Claims and adjudication for the private insurance sector flow through NPHIES as FHIR claim resources.

  • FHIR-based claim resources
  • Adjudication responses
  • CCHI sector participation
  • Billing operations support
  • Eligibility verification
  • Remittance handling
Prior Auth

Prior Authorization

Electronic approval workflows for procedures, medications, and services requiring insurer sign-off.

  • Electronic PA requests
  • Approval / denial responses
  • Procedure authorization
  • Medication authorization
  • Replaces paper workflows
  • Status tracking
Clinical Data

Patient Health Record Exchange

Clinical records exchanged between connected facilities toward a unified national health record.

  • Encounter summaries
  • ICD-10-CM diagnoses
  • Medication records
  • LOINC laboratory results
  • Procedural records
  • NPHIES FHIR profiles
Identity

National Patient Identifier

Records must attach to the correct patient using the appropriate Saudi national identifier.

  • National ID for citizens
  • Iqama for residents
  • Correct identifier transmission
  • Accurate patient matching
  • Rejection handling
  • Duplicate prevention
Formulary

Drug & Formulary Integration

Local medication databases must map to the national drug codes used across NPHIES.

  • National drug database
  • Standardized medication codes
  • SFDA-maintained formulary
  • Claims medication mapping
  • Prescription coding
  • Medication record codes
Onboarding

MoH Onboarding & Conformance

Registration, sandbox testing, and conformance certification precede production connectivity.

  • MoH portal registration
  • Data sharing agreements
  • Sandbox testing
  • Conformance certification
  • Production credentials
  • Ongoing monitoring

The NPHIES Integration Stack We Build With

FHIR servers, terminology services, claims and prior authorization engines, and KSA-resident cloud — selected to match the MoH NPHIES FHIR Implementation Guides and Saudi conformance requirements.

HL7 FHIR R4 H HL7 FHIR R4
HAPI FHIR H HAPI FHIR
NPHIES Implementation Guide N NPHIES Implementation Guide
HL7 v2 H HL7 v2
CDA / C-CDA C CDA / C-CDA
Healthcare Systems in Saudi Arabia Cannot Operate Without NPHIES Integration.

FHIR-conformant submission, claims and prior authorization, National ID and Iqama matching, and the Ministry of Health conformance package — we build NPHIES integration into the architecture and carry it through sandbox testing, certification, and go-live. Book a consultation and we'll scope it for your Saudi deployment.

Book a NPHIES Integration Consultation
AI Readiness

Award-Winning AI Development & Consulting

2025

100 Fastest Growth Companies

2025

Global Spring Winner

2025

Top App Development Company

2024

AWS Partner Network

2024

Google Cloud Partner

2025

Highly Rated on Trustpilot

2024

Verified Agency

2024

Top App Development Company

2024

ASSOCHAM Member

Frequently Asked Questions

[ 1 ]

Is NPHIES integration required for all healthcare facilities in Saudi Arabia?

Yes. The Saudi Ministry of Health mandates NPHIES connectivity for all licensed healthcare facilities — government and private. The rollout is phased, with large hospitals and insurers connecting first, and new facilities applying for an operating license must have a connectivity plan in place.

[ 2 ]

How does NPHIES relate to the Saudi health insurance sector?

NPHIES is the central electronic claims infrastructure for Saudi Arabia's mandatory health insurance system, regulated by the Council of Cooperative Health Insurance. All claims between providers and insurers flow through NPHIES, making integration essential for any provider seeking reimbursement or any insurer in the Saudi market.

[ 3 ]

What coding systems does NPHIES use for clinical data?

NPHIES uses internationally recognized coding standards adapted for Saudi Arabia: ICD-10-CM for diagnoses, LOINC for lab tests, Saudi FDA drug database codes for medications, and CPT plus Saudi-specific codes for procedures. Systems connecting to NPHIES must map their internal codes to these national standards.

Global presence

Two offices. One team.

Hi, I'm ARIA. Ask me anything about Bonami's AI agents.