What works in a Saudi hospital today
The core of Nabd is not country-specific: one medical record per patient, clinics and queues, emergency with five-level triage, inpatient wards with the bed board and nursing station, operating theatres with the WHO checklist, laboratory with critical results, radiology, blood bank, pharmacy with first-expiry-first-out stock, and double-entry accounting. All of it runs in Arabic and English. See the hospital information system and the laboratory system.
NPHIES: integration-ready, not certified
NPHIES is the national health insurance exchange and is based on HL7 FHIR R4. Nabd already contains a FHIR R4 payer connector that builds eligibility checks, pre-authorisations, claims and remittance reviews in the NPHIES message style, and it records every exchange. What it does not have yet is the Saudi profile set, the national code systems and the vendor certification that NPHIES makes mandatory. Until those are done, insurance in a Saudi deployment would run through manual channels, which is not practical for most insured volumes.
Certification also needs the hospital’s side: the CHI / NPHIES provider licence, vendor onboarding and test credentials. We plan this work together with the first Saudi hospital and do not claim it is done before it is.
The KSA country pack
Our roadmap groups the Saudi requirements into one country pack: ZATCA e-invoicing, NPHIES profiles and certification, riyal amounts with Saudi VAT, and Hijri dates. None of these is available today. In a discovery session we map your departments, payers and reporting needs against the pack and agree the scope and timeline in writing.
- ZATCA e-invoicing (FATOORA) — planned.
- NPHIES profiles, code systems and certification — planned on top of the existing FHIR R4 connector.
- Saudi riyal and Saudi VAT — planned; amounts are EGP today.
- Hijri dates — planned.
Data stays in the Kingdom
Saudi Arabia’s Personal Data Protection Law, supervised by SDAIA, treats health data as sensitive. Nabd is installed for one hospital on its own server or on a dedicated server in the Kingdom, so patient data never sits on a shared platform. The licence check sends five technical values only, and an expired licence never locks records. More in on-premise or cloud for hospital data.
How a Saudi project would start
- A demo on fictional data, focused on the departments you run.
- Discovery: departments, payers, price lists, roles and the country-pack items you need first.
- A written scope and plan that separates what exists today from what will be built.
- Installation on your server, data migration from Excel or CSV, training per role and go-live support.
Our checklist for choosing an HIS lists the questions worth asking any vendor, including us.
This page is not legal advice. Regulatory status as of November 2026; confirm your obligations with your counsel, CHI, ZATCA and SDAIA.