Vibe Coding versus Clinical Reality

AbstractIn February 2026, a full-time interventional cardiologist placed third in a global coding competition with a postvisit patient support application called postvisit.ai. Many top participants had no formal engineering background but were domain experts who could describe a problem precisely enough for AI tools to translate it into working software. This process has been called "vibe coding." We discuss what it means and whether it has any relevance to clinical reality. Although AI tools have dramatically lowered the barrier to building a prototype, turning a working demo into a safe, regulated product ready for clinical use still very much requires engineers, security specialists, and regulatory expertise. The EU Medical Device Regulation, the U.S. Food and Drug Administration guidance on AI in healthcare, and the privacy requirements of the General Data Protection Regulation and the Health Insurance Portability and Accountability Act all demand professional teams and rigorous processes that no amount of vibe coding can replace. None of this should discourage physicians from building. The natural next step is for them to move from consulting on software design to actively shaping the tools that they use, creating a new generation of physician-builders.