You don't need to become a programmer to work at the intersection of surgery and AI. Here is the realistic path, from one surgeon's experience.
The most common question we hear from clinicians is also the most important one: where do I even start?
01You don't need to become a programmer
The single biggest misconception about "getting into AI" in medicine is that it requires a computer science degree. It doesn't. What it requires is:
- A clinical problem you understand deeply
- A working vocabulary of how AI systems are built and validated
- One collaborator who can code
02Start with the problem, not the tool
Every successful medical-AI project we know started with a clinician who was frustrated by a specific, repetitive task. In our case, it was the manual cross-referencing of MRI scans in MS follow-up: a task that takes up to 45 minutes per study and varies between observers.
03The three-month starter plan
- Month 1: Learn what a segmentation model actually does. Not how to build one: just what its inputs, outputs, and failure modes are.
- Month 2: Shadow an AI project. Find a medical imaging group, a hospital R&D department, or a company like ours and follow one project end to end.
- Month 3: Define your own problem. Write down the task that eats your time and think about what an automated version would look like.
04What actually matters
Medical AI companies are small, multidisciplinary, and hungry for clinical insight. The people who thrive are the ones who bring a deep understanding of the problem: not the ones who can write the most code.
The fastest way to learn is to be inside one of these companies. That is exactly what our Innovation Hub is for: clinicians and engineers bring their ideas, and we figure out together how to make them real.
This guide is just a start.
If you want to start your own journey, share an idea, or simply talk to our team, reach out at the Innovation Hub. A conversation, no pressure.
Write to the Innovation Hub