Friday, September 25, 2026

Ava Little Didn't Want to Sit on the Sidelines: What Her Story Reveals About the Broken Patient Experience

Healthcare doesn't happen in departments. It happens in the spaces between them—and that is where patients, physicians, and practices often lose time, trust, and money.



“Care does not have to be finished in one encounter. But it must not be allowed to disappear between encounters.” — Alan P. Feren, MD

 

That sentence stopped me.

Not because it is complicated.

Because it is obvious.

And yet much of modern healthcare is designed as though the opposite were true.

The appointment ends.

The physician moves to the next patient.

The patient leaves.

The chart closes.

The referral goes somewhere.

The claim enters another system.

The authorization enters another queue.

The bill arrives weeks later.

And somewhere along the way, everybody assumes somebody else is taking care of the rest.

That is where the trouble begins.

A 14-year-old girl in Michigan offers an unexpectedly powerful way to understand the problem.

Her name is Ava Little.

Ava was diagnosed with Charcot-Marie-Tooth disease, or CMT, at three years old. Fourteen years later, the condition remains part of her life. She has dealt with physical challenges, unwanted attention because of the way she walks, and the ordinary complications of growing up while living with a genetic disorder.

But she made a choice.

She decided she did not want to sit on the sidelines.

As WDIV Local 4 reported this week, Ava has turned her experience into advocacy, fundraising, and awareness work for CMT. She is captain of the “Little But Mighty” team participating in the annual Walk for CMT in Lansing. Her involvement also earned her a Go-4-It Award.

Her father, Matthew Little, knows CMT personally.

So does Ava's brother, Ethan Little.

An earlier Charcot-Marie-Tooth Association family profile identified Ava with her parents, Lisa Little and Matt Little, and her brother Ethan.

Matthew explained to WDIV that everyone in the family has CMT1A, but the condition affects them differently. He and his son have relatively mild symptoms, while Ava experiences the disease more intensely.

Same family.

Same broad diagnosis.

Different experience.

That distinction is the real story.

Because healthcare has a similar problem.

We keep designing healthcare around the diagnosis, the encounter, the claim, or the department.

But the patient experiences none of those things separately.

The patient experiences one life.

And one healthcare journey.


Ava Little's Story Is Not Really About CMT

It is tempting to read Ava's story as a story about rare disease.

It is.

But it is also about something much bigger:

agency.

Ava didn't choose CMT.

She didn't choose the symptoms.

She didn't choose the questions from strangers.

She didn't choose the limitations imposed by her condition.

But she could choose how she responded.

And she chose action.

She chose advocacy.

She chose fundraising.

She chose community.

She chose not to disappear behind the diagnosis.

That matters to physicians.

Because patients don't want to be passive recipients of healthcare.

They want to understand what is happening.

They want to know what happens next.

They want to know who is responsible.

They want their concerns remembered.

They want the system to recognize that they are a person rather than an encounter number.

And increasingly, they want something else:

They want visibility.

Not necessarily visibility into every technical detail.

Visibility into their own journey.

What happened?

Why?

What comes next?

What do I need to do?

Who do I contact?

What will this cost?

Why did insurance deny it?

Why am I receiving this bill?

Why does the bill say one thing while the insurance statement says another?

Those questions aren't peripheral to healthcare.

For the patient, they are healthcare.


The Healthcare Industry Has a Strange Definition of “Patient-Centered”

Here's my slightly provocative question:

If the patient has to navigate the system alone, how patient-centered is the system?

We love the phrase.

Patient-centered care.

Patient engagement.

Patient empowerment.

Patient experience.

Digital health.

Consumer healthcare.

Beautiful words.

But then the patient gets a bill they can't understand.

Or a referral disappears.

Or a prior authorization stalls.

Or they have to call the insurance company because the physician's office can't determine why something was denied.

Then the language suddenly changes.

“That is the payer's issue.”

“That is billing.”

“That is scheduling.”

“That is utilization management.”

“That is the clearinghouse.”

“That is the patient's responsibility.”

Technically, those statements may be correct.

Humanly, they are almost meaningless.

The patient doesn't have a payer problem.

The patient has a healthcare problem.

And they expect the people providing healthcare to help navigate it.


The Patient Doesn't Know Your Organizational Chart

This is one of the most important principles for practice owners:

The patient does not experience your organizational chart.

They don't know:

  • who handles eligibility
  • who handles coding
  • who submits claims
  • who works denials
  • who posts payments
  • who handles appeals
  • who manages prior authorization
  • who handles credentialing
  • who owns the patient portal
  • who manages your clearinghouse

And frankly?

They shouldn't have to.

A patient has enough on their plate.

They're sick.

Or worried about becoming sick.

They're taking care of children.

They're taking care of parents.

They're working.

They're missing work.

They're paying for medications.

They're arranging transportation.

They're trying to understand what a physician just told them.

They don't need another part-time job:

Insurance Claims Analyst.

Yet that's effectively what healthcare sometimes asks them to become.


Here's the Contrarian Part

Medical billing is not a back-office function.

There.

I said it.

And I know some revenue-cycle professionals will disagree.

That's okay.

Let's define what I mean.

I'm not saying billing is clinical care.

It isn't.

I'm saying the consequences of billing are part of the patient experience.

If a patient receives an incorrect bill, that affects trust.

If a claim is repeatedly denied, that affects access.

If an authorization delays treatment, that affects care.

If a financial estimate is unclear, that affects decision-making.

If staff spend hours chasing a claim, that affects practice capacity.

If physicians spend hours dealing with administrative problems, that affects the amount of time available for clinical work.

The department may be called “revenue cycle.”

The patient experiences it as:

“What happened to my healthcare?”

That's a very different perspective.


The 15-Minute Appointment Is Not the Boundary of Care

This is where Alan P. Feren, MD's recent essay becomes particularly relevant.

Writing this week, Feren argues that care doesn't have to be completed in one encounter, but it cannot simply disappear between encounters. He distinguishes the medical service from the larger process of actual care: explanation, treatment planning, follow-through, reassessment, and responsibility for what happens next.

That idea should change how practice owners think about operations.

Because healthcare doesn't end when the physician clicks:

Sign Encounter.

The patient still has to:

  • obtain the medication
  • schedule the referral
  • complete the test
  • receive the result
  • understand the result
  • follow the treatment plan
  • navigate insurance
  • return for reassessment
  • pay the appropriate balance

The clinical encounter is an event.

Healthcare is an episode.

And the episode is where many systems fail.


The Claim Is Also an Episode

Think about a claim.

It doesn't simply exist.

It travels.

Patient information enters the system.

Eligibility is checked.

The encounter occurs.

Documentation is completed.

Codes are assigned.

The claim is created.

The claim is scrubbed.

The claim is submitted.

The payer adjudicates it.

Payment arrives.

The payment is posted.

A denial may appear.

Someone investigates.

Someone corrects something.

Someone appeals.

Someone follows up.

Then perhaps the patient receives a balance.

That's not one event.

It's an ecosystem.

And every handoff is an opportunity for information to disappear.

Which brings us to an uncomfortable question:

Why do we design healthcare around handoffs and then act surprised when things fall between them?


The Handoff Tax

Every time information moves from one person, system, department, or organization to another, there is a potential cost.

Call it the handoff tax.

It isn't always financial.

Sometimes it is:

  • duplicated work
  • delayed work
  • missing information
  • contradictory information
  • manual reconciliation
  • patient confusion
  • staff frustration
  • physician interruption
  • delayed payment

The more handoffs, the more opportunities for something to become unclear.

And healthcare has become spectacularly good at creating handoffs.

Physician to staff.

Staff to payer.

Payer to provider.

Provider to clearinghouse.

Clearinghouse to payer.

Payer to patient.

Patient back to practice.

Practice back to payer.

At some point you almost expect a marching band to appear.


The Administrative Tax on Medicine

The scale of administrative work isn't theoretical.

The American Medical Association's 2025 Prior Authorization Physician Survey found that physicians complete an average of 40 prior authorization requests per week, while physicians and staff spend an average of 13 hours per week completing them. The AMA reported that 95% of physicians say prior authorization delays necessary care, 94% say it contributes to burnout, and 26% report that it has contributed to a serious adverse event.

Read that again.

Thirteen hours.

That's not a little paperwork.

That's a significant portion of a working week.

And that's just prior authorization.

Add:

Claims.

Denials.

Eligibility.

Credentialing.

Documentation.

Coding.

Appeals.

Patient balances.

Payer portals.

Referral management.

And the occasional fax machine that apparently refuses to die.

The industry keeps calling this administration.

At some point, we should probably call it what it is:

operational infrastructure.


The Fax Machine Has Become a Healthcare Immortal

There are many mysteries in healthcare.

Why does a simple referral sometimes require three phone calls?

Why does a payer portal need another password?

Why does one payer accept electronic documentation while another asks for a fax?

Why can a claim be visible in one system but not another?

Why does someone occasionally say:

“We never received it.”

And why, after all the technological revolution of the last two decades, is a fax machine still somehow involved?

We have artificial intelligence.

We have cloud computing.

We have smartphones more powerful than the computers that sent people to the moon.

And somewhere in a medical office:

“Can you fax that again?”

Maybe the problem isn't that healthcare lacks technology.

Maybe healthcare lacks integration and operational discipline.


Stop Adding People to Broken Workflows

Here's another idea that may make some practice owners uncomfortable:

More staff is not always the answer.

Sometimes you genuinely need more people.

But before hiring another person, ask:

Why does this work exist?

Then ask:

Why does a human have to do it?

Then:

Why does that human have to do it repeatedly?

Then:

Why are we discovering the problem this late?

Then:

Could the problem have been prevented upstream?

Those questions are more valuable than simply asking:

“Who can we hire?”

Because a broken process with more people becomes a larger broken process.

It doesn't magically become efficient.


Your Best Employee May Be Spending Half the Day Fixing Yesterday

This is one of the hidden costs of healthcare administration.

Your smartest employee may not be creating value.

They may be repairing value that was already created incorrectly.

A claim was entered incorrectly.

Now someone fixes it.

Eligibility wasn't verified.

Now someone calls.

A modifier was missing.

Now someone researches it.

A payer denied something.

Now someone appeals it.

A patient doesn't understand the statement.

Now someone explains it.

A payment doesn't match expectations.

Now someone reconciles it.

The employee is working.

Hard.

Productively.

And yet the organization may still be losing.

Because the work is reactive.

The goal shouldn't simply be to make people better at cleaning up mistakes.

The goal is to create fewer mistakes to clean up.


The Denial Is Not the Victory

Here's a revenue-cycle paradox I think deserves more attention:

We celebrate denial recovery.

Of course we should recover legitimate revenue.

But imagine a hospital announcing:

“We repaired 8,000 plumbing leaks this year.”

Wonderful.

But the next question would be:

Why were there 8,000 leaks?

Healthcare sometimes does the same thing with denials.

We celebrate the amount recovered.

But we don't always ask:

How many of those denials should never have happened?

Recovery matters.

Prevention matters more.

The real operational question isn't:

“How good are we at fighting denials?”

It's:

“Why are the same denials happening again?”


Your Denial Report Is a Map

A denial report isn't merely an accounting document.

It is a map of system failure.

If eligibility problems keep appearing, something upstream may need attention.

If documentation-related denials recur, the clinical workflow may need improvement.

If one payer repeatedly produces a certain denial category, that pattern deserves investigation.

If claims from a specific provider or service line behave differently, there may be a process issue worth understanding.

If the same denial reason appears month after month, you don't have a denial problem.

You have an information problem.

The denial is simply where the problem became visible.


The Three Questions Every Practice Should Ask

Forget the 50-page dashboard for a moment.

Start with three questions.

1. Where are we losing money?

Not just total A/R.

Where?

Which payer?

Which service?

Which denial?

Which stage?

2. Where are we losing time?

Which tasks consume staff hours?

Which claims require repeated touches?

Which workflows cause the most interruptions?

3. Where are we losing trust?

What causes patients to call?

What causes confusion?

What generates complaints?

What financial questions are staff repeatedly answering?

The interesting part is that these three questions may have the same answer.


The Patient Bill Is a Product

Here's an idea I wish more practices considered:

Your patient statement is a product.

And like every product, it has a user.

The user is a human being who may not understand medical billing.

So ask:

Can they understand it?

Can they tell what service it relates to?

Can they understand what insurance paid?

Can they understand what remains?

Can they determine what to do next?

Can they find help?

Can they challenge an error?

Or does the statement essentially say:

“Here is a number. Good luck.”

We wouldn't design a consumer app that way.

Why do we tolerate it in healthcare?


Patients Don't Need More Transparency

They Need More Comprehensibility.

This distinction matters.

Healthcare loves transparency.

Show the patient more data.

Give them more documents.

Give them another portal.

Send another explanation of benefits.

Put another notification in the app.

Congratulations.

The patient now has 14 pieces of information and no idea what they mean.

Transparency without comprehension is just information overload.

The goal should be understandable information.

What happened?

Why?

What does it mean?

What should I do?

Who can help?

That is patient-centered administration.


And Then There's AI

Every healthcare conference currently seems to contain approximately seventeen presentations titled:

“The Future of AI in Healthcare.”

Most begin with a futuristic image.

Usually a glowing brain.

Sometimes a robot.

Occasionally both.

Then comes the inevitable statement:

“AI will transform healthcare.”

Maybe.

But here's the boring truth:

AI cannot compensate for a badly designed process simply because it has a better vocabulary.

If your workflow is broken, AI can automate the broken workflow.

Faster.

That's not necessarily progress.


Don't Automate Chaos

This should become a rule:

Do not automate a process you haven't understood.

Before deploying AI, map the workflow.

Where does the data originate?

Where does it change?

Where does it get duplicated?

Where does it disappear?

Where does a human intervene?

Why?

Where does the decision occur?

Who owns the exception?

What happens when the system is wrong?

Only then ask:

Where could AI help?

That's a much more sophisticated technology strategy.


Where AI Actually Makes Sense

AI is particularly interesting when it can help with work that is:

  • repetitive
  • rules-driven
  • data-intensive
  • time-consuming
  • pattern-dependent
  • difficult to prioritize manually

That can include areas such as:

  • claim review
  • denial categorization
  • workflow prioritization
  • payer-pattern detection
  • eligibility workflows
  • documentation checks
  • anomaly detection
  • administrative communication
  • work-queue optimization

But the goal should not be:

“Replace the humans.”

The goal should be:

“Stop wasting human judgment on mechanical work.”

That's a much better bargain.


The Human Still Matters

There is a dangerous misconception about automation.

That every human task is inefficient.

It isn't.

Some tasks require judgment.

Some require context.

Some require empathy.

Some require negotiation.

Some require clinical understanding.

Some require knowing when the rules don't fit the patient.

Technology should handle predictable work.

Humans should handle exceptions, judgment, communication, and accountability.

The future isn't:

Humans versus machines.

It's:

Humans doing the work that actually deserves humans.


This Is Why the Middleman Question Matters

For independent and small-to-midsize practices, another question deserves attention:

How much control should the practice surrender in exchange for convenience?

Outsourcing isn't inherently bad.

Neither is bringing work in-house.

The issue is visibility.

If a practice outsources billing but cannot answer:

  • why claims are denied
  • where A/R is accumulating
  • what staff are doing
  • what payers are causing problems
  • which workflows are failing
  • how much rework exists

then it may have outsourced more than labor.

It may have outsourced understanding.

That's dangerous.

A physician practice should not need to become a billing company.

But it should understand its own revenue cycle.


This Is the Philosophy Behind OnnX

This is where OnnX enters the conversation.

I founded OnnX around a simple idea:

Small and midsized medical practices should not have to surrender operational visibility just because medical billing is complicated.

OnnX is an AI-powered medical billing SaaS designed to help practices reduce unnecessary administrative friction and move toward greater visibility and control without relying entirely on traditional middleman-heavy workflows.

The objective isn't to add another dashboard to a physician's life.

Nobody wakes up thinking:

“I hope someone gives me another dashboard today.”

The objective is to make the underlying workflow more intelligent.

More visible.

More actionable.

More connected.

The important distinction is this:

Automation should not hide the work.

It should make the work easier to understand.


The Difference Between Outsourcing Work and Outsourcing Understanding

This distinction is central to the future of medical billing.

A practice can outsource repetitive labor.

That's reasonable.

But outsourcing understanding is different.

If the practice doesn't know:

What is happening?

Why is it happening?

Who owns it?

What should happen next?

then the practice isn't really in control.

Technology should reverse that.

The physician doesn't need to personally work every claim.

But the physician or practice owner should be able to understand the system.

That is operational intelligence.


The 30-Day Practice Challenge

If you're a physician owner, try something simple.

Don't transform everything.

Pick one month.

Days 1–5: Measure

Document:

  • clean-claim rate
  • denial rate
  • denial reasons
  • days in A/R
  • A/R over 90 days
  • patient balance aging
  • staff hours spent on billing
  • manual claim touches
  • average time to resolution

Don't fix anything yet.

Measure.


Days 6–10: Trace

Pick one denied claim.

Follow it from beginning to end.

Where did the information originate?

Who touched it?

What changed?

Where did the problem appear?

Could it have been detected earlier?

Do this repeatedly.

Patterns will emerge.


Days 11–15: Categorize

Divide problems into:

Preventable.

Partially preventable.

Unavoidable.

Don't waste your team's energy pretending every payer behavior can be controlled.

Focus on what you can influence.


Days 16–20: Prioritize

Pick three recurring problems.

Not ten.

Three.

Rank them by:

  • financial impact
  • staff time
  • patient impact
  • frequency
  • ease of intervention

Then tackle them.


Days 21–25: Automate

Identify repetitive work.

Ask:

Could software do this?

If yes:

Could it do it safely?

If yes:

How would a human verify exceptions?

That third question is the one people skip.

Don't skip it.


Days 26–30: Review

Compare the baseline.

What improved?

What didn't?

What surprised you?

What should be redesigned next?

The objective isn't perfection.

It's learning.


The Metrics That Actually Matter

A practice doesn't need 200 KPIs.

Start with a manageable group.

Clean-Claim Rate

How often do claims pass through correctly the first time?

Denial Rate

How frequently are claims denied?

Denial Recurrence

How often are the same problems happening again?

Days in A/R

How quickly is outstanding revenue being resolved?

A/R Over 90 Days

How much money is becoming increasingly difficult to collect?

Cost to Collect

How much operational effort does revenue generation require?

Manual Touches

How many times does a claim require human intervention?

Staff Hours per 100 Claims

This connects revenue performance to labor.

Patient Billing Contacts

How often are patients calling because they don't understand a bill?

Physician Administrative Hours

How much physician time is being consumed by nonclinical administrative work?

That last metric deserves much more attention.


The Metric Nobody Likes

Here's the number that may make practice owners uncomfortable:

How many physician hours are being consumed by work that does not require a physician?

Think about that.

A physician costs more than an administrative employee.

A physician's time is scarce.

A physician's time is clinically valuable.

And yet physicians routinely get pulled into:

  • authorization issues
  • documentation questions
  • payer disputes
  • patient billing questions
  • administrative escalations
  • referral problems

Sometimes the physician must be involved.

Often they don't.

If you can return even a small amount of physician time to clinical work, the operational impact can be meaningful.


Legal and Compliance Reality

Technology does not eliminate compliance obligations.

It creates new ones.

Any practice using automation or AI in revenue-cycle operations should understand issues around:

  • HIPAA and privacy
  • data security
  • access controls
  • audit trails
  • appropriate use of patient information
  • payer requirements
  • coding standards
  • documentation
  • fraud and abuse laws
  • contractual obligations
  • state requirements
  • business associate relationships
  • AI governance

And one question deserves special attention:

What happens when the AI is wrong?

Every responsible system needs an answer.

Who reviews it?

Who can override it?

Is the decision documented?

Can the organization reconstruct what happened?

Can an error be corrected?

Can access be revoked?

What data is being used?

Where is it stored?

Is patient information being used for model development?

Who has access?

What happens during downtime?

Those aren't futuristic questions.

They're governance questions.


Ethics: Efficiency Isn't the Only Goal

There is another trap.

Healthcare can become so obsessed with efficiency that it forgets what efficiency is supposed to serve.

The objective is not simply:

more collections.

The objective is accurate, appropriate, transparent financial operations that support sustainable care.

A patient shouldn't be treated like an outstanding balance.

A denial shouldn't automatically become an aggressive collection opportunity.

An algorithm shouldn't become an unreviewable authority.

Automation shouldn't eliminate accountability.

And convenience for the practice shouldn't automatically become inconvenience for the patient.

The patient is not the friction to be optimized away.

The friction is.

That distinction is fundamental.


What About Independent Practices?

Independent practices face a particularly difficult balancing act.

They need:

  • clinical autonomy
  • financial sustainability
  • operational efficiency
  • technology
  • compliance
  • staffing
  • patient trust

But they often don't have the administrative infrastructure of large health systems.

That creates an interesting technology opportunity.

The answer isn't necessarily to become bigger.

It may be to become smarter.

A 10-provider practice doesn't need to replicate the bureaucracy of a 10,000-provider health system.

It needs systems that give a smaller organization leverage.

That's where intelligent automation can become particularly valuable.


The Future Is Not “No Humans”

I don't believe the future of medical billing is a completely human-free system.

That would be a mistake.

The future is more likely to be:

less repetitive human work + more human oversight + better information.

The machine handles the predictable.

The human handles the exception.

The practice owns the visibility.

The patient receives clearer communication.

The physician gets more time back.

That is a future worth building.


What Healthcare Gets Wrong About Innovation

Healthcare often defines innovation as:

new technology.

But innovation can be much simpler.

Eliminating a redundant step is innovation.

Removing a fax is innovation.

Making a bill understandable is innovation.

Preventing a denial is innovation.

Giving staff better information before they make a phone call is innovation.

Giving a physician five hours back each month is innovation.

Making a patient understand what happens next is innovation.

Technology is merely one mechanism.

The real innovation is reducing unnecessary friction.


The Patient Experience Is an Operational Outcome

This may be the most important idea in the article.

Patient experience isn't just:

“Did the doctor have a good bedside manner?”

It's also:

Did the referral happen?

Did the authorization happen?

Did the result arrive?

Did someone follow up?

Did the patient understand the plan?

Did the bill make sense?

Did the practice respond?

Did the patient know what happens next?

That means patient experience isn't exclusively a communications function.

It is an operational outcome.

And operational outcomes can be measured.


The Ava Little Test

Here's a simple test I would give every healthcare workflow.

Imagine Ava Little is using your system.

Not a billing expert.

Not a healthcare administrator.

Not a coder.

A teenager living with a chronic condition.

Could she understand:

What happened?

Why?

What happens next?

Who is responsible?

What does she need to do?

If the answer is no, perhaps the workflow is designed for the organization rather than the patient.

And that is the distinction we need to confront.


Healthcare Has an Interesting Habit

We often build systems around what is convenient for the organization.

Then we ask patients to adapt.

Patients should use the portal.

Patients should call the insurer.

Patients should understand the statement.

Patients should remember the referral.

Patients should know when to follow up.

Patients should figure out the authorization.

Patients should bring the paperwork.

Patients should wait.

At some point, we need to reverse the question.

Instead of asking:

“Why can't patients follow our process?”

Ask:

“Why did we build a process patients can't reasonably follow?”

That question is much more interesting.

And much more productive.


The Humor Hides a Serious Problem

Healthcare has spent years teaching people to laugh at administrative absurdity.

We joke about prior authorization.

We joke about fax machines.

We joke about insurance hold music.

We joke about portals.

We joke about paperwork.

But humor can sometimes hide normalization.

When everyone jokes about the same broken process for 15 years, perhaps the problem isn't that the joke is funny.

Perhaps the problem is that we stopped expecting the system to change.

That's dangerous.


What Physicians Should Stop Saying

Maybe we should retire a few phrases.

“That's just how insurance works.”

Maybe.

But which part?

And is it actually unavoidable?

“Billing will handle it.”

Who specifically?

And when?

“We'll figure it out later.”

Later has an unfortunate tendency to become never.

“The patient knows what to do.”

Do they?

“We need another person.”

Maybe.

But what problem will that person solve?

“AI will take care of it.”

Which part?

Under what rules?

With what oversight?

“It's only administrative.”

If it consumes physician time, staff time, patient time, or access to care, it isn't insignificant.


The Question Every Practice Owner Should Ask

If I walked into your practice tomorrow and asked:

Where is money getting stuck?

Could you answer?

Then:

Where is staff time getting stuck?

Could you answer?

Then:

Where is patient trust getting stuck?

That's the interesting question.

Because these may all be connected.

A claim problem consumes staff time.

Staff time creates backlog.

Backlog creates delay.

Delay creates patient frustration.

Patient frustration creates calls.

Calls consume more staff time.

More work creates more backlog.

And suddenly everyone is “busy.”

But busy isn't the same as effective.

A system can be incredibly busy and still be broken.


The Real Goal

The goal isn't a perfect revenue cycle.

There is no such thing.

Payers change rules.

Patients change insurance.

Technology fails.

People make mistakes.

Healthcare is complicated.

The goal is something more realistic:

Make the system visible enough to improve.

When something goes wrong, know why.

When something repeats, notice it.

When something can be prevented, prevent it.

When something can be automated safely, automate it.

When something requires judgment, keep a human involved.

When something affects patients, measure the patient impact.

That is operational maturity.


And That Brings Us Back to Ava

Ava Little was diagnosed at three years old.

Today she is 14.

Her diagnosis remains part of her life.

But it doesn't define all of it.

She has chosen to advocate.

To raise awareness.

To fundraise.

To connect with other people living with CMT.

To lead.

Her father, Matthew Little, told WDIV that her attitude toward raising money makes him proud. Ava also described how participating in the CMT walk helped her regain confidence and connect with people who understand what she is going through.

And then she said something that should stay with anyone working in healthcare:

“I just didn’t want to sit on the sidelines anymore.”

That is more than a quote.

It's a challenge.

Because patients shouldn't sit on the sidelines of their own healthcare.

Physicians shouldn't sit on the sidelines of their own practices.

Practice owners shouldn't sit on the sidelines of their own revenue cycle.

And staff shouldn't spend their careers sitting inside administrative queues waiting for someone else to fix a problem.


The Future of Medical Billing Is Bigger Than Billing

I believe the next generation of medical billing will be less about processing transactions and more about understanding the system around those transactions.

That means:

Better visibility.

Better prevention.

Better automation.

Better data.

Better accountability.

Better communication.

Fewer handoffs.

Fewer surprises.

And fewer situations where the answer to a patient's question is:

“You'll need to call your insurance company.”

Technology cannot eliminate every problem.

But it can help us stop pretending that unnecessary problems are inevitable.


Three Expert Perspectives Worth Keeping in Mind

1. Alan P. Feren, MD: Care Continues Beyond the Encounter

Feren's September 24 essay argues that care shouldn't disappear simply because the scheduled encounter has ended. He emphasizes explanation, responsibility, follow-through, and support beyond the initial visit.

The operational lesson: Your workflow after the appointment is part of the care experience.

 

2. The American Medical Association: Administrative Friction Is Measurable

The AMA's 2026 reporting on its prior-authorization survey documents substantial physician and staff time devoted to authorization work, alongside reported delays in care and burnout.

The operational lesson: Administrative burden isn't just a complaint. It can be measured in hours, delays, and resource allocation.

 

3. Ava Little: Patients Want Agency

Ava's story demonstrates the human side of the equation.

Her diagnosis did not disappear.

The challenges did not disappear.

But she found a way to participate, advocate, and help others.

The operational lesson: Patient-centered healthcare should give people understandable information and meaningful participation rather than forcing them to navigate complexity alone.


Recent Healthcare Signals Worth Watching

The timing of this conversation is important.

The AMA's September 25, 2026 advocacy update is emphasizing implementation of electronic prior-authorization infrastructure and the need for health plans, EHR vendors, and health systems to prepare for upcoming requirements. The AMA notes that physicians and staff currently spend an average of 13 hours each week on prior authorization.

That means the industry is moving toward more electronic infrastructure.

But here's the contrarian question:

Will digitizing a bad process actually make it a good process?

Not automatically.

A digital fax is still a fax.

A digital bottleneck is still a bottleneck.

An automated denial is still a denial.

Technology creates leverage.

It does not automatically create wisdom.


Five Pitfalls to Avoid

Pitfall 1: Buying technology before mapping the workflow

You may automate the wrong thing.

Pitfall 2: Measuring collections without measuring effort

More revenue isn't the entire story.

How much did it cost in staff time to obtain it?

Pitfall 3: Treating every denial equally

Some denials are worth immediate attention.

Others may be low-value or unavoidable.

Prioritization matters.

Pitfall 4: Assuming the vendor owns the outcome

A vendor can provide technology or services.

The practice still needs governance.

Pitfall 5: Forgetting the patient

A revenue-cycle strategy that improves collections while destroying patient trust is not necessarily an operational success.


Five Questions to Ask Any AI Billing Vendor

Before buying anything, ask:

1. What exactly is automated?

Not “AI-powered.”

What specifically?

2. What happens when the system is uncertain?

Is there human review?

3. Can I audit what happened?

Can the practice reconstruct decisions and actions?

4. What happens to my data?

Where is it stored?

Who can access it?

How is it protected?

How is it used?

5. Can I actually see what's happening?

If the answer is another 50-page report, keep asking questions.


The Most Important Question

There is one question I would put above all five:

Does this technology give my practice more control—or simply give me another vendor to call?

That question gets to the heart of the matter.

Technology should reduce dependency where appropriate.

It should increase visibility.

It should make work easier to understand.

It should create leverage.

It should not create another black box.


A Different Definition of Efficiency

Maybe healthcare needs to redefine efficiency.

Efficiency isn't:

“How fast can we process this claim?”

It is:

“How much unnecessary work did we eliminate?”

Efficiency isn't:

“How many denials did we recover?”

It is:

“How many preventable denials did we stop?”

Efficiency isn't:

“How many patient calls did staff answer?”

It is:

“How many calls did we make unnecessary?”

Efficiency isn't:

“How many hours did the physician work?”

It is:

“How much physician time was spent where physician expertise actually mattered?”

That is a very different way to think about operations.


What If the Best Billing System Is Almost Boring?

This may sound strange coming from someone building an AI-powered billing platform.

But here it is:

The best technology should eventually feel boring.

You shouldn't need to think about it constantly.

It should simply:

catch problems,

surface exceptions,

organize work,

show patterns,

and help people act.

No fireworks.

No robot speeches.

No “revolutionary transformation” every Tuesday.

Just fewer problems.

That's real innovation.


Final Thoughts

Ava Little didn't choose her diagnosis.

But she chose not to sit on the sidelines.

Healthcare cannot eliminate every hardship patients face.

But it can eliminate unnecessary friction.

Physicians cannot control every payer decision.

But they can control whether their practices understand the patterns surrounding those decisions.

Technology cannot solve every administrative problem.

But it can help humans spend less time fixing predictable problems and more time exercising judgment where it matters.

The future of healthcare will not be defined only by what happens in the exam room.

It will also be defined by what happens before the patient arrives, after the patient leaves, and everywhere the patient's information travels in between.

That is where trust is built.

That is where time is lost.

That is where money gets stuck.

And that is where healthcare has an enormous opportunity to do better.


Your Turn

Here's the question I want to put to physicians and practice owners:

What is the administrative problem in your practice that everyone has learned to tolerate—but nobody should have to?

Is it denials?

Prior authorization?

Eligibility?

Patient statements?

Referral management?

Credentialing?

An EHR workflow that requires six clicks for something that should require two?

Or something else entirely?

Tell me in the comments.

I genuinely want to know what physicians are seeing on the ground.

And if this article challenged how you think about medical billing, repost it for another physician, practice owner, administrator, or healthcare technology leader.

Maybe the next great healthcare improvement isn't another clinical breakthrough.

Maybe it's removing one unnecessary obstacle that thousands of physicians and millions of patients have simply learned to live with.


Free Resource

I've placed a free practical resource in the Featured section of my LinkedIn profile for physicians and practice owners who want to examine their revenue-cycle workflows more systematically.

No signup required.

Use it with your team.

Challenge it.

Adapt it.

And most importantly, measure what changes.


Continue the Conversation

I write and speak about the intersection of medicine, technology, healthcare operations, medical billing, and physician entrepreneurship.

Follow the conversation through my website, podcast, YouTube channel, X, Facebook, and LinkedIn.

Connect with Dr. Daniel Cham on LinkedIn

DrDanielCham.com

Listen on Spotify

Watch on YouTube

Follow on X

Follow on Facebook

The goal isn't simply to talk about what's wrong with healthcare.

It's to ask better questions about what we can build next.

Knowledge drives progress. Better questions drive better systems.


About the Author

Dr. Daniel Cham is a physician and medical consultant specializing in medical technology consulting, healthcare management, and medical billing.

He is the founder of OnnX, an AI-powered medical billing SaaS focused on helping small and midsized medical practices reduce administrative friction while maintaining greater visibility and control over their revenue-cycle operations.

His work explores the intersection of clinical medicine, healthcare technology, practice management, revenue-cycle strategy, and physician entrepreneurship.


Disclaimer

This article is intended for general educational and informational purposes only. It does not constitute medical, legal, financial, coding, compliance, reimbursement, or other professional advice. Healthcare organizations should obtain advice from appropriately qualified professionals regarding their specific clinical, operational, contractual, regulatory, billing, privacy, security, and compliance circumstances.


References

1. Alan P. Feren, MD — “The 15-minute appointment is not the boundary of care,” KevinMD, September 24, 2026. Feren argues that the clinical encounter is only one part of care and that responsibility, explanation, and follow-through must continue beyond the scheduled appointment. Read the full article

2. WDIV Local 4 — “Go 4 It: 14-year-old Michigan girl turns rare disease diagnosis into mission to help others,” September 24, 2026. The report profiles Ava Little, her CMT1A diagnosis, her advocacy and fundraising efforts, and comments from her father, Matthew Little. Read the WDIV story

3. American Medical Association — “Sept. 25, 2026: National Advocacy Update.” The AMA's latest update discusses electronic prior-authorization implementation and cites its survey finding that physicians and staff spend an average of 13 hours per week on prior authorization. Read the AMA update


One Last Question

What if the biggest opportunity in healthcare isn't making the patient visit faster?

What if it is making everything around the visit work better?

Because care doesn't end when the physician leaves the room.

The claim doesn't end when it is submitted.

The patient relationship doesn't end when the encounter is signed.

And the practice doesn't stop operating when the physician closes the exam-room door.

Healthcare is a continuous experience.

We should build it that way.

Ava Little didn't want to sit on the sidelines.

Maybe it's time we stopped asking patients, physicians, and practice staff to do exactly that.

#Healthcare #MedicalBilling #HealthcareLeadership #RevenueCycleManagement #PhysicianPractice #PatientExperience #HealthcareTechnology #HealthTech #MedicalPractice #PhysicianEntrepreneur #HealthcareInnovation #RCM #AIinHealthcare #PatientCenteredCare #IndependentPractice #MedicalTechnology #HealthcareOperations #OnnX

 

Thursday, September 24, 2026

Clint Peterson Was a Nurse. Then He Became the Patient.

What One Rochester Nurse’s Story Reveals About the Human Cost of a Healthcare System That Keeps Asking Humans to Fix Its Machines



“The two dimensions of human relationships and alignment on patient values and agency deserve particular protection as AI advances.” — Eric Horvitz, MD, PhD, Chief Scientific Officer, Microsoft, September 24, 2026

 

On September 16, 2026, Clint Peterson, a 26-year-old registered nurse, was at St. Marys Hospital in Rochester, Minnesota.

He was doing what nurses do.

Taking care of someone else.

Then everything changed.

According to a criminal complaint cited by Rochester-area reporting, Jascon Jacoby Hollins, a 43-year-old man in the custody of the Olmsted County Sheriff’s Office, was receiving medical care at St. Marys when he allegedly broke free from a restraint and ran into a hospital hallway.

A detention deputy pursued him.

During the encounter, the deputy and Hollins collided with Peterson.

Peterson fell and struck his head.

He suffered a skull fracture, traumatic brain injury and brain bleed requiring surgery, according to reporting about his condition.

The nurse became the patient.

And suddenly, the person whose job was helping others needed help himself.

That is the part of this story that stays with you.

Peterson had reportedly recently celebrated his one-year review at Mayo Clinic. He was considering additional leadership responsibilities, including work related to patient safety and patient experience.

Then, in an instant, the future became uncertain.

His longtime friend Matt Wurst, who says he has known Peterson since kindergarten, described the reversal in painfully simple terms:

Clint is a nurse.

Taking care of people is a huge part of who he is.

Now he is the one who needs care.

Peterson reportedly has needed assistance with mobility, medication management and daily activities. His recovery remains uncertain. No one knows exactly when he will live independently again or whether he will return to nursing.

The criminal case surrounding the incident is separate from Peterson's recovery. Hollins faces criminal charges, and the allegations in the complaint should not be treated as adjudicated facts.

But Peterson's story raises a much larger question.

Not about crime.

Not about hospitals.

Not even about nursing.

About human attention.

Because healthcare has a strange habit.

We take some of the most highly trained people in society...

and then ask them to spend enormous amounts of time fixing problems created by the systems surrounding them.

Maybe we should stop calling that productivity.


Healthcare Has a Productivity Problem. But Maybe Not the One We Think.

For decades, healthcare has asked:

How do we make clinicians more efficient?

Better workflows.

Better templates.

Better dashboards.

Better software.

Better automation.

Better artificial intelligence.

Better revenue-cycle management.

Better everything.

And yet the work keeps expanding.

The inbox grows.

The task list grows.

The prior-authorizations grow.

The denials grow.

The documentation grows.

The portals multiply like rabbits.

And somewhere in the middle of all of it sits the physician.

Still seeing patients.

Still answering messages.

Still signing charts.

Still explaining things.

Still fixing things.

Still wondering why a system designed to help healthcare seems to require so much help itself.

Here's the contrarian question:

What if the goal shouldn't be making healthcare workers faster?

What if the goal should be making less work necessary?

That's a very different proposition.


The Healthcare Industry's Favorite Trick

We have become remarkably good at automating the consequences of bad processes.

A claim is denied.

Build an AI denial-management tool.

A payer asks for documentation.

Build an AI authorization assistant.

A physician spends too much time documenting.

Build an AI scribe.

A staff member has to check three systems.

Build a dashboard.

A billing team has too many exceptions.

Build an exception-management platform.

A workflow is inefficient.

Add automation.

A workflow is still inefficient.

Add more automation.

Eventually we have a beautifully automated mess.

That is not a joke.

It is one of the central risks of healthcare AI.

AI is extraordinarily good at doing what we ask.

If we ask it to process unnecessary work faster, it can do that too.

Artificial intelligence does not automatically produce intelligent systems.

Sometimes it simply produces faster bureaucracy.


The Rube Goldberg Revenue Cycle

Consider a typical revenue-cycle problem.

A patient arrives.

Information is collected.

Someone enters it.

Another system receives it.

Someone interprets it.

Someone checks eligibility.

Someone checks authorization.

Someone documents the encounter.

Someone codes it.

Someone submits the claim.

The payer processes it.

Something doesn't match.

The claim is rejected.

Someone investigates.

Someone opens a portal.

Someone calls the payer.

Someone sends documentation.

Someone asks the physician a question.

The physician stops what they're doing.

Someone resubmits the claim.

Someone waits.

Someone checks again.

Someone follows up.

Someone reconciles the payment.

Then everyone celebrates.

Why?

Because the claim finally got paid.

Congratulations.

We successfully completed a process that required twelve people to repair information that should have been correct much earlier.

And then we call that revenue-cycle management.

Sometimes it feels more like revenue-cycle archaeology.


The Problem May Not Be Billing

This is where I disagree with a lot of conventional RCM thinking.

The denial is not necessarily the problem.

The denial may be the symptom.

The billing department may not be the origin.

The claim may not be the origin.

The payer may not even be the origin.

The problem may have started much earlier.

At the point where information was captured.

At the point where a workflow allowed ambiguity.

At the point where two systems interpreted the same information differently.

At the point where a person had to remember something a system should have known.

At the point where someone entered the same information twice.

The farther downstream the problem travels, the more expensive it becomes to fix.

A five-second correction upstream can become a 30-minute administrative event downstream.

And a 30-minute event repeated 500 times isn't a small problem.

It's a business model.


The Human Attention Tax

We tend to calculate healthcare costs in dollars.

We should.

But dollars are not the only scarce resource.

Attention is scarce too.

A physician has a finite amount.

A nurse has a finite amount.

A medical assistant has a finite amount.

A practice manager has a finite amount.

A billing specialist has a finite amount.

And unlike software licenses, human attention does not renew at midnight.

Every interruption consumes some of it.

Every context switch consumes some.

Every ambiguous request consumes some.

Every exception consumes some.

Every missing piece of information consumes some.

And sometimes the cost is invisible.

A physician spends 15 minutes fixing an administrative issue.

The spreadsheet says:

15 minutes.

But the real cost may include:

15 minutes of direct time.

plus interruption.

plus cognitive switching.

plus delayed work.

plus another task pushed later.

plus the possibility of taking unfinished work home.

That is why I think healthcare needs a new metric:

Return on Attention.

Not just return on investment.

Not just productivity.

Return on Attention.

Where did the human attention go?

Was it necessary?

Could it have been prevented?

Could software have handled it?

Could better information have prevented it?

Could the human have spent that time with a patient instead?

Those questions may tell us more about healthcare technology than another dashboard showing utilization.


Eric Horvitz Just Made the Human Point

On September 24, Microsoft Chief Scientific Officer Eric Horvitz, MD, PhD, spoke about AI and healthcare at Washington University in St. Louis.

His warning was not that AI should replace people.

Quite the opposite.

He emphasized protecting human relationships, patient values and patient agency as AI advances. He described a future in which AI assists clinician teams while human needs remain central.

That is important.

Because the conversation around AI can become strangely mechanical.

We ask:

How many tasks can AI perform?

How many employees can AI replace?

How many minutes can AI save?

How many claims can AI process?

Those are useful questions.

But they aren't the whole question.

A better one is:

What should humans do with the attention AI gives back?

If the answer is “more administrative work,” we missed the point.


AI Should Not Become the World's Fastest Intern

Here's another uncomfortable thought.

Healthcare may be at risk of building AI systems that function like extremely energetic interns.

They never sleep.

They never complain.

They process enormous amounts of information.

And then they create 47 tasks for someone to review.

Fantastic.

Now the physician has an AI-generated inbox.

Progress?

Maybe.

But only if the human workload actually falls.

Otherwise we've created a new category of work:

checking the machine that checked the machine.

At some point, someone has to ask:

Who is actually getting the time back?


The Best Automation May Be the Automation Nobody Notices

The most impressive AI demo isn't necessarily the most valuable AI system.

A system that generates a spectacular summary is impressive.

A system that eliminates the need for the summary may be more valuable.

A system that identifies a denial quickly is useful.

A system that prevents the denial is potentially more valuable.

A system that routes an exception efficiently is useful.

A system that makes the exception unnecessary is a different class of improvement.

This is the distinction between:

automation of work

and

elimination of work.

We should stop treating them as the same thing.


Healthcare's Most Expensive Phrase

There is a phrase every practice owner should question:

“That's just how we do it.”

Those six words have probably cost American healthcare billions.

Because work that starts as a workaround can eventually become:

a workflow,

then a policy,

then a habit,

then a software requirement,

then a job description,

then a department,

then an entire industry.

Nobody remembers why the process exists.

Everyone just knows someone has to do it.

This is how organizational folklore becomes infrastructure.


The Physician as Human Middleware

Here's one of the strangest roles physicians have acquired.

Human middleware.

Information doesn't move cleanly between systems.

So the physician becomes the translator.

The payer wants something.

The physician explains.

The coder needs clarification.

The physician explains.

The authorization department needs documentation.

The physician explains.

A claim has a problem.

The physician explains.

The EHR doesn't understand the context.

The physician supplies the context.

The physician becomes the API.

Except the API has a medical degree, a patient schedule and approximately 37 unread messages.

That is not a scalable architecture.


The Real Cost of a Physician Touch

Let's make this concrete.

Suppose a claim requires physician intervention.

Maybe it takes three minutes.

Sounds harmless.

Now multiply it.

One physician.

Twenty claims.

Five days.

Four weeks.

One year.

The number becomes meaningful.

Now imagine the physician is interrupted rather than handling the work in a dedicated block.

The cognitive cost increases.

Now imagine the issue could have been prevented upstream.

The question changes again.

We shouldn't only measure:

How fast did the physician resolve it?

We should measure:

Why did the physician have to touch it?

That is a much more powerful operational question.


Five Metrics I'd Like to See More Practices Track

1. Physician Touches Per Claim

How many claims require physician intervention for administrative reasons?

Not clinical judgment.

Administrative reasons.

Track it.

2. Manual Touches Per Claim

How many people have to touch the transaction?

Every handoff is an opportunity for information loss.

3. Rework Rate

How much work is being repeated because something wasn't correct the first time?

4. Exception Rate

How often does the standard process fail?

5. Administrative Minutes Per Encounter

How much human time surrounds a patient encounter that isn't direct patient care?

These metrics won't solve the problem.

But they expose it.

And you can't redesign what you can't see.


A Seven-Day Experiment for Your Practice

You don't need another software platform.

Start with a spreadsheet.

For seven days, capture every recurring administrative interruption.

Write down:

What happened?

Who discovered it?

When was it discovered?

Who touched it?

Did the physician become involved?

What information was missing?

Where was that information originally available?

Could the problem have been prevented earlier?

What was the downstream consequence?

Don't fix anything yet.

Just observe.

Because healthcare has a bad habit of solving the first visible problem.

The better approach is to find the earliest preventable cause.


The Upstream Test

Here's a simple rule:

When you find a problem, move backward.

A claim was denied.

Move backward.

Why?

Missing information.

Move backward.

Why was it missing?

It wasn't captured.

Move backward.

Why wasn't it captured?

The workflow didn't require it.

Move backward.

Why?

The system assumed someone would know.

Move backward.

Why?

Because that's how the practice has always done it.

There it is.

The real problem may not have been the denial.

It may have been a design assumption made months or years earlier.


This Is Where OnnX Starts

This is the thinking behind OnnX.

The idea is simple:

Most of the problem starts upstream.

Healthcare billing is often treated as a downstream workflow problem.

I think a significant part of it is an information-structure problem.

If clinical and operational information is inconsistent, incomplete or fragmented at the beginning, downstream systems have to compensate.

Someone has to interpret it.

Someone has to correct it.

Someone has to chase it.

Someone has to resubmit it.

Someone has to explain it.

The system becomes increasingly reactive.

OnnX is built around a different premise:

Structure the information earlier.

Reduce variability before it becomes a billing problem.

That doesn't mean every denial disappears.

It doesn't mean every payer rule becomes simple.

And it certainly doesn't mean AI magically understands healthcare.

It means we should attack preventable variability closer to its source.


We're Optimizing Around Noise

Healthcare has become incredibly sophisticated at responding to noise.

We classify it.

Route it.

Prioritize it.

Analyze it.

Escalate it.

Automate it.

Report it.

Measure it.

And then we congratulate ourselves for managing the noise.

But what if the noise is telling us something?

Maybe the system isn't signaling that we need a better noise-management department.

Maybe it's signaling that the information architecture is wrong.

We are often optimizing around noise instead of removing it.

That distinction is central to the future of healthcare AI.


AI Is Only as Good as the Problem You Give It

There is a seductive idea that AI will simply make healthcare more efficient.

It might.

But AI doesn't determine the problem.

Humans do.

If we give AI a bad process, it may optimize the bad process.

If we give it fragmented information, it may organize fragmented information.

If we give it ambiguous instructions, it may produce very sophisticated ambiguity.

That means the most important AI skill may not be prompting.

It may be problem definition.

Before asking:

“What can AI do?”

Ask:

“What should no human have to do anymore?”

That's the better starting point.


Three Experts, Three Lessons

Eric Horvitz, MD, PhD: Protect the Human Relationship

Horvitz's September 24 remarks emphasize human relationships, patient values and agency as AI becomes more capable.

The lesson:

Don't confuse intelligence with understanding.

A system can process information without understanding what matters to a patient.

Healthcare still needs people who listen.

People who interpret.

People who explain.

People who take responsibility.

AI should strengthen those functions, not bury them.


Willie Underwood III, MD, MSc, MPH: Patients Shouldn't Have to Fight the System

Earlier this month, AMA President Willie Underwood III, MD, MSc, MPH, wrote that patients should not have to fight the healthcare system to receive care they need. His comments focused on Medicare payment and prior authorization, but the broader principle is relevant: administrative friction eventually reaches the patient.

The lesson:

Administrative friction isn't merely an employee problem.

It can become a patient problem.

When information doesn't move, care can slow.

When authorization doesn't move, treatment can slow.

When claims don't move, patients and practices can spend time chasing the consequences.

The back office is not disconnected from the exam room.

It is connected by every piece of information moving between them.


Bruce Swords, MD: AI Can Give Physicians Time Back — If We Use It Correctly

In an interview published September 24, Bruce Swords, MD, chief clinical officer at Bon Secours St. Francis, described AI as useful for administrative work historically handled by physicians.

But he also emphasized the continuing importance of direct clinical oversight and human context.

The lesson:

AI should reduce administrative burden without pretending to replace clinical judgment.

That distinction is critical.

Good automation doesn't make physicians less important.

It makes unnecessary physician work less important.


Recent News Is Making the Same Point From Different Directions

Something interesting is happening across healthcare right now.

A family in Massachusetts recently described repeatedly resubmitting a medical insurance claim after it was denied over missing information. The Connecticut Office of the Health Care Advocate said 65% of calls to its office involve denials, including administrative denials that essentially require people to “connect the dots.” The insurer ultimately acknowledged confusion and approved the claim.

That story sounds small.

It isn't.

Because healthcare is full of tiny administrative failures.

One missing code.

One missing field.

One missing document.

One misunderstood requirement.

One incorrect assumption.

Multiply those events across millions of encounters.

Suddenly the “small” problem becomes a system.

And then we hire people to manage the system.


The Billion-Dollar Question

Here's the question I would ask every healthcare technology company:

How much work did your product eliminate?

Not automate.

Not accelerate.

Not route.

Not dashboard.

Eliminate.

If your software saves a billing employee 20 minutes but creates 15 minutes of review, the net gain is five minutes.

If AI creates a draft that requires another person to inspect every line, that's not zero work.

If an automated system generates ten alerts and someone has to review all ten, you've moved the work.

Maybe that's still valuable.

But let's call it what it is.

Work relocation is not work elimination.


What Physicians Should Ask Vendors

The next time someone shows you an impressive AI demo, ask:

What happens when the AI is wrong?

Then ask:

Who reviews it?

Then:

How many new tasks does that create?

Then:

What information does the system need?

Then:

Where does that information come from?

Then:

What happens upstream if that information isn't available?

And finally:

How much human work disappears?

That last question should be on every healthcare technology RFP.


What Clinic Owners Should Ask Their Own Teams

Ask:

What do you do every day that you think is ridiculous?

Not “inefficient.”

Not “suboptimal.”

Ridiculous.

People know.

They may not say it in meetings.

They know which spreadsheet nobody trusts.

They know which payer portal they hate.

They know which report gets exported and immediately re-entered somewhere else.

They know which fax gets sent because “that's what they require.”

They know which task exists because somebody five years ago said, “Just in case.”

That institutional knowledge is valuable.

Use it.


The Ethical Question: What Happens to the Work We Remove?

There is a legitimate concern here.

If AI eliminates repetitive administrative work, what happens to the people who perform it?

That question deserves a serious answer.

The goal should not simply be:

Replace people.

A better goal is:

Remove unnecessary work and redirect human capacity.

People can handle:

  • complex exceptions
  • patient communication
  • problem-solving
  • relationship management
  • quality improvement
  • clinical support
  • coordination
  • judgment

The ethical question is not whether work changes.

It will.

The question is whether the transition produces more human value or simply fewer humans.

Technology is not inherently humane.

Its design and deployment determine the outcome.


The Legal and Compliance Reality

Upstream automation also creates responsibility.

Healthcare organizations still need appropriate controls around:

HIPAA and privacy

Security

Access controls

Business associate relationships

Documentation

Coding accuracy

Claims integrity

Audit trails

Human oversight

Data provenance

Model governance

Automation doesn't transfer responsibility to the algorithm.

“AI did it” is not a compliance strategy.

A trustworthy system should make it possible to answer:

What information was used?

Where did it come from?

What happened to it?

What rule or model influenced the action?

Who approved it?

What changed?

Can the organization reconstruct the decision?

The future of healthcare AI needs not only intelligence.

It needs traceability.


What We Should Stop Measuring

Maybe we need fewer vanity metrics.

Not fewer measurements.

Better ones.

Stop celebrating automation simply because it exists.

Stop celebrating task completion without asking whether the task should exist.

Stop celebrating claims processed without measuring rework.

Stop celebrating denial resolution without measuring avoidable denials.

Stop celebrating staff utilization without measuring unnecessary touches.

Stop celebrating AI adoption without measuring human attention returned.

The important metric is not:

How much technology did we deploy?

It is:

What became unnecessary because we deployed it?


The Future of RCM May Be Less RCM

That sounds strange.

But consider it.

If information is structured earlier...

If fewer errors occur...

If fewer claims require intervention...

If fewer denials occur...

If fewer people have to touch the same transaction...

If fewer physician interruptions happen...

Then the organization needs less downstream repair.

That's not necessarily a better billing department.

It's a smaller problem.

And smaller problems are usually easier to manage.

The best revenue cycle may eventually be the one that gives people less revenue-cycle work to do.


The Human Story Matters More Than the Technology

This is why Clint Peterson matters.

Not because his injury proves anything about medical billing.

It doesn't.

Not because his story should be exploited as a metaphor for AI.

It shouldn't.

He is a real person recovering from a serious injury.

But his story reminds us of something easy to forget:

The people who work inside healthcare are human beings before they are job titles.

A nurse can become a patient.

A physician can become a patient.

A practice manager can become a patient.

A biller can become a patient.

And one day, every person working inside the system will stand on the other side of it.

That changes the question.

We aren't designing workflows for machines.

We are designing them for people who may eventually need the care those workflows support.


Imagine Getting 20% of Your Attention Back

Imagine a practice where 20% of recurring administrative interruptions disappeared.

Not moved.

Not outsourced.

Gone.

What would happen?

Maybe physicians would finish clinic earlier.

Maybe nurses would have more time with patients.

Maybe staff would spend less time on repetitive work.

Maybe managers would have time to improve the practice instead of constantly rescuing it.

Maybe patients would get faster answers.

Maybe nobody would notice at first.

And that's okay.

The best infrastructure often becomes invisible.

Nobody compliments the plumbing when the water comes out.

Nobody celebrates a bridge because traffic crossed it without incident.

Nobody says:

“Wow, what an amazing absence of administrative friction.”

But that's the point.

Good infrastructure disappears into the background.


Three Things to Do Monday Morning

1. Find the work everyone has normalized.

Ask your team:

“What task do we do every week that makes no sense?”

Listen.

Don't defend the process.

2. Trace the problem upstream.

Don't stop at the denial.

Don't stop at the rejected claim.

Don't stop at the phone call.

Find the earliest point where better information could have prevented the problem.

3. Measure attention returned.

Count:

physician minutes

staff minutes

manual touches

handoffs

rework

exceptions

Then ask:

How much of that disappeared?

That's your real automation ROI.


A Different Definition of Innovation

Healthcare doesn't need another technology arms race.

It needs better questions.

Instead of:

How can we automate this?

Ask:

Why does this exist?

Instead of:

How can we process it faster?

Ask:

Why are we processing it at all?

Instead of:

How can AI fix this?

Ask:

What information would prevent it?

Instead of:

How many tasks did we automate?

Ask:

How many tasks disappeared?

Instead of:

How productive is our staff?

Ask:

How much unnecessary work are we asking them to absorb?

That's a different philosophy of healthcare technology.

And I think it is overdue.


Don't Automate the Mess

Clint Peterson's story began with a sudden reversal.

The person who cared for others became the person who needed care.

It is a reminder that human attention is not an unlimited resource.

We should spend it carefully.

Healthcare workers shouldn't have to spend their best cognitive energy repairing systems that could have been designed better.

Physicians shouldn't be the fallback database.

Nurses shouldn't have to become information detectives.

Practice managers shouldn't have to become professional firefighters.

Billers shouldn't have to repeatedly reconstruct information that should have been structured earlier.

And AI shouldn't become another layer of complexity sitting on top of complexity.

The opportunity is bigger.

Don't automate the mess.

Don't optimize the noise.

Don't make humans faster at unnecessary work.

Remove the reason the work exists.

Then give the attention back to healthcare.


Frequently Asked Questions

Is all administrative work bad?

No.

Healthcare requires documentation, compliance, coordination and financial operations.

The issue is avoidable administrative work.

Does upstream optimization mean eliminating billing departments?

No.

Billing professionals still handle complex cases, payer interactions, exceptions and judgment-intensive work.

The goal is to reduce preventable rework.

Is AI enough?

No.

AI is a tool.

Better information architecture, process design, governance and accountability are equally important.

Should physicians trust AI?

Physicians should evaluate AI based on its intended use, evidence, reliability, integration, oversight and risk.

AI should support appropriate clinical judgment rather than replace it.

What should a small practice measure first?

Start with:

physician administrative minutes

manual touches

rework

exceptions

avoidable denials

Those numbers can reveal where the system is consuming human attention.

What is OnnX trying to change?

OnnX focuses on the idea that many downstream billing problems originate upstream in how clinical and operational information is captured and structured.

The objective is not simply to manage more billing work.

It is to reduce the amount of preventable work that reaches the revenue cycle in the first place.


Myth Busters

Myth: More automation always means less work.

Reality: Poorly designed automation can create new review and exception work.

Myth: A denial is simply a billing problem.

Reality: The cause may originate much earlier in the information chain.

Myth: More staff automatically fixes inefficiency.

Reality: Additional staff can add capacity while leaving the underlying process unchanged.

Myth: AI makes bad information good.

Reality: AI can organize, summarize or process bad information without correcting its underlying quality.

Myth: The physician should resolve administrative exceptions.

Reality: Some require clinical judgment. Many do not.

Myth: Technology is transformation.

Reality: Technology is an instrument. Transformation occurs when the system itself improves.


Final Thought

Clint Peterson went to work as a nurse.

Then he became the patient.

His story reminds us that the people inside healthcare are the same people who eventually depend on healthcare.

That should change how we think about technology.

The goal shouldn't be to make people endlessly more efficient at absorbing system failure.

The goal should be to reduce the amount of system failure they have to absorb.

That is a different vision.

A quieter one.

Less glamorous, perhaps.

But much more useful.

Because the future of healthcare may not belong to the system that automates the most.

It may belong to the system that makes the most unnecessary work disappear.

And when that happens, something important comes back.

Time.

Attention.

Judgment.

Human connection.

Maybe that is what healthcare technology should have been giving us all along.


Get Involved

Here's my question for physicians and clinic owners:

What is one administrative task in your practice that everyone accepts as “normal” even though nobody would design it that way today?

Tell me in the comments.

Not the symptom.

The actual task.

And if you know another physician or clinic owner who is spending valuable time fixing work that shouldn't exist, share this with them.

Because maybe the next breakthrough in healthcare won't be another AI tool.

Maybe it will be the decision to stop building tools around broken processes.


About the Author

Dr. Daniel Cham is a physician, entrepreneur and healthcare technology founder focused on the intersection of clinical practice, healthcare operations and medical billing.

LinkedIn: Connect with Dr. Daniel Cham

Website: Dr. Daniel Cham

Spotify: Listen to the podcast

YouTube: Watch on YouTube

X: Follow on X

Facebook: Follow on Facebook

Through OnnX, he is exploring how AI and better information architecture can reduce unnecessary administrative work for physician-owned and independent medical practices.

His central premise is simple:

Healthcare should spend more human attention on patients and less on repairing preventable system friction.


Disclaimer

This article is intended for general educational and informational purposes. It is not legal, medical, financial or compliance advice. Healthcare organizations should consult appropriately qualified professionals regarding their specific circumstances.

The discussion of the September 16, 2026 incident involving Clint Peterson reflects currently reported information. Allegations described in a criminal complaint should not be treated as established facts unless determined through the appropriate legal process.


Continue the Conversation

What healthcare problem have we become so accustomed to that we no longer question whether it should exist?

That's the conversation worth having.

If this perspective resonates with you, share it with another physician, clinic owner or healthcare operator.

And check the Featured section of my LinkedIn profile for a free resource — no signup required.


References

  1. Galloway, Aaron. “Rochester Nurse’s Life Changed in Seconds After St. Marys Incident.” Rochester Now, September 23, 2026.
    Primary source for the Clint Peterson story, including Peterson's injury, Matt Wurst's comments, St. Marys Hospital, Rochester, Minnesota, and the reported circumstances involving Jascon Jacoby Hollins.
    Read the Rochester Now report
  2. Shiloach, Noa, and Tanvi Gorre. “Chief Scientific Officer of Microsoft Talks AI in Healthcare.” Student Life, Washington University in St. Louis, September 24, 2026.
    Source for Eric Horvitz, MD, PhD's September 24 discussion of AI in healthcare and his warning that human relationships, patient values, and patient agency deserve particular protection as AI advances.
    Read the Eric Horvitz interview/report
  3. American Medical Association. “AMA: Physician Burnout Rates Are Falling, Specialty Gaps Remain.” April 16, 2026.
    Source for the 2025 physician burnout figure of 41.9%, compared with 43.2% in 2024 and 48.2% in 2023. The data came from nearly 19,000 physician responses across 106 health systems and organizations.
    Read the AMA burnout report
  4. American Medical Association. “Allocation of Physician Time in Ambulatory Practice.”
    Source for the finding that physicians spend nearly two hours on EHR and desk work for every hour of direct clinical face time during the clinic day, with another 1–2 hours of computer and clerical work outside office hours.
    Read the AMA physician-time research
  5. American Medical Association. “Doctors Work Fewer Hours, but the EHR Still Follows Them Home.”
    Source for the 2024 physician-workweek data: 57.8 hours per week, including 27.2 hours of direct patient care, 13 hours of indirect patient care and 7.3 hours of administrative work.
    Read the AMA physician-workweek report
  6. American Medical Association. “Delays in Reforming Medicare, Prior Authorization Harm Patients.”
    Source for Willie Underwood III, MD, MSc, MPH's discussion of administrative barriers and patient access to care. This is useful as a supporting reference, but I would not present Underwood's statement as the article's “this week” quote, since the article's current lead quote is now Eric Horvitz's September 24 statement.
    Read the AMA article

#Healthcare #HealthcareAI #MedicalBilling #MedicalPractice #PhysicianPractice #HealthTech #ArtificialIntelligence #RevenueCycleManagement #PhysicianBurnout #HealthcareInnovation #AdministrativeBurden #DigitalHealth #PhysicianEntrepreneur #AIinHealthcare #IndependentPractice

 

Ava Little Didn't Want to Sit on the Sidelines: What Her Story Reveals About the Broken Patient Experience

Healthcare doesn't happen in departments. It happens in the spaces between them—and that is where patients, physicians, and practices of...