Resources · 3 September 2026 · 7 min read

IOL Inventory Management for Eye Hospitals: Batches, Recalls and the Store Room

An intraocular lens is the one item in an eye hospital's store that is implanted in a patient and stays there. That single fact should decide how it is tracked — and it is exactly the fact spreadsheets ignore.

Why IOLs are not ordinary stock

Pharmacy stock is consumed; consumables are used up; an IOL becomes part of a person. That changes the questions your records must be able to answer. Not just "how many lenses do we have?" but "which exact lens — brand, power, batch — went into which eye of which patient, on which date, implanted by whom?" The day a manufacturer issues a batch recall, that second question is the only one that matters, and a hospital that cannot answer it from a search box answers it by pulling paper theatre registers for an afternoon — or worse, by calling every cataract patient of the last six months.

IOLs also have properties that make them uniquely awkward for general-purpose inventory: dozens of powers per model (a +19.5 D and a +20.0 D are different items, not the same SKU), consignment stock owned by the vendor until implanted, expiry dates that matter, and the reality that the lens chosen in counselling is not always the lens implanted — a surgeon may switch power intra-operatively after final biometry review.

What a proper IOL record tracks

  • A master by brand, model and power — every power a separate, countable line, not a free-text note.
  • Batch and expiry on every unit — recorded at goods-in, not reconstructed later from purchase bills.
  • Branch-level stock — a chain must know which branch holds which lenses; transfers recorded, not messaged.
  • Issue against a named patient — the lens leaves stock at implant, tied to the patient, eye, surgeon and case record.
  • Consignment separation — vendor-owned stock visible and countable but not on your books until used.
  • The audit trail — who received, issued, returned or wrote off each lens, and when.

The recall test

Whatever system an eye hospital uses — software, register or spreadsheet — it should be judged against one scenario. A manufacturer notifies you that batch X of a lens model is recalled. How long does it take to produce: the number of units of batch X still in stock (and in which branches), and the complete list of patients already implanted with batch X, with dates and operating surgeons? In a system where lenses are issued against patients, this is a two-minute search. In a spreadsheet maintained by the store keeper, it is archaeology — and every hour it takes is clinical risk plus regulatory exposure.

Where this fits in the wider system

IOL tracking works best when it is not a separate inventory app but a thread through the clinical system itself: the lens is chosen at counselling with the cost estimate, confirmed against biometry, issued in theatre when the checklist completes, and appears on the bill and the discharge record — one record from store room to surgery. That flow is exactly how Aviral Medcare treats implants, and you can watch the sequence — order, theatre, consumption — on the product tour. The same batch-and-expiry discipline applies to intravitreal drugs and theatre consumables; the lens is simply where the stakes are highest.

Questions to ask your team this week

  • Can we run the recall test today, and how long would it take?
  • Do we know our consignment position per vendor without calling them?
  • How many lenses expired on the shelf in the last year, and who noticed?
  • When a surgeon switches power in theatre, where is that recorded — and does the bill follow?

Run the recall test on our screens

Bring your store-room reality to a demo and see the IOL master, batch tracking and patient-wise issue working on sample data.