Tag

openmfm

9 posts

Editorial illustration of a pregnant patient and physician discussing research calmly during a prenatal consultation.
Physician Development Featured

What Physicians Owe Patients After a Frightening Research Headline

A prenatal stress study shows why physicians must explain the limits of research, support patients, and build accessible tools for better clinical conversations.

· 6 min read
Clinical CommunicationEvidence-Based MedicinePrenatal Stress
Physician reviewing glucose-monitoring educational materials beside the title: I Had a Clinical Presumption. I Built Tools to Examine It.
Technology Featured

I Had a Clinical Presumption. I Built Tools to Examine It.

A question about glucose monitoring became an evidence review, two presentations, and a lesson in why clinical responsibility includes the interface.

· 6 min read
Physician DevelopmentEvidence-Based MedicineClinical Research
Two physicians designing clinical software beside a patient, with interfaces for ambient documentation, evidence-based algorithms, and standardized patient care
Physician-Developer Featured

Why I Rebuilt Doctors Who Code

Doctors Who Code began as a blog encouraging physicians to learn programming. It is now a learning platform for physicians who want to use AI with judgment and build clinical tools that improve care.

· 13 min read
doctors-who-codephysician-developermedical-education
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-developer sitting with a laptop at night, surrounded by visible signs of technical friction and clinical responsibility
Technology Featured

Burnout Is Not From Working Too Hard. It Is From Working on the Wrong Things.

For physician-developers, burnout often comes from low-value technical friction. The answer is not more endurance. It is better delegation to systems, automation, and agents.

· 7 min read
automationphysician-developerburnout
Physician-developer reviewing a Markdown-based clinical presentation workflow on a monitor in a dark, cyan-lit workspace
Technology

My Slides Became Code: Why I Use Marp for AI-Generated Presentations

Marp lets physician-builders turn reviewed knowledge into version-controlled, AI-assisted teaching decks without surrendering clinical responsibility.

· 9 min read
doctors-who-codemarpai-generated-presentations
Dark terminal screen showing timestamped biometric log entries with the text LOGS BEFORE INTELLIGENCE centered in the foreground
Clinical + Code

Logs Before Intelligence: Why Data Discipline Must Precede AI Insight

Before you build any AI feature, you must first build the log. The principle every physician-developer needs to internalize before writing a single line of intelligence code.

· 8 min read
ai-in-medicineclinical-data-architecturedata-discipline
Patient alone in a hospital labor and delivery room, looking at a smartphone with a worried expression
Clinical + Code

The Limits of Viability: What Patients Find Before They Find You

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.

· 7 min read
periviabilitypatient educationOpenMFM
Physician-developer building clinical knowledge infrastructure
Blogging

The Protocol-to-Website Industrial Complex:

By Dr. Chukwuma Onyeije, MD, FACOG | Maternal-Fetal Medicine Specialist & Medical Director, Atlanta Perinatal Associates

· 11 min read
acog-guidelinesclinical-knowledge-managementclinical-microsites