Technology 4 min read

Doctors Who Code: From GitHub to Medical AI

A practical path for physicians who want to move from GitHub basics to building real medical AI projects.

By Dr. Chukwuma Onyeije, MD, FACOG

Maternal-Fetal Medicine · · 4 min read

Listen to this post

Doctors Who Code: From GitHub to Medical AI

0:00 / 0:00
On this page1 sections

Most physicians do not need another speech about why technology matters in medicine.

We already live inside broken systems. We already feel the friction. The real question is whether physicians will keep adapting to tools designed by other people, or whether more of us will learn to build.

This series is a practical path into that work.

It starts with GitHub, not because version control is glamorous, but because unfinished work needs a real home. It then moves into project scoping, structured clinical data, and the realities of finding and building medical AI tools that are actually worth your time.

This is not a series about becoming a full-time software engineer. It is a series about technical ownership. About learning enough to turn a recurring clinical frustration into a tool, a workflow, or a first real project.

If you are a physician who has been circling this world without entering it, start here.

Series Roadmap

  1. Stop Lurking: Why Physicians Should Start GitHub Before They Feel Ready
  2. GitHub for Physicians: Why Version Control Changes How You Build
  3. Your First Week on GitHub as a Physician: A Practical Starter Plan
  4. Three GitHub Projects Physicians Can Actually Finish
  5. JSON for Physicians: The Structured Data Your Clinical AI Actually Needs
  6. Navigating Medical AI on GitHub: What Is Worth Your Time
  7. Your First Medical AI Project on GitHub: How to Choose One You Will Actually Finish

Share this article

Share X / Twitter Bluesky LinkedIn

Related articles

A physician-developer in a white coat holding a glowing GitHub Gist icon, connected by streams of light to clinical diagrams, decision trees, and code panels around him
Physician Development Featured

GitHub Gists: The Most Underrated Tool Every Physician-Developer Should Be Using

GitHub Gists look like scratch space for code snippets. Used correctly, they become a version-controlled clinical reference library that decks, apps, and blog posts can all cite from a single source.

· 9 min read
githubgithub-gistsphysician-developer
Physician at a workstation reviewing medical images, code, and system monitoring dashboards side by side
Clinical + Code Featured

Doctors Who Code: Build Systems, Not Just Models

A TEDx pitch says physicians should build AI. I agree. But the work that matters is governance, validation, and delivery, not one-afternoon demos.

· 8 min read
aidoctors-who-codemedical-ai
Cinematic physician-developer workflow showing research inputs flowing from Telegram and source materials into structured drafts, PDFs, and a publishable editorial pipeline
Technology Featured

Inbox to Insight: Building the DoctorsWhoCode Engine

Physicians do not have an information problem. We have a conversion problem. Inside the Telegram-driven research engine I built to turn links, papers, transcripts, and videos into drafts, PDFs, and durable editorial records.

· 10 min read
doctors-who-codephysician-developerresearch-automation
Chukwuma Onyeije, MD, FACOG

Chukwuma Onyeije, MD, FACOG

Maternal-Fetal Medicine Specialist

MFM specialist at Atlanta Perinatal Associates. Founder of CodeCraftMD and OpenMFM.org. I write about building physician-owned AI tools, clinical software, and the case for doctors who code.

LinkedIn X / Twitter About Chukwuma Onyeije, MD, FACOG