How to choose a hospital information system in Egypt or Saudi Arabia: a practical checklist

Every vendor shows a polished dashboard. What separates a system that fits from one that stalls after go-live is in the details: insurance, e-invoicing, Arabic, data residency and the exit door. Use these questions in every demo, including ours.

Choosing a hospital information system (HIS) is one of the few decisions a hospital lives with for a decade. It touches every department, every invoice and every patient file. Yet many selections are made on a two-hour presentation and a price. This checklist is written for owners, medical directors, finance managers and IT heads in Egypt and Saudi Arabia. It is the list we would use ourselves, and we answer it honestly for Nabd at the end of each point.

1. Arabic that works, not Arabic that was translated

Arabic support is more than translated menus. Ask to see a full right-to-left screen with mixed content: an Arabic patient name, a national ID, a dosage, an English drug name. Check that search finds a patient whatever way reception types the hamza or the taa marbuta, and that printed invoices and reports are bilingual. Ask whether every user can switch language, because doctors and accountants often prefer different ones.

Nabd: the interface is right-to-left Arabic by default with English for every user, names are stored in both languages, search is Arabic-normalised, and invoices print in Arabic and English.

2. One financial pipeline from order to accounts

The most expensive problem in hospital software is re-keying between departments and finance. Ask the vendor to order a lab test in the clinic and then show, without leaving the system, where it was priced, how the patient and insurer shares were split, which invoice line it became and which journal entry it posted. If the answer involves an export to an accounting package, expect monthly reconciliation work.

Nabd: every service becomes a charge priced from the payer’s price list, split between patient and payer when it is recorded, and invoices, payments, stock and doctor fees post balanced journal entries automatically.

3. Insurance and TPA work as it really happens

In Egypt most approvals still go through TPA portals, e-mail, WhatsApp and phone, often with an approval code and a validity of 7 or 14 days. In Saudi Arabia, insurance exchange runs through NPHIES, which requires vendor certification. Ask how the system records a pre-authorisation that arrived by WhatsApp, how it tracks approved versus used amounts, how line-level rejections are coded and resubmitted, and what is live today versus promised. Our article on insurance approvals and claim rejections goes deeper.

Nabd: document channels used today are recorded end to end, with rejection codes, resubmissions and payer receivables aging. Electronic exchange is integration-ready: a generic FHIR R4 payer connector built in NPHIES style and connectors for TPAs are connected per payer after an agreement. The FHIR connector is not certified against NPHIES; certification would be required before live use in Saudi Arabia.

4. Local e-invoicing

Egyptian hospitals must issue e-receipts and e-invoices to the Egyptian Tax Authority (ETA); Saudi providers must comply with ZATCA e-invoicing. Ask exactly what the system produces, whether it signs and submits or only prepares documents, and what the hospital must provide itself (registration, devices, signing certificate).

Nabd: it produces ETA e-receipt and e-invoice documents with a submission queue; the live connection is configured with each hospital’s own ETA credentials. ZATCA e-invoicing for Saudi Arabia is planned as part of a Saudi country pack and is not available yet. See e-invoicing for Egyptian hospitals.

5. Where the data lives

Health data is sensitive personal data under Egypt’s Personal Data Protection Law (151/2020) and under Saudi Arabia’s Personal Data Protection Law, and both restrict transfers abroad. Ask where the database, backups and attachments are stored, who can reach them, and whether any feature sends patient data to a foreign service. Decide between a server inside the hospital and a dedicated server in-country; the trade-offs are in on-premise vs cloud for hospital data.

Nabd: it is installed on the hospital’s own server or a dedicated server, not shared software-as-a-service. The optional AI assistant is off by default and receives de-identified data only. Nabd is built to support PDPL 151/2020 with a consent registry, data-subject requests and a breach register; it is not certified by any authority.

6. Security, permissions and audit

Ask how roles are defined, whether a user can grant permissions they do not have, how sessions are revoked when someone leaves, and whether the system can tell you who opened a given patient’s file. Accreditation surveys and complaints both depend on that last answer.

Nabd: 83 permissions assigned through editable roles, no granting of permissions one does not hold, sessions revocable at once, every change recorded with the fields that changed, and a patient access report.

7. Migration in, and the exit door out

Two questions are asked too rarely. How will our current data come in, and how would it go out if we ever leave? Ask for a test import of your own exported file during selection. Ask what happens if the licence expires or the vendor’s server is unreachable: can the hospital still open patient files?

Nabd: patients, items, payers, opening stock and opening balances are imported from Excel or CSV after a full check (see moving patient records safely). An administrator can export all data at any time. If the licence lapses, the system becomes read-only after a grace period, never deleting or hiding data, and emergency care, medication administration and critical-result acknowledgement keep working. An unreachable licence server never restricts anything.

8. Operational boards and daily speed

Ask to see the bed board, the emergency board, the clinic queue and the pharmacy queue on two screens at once, and change something on one of them. If the other screen needs a reload, staff will keep phoning each other. Nabd’s boards update in real time.

9. Implementation, training and support

Software is half of the project. Ask who configures price lists and payers, who trains each role, how long the vendor stays on site after go-live and what support looks like a year later. Ask to meet the people who will do the work, not only the sales team. Flexcode Systems implements Nabd in four stages: discovery and configuration, data migration, role-based training, and go-live with continued support.

The comparison table

Questions for every vendor, with Nabd’s answers today
CriterionQuestion to askWhat Nabd does today
ArabicShow a full RTL screen with mixed content and a bilingual printArabic-first RTL, English per user, bilingual invoices
FinanceFollow one lab test to the journal entryAutomatic pricing, patient/payer split and GL posting
InsuranceRecord a WhatsApp approval and a line rejectionDocument channels live; electronic connectors integration-ready per payer
NPHIES (KSA)Is the software certified?FHIR R4 connector integration-ready, not certified
E-invoicingWhat is produced, signed and submitted?ETA documents and queue (Egypt); ZATCA planned
Data residencyWhere are database and backups stored?Hospital server or dedicated server; no shared SaaS
AuditWho opened this patient’s file?Field-level audit trail and patient access report
ExitWhat if the licence expires?Read-only fail-safe, full data export at any time

A ten-point checklist for your demo

  1. Bring one of your own exported patient files and ask for a test import.
  2. Order a test in the clinic and follow it to the lab, the invoice and the accounts.
  3. Record an insurance approval exactly as your TPA sends it today.
  4. Ask what is live, what is integration-ready and what is planned, in writing.
  5. Ask where data is stored and whether anything leaves the country.
  6. Open the audit trail for one patient.
  7. Change a bed status and watch the board on another screen.
  8. Print a bilingual invoice and a lab report, and check every Arabic name and number on them.
  9. Ask what happens to your data if the licence expires.
  10. Ask any vendor for the hospitals you can call, and call them yourself.

The demo of Nabd runs on fictional patients and figures. We prefer that you test with your own exported files on a separate installation rather than judging from a presentation.

If you are comparing systems for a hospital in Egypt or Saudi Arabia, read our pages for Egypt and Saudi Arabia, or request a demo and bring this list with you.

See Nabd on sample data

A live demo focused on the departments that matter to your hospital.