In Saudi Arabia, choosing a hospital information system (HIS) is no longer just about clinical features. Insurance claims for mandatory health cover run through a national platform, NPHIES, and personal data is governed by the Personal Data Protection Law (PDPL), which the Saudi Data and AI Authority (SDAIA) enforces. A system that cannot exchange standards-based claims with NPHIES, or that cannot demonstrate strong data protection, will be a liability from day one.
This guide is for hospital and clinic owners, CIOs, and procurement teams in the Kingdom who are comparing an HIS or EMR in Saudi Arabia. It explains what NPHIES expects, what the PDPL means for software, the adjacent national services worth asking about, and how to test vendors. It is general information, not legal advice, so confirm current requirements with the relevant authorities.
NPHIES: The National Claims Gateway
NPHIES, the National Platform for Health Information Exchange Services, is a central, standards-based gateway that connects healthcare providers and payers. It is based on HL7 FHIR (version 4.0.1): providers submit FHIR claim resources and insurers return adjudication decisions through the platform. It works with the mandatory health insurance framework. Health insurance was long supervised by the Council of Health Insurance (formerly the Council of Cooperative Health Insurance, CCHI); since 4 March 2024, supervision of health insurance has sat with the Insurance Authority, so check current rules and circulars with the Insurance Authority rather than relying on older CCHI guidance. Practitioner sources report that connectivity is expected for licensed public and private facilities, and that new facilities need a connectivity plan as part of licensing. The technical rules are published in the NPHIES implementation guide.
For a software buyer, this means the system has to do more than print an invoice. It should:
- Check patient coverage and eligibility with the payer through the platform.
- Request and track prior authorisations for services that need them.
- Build and submit claims as valid FHIR resources, and process the payer's response.
- Handle rejections and resubmissions with clear reasons for billing staff.
- Reconcile payments against claims and report outstanding amounts by payer.
PDPL and SDAIA
The Personal Data Protection Law is Saudi Arabia's first comprehensive data protection law. Since 14 September 2023, SDAIA has acted as the competent authority responsible for it. Health data receives special treatment, and organisations are expected to be accountable for how they collect, use, store, and transfer personal data. Vendors and processors are also part of that accountability.
When you assess a system, look for:
- Role-based access control and a complete audit trail.
- Consent and purpose management where consent is the basis for processing.
- Support for data subject rights, such as access and correction.
- Clear data location, hosting, and cross-border transfer controls, since the law sets conditions for transferring personal data outside the Kingdom.
- Breach detection, evidence, and a defined response process.
- Written data processing terms with the vendor.
Other National Services to Ask About
Practice guides for the Saudi market commonly mention several adjacent services that a hospital system may need to work with: national identity verification, electronic prescribing, and tax e-invoicing requirements. Requirements and versions change, so ask each vendor which of these they support in production today, rather than assuming.
What a Saudi HIS Must Do
| Need | What to check |
|---|---|
| NPHIES connectivity | Eligibility, prior authorisation, claims, and responses as FHIR resources, with a live production reference |
| Payer management | Per-payer contracts, tariffs, coverage rules, and claim status tracking |
| PDPL controls | Access control, audit, consent, data subject rights, and data location clarity |
| Clinical breadth | OPD, inpatient, emergency, lab, radiology, pharmacy, and specialty workflows |
| Arabic and English | Bilingual interface, patient-facing documents, and reports |
| Interoperability | FHIR and HL7 interfaces for imaging, lab equipment, and other systems |
Where Quecorex Fits
Quecorex provides a full hospital platform: registration, OPD, inpatient, emergency, EMR, lab, radiology, pharmacy, nursing, and billing. In billing, the module includes payer management, claims management, pre-authorisation, and insurance exclusions, and the platform includes a FHIR client, FHIR outbound sync, and HL7 interface management, which are the technical foundations for a FHIR-based exchange. Security and compliance tools cover audit, compliance management, and data privacy.
Two points to be clear about. First, a FHIR foundation is not the same as a certified NPHIES connection, so ask us what is live in production for the Kingdom and get it in writing. Second, the interface is primarily English today. Arabic localisation is planned for later, so if a fully Arabic interface is a hard requirement, tell us. Pricing is modular and adjusted for your country, which you can estimate on our pricing page.
Questions to Ask Any Vendor
- Which NPHIES functions are live in production, and at which hospitals?
- How do you handle eligibility, prior authorisation, claims, and rejections end to end?
- Where is data hosted and backed up, and how do you address PDPL transfer rules?
- Is the interface fully Arabic and English, including printed documents?
- Who updates the integration when the platform specification changes?
- What is the full three-year cost, including integration and support?
For the technical background, read our HL7 and FHIR interoperability guide, and for regional context see smart hospital solutions in the UAE.
A Realistic Implementation Plan for Saudi Hospitals
- Weeks 1 to 3: scope and contract. List your payers and the NPHIES functions you need first (eligibility, prior authorisation, claims). Agree in writing which are live, which are in testing, and the dates.
- Weeks 4 to 8: configure and test. Configure payers, tariffs, and roles, and validate your FHIR claim messages in a test environment before any live submission. Check Arabic screens and printed documents with real users.
- Weeks 9 to 10: pilot. Go live in one department, monitor rejections daily, and confirm that data location and backup match your PDPL position.
- After go-live: govern. Assign an owner for platform specification changes, review access logs regularly, and report claim performance by payer each month.
Common Mistakes to Avoid
- Accepting a FHIR capability as proof of a working NPHIES connection.
- Discovering late that key screens or documents are not truly bilingual.
- Not asking where data is hosted and backed up until after signing.
- Underestimating the effort of rejection handling for claims that fail validation.
- Leaving specification updates without an owner or a price.
Final Thoughts
The Saudi market rewards systems that speak standards: FHIR for claims, and strong data protection under the PDPL. Insist on evidence of live NPHIES use, test the workflow with your own payers, and get every integration and language promise in writing. Book a demo and we will walk through an eligibility check and claim with you.
