A half-century-old textbook on congenital heart disease. A chapter on Ebstein's anomaly. A comparison that changed how I think about evidence, AI, and what we owe the next generation of physicians.
Move 37 was not a parlor trick. It was a warning. Physician-developers need to be ready for the moment AI starts finding medically important patterns our inherited maps never taught us to see.
HealthBench Professional shows AI has already crossed the threshold in clinical writing and documentation. The real lesson is not replacement. It is that physician-developers need to build the harness.
Joe Riley trusted AI over his oncologist and died of a treatable cancer. His tragedy wasn't naivety — it was earned distrust, amplified by a machine that had no way to know the difference.
Your clinical RAG system is not hallucinating because the model is bad. It is hallucinating because your document pipeline is broken. Here is what clinical PDF parsing actually requires, and why Docling is the fix.
Consumer AI tools like ChatGPT and Claude are useful. But a physician-developer who deploys a locally fine-tuned model on controlled infrastructure has something more powerful: a clinical tool that learns your practice, respects your data, and costs less at scale.
Documentation automation is not a typing solution. It is a workflow design problem. For physicians and physician-developers, the real goal is protecting clinical judgment from administrative drag.
A TEDx pitch says physicians should build AI. I agree. But the work that matters is governance, validation, and delivery, not one-afternoon demos.
Nobody lost your fax. The system was designed to lose it. Referral failures are not clerical accidents. They are the predictable result of clinical infrastructure built for a different era.
Race-based clinical algorithms in kidney care and obstetrics did not just reflect bias. They operationalized it. Physicians now have a responsibility to challenge the software, logic, and architecture that turn racial fiction into patient harm.
They are not asking it for fun. They are asking it because the triage line puts them on hold for 45 minutes. The threat is not the technology. The threat is the system that made the technology necessary.
Physician passivity in health tech is not an accident. It is a business model. Understanding the structural incentives is the first step to building outside of them.
When families face periviability, they search before they call. What they find shapes everything. Here is why physician-developers have a responsibility to build better.
Every physician using an AI tool has heard the liability question. Most of us answer it wrong. The real answer is not about insurance. It is about who was in the room when the tool was designed.
The AMA opened the door. Physicians must decide what to do with it. The survey data is not a comfort. It's a challenge. Here's what physician-developers do next.
Maternal-Fetal Medicine Specialist & Founder, CodeCraftMD
Maternal-Fetal Medicine Specialist & Founder, CodeCraftMD