OpenMRS
Open-source medical record platform built in Java, running on Tomcat with a MySQL or MariaDB database. It is memory hungry rather than CPU hungry, so give it several gigabytes of RAM and fast disk for the database.
Run OpenMRS, KenyaEMR, Bahmni, OpenEMR or your own clinic system on a VPS with full root access. Your branches, labs and doctors on call reach the same records over HTTPS, and a power cut at the facility no longer takes the patient file offline.
Its 8 GB of RAM is what OpenMRS and KenyaEMR want for a busy clinic or small hospital, with room for MySQL buffers and a nightly backup job running alongside.
Order VPS V2Many Kenyan clinics still run their records system on a desktop in the back office. It works until the UPS gives up during a blackout, a technician reinstalls Windows, or a second branch opens in another town and needs the same patient history. A VPS keeps one copy of the database in a data centre, reachable from every consultation room, pharmacy counter and lab bench with a browser.
Hospital software is heavier than a typical website. OpenMRS and KenyaEMR run on Java and keep a large part of the concept dictionary in memory, so RAM matters more than raw disk. Bahmni adds a lab system and Odoo for billing and stock. Scanned referral letters, lab PDFs and imaging reports grow storage month after month, and the database must be backed up every night, not whenever someone remembers.
Patient information is sensitive personal data under the Data Protection Act 2019, so who can log in to the server, how backups are encrypted and where copies are kept are decisions the facility owns. With root access on a HostingKE VPS you control the firewall, the user accounts and the backup schedule, and our support team can advise on sizing and setup when you need a second opinion.
When the EMR lives on a local PC, every power cut or tripped breaker stops registration, triage and dispensing. A hosted server stays up while the facility runs on generator or paper, and staff carry on from phones on mobile data.
A patient seen at your main clinic walks into the satellite branch and the history is missing. One central database means allergies, prescriptions and lab results follow the patient across every site you run.
Clinic servers are often exposed with default passwords and a database port open to the internet. On your own VPS you close everything except HTTPS and SSH, give each clinician an individual account and keep an audit trail of access.
A copy of the database on a flash disk in a drawer is not a backup plan. Scheduled dumps, copied off the server and restored on a test machine each month, are what get a facility running again after a disk or ransomware incident.
These are the platforms Kenyan facilities most often ask us about. Each has its own requirements, so check the vendor documentation for the version you install.
Open-source medical record platform built in Java, running on Tomcat with a MySQL or MariaDB database. It is memory hungry rather than CPU hungry, so give it several gigabytes of RAM and fast disk for the database.
An OpenMRS distribution widely used in Kenyan public and faith-based facilities, especially for HIV care and national reporting. It inherits the Java and MySQL needs of OpenMRS and benefits from scheduled database backups and a reliable connection for data exchange.
A hospital system that combines OpenMRS for clinical records, OpenELIS for the laboratory and Odoo for billing and stock. Recent releases install with Docker, and the full stack needs far more memory than OpenMRS on its own.
A mature open-source practice management and EHR system written in PHP with a MySQL or MariaDB database. It suits outpatient clinics and specialists, and runs comfortably on a smaller server than the Java-based options.
Many Kenyan clinics run a system written in Laravel, Django or .NET by a local developer, covering registration, billing, pharmacy and insurance claims. A VPS gives your developer root access to install the exact runtime and database the code expects.
Move the slider to the number of staff who are logged in at the busiest hour of the day, usually the morning outpatient rush.
Treat this as a starting point: real load depends on the software, how many reports run during clinic hours and how many scanned files you store.
0 of 8 done. Tick them off as you go.
The Data Protection Act 2019 treats health information as sensitive personal data, and facilities that process it are generally expected to register with the Office of the Data Protection Commissioner. Ask your legal adviser what applies to you; the server setup should support those obligations.
Insurance and SHA claims are only as good as the clinical and billing data behind them. A central system that every department updates, instead of separate spreadsheets per branch, makes it easier to prepare claims and answer queries when they come back.
Hosting off the premises protects the data from local outages, but staff still need to reach it. Many clinics keep a fibre line plus a mobile data router as backup, so registration continues when one provider has a fault.
Plans from KES 2,000 a month, paid by M-Pesa or card.
Size your server