Built by an engineer and an anesthesiologist
Not a company. Not a product team. Just two people who thought bedside monitor training shouldn't require a manikin that costs as much as a car.
Where it started
One of us builds software. The other spends their working life next to real bedside monitors, running codes and teaching residents to read a rhythm strip under pressure. Between the two of us, patientmonitorsimulator started as a weekend project: could a phone convincingly act as a training monitor if another phone controlled it?
The first version was rough. It looked like a monitor and not much else. What actually made it useful came later, from watching a real training session and noticing what didn't work: a stop button that only stopped in one direction, a blood pressure cuff that read out instantly instead of taking its time, a rhythm label sitting right there on screen giving the answer away before anyone had to look at the waveform.
Built from bedside feedback, not a feature list
Almost every detail in patientmonitorsimulator traces back to a specific note from an actual training session rather than a brainstorm. That's why the stop and pause buttons behave like real ones on a real monitor. It's why a "poor perfusion" toggle exists at all: because a badly placed probe reading falsely low is something every anesthesiologist has seen and no simulator bothered to model.
It's since been run in roughly a hundred real training exercises, all led by that same anesthesiologist, and each one has fed something back into the product.
We kept it free while we build it out, because the point was never to sell software. It was to make one particular kind of training easier to run, for anyone who needs it: a nursing program with no simulation budget, a paramedic instructor working from a laptop, a doctor prepping a resident for their first night shift.