One platform
Strong inside. Simple outside. Built for the future.
Every Application stands on one platform, built on our own hardware and software. Strong inside: tags, readers and access points that see what moves, and one system that knows what, who, where and when, in real time. Simple outside: each person sees what their role needs, on screens designed for the work they do, from the porter’s phone to the director’s dashboard. And because it is one foundation, a hospital can start with one problem and add the next without starting over.
True real time
A hospital that runs on Mutrack never stops moving, and every movement is a signal. Take one minute, at 10:02. Twenty porters walk between jobs, each phone calling out over Bluetooth once a second: 1,200 signals. A hundred and fifty doctors wear badges that do the same: 9,000 more. Three hundred pieces of linen are scanned into the Main Store, and five hundred in the Dirty Room. Forty infusion pumps tell the access points where they are, every ten seconds. The platform reads every one of them, and each finds its way to the Application that understands it and the person whose work it is. Pause the minute at any moment to see what each signal is, where, when, how it was seen, and for whom.
10:02:00
0 signals
Each signal: what or who · where · when · how it was seen → for whom
-
Dispatcher0
- New job · Wheelchair, Ward 7 → X-ray
- New job · Infusion pump, ICU → Ward 7
- Accepted · Wiroj, on his way
- New job · Linen delivery, Main Store → Ward 7
WirojSenior Porter
-
Linen0
- Dirty Room · Ward 7’s bag counted, 46 pieces
- Main Store · Ward 7 below par, a delivery asked of Dispatcher
- Send to laundry · Dirty Room → Clearwater Laundry
PafunLinen Manager
-
People0
- Dr. Kamala · Ward 7, since 09:38
- Dr. Niran · Outpatient Center, since 08:05
- Dr. Nalintra · Ward 7, 09:07–09:44, 37m
SudaHead of Internal Medicine
-
Things0
- IP-0412 · leaving ICU, with Siriporn
- IP-0412 · arrived in Ward 7
KanokjanBME Manager
Just enough technology
We don’t put one technology on every problem. Each one gets just enough to solve it well, at a price that makes sense, from hardware we choose for the job: RFID where a whole cart must be counted at once, Bluetooth where equipment and people must be found as they move, and the hospital’s own Wi-Fi where staff already carry a phone. However different they are underneath, Admin runs them as one, and every Application reads the same facts.
-
DispatcherWi-FiBLE
Who is free, and nearest?
Porters already carry a phone to accept their jobs, so the hospital’s own Wi-Fi tells Dispatcher where they are. They accept their jobs and update each one’s status right on the phone.
Why not a badge alone? A badge can say where a porter is, but only a phone can take the job.
Learn more about Dispatcher → -
LinenRFID
How many pieces went out, and how many came back?
A passive tag sewn into every piece needs no battery and lasts through the wash. A reader counts a whole cart in seconds, without opening a bag.
Why not Bluetooth? A battery in every sheet, washed every day, would cost far more and need changing.
Learn more about Linen → -
PeopleBLE
When is the team where the work is?
A badge on a lanyard, with nothing to press. Access points see it pass, and People’s rule turns that into presences, named to the ward or the room.
Why not RFID? It needs many readers deployed across the hospital, a far larger investment for it to make.
Learn more about People → -
ThingsBLE
Where is the infusion pump?
A small battery tag on each device is heard by access points across the wards, so where it is stays known as it moves, with no one scanning it.
Why not RFID? A reader knows only where a device last passed one, not where it is now.
Simple outside, connected inside
Inside, one system. Outside, a screen for each person, made for the work they do and nothing more. We designed them by watching real hospital work, across roles and shifts: the nurse who needs a wheelchair now, the supervisor who must know where every pump has gone. Each sees only what their work needs, and the same facts underneath keep them all in step.
Ask once, then watch it happen
Kwanrat asks for a porter from the ward’s own screen. Dispatcher finds the right one, and she sees who is coming and when, without a single phone call.
Know how much every device is used
Bussaba sees each kind of equipment: what it is, and how many hours of the day it really works, month by month, so the hospital buys and maintains only what it needs.
Patterns to look at, not verdicts
Wirada reads a month of the doctors’ presences against their schedules: patterns for a person to look into, never a verdict on anyone.
Staff Profile DashboardDoctors · last 30 days
We design every screen with care, because people spend their working day in it. Good design makes them more productive and the work easier, until managing work inside a hospital becomes something people enjoy. And what they do does not end on the screen: every Application gathers data as the work happens and comes with deep analytics, so a hospital understands more and makes better decisions, sooner. Because it all stands on one platform, its value lasts. A hospital can start small and add capabilities over time, without replacing what it has, reworking it, or meeting hidden costs as it grows.
Built for the future
We build Mutrack for the hospital’s work today, and for what it will need next. Location sits underneath most of that work: where people are, where things are, what waits and what moves. So we built that foundation once, and every Application stands on it, instead of becoming another tool on its own. Here is a hospital that runs all of them in its building today. Press play and let a day go by. On the next, it builds again, on its car park, and the new floors join the same platform the day they open.
What the second building shows holds for a second hospital too. One platform runs a single building or a network of sites, on the same infrastructure, with the same screens, and one partner to call. Growing this way takes more than the technology, though. The hardware has to be reliable, and looked after once it is in. The work itself has to change: routine steps done automatically, decisions made by the people closest to the work, and results measured, so a team sees what it has achieved and is rewarded for it. The data stays the hospital’s, ready to take out and use elsewhere. And the terms have to be fair. There is no Basic or Enterprise Mutrack, and nothing locked behind a paywall: every hospital gets every feature, and every update we make from here on, at no extra cost. Six hospitals already run on Mutrack this way, and this is only the beginning.
Where it goes next: Toward a Precision Society →