We have spent a lot of hours sitting inside Nigerian hospitals, and the same picture keeps turning up. The patient file is paper. The pharmacy invoice travels between departments on a slip. Lab results land in a WhatsApp group. And the HMO you billed two months ago still has not paid, because half the claim was filled in by hand.
If you run a private hospital here, none of that is news to you. This guide is for you anyway: the medical director, the administrator, the owner trying to work out which hospital management system to put on top of all that. It is not a sales page. It is roughly what we would say to a friend who called and asked where to start.
What a hospital management system actually is
Strip away the acronyms and it is simple enough. A hospital management system, or HMS, is the software that runs the day-to-day of a hospital. Registration, appointments, consultations, prescriptions, lab orders and results, pharmacy stock, billing, HMO claims, ward and theatre management, and a record of who touched what.
You will also hear HMIS and EHR thrown around. Internationally, an EHR is the clinical record a doctor edits in front of a patient, and an HMS is the wider operation around it. In Nigeria nobody is precious about that line. Most private hospitals want one system that does the lot, so when we say hospital management system, we mean the whole thing.
Why a system built for Nigeria, not just any system
Plenty of HMS products exist. Epic, Cerner and Allscripts at the top end; OpenMRS and Bahmni if you go open source. We have looked hard at all of them. None was built with a Nigerian hospital in mind, and three things keep tripping them up.
First, the rules here are ours, not theirs. You bill HMOs through NHIA channels, with NHIA code structures. You hold the NIN as part of a patient's identity, and before long you will be expected to check it against NIMC. You answer to NDPR for the personal data you keep. A system written for Ohio or Surrey has never met any of that.
Second, the network. In the middle of Lagos and Abuja the internet mostly holds. Step outside that and it does not. Software that assumes a steady connection will freeze the moment a fibre line is cut or the diesel runs out. What you actually need is a system that keeps working when the link drops and quietly catches up when it returns.
Third, the money. A twenty-bed hospital is not about to sign a six-figure dollar contract and fly in consultants. The price has to make sense in naira, and it has to grow gently as you go from five beds to fifty.
The features that actually matter
Take this list into any vendor conversation, ours included, and hold them to it.
1. Separate records per hospital, with the NIN locked down
Your patients and another hospital's patients should never sit in the same database. And the NIN has to be encrypted where it is stored. Plain-text NIN might pass today. It will not pass the auditor who knocks in 2027.
2. Access that matches the job
The receptionist sees who the patient is, not their lab results. The doctor sees the clinical notes, not the pharmacy stock sheet. The pharmacist sees the prescriptions sent to them, and nothing from HR. Get this wrong and an NDPR audit becomes a very bad afternoon.
3. A log of every change
Who edited the record, what they changed, when, and from which device. Not so the IT person can snoop, but so that when a dispute lands on your desk, you have an answer. NDPR effectively requires it anyway.
4. Billing that speaks HMO
Cash and card are the easy part. The real test is the HMO flow: capturing the authorisation code, building the claim while the encounter is happening, and exporting it in a shape NHIA will accept. If your staff have to rekey everything to raise a claim, that is six to twelve weeks of cash sitting in someone else's inbox. Every single time.
5. Pharmacy stock that counts itself
Dispense a drug and the count should fall on its own. Expiry tracked first-to-expire-first-out, so nobody hands out something three months gone. Reorder alerts before you run dry. And figures the accountant can actually use at month end.
6. Lab results in real fields, not free text
Technicians type into proper fields, not a notes box. The doctor sees the result inside the consultation, with the technician's name and the time stamped on it. That is the difference between a record you can defend and a shrug of "we cannot find it."
7. Scheduling that knows how a clinic really runs
Foreign scheduling assumes nine to five and tidy fifteen-minute slots. Your hospital runs shifts, public holidays, a consultant who only shows up on Tuesdays, OPD rotations, and theatre clashes. The calendar has to handle all of that, or the front desk will just go back to the paper diary.
8. A patient portal
In 2026 this is table stakes. People want to check their records, book a slot, and pick up a lab result without trekking in for every small thing. Done well, it quietly lifts a good chunk of work off your front desk within a few months.
9. It has to survive a bad connection
We said this already, and it is still the thing people skip. If the software sulks the moment the network drops, it is wrong for where you are. Walk away.
10. Built for a phone first
Most Nigerians get online on a phone. Your doctors check the list on theirs, your pharmacists work off a tablet. Anything that needs a desktop browser to function properly is already a step behind.
11. Backups you would actually bet on
Encrypted, daily, copied somewhere off-site, with a restore you have tested at least once. Not "it is on the server in the back room." Hard drives die. What matters is the morning after.
12. Data you can take with you
The records belong to the patient, and the export belongs to you. Any system worth signing lets you pull everything out in a standard format whenever you ask. Build that in early and it is cheap. Bolt it on after a regulator asks and it is not.
What about the big international names?
For most private hospitals here, the honest answer is no. Here is why.
Epic, Cerner and Allscripts are built for hospital groups with thousands of beds and an IT department to match. The contracts open in the high tens of thousands of dollars a year and the rollouts run for months. Even with the budget, you would still be paying consultants to bend them around NHIA and NDPR.
OpenMRS and Bahmni are free to licence, which sounds wonderful until you price the full-time engineers it takes to run them. They are brilliant in teaching hospitals and large NGOs. For a private hospital that just wants the thing to work on Monday morning, they are a heavy lift.
Then there are the international cloud products aimed at the US, UK and India. They make a perfectly good clinical record. But their billing has never met an HMO and their patient identity has never met a NIN, so you end up running a second system for claims, which is exactly the mess you set out to fix.
The fit for most Nigerian hospitals in 2026 is a local product, built around local rules, local networks and local prices. A few of these exist. We are one of them. Whoever you go with, hold them to the checklist above.
What does it cost in Nigeria?
Pricing usually works per bed or per active clinician, with modules stacked on top. Rough numbers for 2026:
A small hospital of five to fifteen beds should look at somewhere around ₦200,000 to ₦600,000 a month for a full cloud system, hosting and support and the standard modules included. Setup is normally part of the deal. A mid-sized hospital, fifteen to fifty beds, tends to land between ₦600,000 and ₦2.5 million a month, depending on which modules you switch on and how many sites you run. Chains across several locations get a custom figure, and the per-bed rate drops as you scale.
Those numbers should already cover hosting, support, free upgrades, daily backups and onboarding. Watch the vendor who waves a low headline price and then bills you separately for backup, for training, for each module and each extra user. Add it all up and you are paying double.
And if the quote arrives in dollars, ask why. A Nigerian system should bill in naira. Dollar pricing usually means someone is reselling a foreign product and hoping you will not notice the mismatch.
Should you move off what you have now?
If you are running on paper, a spreadsheet, or some blend of WhatsApp and Excel, then yes, and soon. You are already paying for it in slow HMO claims, lab results that vanish, files nobody can search, an audit trail that does not exist, and the patients who quietly move to the better-organised hospital down the road. Three focused months of migration usually pays for itself inside a year.
If you have an older system that is not cloud-hosted, not built for a phone, or has never heard of NHIA, also yes, but give it six to twelve months because you have history to carry across. A decent vendor helps you move the data. Put that on the table before you sign, not after.
And if you already run a cloud system that bills HMOs, encrypts the NIN, keeps an audit log, and your staff are not cursing it every morning, then leave it alone. New is not the same as better.
Questions to take into every demo
When you sit down with a vendor, ours included, bring this list and watch how they react.
- Show me an HMO claim built from start to finish, on an NHIA flow we actually use.
- Show me where the NIN is encrypted: at rest, in transit, and on the screen.
- Pull the WiFi. Now show me what my staff can still do.
- Give me three customers I can call, and let me call them.
- Open the audit log for one patient and prove every field is captured.
- If we leave you, what does our export contain, and in what format?
- Who runs onboarding and training, how long does it take, and is it included?
- What does year two cost, not just year one?
- Where does our patient data physically live, and why there?
- It is 2am and the system is down. Walk me through exactly what happens next.
A vendor who is relaxed about all ten is probably one you can trust. One who gets twitchy on any of them is telling you something. Listen to it.
So, where does that leave you?
The Nigerian hospital software market in 2026 is younger and scrappier than the global picture makes it look, and that is good news. There is real room to put in software that helps the work instead of fighting it, costs a number that makes sense, and was built for the rules and the realities you actually live with.
If you want to see what that looks like in practice, NaijaHealth runs a three-month free trial with onboarding included. Talk to us and we will run the twelve-point checklist against your actual workflow, and tell you straight if we are not the right fit.
Frequently asked questions
What is the difference between an HMS and an EHR in Nigeria?
In day-to-day use, not much. An EHR is the clinical record itself, the part a doctor edits in front of a patient. An HMS wraps the whole operation around it: billing, pharmacy, lab, scheduling, the lot. Most private hospitals want both in one place, so vendors bundle them and call it whichever name the buyer prefers to hear.
Do Nigerian hospitals legally have to use software?
No single law forces it. But the pressure all points one way. NHIA wants structured claims. NDPR wants audit trails and proper access control on personal data. HMOs increasingly want to be billed electronically. A hospital still on paper is going to struggle to meet any of that over the next two or three years.
How long does it take to set up?
For a small to mid-sized hospital with its data ready and staff free to train, two to four weeks on a cloud product is realistic. A bigger hospital moving off an old system, give it up to three months because of the history. Anyone promising under a week has quietly dropped training from the plan. Anyone quoting half a year for a small hospital is overcomplicating it.
Is patient data safe in the cloud?
Set up properly, yes, and a good deal safer than a room full of paper files. Look for encryption at rest and in transit, role-based access, NDPR-aware handling, daily off-site backups, and a restore someone has actually tested. Ask where the data physically lives. In 2026 it is fair to expect Nigerian patient data to sit in a Nigerian or African data centre.
Can it work offline?
It should. The network here comes and goes, and a system that locks up the moment it drops is unfit for the job. The right setup lets staff carry on at the desk and syncs once the connection is back. Ask for the live test before you sign, not a slide about it.
Does NaijaHealth handle NHIA claims?
We capture NHIA numbers, store the NIN encrypted, keep HMO details on every patient, and invoice across consultation, lab, pharmacy, ward and procedures. Full NHIA claims submission and NIN checks against NIMC are in active development as the NHIA digital channels open up.
What happens to our data if we switch vendors?
You take it with you. It is yours, not ours. Before signing with anyone, ask exactly what the export includes, the patient lists, appointment history, billing and audit logs, in what format, and how you trigger it. With us it is a full export on request, in a standard format, with no exit fee.