Inventory App Starter · Industry version
Medical Inventory Template
Clinical supply control — lot tracking, room-level par, recall response — on an auditable ledger you own.
In a clinic, inventory questions are clinical questions: which lot did this patient receive, what expires in the crash cart, where did the recalled batch go. This starter builds those answers into the schema and generates the system as code your practice owns and runs.
- 6 core entities
- Movement-level ledger
- Code you own
- Vibe + Governed modes
01 · The problem
Why a generic Inventory falls short
Clinical supplies are accountable at the lot level. When a manufacturer recalls a batch of gloves, saline, or a vaccine lot, 'we stock that item' is not an answer — you need which lots you received, where each unit went, and what remains on which shelf. Generic inventory that stops at SKU and quantity cannot produce that trace, and producing it by hand is a bad week.
Storage is also clinical geography. Stock lives in exam rooms, procedure carts, refrigerators with temperature requirements, and a supply closet — each with its own par level, because an empty cart during a procedure is a patient-safety event, not a stockout. A single warehouse bucket erases exactly the resolution that matters.
And expiry in healthcare is a compliance line, not a preference. Administering from an expired lot is reportable; an audit that finds expired stock on a shelf is a finding. The system has to surface expiring lots by location before the auditor or the incident report does.
02 · Data model
The data model, adapted
Everything in the base Inventory starter —
itemswarehousesstock_movementssupplierspurchase_ordersreorder_rules— plus the entities this industry actually runs on:
| table | what it holds |
|---|---|
lots | Received batches with lot number, expiry, and manufacturer — every clinical unit traces to one. |
par_locations | Exam rooms, carts, and fridges with per-item par levels and restock assignments. |
recall_events | Manufacturer recalls linked to affected lots, with quarantine status and disposition per unit. |
03 · Screens
Modules through the industry lens
Lot-traced stock ledger
01Every movement carries its lot, so the ledger answers recall and audit questions directly: where lot 4471 went, what's left, and who moved it. The trace that took an afternoon of paper is a filtered query on your own tables.
Par-level restocking rounds
02Reorder logic runs at the room and cart level, generating a restocking round sheet: what each location needs to return to par, pulled from central supply. The morning round replaces the mid-procedure sprint to the closet.
Expiry and quarantine dashboard
03Expiring lots surface by location and days remaining, and recalled lots flip to quarantined — excluded from usable counts and flagged wherever they sit. Compliance review becomes reading a screen, not opening every fridge.
04 · In practice
Workflows it models
Recall response in an hour
01The notice names a lot. One lookup shows units received, administered or consumed, remaining by location. Remaining units flip to quarantined, the round sheet routes their pull, and the disposition report is ready for the file.
Vaccine fridge management
02Each fridge is a par location with lot-level contents and expiry ordering. The use-first list keeps administration on the oldest viable lot, and a fridge failure becomes a documented write-off of specific lots — not an estimate.
Monthly expiry sweep
03The dashboard lists lots expiring in 30, 60, and 90 days by location. Near-dated stock rotates toward high-use rooms, true short-daters are returned or written off with reasons, and the audit binder fills itself.
Medical Inventory template — frequently asked questions
Does it track lot numbers and expiration dates?
Yes — lots are a core entity, every movement references one, and expiry is tracked per lot per location. Recall traceability and expiry sweeps are queries against your ledger, not manual reconstruction from packing slips.
Can it manage supplies across rooms, carts, and fridges?
Each is a par location with its own item pars and restock assignment. On-hand is answerable per room, restocking rounds are generated from par gaps, and a missing item on a cart shows up before a procedure does.
Is patient data involved, and where does the data live?
The starter tracks supplies, not patient records — and everything runs on your infrastructure with data in your database, which keeps the compliance surface small. If you later link administration events to your clinical system, that integration is code you own and can review.
Does this handle medication-level dispensing?
It's built for supplies and consumables with lot accountability. Full pharmacy dispensing — controlled-substance schedules, prescription workflows — is a deeper regulatory domain; many clinics run this starter for supplies alongside their pharmacy system.
Related
Dual7 App Starters
Build your Medical Inventory on your terms
Clinical supply control — lot tracking, room-level par, recall response — on an auditable ledger you own. Describe your version to start — the output is a project you own.