NPHIES (National Platform for Health Information Exchange Services) is now mandatory for every healthcare provider in Saudi Arabia — hospitals, clinics, pharmacies, labs. If you're still working with manual claims or a system disconnected from your EHR/ERP, you're losing a significant share of claim value to rejections and delays. This guide shows how Odoo + NPHIES integration solves that.
What Exactly is NPHIES?
NPHIES is a platform run by the Saudi Health Council (CCHI), unifying communication between:
- Providers — hospitals, clinics, pharmacies, labs
- Payers — health insurers (Bupa, Tawuniya, MedGulf, etc.)
- Regulators — CCHI, MoH, CHI
Before NPHIES, every provider dealt with each insurer through a different system. Now everything is FHIR R4 — one standard, one XML/JSON, one endpoint.
The 4 Core NPHIES Transactions
1. Eligibility Check
Before providing a service, verify the patient is covered. The eligibility check returns in seconds:
- Is the policy active?
- What's the remaining coverage limit?
- Is the requested service covered?
- What's the co-payment percentage?
With Odoo Healthcare + Softloomer NPHIES module, we scan the patient card, eligibility check runs automatically before appointment booking.
2. Pre-authorization
For major procedures (operations, MRI, expensive treatments), insurer authorization is needed beforehand. NPHIES closes this loop in 1-3 days instead of 7-14.
3. Claim Submission
After service, the claim goes to NPHIES with:
- ICD-10 diagnosis codes
- CPT/HCPCS procedure codes
- Lab + radiology results
- Pharmacy items (SFDA drug codes)
- Provider attachments (PDFs)
In Odoo, all of this is generated from the encounter automatically — no more re-entering data.
4. Payment Reconciliation
When the payer pays, NPHIES sends remittance advice with all approved/rejected claims and reasons. Odoo takes it and auto-reconciles with accounting.
The 5 Most Common Integration Challenges
1. ICD-9 to ICD-10 Mapping
Many hospitals still use ICD-9. NPHIES requires ICD-10. A precise mapping table is essential.
2. SFDA Drug Codes
Every drug must have its SFDA registration number. Every drug item in Odoo must carry its SFDA registration code, so the product master needs a clean SFDA mapping before go-live.
3. Lab + Radiology Integration
HL7 messages from LIS/RIS must convert to NPHIES FHIR. Odoo Healthcare with Softloomer NPHIES module handles the conversion.
4. Multi-insurer Support
A patient may have primary + secondary insurance. NPHIES supports coordination of benefits — Odoo must apply this logic correctly.
5. CSID + Certificates
NPHIES uses digital signatures with CCHI certificates. Certs must be renewed annually.
ROI: Before vs After NPHIES Integration
| Metric | Before (Manual) | After Odoo + NPHIES |
|---|---|---|
| Claim submission time | 15-30 minutes | 10 seconds |
| Rejection rate | 35% | 8% |
| Days Sales Outstanding | 90 days | 30 days |
| Eligibility errors | 22% | <2% |
| Cost per claim | 45 SAR | 5 SAR |
Figures are illustrative ranges commonly reported by providers; actual results depend on claim volume and data quality.
Code Example: Eligibility Request in Odoo
def check_eligibility(self, patient_id, payer_id, service_date):
payload = self._build_fhir_eligibility(
patient=patient_id,
payer=payer_id,
date=service_date,
)
response = self._nphies_post('/CoverageEligibilityRequest', payload)
if response.get('outcome') == 'complete':
return self._parse_eligibility(response)
return {'eligible': False, 'reason': response.get('error')}NPHIES Compliance Checklist
- ☐ CCHI license + provider registration
- ☐ Digital certificate from NPHIES portal
- ☐ FHIR R4 endpoint integration
- ☐ ICD-10 + CPT mapping table
- ☐ SFDA drug codes database
- ☐ HL7-to-FHIR converter for LIS/RIS
- ☐ Multi-insurer coordination logic
- ☐ Remittance advice auto-reconciliation
- ☐ Staff training on new workflow
Try a Live Odoo + NPHIES Demo
Reading about integration is one thing; seeing the messages is another. Softloomer runs a live Odoo demo with patients, practitioners, insurance policies and payers. You can run an eligibility check and inspect the complete FHIR R4 bundle that was sent and the response that came back. A built-in simulator answers in the same shape as NPHIES, so you can test the full workflow before your facility finishes onboarding. Request access to the demo.
NPHIES Onboarding: What Your Facility Must Prepare
The software side can be ready quickly, but production access depends on steps only the facility can complete:
- Licensed facility with its official data ready.
- Onboarding with the Council of Health Insurance as a provider.
- Digital certificates for the mutual-TLS connection to the NPHIES gateway.
- Conformance testing in the sandbox before production is opened.
- Reference data: payer, practitioner and service codes.
We wrote a dedicated NPHIES go-live checklist covering each step.
Frequently Asked Questions
Is NPHIES integration mandatory in Saudi Arabia?
For providers serving insured patients, NPHIES is the national channel for exchanging eligibility, pre-authorization, claims and payment information with insurers, so connecting to it is part of operating with health insurance in the Kingdom.
Does Odoo support NPHIES out of the box?
No. Standard Odoo has no NPHIES connector. You need an integration module that builds FHIR R4 messages with the official NPHIES profiles, validates patient identity data and handles the secure connection — which is what we build on top of Odoo.
What is FHIR R4?
HL7 FHIR Release 4 is the international standard NPHIES uses for health data exchange. Every request and response is a structured FHIR bundle, which is why one integration works with every insurer on the platform.
How long does an Odoo NPHIES integration take?
The software work is usually measured in weeks. The overall timeline is typically driven by CCHI onboarding, certificates and conformance testing, which run in parallel with the system setup.
Can we test before our facility is approved?
Yes. Our integration ships with a simulator mode that answers like NPHIES, so staff can be trained and workflows tested; switching to sandbox or production is a configuration change, not a rewrite.
Which NPHIES transactions should we start with?
Start with eligibility checks at registration — they prevent most downstream rejections — then add pre-authorization for procedures that need it, and finally claims and payment reconciliation.
Next Step
Have a hospital or clinic in Saudi Arabia and need full NPHIES integration on Odoo? Book a free consultation with the Softloomer team, or visit our healthcare page for the full offering. To compare Odoo with SAP/Oracle: comparison guide.