A lab system is judged on the days when nothing goes to plan. This guide covers the questions that separate a system that holds up in a Nigerian lab from one that only looks good in a demo.
A laboratory information system runs the work of a lab, from the moment a sample is received to the moment a validated result is released. Choosing one in Nigeria means weighing the same fundamentals any lab cares about against the local conditions that decide whether a system actually works here. Power and connectivity are intermittent, payment is mixed, and the lab often sits inside a hospital rather than standing alone. This guide is built around those realities.
If you are still settling the difference between a LIS and a LIMS, our explainer on LIS versus LIMS is a useful starting point. This piece assumes you know you need a lab system and are choosing one.
The single most valuable thing a LIS does is talk to your analysers, so results flow from the instrument into the system without a person re-typing them. Re-keying results is slow and it is where transcription errors enter. Ask the vendor which of your specific analysers they connect to, how that connection is made, and whether bidirectional ordering is supported so the worklist goes out to the instrument as well. A LIS that cannot reliably connect your benches is doing only half the job.
If a vendor will not run the demo with the network unplugged, treat the offline claim as marketing until it is proven.
This is non-negotiable in Nigeria. A lab cannot stop accessioning samples because the internet dropped. Ask the vendor to disconnect during the demo and complete a full lab journey, receive a sample, run the worklist, validate, and release, with the connection down, then reconnect and watch it sync cleanly. Offline behaviour is an architectural property, not a checkbox, which is why we treat it as foundational. Our piece on why offline-first matters explains the difference.
A reputable lab lives by its quality controls. Check that the system supports running and recording QC, flags results that fall outside expected ranges, and keeps the validation step firmly in human hands where it belongs. Ask how the system handles result authorisation, who can release, and whether the audit trail records who validated what and when. These controls are what make a result trustworthy.
Payment is mixed: cash, transfer, mobile money, and a meaningful share through HMOs and insurance schemes. A LIS that assumes simple cash billing leaves you managing claims on the side. Check that tests are billed from what was actually ordered and done, that HMO and scheme tariffs can be applied, and that the system can produce the claims you need rather than forcing a separate process. If billing lives entirely outside the lab system, that is a gap you will feel monthly.
This is the question that shapes everything else. If your lab is independent, a focused standalone LIS may suit you. If the lab sits inside a hospital, a standalone system has to be connected to the hospital's patient records, ordering, and billing, and each of those connections is an integration to build and maintain. A lab that is part of the hospital platform shares one patient record, so orders arrive without re-entry and results return to the same chart automatically. We weigh this directly in Veona versus a standalone LIS and more broadly in one platform versus separate systems.
If your lab contributes to facility reporting, ask whether the data it captures can feed aggregate returns without a manual count, and whether the system speaks recognised standards. Standards support, including the protocols labs use to talk to instruments and the coding that makes results portable, is what keeps your data usable beyond one vendor's product. Our guide to DHIS2 reporting covers what good reporting looks like.
The licence is the visible cost. The real number includes implementation, training, analyser interfacing, support, and every integration to the systems around the lab. A cheap LIS licence that needs paid connections to hospital records, billing, and reporting can cost more than a platform that includes the lab. Ask for pricing that is clear about what is included and what is charged per integration so you can compare like with like.
Veona's laboratory is part of the platform, offline-first, and built to connect to analysers so results flow without re-typing. It supports QC and human validation with full audit trails, bills from what was actually ordered including HMO workflows, and shares one patient record with the rest of care so there is no separate system to license and connect. You can see what is included on our pricing page. The most honest evaluation is to bring your own analysers and workflow to a demo and run them, with the network off.
Book a demo and we will test analyser connectivity, offline behaviour, QC, and billing against your real lab.