Picture a busy clinic on a Tuesday morning. A nurse opens the supply cupboard for a box of dressings and finds three boxes, one of which expired last month. Across the hall, the person who orders supplies is deciding whether to reorder gloves, based on a glance at the shelf and a feeling. Nobody is careless. The clinic simply has no reliable way to know what it holds, where it is, and when it stops being usable.
This article is about the process and the software around stock in a clinic. It is not clinical guidance: what you may store, how, and for how long is for your clinicians, your suppliers and your regulator to decide.
Why clinic stock goes wrong
Clinic stock is harder than shop stock for one reason: a lot of it has a date after which it must not be used. A shop that overstocks loses money. A clinic that overstocks may also end up throwing items away, or worse, using something it shouldn't.
Three habits make it worse. Stock is counted rarely, and by eye. New deliveries go to the front of the shelf, so the oldest items hide at the back. And the same item sits in several places: the cupboard, the treatment room, a bag for home visits. Nobody sees the total.
Lots and expiry dates: the minimum worth recording
Every box that expires has two things printed on it that matter to software: an expiry date and a lot (batch) number. Two boxes of the same product can carry different ones.
A system that only records "dressings, 12 boxes" cannot tell you that four of them expire next month. A system that records quantity, lot and expiry at the moment of receiving can. That small extra effort at the delivery desk is what powers everything else: expiry warnings, correct picking, and recalls.
FEFO: use what expires first
You may have heard of FIFO, first in, first out. For items with an expiry date, the better rule is FEFO: first expired, first out. The box that expires soonest is used first, even if it arrived later than another.
Done by hand, FEFO depends on someone's memory and discipline. In a well-built system it becomes the default: when staff record that they took an item, the system tells them which lot to take. And a weekly list of what expires in the next 30 or 60 days lets you use it, move it, or return it to the supplier while there's still time, instead of finding out when it's already past.
Temperature-sensitive items
Some items need to be kept within a temperature range, in a fridge for example. The chain of storage and transport that keeps them there is usually called the cold chain.
I'm not going to tell you what temperatures apply to what. Your manufacturers' instructions and local health authorities do. What software can do is support the process. The US CDC's guidance on vaccine storage, as one example, recommends digital data loggers for routine storage and keeping at least one backup device. A system can record readings, flag one outside the range, and tie that alert to the lots that were in that fridge at the time. And it can keep a record of what was done about it, which is the part that matters later.
Whatever happens with the affected items, a person with the right training makes that call. The system's job is to make sure the question is asked at all, quickly, and that the answer is written down.
Controlled substances need extra rules
Some medications are classed as controlled, and many countries add specific requirements for them: who may order, store and handle them, how they are counted, and what has to be recorded and reported. These rules differ from country to country and sometimes from region to region.
So treat them as a separate case. Find out exactly what your local regulator requires, in writing, before anyone designs a screen. A custom system can then follow those rules: separate stock, mandatory records, restricted access. A general-purpose inventory template will not know them.
Recalls: the question you hope never to ask
Sometimes a manufacturer or a regulator asks for a product to be pulled back. The US FDA, for instance, defines a recall as an action taken by a firm to remove a product from the market, and says it can start on the firm's own initiative, at FDA's request, or by FDA order. Other countries have their own bodies and procedures.
When a notice arrives naming a lot number, the question is immediate: do we have it, how many, where, and who received any? If you record lots at receiving and record every movement, you can answer in minutes, from a search. If you don't, the answer is a day of opening cupboards and hoping.
What to ask for in a system
- Quantity, lot and expiry captured when stock arrives, ideally with a barcode scan rather than typing.
- Stock by location, so the treatment room and the home-visit bag are visible too.
- Picking suggestions that follow expiry dates (FEFO).
- Expiry and low-stock lists that arrive without anyone asking.
- Records for temperature checks and what was done about problems.
- A history of every movement, so a recall search is quick.
- Room for special rules for controlled items, once you know your local ones.
A first step
Pick one cupboard and one fridge. Spend an hour writing down what is in them with lot and expiry, and notice how long it takes and what you found. That small exercise shows how much of the problem is process and how much is tooling, and it gives you real examples for any developer you talk to.