Delivery day is the easiest day in a hospital IT contract.
Everything is new, and the people who installed it are standing in the room. Hospital IT support only gets tested later, when a printer stops at the billing desk in the evening, or a department asks for an eighth machine.
We wrote up the original job for a private hospital in Abuja in What a Seven-Workstation Deployment Actually Involves: seven desktop workstations, seven monitors, Canon printers and a buffer of Canon consumables, which we specified and deployed. This piece is about what came after. We provide ongoing support and maintenance for that equipment, and the hospital comes back to us when it needs more.
A note on what we will and will not say. We are not going to publish ticket counts or response times from a client's estate. What we can describe is how the arrangement is built, and why it is built that way.
What the hospital was really buying
The order was for hardware. The requirement was a records desk that works at 6am and a billing printer that works at 9pm, every day, for years.
A supplier who disappears after delivery has met the first half of that and handed the hospital the second half to carry alone. Plenty of hospitals in Abuja know the pattern. The machines arrive, the vendor stops picking up, and the first fault becomes a hunt for whoever still has the invoice.
So on this job we treated go-live as the start. The deployment was built to make the years of support after it cheap and predictable. A hospital does not need another sale.
Support is designed during the deployment
The most useful support work on that job happened before anything broke. Three decisions made in the original deployment carry most of the weight now.
Identical machines. The seven workstations were specified to a common model and built from one image. A fault on one is diagnosed against six identical working units. There is one driver set and one spares profile. Seven different machines from seven different sources would turn every fault into an investigation.
A real asset register. Every unit was recorded by serial and physical location before it was powered on, and the hospital holds a register listing model, serial, location, purchase date and warranty expiry. When a desk calls, we already know what sits on it and whether it is still under warranty.
Warranty in the hospital's name. Registered to the hospital, with the paperwork handed over. Cover belongs to the owner of the equipment, not to whichever supplier happens to be holding the file.
None of this is visible on delivery day. It decides what a fault costs in month ten.
How we run hospital IT support
Our managed services practice is the same whether the client is a hospital or an office. What changes in a hospital is how a problem is ranked and how fast it has to move.
The working pattern:
- Scope and targets in writing. We agree what is covered and to what response targets before anything else. Neither side should have to guess later about what was promised.
- Remote first. Most day-to-day faults get diagnosed and fixed remotely, without waiting for anyone to drive across Abuja.
- On-site when it has to be. A dead power supply or a failed printer roller does not fix down a phone line. An engineer goes out.
- Act early. A UPS battery that no longer holds its runtime, or a printer that has started to jam, gets dealt with before it takes a desk down.
- Report what to fix next. Regular reporting includes our view of what the hospital should replace or change, and when.
We rank faults by what they stop. A records desk that has stopped is a queue in a corridor. A slow machine in an administrative office can wait until the afternoon. Printers sit in the same ranking as workstations, because lab slips and discharge summaries end on paper. That is also why the deployment used a brand whose consumables and parts are sold across Abuja: a part available locally turns a fault into a short repair instead of a wait. Our guide to what hospital IT support in Abuja should cover sets out the priority levels and the printer question in full.
Staying accountable after delivery
The real question is who chases the problem.
When a covered unit fails, the hospital should not be told to phone a manufacturer helpline and wait. Under the end-to-end model we work to, one party owns the problem from report to fix, including taking a failed unit through its warranty claim. The hospital deals with one name.
The other half is honesty about the limits. Some faults are not hardware faults. A bug in the clinical application belongs to its vendor. A mains problem belongs to the building. Our job there is to say so plainly and help the right party fix it. We should not absorb a problem we cannot solve, or pass on one we can.
Repeat procurement: the second order matches the first
The hospital comes back to us for more equipment. That is the part of the relationship that shows whether the first job was done properly.
When a request comes in, our default is to quote the same model that is already installed, provided it is still current. One more identical workstation keeps the estate at one image and one spares profile. A cheaper-looking alternative that breaks the standard costs more over its life than it saves at purchase.
When the installed model has gone end-of-line, we say so before quoting. We propose the nearest current equivalent, confirm it runs the same image and the same clinical software, and put the difference in writing so the hospital can see exactly where the standard has moved. We set out the reasoning in more detail in standardising repeat IT procurement for hospitals.
Every new unit goes into the same asset register as the first seven. The register grows with the estate. It never gets restarted.
Consumables are the quiet half of the relationship
The buffer stock of Canon consumables that went in with the deployment was the first consumables order. It was never meant to be the last.
Hospitals get caught out on consumables because nobody owns the reorder. The fix is arithmetic against print volume and lead time, and we set out the method in standardising repeat IT procurement. For a brand sold locally the lead time is short, which keeps the buffer small and stops cash sitting on a shelf.
Because the printer models are fixed and recorded, a consumables order is a line item against known part numbers. No one has to read a label off a machine in the middle of a busy clinic.
Frequently asked questions
Does the supplier who installed the equipment have to support it?
No. Any competent provider can support a hospital estate. The condition is that the documentation moves with it: the asset register, warranty records, admin credentials and the build image. Without those, a new provider starts from nothing and the hospital pays for the rediscovery.
What should hospital IT support cover after a deployment?
At minimum: the workstations, the printers, power protection at critical desks, and the network those devices use. It should state support hours that match clinical hours, response targets by priority, and who handles warranty claims. Our guide to IT support for private hospitals in Abuja covers the full list.
How often should a hospital reorder printer consumables?
Print volume per printer and the supplier's lead time decide it. Measure a normal week of pages, work out how many weeks one cartridge or bottle lasts, and reorder when remaining stock covers the lead time plus a margin. Recheck the figure when a department starts printing more.
Is buying more of the same model always right?
No. If the installed model is end-of-line, or its remaining warranty and software support are shorter than the life you need, a newer model is the better buy. The point is to change the standard deliberately and in writing.
If your hospital has equipment on the desks and nobody clearly accountable for it, send us the list of what is installed and where. We will tell you what a sensible support scope looks like for it. For the wider picture, see our healthcare IT work.
