EquiTrackr — equipment
coordination, orchestrated.
A healthcare equipment workflow platform — track, request, clean, and maintain mobile clinical assets across departments, with one operational registry underneath.
- Role
- Product & systems design
- Surface
- Web platform
- Scope
- Multi-department
- Stack
- Next.js · TS · Postgres · Prisma
Asset classes
EVS · ready
Ward 4B
ICU · req #4821
EVS · queued
EVS · in prog
01 · The operational friction
Equipment moves all day. Knowledge of it doesn’t.
Mobile clinical assets cross departments constantly — but coordination still happens by phone, paper, and footwork. The pool is shared; the picture of it isn’t.
Before · coordination by phone, paper, and footwork
Every dotted path is a call, a sheet, or a walk — and none of it leaves a record.
Equipment goes missing
An asset leaves a unit and effectively drops off the map.
Fragmented coordination
Departments negotiate one device at a time, by phone.
Delayed retrieval
Care waits while someone hunts a pump or a lift.
Unclear status
Clean? In use? Out of service? Nobody can say for sure.
Manual tracking friction
Sign-out sheets and whiteboards that go stale by lunch.
Pre-platform state · representative.
02 · Workflow architecture
Every asset, every state, one registry.
A scan resolves to a transition; the lifecycle engine decides what’s valid; the registry records it. Boards, queues, and workflows all read downstream from there.
The spine
Scan layer
QR + barcode
Check-in / check-out
who, where, when
Lifecycle engine
valid transitions
Operational registry
source of truth
One pool, many roles
Built for mobile clinical assets
Same scan, same states, same registry — whether it’s a wheelchair or an infusion pump. New asset classes are configuration, not a rebuild.
Scan layer
Every asset carries a code; a scan is the only input the workflow needs.
Lifecycle engine
Each scan resolves to a valid transition — the rules live here, not in people’s heads.
Operational registry
One record per asset: class, state, location, owner, and full history.
Multi-role surfaces
Boards and queues shaped to each role — frontline, transport, EVS, biomed, coordinators.
03 · Operational console
Scan → transition → visibility → coordination.
One scan, four effects. Step through a real request being fulfilled — or let it run.
The scan
IP-1140
Infusion pump · Imaging
Registry record
IP-1140 · infusion pump
Available08:50 · available · Imaging store
Boards & coordination
1. Scan asset — A porter scans pump IP-1140 at Imaging on pickup — the only input the workflow needs.
Interactive prototype · representative workflow & figures.
04 · Equipment lifecycle
Six states. Every asset knows which one it’s in.
Inventory is a count. A lifecycle is memory — it’s how the system knows what’s overdue for cleaning, what’s waiting on biomed, and what’s actually available right now.
The cycle
in the pool, ready to assign
checked out to a unit / request
scanned back, awaiting turnaround
EVS cleans & confirms
biomed services & signs off
removed from the pool
Returned or Cleaning can branch to Maintenance; Maintenance can end at Out of Service. Every hop is one scan and one record.
Where the fleet is right now
representativeState mix is representative.
05 · Impact & operational benefits
Find it faster. Coordinate it cleaner.
EquiTrackr is built around the outcomes that matter on the floor: less time hunting, requests that don’t fall through, and a clean record of every move.
6 asset classes
one shared registry & state model
Multi-department
by design — roles, boards, queues
Every change
logged — owner, location, history
Before → after
Find an asset
call around, walk the units
filter by class, state, location
Equipment requests
phone call + sticky note
a queue with assignment + ETA
Cleaning
ad hoc, untracked
queued on return, confirmed by EVS
Maintenance
discovered when it fails
flagged by usage + state thresholds
Accountability
who has it? unclear
owner + full history per asset
Operational observability · the surfaces that come for free
illustrativeTime to locate an asset
Requests fulfilled / day
Fleet utilization
EquiTrackr is a product build; the figures here are design targets and illustrative trends, not production measurements.
06 · Where the platform goes
The registry becomes the training set.
Every scan is already a labelled event. Over time that’s a clean operational dataset — and a foundation for intelligence that stays grounded in what the platform actually records.
Predictive maintenance
Usage hours and state history surface the assets most likely to need service before they fail in a unit.
Utilization forecasting
Anticipate demand by department and shift; pre-position equipment instead of chasing it.
Operational copilot
Ask the registry plainly — “which pumps are idle in Imaging?” — grounded in real records, not guesses.
Workflow intelligence
Spot where turnaround stalls — long cleaning queues, slow returns — and where the process needs help.
Anomaly detection
Flag the unusual: an asset that never returns, a unit hoarding pumps, a state that’s been stuck too long.
Intelligent routing
Match a request to the nearest suitable asset and suggest the handoff — before a shortage delays care.
Roadmap — grounded in the data the platform already produces; no model where a rule will do.
Want a walkthrough of the platform?
Happy to talk through the lifecycle engine, the role-based surfaces, and how new asset classes get added.