LIMS
Laboratory Information System
A LIMS that takes a sample from intake to PDF report without anyone touching a spreadsheet. Role-based access, audit-clean, Livewire-fast.
0
Lost Samples
On Demand
How it came together
The setup
A working lab was running on Excel and email: sample intake, test results, and final reports all hand-stitched. Audit prep was a weekend job.
The challenge
Make the lab’s real workflow (intake, run, review, report) fit into one tool that auditors can sign off on.
Scale
End-to-end sample tracking, multi-role workflows, branded PDF reports.
The hard parts
Non-negotiables
- Every state change traceable
- Roles strict (technician ≠ reviewer ≠ admin)
- PDF reports indistinguishable from the old letterhead
Trade-offs we made
- Did not build a mobile app. The lab works at desks; a responsive web app was the right ceiling.
- PDF rendering is server-side, slower than client, but every report is identical.
Calls I made
Livewire over SPA
Server-rendered components keep the auth model simple and the build pipeline thin. The lab’s laptops are not fast, so every kilobyte counts.
Laratrust for permissions
Picked off-the-shelf RBAC instead of rolling our own. One less attack surface, one less bug class.