Built by someone who's still on shift.
ResponderOS wasn't designed in a boardroom. It was built by a working EMS Captain who needed it for the next shift.
I'm an EMS Captain with a high volume municipal EMS department who built ResponderOS because I was living the problem it solves.
I came up as a Firefighter/Paramedic in Newport News, then went on to serve with a busy municipal EMS department. I have served as a Senior Paramedic, an ALS Field Training Officer, and eventually an EMS Captain managing field operations, personnel, and quality assurance across a busy district. Along the way I've served as a SWAT medic embedded with a local police tactical team, marine medic supporting maritime operations, and as a Staff Sergeant in the Army National Guard, where I additionally led a hazmat and technical rescue team (CERFP) and ran a medical section supporting more than 100 soldiers on a forward operating base in Iraq.
I hold a Master of Public Health from the University of Nebraska Medical Center and a Bachelor of Science in Health Sciences from Old Dominion University. My graduate research on non-emergency utilization of EMS is published through UNMC's digital commons. I've built and run a medical instruction program, taught as a certified instructor, and spent years analyzing EMS system performance data to drive decisions at the leadership level. That same instinct shaped how ResponderOS reports on a shift.
None of that makes me a software company. It means every module in this platform was designed by someone who has run the call, filled out the form, sat in the QA review, and stood the incident command post, not someone guessing at what the job looks like from the outside.