Guide · Uganda

What a small clinic actually needs from software

Almost every clinic system on sale was designed for a hospital and is being sold downward. That is why the demo has modules for departments you do not have, a price that grows when you hire, and a training plan measured in days. You are being quoted for somebody else's problem.

A facility seeing twenty to forty patients a day, taking mostly cash, with one lockable drug cupboard and staff who each do three jobs, has a short and specific list of needs. It is worth knowing what is on it before you sit through anybody's presentation.

The five things

1. Know who is waiting, and for what

The single most common failure in a busy clinic is not clinical. It is a patient who paid, sat down, and was forgotten — or who was sent to the lab while the doctor waited for them. If nobody can see the queue, the queue is whoever shouts.

What this means in practice: every station sees its own list, and a patient moves onto the next list automatically when the previous step finishes. Nobody should have to walk to reception to ask who is next.

2. Account for the money, to the shilling, daily

Cash clinics do not lose money to one dramatic theft. They lose it in small leaks: a consultation not charged because the queue was long, a test done and never billed, a mobile-money confirmation nobody checked. Each is trivial. Together they are the margin.

What this means in practice: a charge is created by the clinical action, not typed separately by a person who might not bother. And at the end of the day, one number the owner can reconcile against the drawer.

3. Stop a dangerous prescription before it is written

This is the one thing software can do that a busy human reliably cannot. A clinician who has seen thirty patients will not remember that the woman in front of them reacted to penicillin two years ago. The record does.

What this means in practice: the allergy is checked when the drug is chosen, the block is hard rather than a dismissible warning, and an override is recorded with a reason. A system that shows the allergy on a sticker somewhere and hopes you look is not doing this.

4. Know what is on the shelf

If the only way to answer "how much amoxicillin do we have" is to walk over and look, then nobody looks until it runs out — and the slow-moving stock behind the fast-moving stock ages out unseen. Expiry is a stock-record problem, which we wrote about separately.

What this means in practice: dispensing moves the stock figure by itself. Any system where someone has to remember to update the count will drift within a fortnight.

5. Produce the reports you are legally required to file

Somebody spends two days a month assembling HMIS 105 from registers. That time is not clinical work and it is not optional. If the day's activity is already recorded, most of the form is arithmetic the system can do.

See the HMIS 105 guide for which register each number comes from.

What is somebody else's requirement

A demo will show you things that sound impressive and cost you money. Ask yourself who they were built for.

Department modules you do not have. Theatre, radiology PACS, dietetics, a bed-management dashboard for forty beds. If you do not have the department, the module is complexity you pay for and navigate around.
Per-doctor or per-user pricing. This means your bill grows exactly when you get busier — see what clinic software actually costs. Per-facility pricing is structurally different, not a discount.
A server in your back room. Somebody has to power it, back it up, and fix it at 8pm on a Sunday. Unless you have that person, an on-premise system transfers the vendor's cost onto you.
Integrations with systems you do not use. Impressive in a demo, irrelevant until you have an insurer or a laboratory that actually connects.
Data migration of years of history. Almost always the wrong call for a small facility — here is why.

Four questions that separate the two

"Show me a patient going from the door to the pharmacy." Not a feature tour — one patient, all the way through. If that takes twenty minutes of clicking in a demo, imagine it at 11am with fourteen people waiting.
"What happens if I prescribe something this patient is allergic to?" Watch whether it blocks or merely mentions. A warning you can click past is a warning that gets clicked past.
"What does my bill do if I hire another clinical officer?" The answer tells you whether you are buying software or renting seats.
"How do I get all my data out, and can I do it myself?" Anyone confident in their product answers this immediately. Hesitation here is the single most useful signal in the whole conversation.

Being straight about our own position: CareBoon is built for exactly the facility described above, which means it is a poor fit for a large hospital with established departments and its own IT staff — those are genuinely better served by the bigger products. And no software fixes a clinic that has not decided who owns the change. The five things above are worth having; none of them happens because a system was installed.

Start free See what it costs