Most IT support contracts are written for offices. Hospitals sign them anyway.
The result is a support window of 8am to 5pm, Monday to Friday, for a building that admits patients at 2am on a Sunday. Hospital IT support in Abuja has to start from the hospital's hours and the hospital's failure points, then work back to the contract. This guide sets out what a private hospital should expect the arrangement to cover, and what to insist is in writing before anyone signs.
It assumes the hospital is already set up. If you are still planning the build, start with our IT setup guide for hospitals and clinics.
Coverage has to match clinical hours
Start with a plain question. When is the building working?
An outpatient-only clinic may genuinely run 8am to 6pm. A hospital with wards or a 24-hour pharmacy does not. Records and billing keep working at night, and they fail at night too.
Support hours should be written to match. In practice there are two sensible shapes:
- Full 24/7 cover for a short list of critical systems, with ordinary business-hours cover for everything else.
- Business-hours cover with an out-of-hours line for critical faults only, at a priced call-out rate agreed in advance.
The first costs more every month. The second costs more on the night you use it. For a hospital with a busy night service, the first is usually right. For a day clinic with a small ward, the second is often enough, and it would be wasteful to pay for more.
Whichever you choose, the contract has to name the critical systems. "All IT" is not a priority list. A records workstation and the pharmacy printer are.
Priority is defined by what stops
A generic support contract ranks faults by technical severity.
A slow machine in the finance office is a nuisance. A dead registration desk at 7am is a queue of patients in a corridor. Both might be the same fault on the same model of workstation. They are not the same priority.
Write the priority levels around clinical impact, and give each one a response target and a resolution target. Response means someone qualified is working on it. Resolution means it works again, or a workaround is in place that staff can actually use. A contract with only a response time lets a provider answer quickly and fix slowly. Our piece on what an IT SLA should cover goes through the clauses in detail.
On-site response in Abuja is a travel question
Remote support fixes most day-to-day faults. Hardware does not fix remotely. When a power supply dies, someone has to drive.
So ask where the provider's engineers are based, relative to the hospital. Abuja traffic between the city centre and the satellite towns at rush hour turns a short distance into a long trip. A four-hour on-site target is easy to promise and hard to meet from the wrong side of the city at 5pm. Ask how the provider meets the target at that hour, not on a quiet Saturday morning.
Spares on site beat fast engineers
The fastest repair is a swap. A hospital that keeps a small stock of spares on its own premises can be working again before an engineer arrives.
A sensible spares kit for a small hospital estate:
- One pre-imaged spare workstation of the same model as the fleet, ready to drop onto any critical desk.
- A spare monitor and a spare keyboard and mouse. Cheap, and the most common physical failures.
- One full set of printer consumables per printer model, beyond the stock in use.
- A known-good network patch lead and a spare small switch if desks share one.
The spare workstation is the one that pays for itself. It only works if the fleet is standardised, which is a procurement decision as much as a support one. We cover why in standardising repeat IT procurement for hospitals.
Write into the contract who owns the spares and how fast they are restocked after a swap.
Printers are clinical equipment
Patient cards, lab slips, receipts, referral letters and discharge summaries all end on paper. A stopped printer at the pharmacy or the lab stops a clinical step, with every computer in the building still working.
Most office contracts treat printers as peripherals and exclude them, or cover the network side and leave the hardware to "the printer vendor". In a hospital that gap lands on the busiest desk. Insist that printers are in scope. Then set the consumables reorder point from actual print volume and the supply lead time. Brands whose consumables are sold locally keep that lead time short.
Power is part of support
Plenty of hardware faults in Abuja start with power. A UPS that held 15 minutes when new may hold four after two years of daily changeovers. Nobody notices until the generator is slow to start and a records workstation goes dark mid-save.
The support arrangement should include periodic checks of UPS battery health and runtime at the critical desks, and replacement before failure. Batteries are a consumable. Budget them as one. The design side of this, sizing and offline-first records, is covered in designing IT infrastructure for continuity of care.
Records continuity is a shared job
The support provider cannot own the hospital's records. It can own the plumbing under them.
Agree in writing who runs backups, how often, where copies are kept and who tests a restore. A backup that has never been restored is an assumption. Ask for a restore test on a schedule, with the result written down. If the hospital management system is hosted by its vendor, the support contract should say where the IT provider's job ends and the software vendor's begins, so a fault at 10pm is not passed between them.
Then plan for the hour when the system is down anyway. Downtime forms, printed in advance, and a named person who decides when to switch to paper. That is a clinical procedure. IT supports it, but the hospital owns it.
What to put in writing for hospital IT support
Before signing, the written arrangement should state:
- Support hours, and which systems get cover outside them.
- Priority levels defined by clinical impact, each with response and resolution targets.
- Where on-site engineers come from and the on-site target for critical faults.
- What is in scope, explicitly including printers and UPS units.
- Spares: what is held on site and who restocks it.
- Who handles warranty claims on failed units.
- Backup and restore duties, and how often a restore is tested.
- How the asset register is kept current, and who holds the admin credentials.
- What reporting you receive, and how often you review it together.
- What happens to your documentation if you end the contract.
That last line matters more than it looks. A hospital that cannot leave its provider cleanly cannot really hold that provider to account.
If you are weighing whether this belongs in-house at all, our comparison of in-house and outsourced IT support sets out the trade-off. A common answer is a hybrid: one in-house coordinator who owns the relationship, with an external provider carrying the engineering.
Frequently asked questions
Does a private hospital in Abuja need 24/7 IT support?
Only for the systems that run at night. If wards or a night pharmacy depend on a workstation or printer, those need out-of-hours cover. Administrative systems can usually stay on business-hours support.
What response time should a hospital IT support contract commit to?
Two things decide it: what the fault stops, and how far the engineers have to travel. Set the tightest targets for registration, records, billing and pharmacy desks, and require a resolution target alongside each response target.
Should printers be included in hospital IT support?
Yes. In a hospital the printer is the last step of many clinical processes. Exclude them and the most frequent failures in the building fall outside the contract.
Can one in-house IT person replace a support provider?
For a small hospital, rarely. One person cannot cover every shift, and cannot be expert in both networks and backup. A coordinator plus an external provider survives that person's annual leave.
If you run a private hospital in Abuja and want a second opinion on your current support terms, send us the contract and a list of what is installed. We will mark up what we would change. Our managed services and healthcare pages describe how we work, and we work from our Abuja base.
