Hospital store management: ward indents and minimum stock

Abstract
How the store module in Nice HMS gives a hospital one main store, ward cupboards, indents you can approve and part-issue, consumption recorded where the stock is used, and a minimum level that builds the shortage list for you.A hospital's consumables store is where money quietly disappears. Gloves, gauze, sutures, IV sets, syringes — cheap per item, relentless in aggregate. In most systems that store is one number on a purchase bill and another number in a stock report, and nothing connects the two to the cupboard the nurse actually opens at 2 a.m.
The store module in Nice HMS is now live, and it is built around a different idea: a ward asks for what it needs, the main store answers, the ward records what it used, and the stock level itself tells you when to buy. No forecast. No manual reorder sheet. The signal to replenish is consumption.
Here is how it works end to end.
Two kinds of store, one of them buys
Every hospital gets exactly one Main Store. It receives purchases, holds the real stock, and is the only place that issues material to wards. Ward stores are cupboards: each nursing station or ward holds a small working stock and never buys anything.
That split is the whole point. When one place buys and many places hold, you can answer the only question that matters in a store audit: where did it go? Stock sits at a named store, not in an org-wide pool that nobody can reconcile.
Reading is open — any authorised user can see any store's stock, which is what stops two wards from indenting the same item that is already sitting in the next cupboard. Writing is confined to the store you are in-charge of. Administrators and directors can act for any store.
An indent is a request, not a movement
A ward's in-charge raises an indent: pick the ward, add lines of item and quantity, send it to the Main Store.
Nothing moves yet. Raising an indent reserves the quantity, so the Main Store cannot promise the same gloves to a second ward. On hand stays where it is; available drops by the reserved amount.
The Main Store's in-charge then approves. They can reduce any line to what they can actually supply — never above what was asked, never below what has already gone out. A ward's in-charge can never approve their own indent; supplying and approving are deliberately two different people.
Issuing is the only step that moves stock, from the Main Store to the ward. If you can only send part of it, send part of it: the indent becomes Partly issued, the remainder stays reserved, and a later issue closes it. Until then the outstanding quantity is printed on the issue note, not lost in someone's memory.
An indent left untouched for seven days expires on its own — the whole thing if it was never approved, or just the unissued remainder if part of it went out. That way a forgotten request cannot reserve stock forever. Indents support up to 200 lines, and anything that is billed rather than stocked — a consultation, a bed charge — cannot be indented.
The shelf is the truth; the screen is only the record
This is the rule that shaped the module.
If the Main Store's book says zero but the material is physically on the shelf, the system lets it issue. It does not block the transaction to protect a number. Blocking would not prevent the handover — staff would simply hand the item over off-system, and the record would drift further from reality.
So the book is allowed to go negative, and the gap becomes information instead of an error. It is cleared the honest way: a physical count, by someone who names themselves, with the reason recorded. Stock that leaves the shelf without being consumed surfaces as unreconciled movement in the monthly report.
Consumption is recorded where the stock is used
A ward knows what it used, usually minutes after using it. So the ward records it: pick the ward, pick a date, add the item lines. No approval step, because the goods are already gone and an approval would only be retrospective.
Two limits keep the screen honest. A consumption can be dated today or up to three days back — never in the future. So it records usage that has happened, and it cannot be used to pre-book or schedule stock. A ward that needs material for tomorrow raises an indent.
If a ward records more than its book shows — usually because an issue was never entered — the form warns and still posts. The stock is already used; refusing the entry would push staff to invent an indent they never raised, which is worse data.
And a consumption is never edited. A mistake is cancelled with a reason and re-entered, so the audit thread shows the wrong entry, its cancellation, and the replacement.
A minimum level that builds the shortage list for you
Every item can carry a minimum level, set per store. Leave it blank and the item is simply not tracked — it never appears in a shortage list or a report.
For the Main Store, a blank level comes with a suggestion: 25% of the item's latest purchase, rounded up. It is shown next to the empty field and can be applied in one click for the whole store, but it is never switched on by itself. A suggestion that silently became policy would put your entire catalogue on the first shortage list, and the list would be ignored.
Once floors exist, the shortage screen is live and needs no preparation: every item whose available quantity has fallen below its floor, per store, with the gap in units. Open indents count, because a reserved item is not available to anyone else.
The main store then buys against that list. There is deliberately no automatic purchase order — the shortage list is the input a buyer acts on.
Dormant stock comes back
A ward that has not used an item for 90 days is holding someone else's working capital. The dormant screen lists those items per ward, above the ward's floor, with a suggested quantity to hand back.
The ward raises the return and attests what it is giving up. Stock does not move yet. The Main Store confirms receipt — and only then does the stock transfer, at the quantity that actually arrived. The receiver may lower a line if the goods came up short, but never claim more than was handed over. Both figures stay on the line, so the trail reads "handed over 10, received 6".
Any hospital stock item can be returned, not just a dormant one: physical stock can exceed the book, and a ward should be able to hand back what it holds. A return nobody receives expires after seven days and can never be confirmed afterwards.
It ends in the monthly report
The store figures travel in the monthly report every subscriber already receives — no second email to ignore. For hospitals on the Large Enterprise plan, the report adds a store section per store: purchases with the previous purchase rate, stock valuation, expiry dates read from batch details, and an action list ranked by rupee value.
The actions are the part that gets read: buy N units of an item whose cover is running out, chase a movement that left the shelf but was never consumed, clear stock expiring within 90 days, send back dormant material, look at a ward consuming at twice its usual rate, note a price rise on the last purchase. Each row names the store, the item, the quantity, the value, and the person responsible for the store.
Getting started
Create your Main Store, add a ward store per nursing station, assign an in-charge to each, then set minimum levels. Set them for the items you actually track — you can leave the long tail blank. The shortage list appears as soon as floors exist; the first indents usually follow within a week.
The detailed guides are in the product documentation: Ward Indents, Ward Consumption, Store Minimum Levels, Store Shortage and Stock Returns.
The module ships on the Large Enterprise plan. If your clinicians already use PatientOS, the two sit side by side: PatientOS records the clinical encounter, this module records the material behind it — the same product, the same login.
Frequently asked questions
Does this replace pharmacy stock?
No. This release is the hospital store — consumables, not drugs. The pharmacy keeps its existing stock and billing flow, where a medicine leaves at the moment of a patient sale and there is nothing to approve. Ward drug cupboards are not part of this release.
Can one ward see what another ward is holding?
Yes, and it is deliberate. Reading across wards is what stops a duplicate indent for an item that is already in the next cupboard. Writing is still confined to the store you are in-charge of.
What happens if a ward asks for more than the Main Store has?
The indent is still raised and reserved; the Main Store approves what it can supply and issues what is physically there. The book may go negative until a purchase or a physical count corrects it. Refusing the issue would not stop the material leaving the shelf.
Who can record consumption for a ward?
The ward's assigned in-charge, or an administrator or director acting for any ward. One named person per ward keeps the record answerable; assigning the in-charge is how a ward gains a writer.
Do indents affect the accounts?
No. Indents, issues, returns and consumption are stock documents only. They move quantities between stores and out of the hospital; they do not touch ledger balances.
Hospital software updates, by email
What changes in Indian hospital software: new Nice HMS releases, ABDM/NHCX and PMJAY updates, and practical notes on running a hospital — a few emails a month. Unsubscribe in one click.
Related reading
- How to onboard your whole doctor panel in an afternoonImport your entire doctor panel from one spreadsheet, let new doctor users create their own profile, and know the two rules that catch most hospitals out.
- How to build a clean pharmacy item masterA practical guide to pharmacy item masters: naming, units, GST, batches and opening stock — and importing up to 5,000 items from one spreadsheet instead of typing them one by one.
This Unlock the Future of Healthcare Management! 🚀🏥🌟
Is managing your hospital, clinic, or lab becoming a daunting task? Experience the ease and efficiency of our cutting-edge Management Software through a personalized demo.
