Nabd in Saudi Arabia

Hospital information system for Saudi Arabia

Nabd’s clinical, operational and financial modules work in Arabic and English today. A Saudi go-live also needs the KSA country pack — NPHIES certification, ZATCA e-invoicing, riyal and Saudi VAT, Hijri dates — which is on the roadmap. This page says plainly what exists and what does not yet.

Key facts

Interface language
Arabic (right-to-left) and English, per user
Currency
EGP today; Saudi riyal (SAR) and Saudi VAT are planned in the KSA country pack
Calendar
Gregorian today; Hijri dates are planned
Deployment
On the hospital’s own server or a dedicated server inside the Kingdom; no shared SaaS
Data residency
Data stays on the hospital’s server; nothing about patients is sent to us
NPHIES
FHIR R4 connector built and tested; certification and Saudi profiles still required

Saudi regulations and integrations

NPHIES requires every vendor’s software to be certified before it exchanges live transactions. Nabd is not certified today; the table below shows exactly where each item stands.

  • NPHIES (eligibility, pre-authorisation, claims)

    Integration-ready

    A generic HL7 FHIR R4 payer connector with NPHIES-style message bundles (CoverageEligibilityRequest, Claim, ClaimResponse, PaymentReconciliation) is built and tested against a test payer. It is not certified: the NPHIES profiles, code systems and the mandatory vendor certification are still required, so it cannot be used live before certification.

  • ZATCA e-invoicing (FATOORA)

    Planned

    Part of the KSA country pack on the roadmap. Not available today.

  • Saudi riyal and Saudi VAT

    Planned

    Amounts in the product are in Egyptian pounds today. Riyal amounts and Saudi VAT rules come with the KSA country pack.

  • Hijri dates

    Planned

    Planned in the KSA country pack; dates are Gregorian today.

  • Arabic and English interface

    Built in

    A complete right-to-left Arabic interface with English per user, bilingual patient names and bilingual printed documents.

  • Read-only FHIR R4 API

    Built in

    Patients, encounters, observations, conditions, allergies, medications, orders, reports and coverages can be read in FHIR R4 by authorised systems, with every read audited.

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.

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

  1. A demo on fictional data, focused on the departments you run.
  2. Discovery: departments, payers, price lists, roles and the country-pack items you need first.
  3. A written scope and plan that separates what exists today from what will be built.
  4. 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.

Frequently asked questions

Is Nabd NPHIES-certified?

No. Nabd has a FHIR R4 payer connector in the NPHIES message style, built and tested against a test payer, but the NPHIES profiles and the mandatory vendor certification are still required. It cannot exchange live NPHIES transactions before certification.

Does Nabd support ZATCA e-invoicing?

Not yet. ZATCA e-invoicing is planned as part of the KSA country pack.

Can invoices be in Saudi riyals?

Amounts are in Egyptian pounds today. Riyal amounts and Saudi VAT are planned in the KSA country pack; we cover the timing in the discovery session.

Where is the data hosted?

On the hospital’s own server or a dedicated server inside the Kingdom. Nabd is not a shared SaaS, and no patient data is sent to Flexcode Systems.

Which parts can we see in a demo today?

All clinical and operational modules, billing, inventory and accounting, in Arabic and English, on fictional data. Saudi-specific items appear in the demo only as roadmap items.

Discuss a Saudi deployment

See the modules on fictional data and get a clear picture of what the KSA country pack involves.