Deep dives into healthcare IT, enterprise systems, and the technology behind the products we build. Written by engineers, for engineers.
I walked into a surgical center and found staff frantically calling suppliers over a missing implant. That chaos is costing healthcare $25.7 billion a year. Here is how we fixed it for a 25-center network.
I watched a claims examiner spend 9 minutes reviewing a $120 cleaning. Multiply that by 500,000 claims a month. Then we built a system that does it in 47 seconds. Here is what we learned.
First day back from winter break. 50,000 users hit our servers at 8 AM. The old system crumbled. Here is the architecture we built so that Monday morning never happens again.
I got the call at 6:47 AM. A manufacturer had spent $2.3M on an ERP rollout and their production floor was at a standstill. Here is how we fixed it — and how to avoid it entirely.
A practice manager ran a routine audit and found $1.2 million hiding in five billing patterns. That discovery is not unusual. Here is how AI-assisted coding makes it automatic.
I ran a real experiment: 500 resumes, 4 prompt iterations, 90 days of tracking. The AI-generated resumes got 31% more interviews. Here is the prompt engineering journey that got us there.
After three weeks of scrutiny, our SOC 2 auditor said something we never expected: "This is one of the cleanest RBAC implementations I have seen." Here is how we built it.
A VP of Operations stared at a loading spinner for 47 seconds. We had two weeks to fix it or lose the contract. We cut it to 180ms without rebuilding anything.
A healthcare provider paid $2.1M because a developer pushed PHI to a public S3 bucket. I have spent a decade making sure that never happens to my clients. Here is the architecture.
It was 2 AM and 50,000 lab results had just been routed to the wrong patient charts. That incident made us tear down 47 point-to-point integrations and build something better.
A $340 bearing failed and cost $847,000. The maintenance team had inspected the machine two weeks earlier and found nothing wrong. So we built a system that actually sees failures coming.
I broke my wrist and suddenly could not use my own software. That six-week experience changed everything I thought I knew about building products that actually work for everyone.
Get our latest technical insights delivered to your inbox. No spam, just valuable engineering content.