sethserver.com Subscribe
A white and turquoise robot wearing a doctor's coat stands beside a hospital bed where a patient with black curly hair and an orange cast on their arm lies under turquoise bedding. Behind them is a white board with a light blue heart, and green potted plants flank both sides of the scene against a turquoise and white background.

The Doctor is in Silicon: AI Isn't Replacing Your Doctor, It's Upgrading Them

By Seth Black • Updated: September 17, 2026

AI · 10 min read

Like this kind of writing? Get one email a week with notes on startups, AI, and the occasional strong opinion about Python: subscribe to the newsletter.

The first time I saw a company brag about "AI automation," it turned out to be a spreadsheet with a nicer haircut. A few weeks into the job, I learned the "model" was mostly column mapping, data formatting, and a support team quietly doing the real work off to the side. I got the classic line: "Come to our office and watch us work." That's not artificial intelligence. That's Excel with a witness protection program.

Healthcare is full of that same temptation. Big promises. Small reality. But the interesting part is: real AI in medicine isn't mainly about replacing doctors. It's about replacing the junk work around doctors. And that's where the upgrades actually land.

Hospitals and clinics already have plenty of smart people. What they don't have is time. Or clean data. Or a workflow that doesn't feel like it was designed by a committee that hates joy.

The boring parts are the expensive parts

If you've ever been in a clinic waiting room, you've already seen the problem. Intake forms. Repeated questions. Insurance details. Medication lists that get typed three different times by three different people.

Doctors aren't slow. The system is slow.

Here's a normal day in a normal clinic:

None of that improves care. It's just plumbing. And plumbing is expensive when it's done manually.

AI is a good fit for:

This is the stuff that burns out teams. It's also the stuff that makes care worse because it steals time from the actual patient.

A useful mental test: if the task is mostly reading, sorting, reformatting, and copying, AI can probably help. If the task is mostly judgment under uncertainty, you still want a clinician in the loop.

"Diagnostics AI" is the flashy demo. Intake AI is the paycheck.

Diagnostics gets headlines because it's dramatic. "AI detects cancer better than humans" is a great pitch deck slide.

But if you want real value fast, look at the front desk and the nurse station.

Intake is where clinics lose time and accuracy. Patients don't speak ICD-10. They speak human. They say stuff like:

That's not useless. It's just unstructured. A good intake system can turn that into a clinician-friendly starting point.

Imagine a patient types: "I get dizzy after standing, heart races, worse after hot showers, started after COVID." A decent system can ask follow-ups, normalize the timeline, and hand the clinician something like:

Not a diagnosis. A clean starting point.

That's an upgrade.

And it can be very practical. You can build intake AI as a guided chat that does three simple things:

  1. Collect: Ask targeted follow-ups based on what the patient says.
  2. Normalize: Convert "a while ago" into "~6 months," and "heart races" into "palpitations/tachycardia (patient-reported)."
  3. Summarize: Produce a structured note and a short narrative the clinician can scan.

The tradeoff is obvious: if you ask too many questions, patients abandon the form. If you ask too few, clinicians don't trust it. The sweet spot is usually "short first pass, then adaptive follow-ups."

A good pattern is:

Also: don't pretend it's a doctor. Label it as an intake assistant. People are fine with that. They just want the visit to be smoother.

Chart summarization: the hidden time sink

If you want to see clinician pain, watch someone scroll through a chart with 10 years of notes. Half of it is copied forward. A quarter of it is irrelevant. The rest is buried in PDFs.

Summarization sounds simple until you try it. A good summary has to answer:

A bad summary is worse than no summary because it creates false confidence.

So the implementation detail that matters is grounding. The model should cite sources in the chart. Not in an academic way, but in a "this came from the cardiology note dated X" way.

A workable approach looks like:

Clinicians don't need poetry. They need a reliable index.

Back-office workflows: where money leaks out

Everyone talks about "saving doctors time," which is true. But the other big lever is back-office work that delays care and burns cash.

Prior auth is the classic villain. It's not medically hard. It's administratively hard.

A prior auth packet often needs:

Most of that is document assembly. AI can help by:

The tradeoff: you must keep humans in the loop, because a wrong code or missing contraindication can cause denial or, worse, a compliance problem. Think "draft + checklist," not "auto-submit and pray."

Billing and coding is similar. AI can suggest codes based on the note, but it should also show why it suggested them, and what documentation is missing to support them. Otherwise you get upcoding risk, audits, and a mess.

Scheduling is another quiet win. Clinics lose appointments because of simple friction: phone tag, unclear instructions, patients not knowing where to go. AI can handle:

Again, not magic. Just fewer dropped balls.

Follow-up messages: the endless loop

Patient portals are great until you realize they create a second job for staff: answering the same questions forever.

A safe and useful AI system can draft replies like:

But the key word is draft. You want a clinician or nurse to approve, especially for anything that could change a plan.

Implementation detail: build a library of clinic-approved templates, and let the model fill in the blanks from the chart. That keeps tone consistent and reduces hallucinations. It also makes the legal team less twitchy, which is its own kind of medical necessity.

Small language models are the quiet win here

I'm still obsessed with small language models. I want these things shrunk down enough to live on a phone, or at least run close to where the data lives. Healthcare data is sensitive, and shipping everything to a giant cloud model is not always the smart move.

A practical setup looks more like:

This isn't just a privacy thing. It's also a reliability thing.

If your workflow depends on a cloud call, you inherit:

Local models give you stable behavior and predictable costs. They also make it easier to prove where data went, which matters in healthcare.

The tradeoff is capability. Small models can be great at narrow tasks (cleanup, extraction, routing). They can struggle with long-context reasoning across a huge chart. That's why hybrid is realistic: local first, cloud only if needed, and only with redaction and consent.

A simple architecture that works:

  1. Redact locally: remove names, addresses, phone numbers, and anything not needed for the task.
  2. Route the task: is this extraction, summarization, drafting, or classification?
  3. Run locally if possible: small model + rules + templates.
  4. Escalate if necessary: send minimal context to a larger model, log it, and store outputs with citations.

This is the same pattern I keep thinking about for manufacturing too. Smaller AI chips. Smaller robots. More local autonomy. Less "send it to the mothership and wait."

Healthcare has different constraints, but the architecture rhyme is there.

The real risk: fake AI and hidden humans

That old SaaS job taught me something: if a company won't show you how the sausage is made, it's probably because the sausage is made of people.

Medicine can't afford that. If your "AI scribe" is actually a human in another country cleaning up notes at 2 a.m., you have a privacy and compliance nightmare. Also, the latency will be "mysteriously variable," which is a polite way of saying "someone went on lunch break."

There's also a subtler risk: even if humans are "quality checking," you need to know who they are, what they can see, and what gets stored. A clinic can't just shrug and say "the vendor handles it."

So I look for boring proof:

If a vendor can't answer those questions plainly, that's the answer. The warning signs that distinguish real AI products from manual labor disguised as automation apply just as much in healthcare as anywhere else.

Doctors stay. The admin sludge goes.

Replacing doctors is a bad idea and a worse product plan. Upgrading them is realistic.

Give clinicians cleaner notes, better summaries, fewer clicks, and fewer repetitive questions. Let staff focus on patients instead of chasing forms. Do that, and you get higher accuracy because humans have time to think again.

The best version of "AI in healthcare" is boring in the right way:

No robot doctor. A doctor with fewer stupid obstacles.

-Sethers

Share this post
Newsletter

One email, once a week.

Notes on databases, systems, and the occasional strong opinion about Python. No spam, unsubscribe anytime.

Seth Black
Written by

Seth Black

Engineer and founder based in Texas. Writes about databases, AI, and running things in production. Embeds in small teams as lead engineer.

More from AI

View all →
AI

How to be a Good Farrier: What the Car Teaches Us About AI and Your Job

Nov 10, 2026
AI

Principle of Least Privilege in the AI Age

Apr 14, 2026
AI

How to Actually Secure MCP (Model Context Protocol)

Apr 14, 2026