On-premise or cloud for hospital data: a practical guide for Egypt, Saudi Arabia and beyond

Where patient data lives is a legal question, an operational question and a budget question. This guide compares a server inside the hospital with a dedicated cloud server, and explains how Nabd is installed.

This article is general information, not legal advice. Data-protection rules and their executive regulations change; confirm your obligations with your data protection officer (DPO) and legal counsel.

First, what “cloud” means here

Many hospital software products are sold as shared online services: every hospital’s data sits in the vendor’s database, and the hospital pays a subscription. Nabd is not sold that way. Each hospital gets its own installation, on a server inside the hospital (on-premise) or on a dedicated cloud server reserved for that hospital. The choice in this article is therefore between two kinds of server that both belong to the hospital’s installation, not between owning the system and renting someone else’s.

What the law says about health data

Egypt: Personal Data Protection Law 151/2020

Under Egypt’s Personal Data Protection Law (151 of 2020) and its executive regulations, health data is sensitive personal data. Processing it generally requires the person’s explicit written consent (a guardian’s for children), and transferring personal data outside Egypt needs a licence from the Personal Data Protection Center. The practical rule we follow in our deployment guidance is simple: host the production database, backups and file storage inside Egypt unless a cross-border licence covers the destination. The law also sets breach notification deadlines, such as notifying the regulator within 72 hours, which Nabd’s breach register tracks with live clocks.

Saudi Arabia: Personal Data Protection Law

Saudi Arabia’s Personal Data Protection Law, supervised by the Saudi Data and Artificial Intelligence Authority (SDAIA), treats health data as sensitive and restricts transferring personal data outside the Kingdom to the cases and conditions set by its regulations. Healthcare regulators add their own requirements. For a Saudi hospital, keeping the database and backups in the Kingdom is the simplest position to defend.

For German readers: GDPR (DSGVO) principles

Under the GDPR, health data is a special category of personal data. The principles that matter most for hosting are data minimisation, purpose limitation, integrity and confidentiality (appropriate technical and organisational security measures), storage limitation and accountability. When a third party hosts or operates the system, a data processing agreement is required. An installation on the hospital’s own server keeps the data inside the hospital and reduces the number of processors involved. Nabd’s architecture is designed around these principles; it is not certified against any German or European scheme.

Side-by-side comparison

Server inside the hospital vs dedicated cloud server
Server inside the hospitalDedicated cloud server
ControlFull physical and logical control by the hospital’s ITLogical control by the hospital; physical control by the data centre
Data residencyData stays in the buildingDepends on the data centre’s country; choose one inside your country
Internet dependencyWards and clinics keep working during an internet outageAn internet outage at the hospital stops access unless there is a redundant link
BackupsHospital runs encrypted backups and keeps an off-site copyProvider snapshots plus the hospital’s own encrypted database backups
Cost modelUp-front hardware, power, cooling and replacement cycleMonthly server rent; no hardware to buy
IT staff neededOn-site staff for hardware, operating system and backupsFewer on-site tasks; still needs someone accountable for backups and access

For most hospitals with a stable on-site IT team and an unreliable internet connection, the server inside the hospital is the safer choice. For a group of clinics without a server room, a dedicated cloud server in the same country is often more practical. Both are supported, and the clinical software is identical.

How Nabd is delivered to a hospital

Whichever server you choose, the installation is the same. The hospital receives a ready program, never our source code: four Docker images pulled from our private registry with a per-hospital, read-only access token, or loaded from an offline archive for hospitals without internet. No TypeScript source, no source maps and no tests are shipped. A typical Docker Compose installation for a 100–200 bed hospital needs 4 vCPU, 8 GB of RAM and a 100 GB SSD.

A licence check that never stops a hospital

Software licences are a real concern for on-premise systems: what happens if the vendor’s server is down? Nabd’s licence is a signed document, and the daily check-in sends exactly five technical values: the licence ID, the installation ID, a non-reversible fingerprint, the application version and the number of active staff users. No patient data, no names and no usage logs leave the hospital.

Security that does not depend on where the server is

These controls are described on our features page and in more detail for each market on the Egypt and Saudi Arabia pages.

Questions to ask any vendor

  1. Where exactly will our database and backups be stored, and in which country?
  2. Can we run the system on our own server, and does it keep working when the internet is down?
  3. What does the licence check send, and what happens to our access if your company or server is unavailable?
  4. Can we export all of our data at any time, in an open format, without your involvement?
  5. Who at your company can access our data for support, and how is that access recorded?
  6. How often are restores tested, and who signs off the result?

A vendor who answers these clearly is easier to work with for the next ten years. If you are moving from an existing system, our article on keeping patient history safe during migration covers the other half of the decision, and you can request a demo to see the licence page, the data export and the audit trail on fictional data.

See Nabd on sample data

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