Healthcare software, three kids,
and a quiet belief that EHRs
can be better than they are.

Minnesota born and raised. I like to think I enjoy the misery of living here — cold winters plus terrible sports teams equals fantastic.

Father of three kids who try to play every activity they hear about, which means if I'm not coding, I'm driving them somewhere. Thankfully my wife juggles her own career while ensuring our family runs smoothly — she makes sure we take vacations and celebrate the milestones of our lives (birthdays, anniversaries, Tuesdays).

I've been fortunate. I'm a software engineer who has spent my entire career in healthcare, which hopefully means the code I ship helps someone. A good portion of that was EHRs — including ten years at a large EHR vendor. I owe that company a ton; it's where I learned what it means to get software out the door, and also how a large company can stay focused on doing what it has always done, slow to change. Then came Datica (formerly Sansoro Health), my real introduction to the startup world — many hats, the whole product pipe, and chasing the maddening, elusive single layer between any health system's EHR and any app built on top of it. I really wished it had worked.

Lead engineer at Vida since 2019 — a small company focused on clinical trials and AI, mostly in lungs. Cloud engineering, orchestrating AI models, and mentoring the junior engineers who pretend to listen to me. It's a genuinely interesting time to be building with AI tech.

My career dream is to lead a team building a new EHR from the ground up. I'm aware of how dumb that sounds — it's similar to saying I want to build an OS to compete with Windows. But I believe software should enhance, not hinder, quality healthcare, and I want to remove software from the list of obstacles. The EHR vendors are good people working on extremely complicated problems. I just think we can demand better, and health systems need to understand their own needs instead of relying on the vendor to tell them. The world probably doesn't need another EHR, but building one is a great way to learn how to build something like that — so why not.