Saturday, August 22, 2026

Kourtney Martin Spent Her Career Caring for Patients. Then She Became One.

She knew how healthcare worked. Then she experienced it from the other side. What she learned should make every healthcare leader rethink innovation, physician time, and the work technology should actually remove.



“Kedar has spent his career helping healthcare organizations deliver better outcomes for the people they serve.” — Pamela DeCoste, Board Chair, Blue Shield of California, August 21, 2026


Kourtney B. Martin, CNM, knew exactly what was supposed to happen.

That was the problem.

She was not a first-time observer of pregnancy, labor or delivery.

She was a certified nurse midwife with Norton Women’s Care in Louisville, Kentucky.

She had spent years caring for women during some of the most vulnerable moments of their lives.

She knew the terminology.

She knew the procedures.

She knew the warning signs.

She knew what clinicians were looking for.

She knew what questions patients were likely to ask.

She knew what could go wrong.

And then she became pregnant with her second child.

Suddenly, Kourtney Martin was not standing beside the bed.

She was in it.

Her colleague and friend, Kimberly S. Barnes, APRN, CNM, was there to help guide her.

So was a labor-and-delivery nurse named Devin, who was training to become a midwife.

Before Martin's induction, Devin decorated her room with streamers and the baby's name.

Later, when Martin became nervous during her epidural, Devin held her.

Think about that for a second.

No algorithm did it.

No dashboard did it.

No chatbot did it.

No billion-dollar healthcare platform did it.

A person held another person's hand.

And Martin remembered.

She later described how reassuring it was to have familiar people around her who she trusted to care for and protect her and her baby.

She also said that experiencing pregnancy, delivery and postpartum care from the patient's side made her more empathetic.

That is a beautiful story about childbirth.

But I think it is also a story about healthcare's biggest problem.

And it has surprisingly little to do with childbirth.

It has to do with attention.

Who gets it?

Who loses it?

Who protects it?

And who gets buried under everything else?

Because there is another person in healthcare who knows exactly what it feels like to be pulled away from the thing that matters most.

The physician.


What if the problem isn't physician burnout?

Before you disagree with me, hear me out.

We have spent years talking about physician burnout.

We have conferences about it.

Surveys about it.

Wellness programs about it.

Resilience workshops.

Mindfulness sessions.

Leadership initiatives.

Employee assistance programs.

Sometimes we even give doctors pizza.

Nothing against pizza.

But perhaps we have been asking the wrong question.

Maybe the question isn't:

“Why can't physicians handle the pressure?”

Maybe it is:

“Why have we designed so much work that physicians shouldn't have to do in the first place?”

That is a very different question.

And it changes the solution.

The American Medical Association reports that physician burnout has improved, with 41.9% of physicians reporting at least one symptom of burnout in 2025, down from 43.2% in 2024 and 48.2% in 2023.

That is genuinely good news.

But improvement does not mean the problem has disappeared.

Administrative work, EHR inefficiencies and staffing challenges remain important sources of physician stress.

So perhaps we should stop treating burnout as an individual defect.

Maybe some of it is simply workflow debt.

Healthcare has accumulated years of inefficient processes.

Physicians are paying the interest.


The physician's second job

Nobody really tells you about this part of becoming a physician.

You go to medical school.

You learn anatomy.

You learn physiology.

You learn pharmacology.

You learn diagnosis.

You learn procedures.

You learn how to manage uncertainty.

You learn how to sit with someone who has just received devastating news.

Then you discover another career waiting for you.

Claims analyst.

Coder.

Payer negotiator.

Prior-authorization specialist.

Documentation auditor.

Portal operator.

A/R investigator.

Sometimes amateur IT technician.

Occasionally unpaid collections manager.

It is quite the residency curriculum.

And somehow, "medical billing" wasn't on the MCAT.

Yet physicians can end up spending substantial time dealing with it.

That should bother us.

Not because billing is unimportant.

It is extremely important.

A medical practice cannot survive if it does not get paid.

But the physician is not necessarily the right person to perform every step required to get the practice paid.

That distinction matters.


The hidden cost of a denied claim

Let's say a claim gets denied.

On paper, it is a financial event.

$287 denied.

$1,400 denied.

$7,800 denied.

The revenue-cycle department sees a dollar amount.

But the real cost may be much larger.

Someone has to open the denial.

Someone has to understand why it happened.

Someone has to find the documentation.

Someone has to check the payer's rules.

Someone has to determine whether the claim needs correction or appeal.

Someone has to prepare the response.

Someone has to submit it.

Someone has to track it.

Someone has to follow up.

And sometimes the physician gets pulled into the middle.

Now that $287 denial is no longer $287.

It is:

$287 + staff time + physician time + rework + cognitive interruption + delay + frustration.

The spreadsheet sees revenue.

The human sees another interruption.

That is the hidden economy of administrative healthcare.


We measure dollars. We rarely measure attention.

This is one of the biggest blind spots in healthcare operations.

We measure:

Revenue.

A/R.

Denial rates.

Collection rates.

Visits.

Productivity.

Length of stay.

Readmissions.

But how often do we measure:

How many times did we interrupt the physician today?

How much time did the practice spend looking for information that already existed somewhere?

How many times did staff enter the same information into different systems?

How many tasks were created because another task was done incorrectly?

How many hours were spent fixing problems that should never have occurred?

And perhaps the most important question:

How much human attention did the workflow consume?

Attention is a healthcare resource.

We just don't put it on the balance sheet.


Kourtney Martin understood something about healthcare that dashboards cannot capture

When Martin became the patient, she already knew what was happening clinically.

But clinical knowledge didn't eliminate vulnerability.

She still needed reassurance.

She still needed communication.

She still needed trust.

She still needed someone she knew.

That tells us something important.

Healthcare is not merely an information-delivery system.

It is a relationship.

The patient is not a case.

The physician is not a productivity unit.

The nurse is not a staffing ratio.

The biller is not a labor expense.

These are human beings operating inside a complicated system.

And systems can either protect human attention or consume it.


Here is my contrarian take

I think healthcare has a technology problem.

But it is not the technology problem most people talk about.

We do not necessarily need more technology.

We need better choreography between people, technology and workflow.

Healthcare has accumulated tools like a person who keeps downloading productivity apps but never cleans the kitchen.

We have:

An EHR.

A clearinghouse.

A billing platform.

A payer portal.

A scheduling system.

A fax machine that somehow survived the digital revolution.

A spreadsheet.

Email.

Text messages.

Phone calls.

Passwords.

More passwords.

And another password to reset the password.

Then we put AI on top.

And call it innovation.

Sometimes it is.

Sometimes it is just digital clutter with a language model attached.

The real innovation is not adding another tool.

It is removing unnecessary steps.


Start with the work, not the AI

This is the part I wish more healthcare technology companies talked about.

Don't start with:

“Where can we use AI?”

Start with:

“Where are humans doing repetitive cognitive work that does not require human judgment?”

That question is much more useful.

For example:

A claim is rejected.

Does a human really need to manually determine the basic rejection category every time?

A payer sends a repetitive message.

Does someone need to read it from scratch?

A work queue contains hundreds of claims.

Does a manager need to manually determine which ones deserve attention first?

A denial follows a familiar pattern.

Does someone need to rediscover the same solution every week?

Maybe.

Maybe not.

But these are questions worth asking.


AI's best job may be boring

There is a lot of excitement about AI diagnosing rare diseases.

AI discovering drugs.

AI transforming medicine.

AI replacing entire departments.

Those stories get clicks.

But the most valuable AI in a medical practice may do something incredibly boring.

It might say:

“This claim looks like the last 37 claims that were denied for the same reason.”

That doesn't sound revolutionary.

Good.

Maybe healthcare needs fewer revolutionary demos and more boring things that actually work.

An AI system that quietly identifies a pattern before a human spends 20 minutes investigating it can create real value.

An AI system that prepares a denial for review can create real value.

An AI system that prioritizes A/R work can create real value.

An AI system that identifies missing information before submission can create real value.

The future may be less glamorous than the keynote speeches suggest.

And that's okay.


The real opportunity: cognitive offloading

We talk about outsourcing labor.

But AI's more interesting opportunity in healthcare may be cognitive offloading.

Not:

“Let the machine replace the person.”

But:

“Let the machine carry some of the mental load.”

That is different.

A physician should not have to remember every payer rule.

A biller should not have to manually rediscover every denial pattern.

A clinic manager should not have to monitor every workflow manually.

A nurse should not have to become an insurance detective.

The human still makes the important decision.

The system helps prepare the ground.

That is where I see responsible AI becoming genuinely useful.


The revenue cycle is a workflow, not a collection of departments

Here is the model I use:

Patient

Documentation

Coding

Claim

Payer

Denial

Appeal

Payment

A/R

Most organizations manage these as separate functions.

Patients don't experience them separately.

Neither does the money.

Neither does the physician.

A documentation problem can become a coding problem.

A coding problem can become a denial.

A denial becomes A/R.

A/R becomes staff work.

Staff work becomes operational cost.

And eventually someone asks:

“Why are our physicians spending so much time on administration?”

Because the workflow is connected.

We just happen to manage it in pieces.


The three questions I would ask every clinic owner

If I walked into a small medical practice tomorrow, I would not ask:

“What AI platform are you using?”

I'd ask:

1. Where are you losing money?

Not theoretically.

Show me the actual data.

2. Where are your people wasting time?

Not where they say they are busy.

Where are they repeatedly doing work that could be eliminated, simplified or automated?

3. Where does the physician get pulled into the workflow?

This one matters.

Every time a physician has to intervene in an administrative process, ask:

Why?

Sometimes the answer will be legitimate.

Sometimes it will be embarrassing.


Three experts. Three uncomfortable lessons.

Christine Sinsky, MD: Fix the system

Christine Sinsky, MD, has spent years studying physician work and burnout.

One of the most important ideas in this conversation is that burnout is not simply an individual resilience problem.

It is deeply influenced by the environment in which physicians work.

That should change how leaders respond.

If the workflow is broken, telling physicians to become more resilient is like telling someone to exercise harder because the office chair is broken.

It misses the point.

Fix the chair.

Then talk about exercise.


Kimberly S. Barnes, APRN, CNM: Trust matters

Barnes matters to this story because Martin chose her.

That choice says something.

When the caregiver becomes the patient, clinical competence is not the only thing that matters.

Trust matters.

Familiarity matters.

Knowing that someone has your back matters.

Healthcare organizations sometimes try to manufacture patient experience with surveys and scripts.

But trust is not manufactured by a script.

It is earned through relationships.


The lesson from Devin: Small acts are not small

Devin's role in Martin's story is easy to overlook.

A nurse decorated the room.

A nurse stayed close.

A nurse held her during a frightening moment.

None of this would make a hospital technology conference keynote.

But the patient remembered it.

That should make us uncomfortable.

Because healthcare sometimes measures what is easy to count and ignores what is easy to feel.

A human hand cannot be easily entered into a dashboard.

But a patient knows when it is there.


The statistics tell one story. Kourtney tells another.

The statistics tell us physician burnout is improving.

That's good.

The statistics also tell us administrative burden remains a significant issue.

That's important.

The story of Kourtney Martin tells us something the numbers cannot:

When you are vulnerable, the experience of care is personal.

Put those together and we get a different definition of healthcare innovation.

Not:

More technology.

Not:

More automation.

Not:

More data.

Instead:

Less unnecessary work between the human beings who need each other.

That is a much harder problem.

It is also a much more interesting one.


A practical framework: Eliminate before you automate

Here is the framework I would recommend:

1. Eliminate

Ask:

Does this task need to exist?

If the answer is no, stop doing it.

Congratulations.

You just built your first automation.

Without buying anything.

2. Simplify

If the task must exist, make it easier.

Remove unnecessary steps.

Reduce handoffs.

Standardize information.

3. Standardize

Create a predictable process.

AI works better when workflows are understandable.

Humans do too.

4. Automate

Only now should you ask what software can do.

5. Measure

Did it actually improve the workflow?

If not, change it.

Or kill it.

That last part is important.

Healthcare needs more permission to kill bad workflows.


Don't automate chaos

This may be the most important warning in this article.

AI can make a bad process faster.

It cannot automatically make the process good.

If your workflow requires six unnecessary steps, adding AI to step four does not solve the other five.

You have simply created a faster inefficient workflow.

That is why the sequence matters:

Eliminate → Simplify → Standardize → Automate → Measure.

Not:

Buy AI → announce AI → hope for ROI.


A 30-day experiment for your practice

You do not need a three-year transformation project.

Start with 30 days.

Days 1–7: Watch

Have staff document administrative interruptions.

Every time someone has to:

  • re-enter data
  • search for information
  • call a payer
  • check a portal
  • correct a claim
  • chase documentation
  • explain a denial
  • escalate something to the physician

Record it.

No judgment.

Just observe.

Days 8–14: Rank

Score each task on:

Frequency

Time

Frustration

Financial impact

The worst combination is high frequency + high time + high frustration.

Start there.

Days 15–21: Redesign

Ask:

Can we eliminate it?

Can we simplify it?

Can someone else do it?

Can we standardize it?

Can software handle part of it?

Days 22–30: Test

Automate one small part.

Keep a human review step.

Measure the outcome.

Then decide.

That is innovation without the theater.


What should you measure?

Forget vanity metrics.

Measure:

Denial rate

Clean claim rate

Days in A/R

First-pass resolution

Appeal success

Rework

Staff hours

Physician administrative hours

Time to resolution

Revenue recovered

And one metric I wish more healthcare companies used:

Human hours returned.

If your system saves 500 hours, where did those hours go?

Did physicians spend them with patients?

Did staff handle more meaningful work?

Did someone stop taking work home?

Did your practice increase capacity?

Did patients get faster answers?

If the answer is yes, now we're talking.


The AI safety question nobody should skip

Before automating a workflow, ask:

What happens when the system is wrong?

That question is more important than:

“How accurate is the AI?”

Why?

Because accuracy without context is meaningless.

A 99% accurate system can still cause serious problems if the 1% occurs in the wrong place.

So build:

Human review.

Escalation rules.

Audit trails.

Confidence thresholds.

Exception handling.

Monitoring.

Clear accountability.

AI should not become the new mysterious employee nobody knows how to supervise.


Legal and compliance considerations

Medical billing is not a playground for improvisation.

AI systems handling healthcare information need appropriate privacy and security safeguards.

Practices should consider:

HIPAA and protected health information

Business associate requirements where applicable

Data retention

Access controls

Auditability

Coding and billing compliance

Documentation requirements

Payer contracts and rules

Human accountability

Vendor agreements

Most importantly, never confuse:

“The AI suggested it”

with

“The practice is not responsible.”

Technology does not magically transfer accountability.

Healthcare organizations should obtain appropriate legal, compliance and security advice for their specific use case.


Ethical considerations

There is another question beyond compliance.

Should we automate this?

That is an ethical question.

Suppose automation saves the practice money.

Great.

But does it make the patient's experience worse?

Does it create barriers?

Does it unfairly reject claims?

Does it hide errors?

Does it make it harder for staff to challenge an incorrect recommendation?

Does it shift work onto patients?

Does it create a system that nobody can explain?

Efficiency is not automatically ethical.

A healthcare system can be extremely efficient at doing the wrong thing.

The goal is responsible efficiency.


What I think healthcare gets wrong about AI

We keep asking AI to do increasingly complicated things.

Maybe we should first ask it to do simpler things extremely well.

Find.

Classify.

Summarize.

Prioritize.

Recommend.

Prepare.

Route.

Monitor.

Then let a human decide.

That may sound less exciting.

But it is much closer to how trustworthy healthcare systems should evolve.


What OnnX is trying to build

This is the problem that led me to build OnnX.

I am not interested in putting an AI chatbot on top of an already complicated billing workflow and calling it transformation.

I am interested in something much more practical.

Can AI remove repetitive cognitive work from medical billing while keeping humans in control?

Consider a denied claim.

Instead of:

Denial → human searches → human interprets → human hunts for documentation → human decides → human prepares response

Imagine:

Denial → AI analyzes → AI identifies likely cause → AI retrieves relevant information → AI recommends action → human approves → workflow proceeds

That is the difference between an AI feature and an AI workflow.

One answers questions.

The other helps move work forward.


Why small and midsize practices matter

Large health systems can throw people at administrative problems.

Small practices cannot.

A five-physician practice cannot necessarily hire another department every time a payer creates another administrative requirement.

The physician becomes the safety net.

The office manager becomes the safety net.

The biller becomes the safety net.

Eventually, everyone becomes the safety net.

That is not a scalable operating model.

For smaller practices, workflow automation is not necessarily about replacing people.

It can be about making a small team capable of operating like a much larger one.

That is where AI could become economically meaningful.


But here is the uncomfortable part

Sometimes the answer is not AI.

I want to say that clearly as someone building an AI company.

If a process can be fixed with a policy change, fix the policy.

If delegation solves it, delegate it.

If training solves it, train people.

If the task should not exist, eliminate it.

If a simple rule handles it, use the rule.

Only use AI when AI actually adds value.

Healthcare does not need another company telling it that every problem requires artificial intelligence.

Sometimes the smartest algorithm is:

Stop doing that.


The future of healthcare AI may be surprisingly boring

I think the best healthcare AI may eventually become almost invisible.

It won't announce itself.

It won't necessarily have a flashy interface.

It will quietly notice:

“This looks familiar.”

“This information is missing.”

“This claim resembles previous denials.”

“This account needs attention.”

“This task can wait.”

“This one cannot.”

“This requires a human.”

And then it will get out of the way.

That is important.

Because the ultimate goal of healthcare technology should not be to make technology more visible.

It should make care more visible.


The patient should never have to know how complicated the back office is

This is one of my favorite tests.

Imagine a patient sitting in an exam room.

They should not have to care about:

The clearinghouse.

The payer portal.

The denial queue.

The coding edit.

The A/R aging report.

The workflow exception.

The billing system.

They just want to know:

What is wrong with me?

What do we do next?

Will I be okay?

That's it.

And physicians should have more time to answer those questions.


What if AI's greatest healthcare contribution is time?

We usually describe AI using capability.

What can it generate?

What can it predict?

What can it summarize?

What can it automate?

But maybe the most important metric is simpler:

What can it give back?

Five minutes.

Twenty minutes.

An hour.

An evening.

A weekend.

A little less cognitive noise.

A little more attention.

A little more patience.

A little more time to explain.

A little more time to listen.

A little more time to hold someone's hand.

That is not a small outcome.

That is healthcare.


The Kourtney Martin test

Here is the test I would use for any healthcare technology:

If Kourtney Martin were sitting in the exam room, would this technology make her experience better?

Not theoretically.

Actually.

Would the physician have more time?

Would the nurse have more attention?

Would the patient receive clearer communication?

Would unnecessary administrative work disappear?

Would the system make someone feel less alone?

If yes, keep exploring it.

If not, perhaps we are solving the wrong problem.


Three myths worth killing

Myth #1: More technology means better healthcare.

No.

Better workflow means better healthcare.

Technology is one possible ingredient.

Not the recipe.

Myth #2: AI's goal should be replacing humans.

No.

The better goal is replacing unnecessary human work.

Those are very different things.

Myth #3: Billing is separate from patient care.

Absolutely not.

Billing affects staffing.

Staffing affects capacity.

Capacity affects access.

Administrative burden affects physicians.

Physician time affects patient care.

Everything connects.


The biggest opportunity may be hiding in plain sight

Healthcare has spent enormous amounts of energy trying to improve the clinical encounter.

But what surrounds the clinical encounter?

A mountain of administrative work.

Before the patient enters:

Scheduling.

Eligibility.

Authorization.

Documentation.

After the patient leaves:

Coding.

Claims.

Denials.

Appeals.

A/R.

Follow-up.

The clinical encounter is only one part of the journey.

If we want truly human-centered healthcare, we have to redesign the entire journey.

That includes the back office.

Especially the back office.


A physician entrepreneur's confession

I will admit something.

When I first started thinking about healthcare AI, it was tempting to focus on the technology.

That's what entrepreneurs do.

We see a capability and immediately ask:

“What can we build?”

But healthcare forces you to ask a harder question:

“What should we build?”

And then an even harder one:

“Will anyone actually use it?”

That changed how I think about OnnX.

The goal is not to build something impressive.

The goal is to solve something painful.

There is a difference.


The best product may be the one nobody talks about

Imagine a clinic owner telling a friend:

“We bought this incredible AI platform.”

That's nice.

Now imagine saying:

“We don't spend three hours every Friday fixing the same billing problems anymore.”

That is better.

The second statement is not sexy.

It is useful.

And usefulness compounds.


What I would tell every physician starting a practice

Do not wait until your practice is overwhelmed to map your workflows.

Do it early.

Document who does what.

Measure where claims fail.

Track A/R.

Understand payer patterns.

Separate clinical judgment from administrative work.

Build escalation rules.

Standardize repetitive tasks.

And when technology can safely remove work, use it.

But keep asking:

Does this make the practice more human?

If the answer is no, rethink it.


What I would tell every clinic owner

Your billing workflow is not merely a finance function.

It is an operating system.

It affects:

Cash flow.

Staff workload.

Physician time.

Patient access.

Practice growth.

Retention.

Stress.

Treat it accordingly.

Do not wait for your A/R to become a crisis.

Do not wait for physicians to become exhausted.

Do not wait until your best employee quits because they spend every Friday afternoon fixing the same problem.

Measure the workflow now.


What I would tell healthcare innovators

Stop selling AI.

Start selling outcomes.

Don't tell a physician:

“Our model has impressive reasoning capabilities.”

Tell them:

“We reduced denial-review time by 40%.”

Don't say:

“We have an intelligent agent.”

Say:

“Your staff no longer has to manually review these 300 routine cases.”

Don't say:

“We use generative AI.”

Say:

“Your physician spends less time on administrative work.”

The technology is interesting.

The outcome is the product.


Final Thoughts: Give the caregiver back

Kourtney B. Martin knew how healthcare worked.

Then she became the patient.

And when she needed reassurance, what mattered was not another layer of technology.

It was another human being.

Kimberly S. Barnes was there.

Devin was there.

They gave Martin something healthcare cannot manufacture at scale:

presence.

That story should make every healthcare leader pause.

Because we are building increasingly intelligent systems while simultaneously asking whether physicians have enough time to be present with patients.

That is backwards.

The question isn't whether AI can make healthcare more technologically sophisticated.

It can.

The question is whether we will use it wisely.

Will we use AI to add another layer of complexity?

Or will we use it to remove complexity?

Will we automate people?

Or will we automate the work that prevents people from doing what only people can do?

Will we chase productivity?

Or will we protect attention?

I know which future I want to build.

Less clicking.

Less chasing.

Less rework.

Less administrative noise.

And more time for the work that brought most of us into healthcare in the first place.

Caring for people.


Get Involved

So here is my challenge to physicians and clinic owners:

If you could permanently eliminate ONE administrative task from your practice tomorrow, what would it be?

Don't give me the politically correct answer.

Give me the task that makes you mutter something under your breath when nobody is listening.

Tell me in the comments.

I want to know where the real friction is.

And if this perspective resonates with you, repost this article and send it to another physician, practice leader or healthcare innovator.

Maybe someone in your network is fighting the exact same workflow you are.

Maybe they have already solved it.

Either way, the conversation is worth having.

Question the workflow.

Protect human attention.

Use AI where it actually helps.

The future of healthcare does not need to be less human.

It needs to be less unnecessarily difficult for humans.


About the Author

Dr. Daniel Cham is a physician, medical consultant and healthcare entrepreneur whose work sits at the intersection of medical technology, healthcare management, medical billing and AI-powered workflow automation.

He is the founder of OnnX, an AI-powered medical billing SaaS focused on helping small and midsize medical practices reduce unnecessary administrative work and improve revenue-cycle workflows.

His perspective is simple:

Technology should make healthcare easier to practice, not harder.

Connect with Dr. Cham on LinkedIn to follow his work on healthcare operations, AI, medical billing and practical innovation.

LinkedIn: linkedin.com/in/daniel-cham-md-669036285


Disclaimer

This article is intended for general educational and informational purposes. It does not constitute medical, legal, regulatory, compliance, financial or professional advice. Specific healthcare, billing, technology and compliance decisions should be evaluated with appropriately qualified professionals.


Continue the Conversation

Healthcare is moving quickly.

But the most useful ideas are often found in the less glamorous parts of medicine: the workflows, decisions, operational problems and everyday experiences that determine whether healthcare actually works.

Explore more perspectives on healthcare, medical practice, technology, billing, operations and innovation.

Visit the personal website:

Dr. Daniel Cham's website

Listen to the podcast:

Dr. Daniel Cham on Spotify

Watch and subscribe on YouTube:

Dr. Daniel Cham on YouTube

Follow updates on X:

Dr. Daniel Cham on X

Follow on Facebook:

Dr. Daniel Cham on Facebook

Knowledge creates options. Curiosity creates better questions. Better questions create better healthcare.

Start there.


Free Resource

Want a practical starting point?

Check the Featured section of my LinkedIn profile for a free resource.

No signup required.

Take it.

Use it.

Share it with your team.


References

Norton Healthcare — “From caregiver to patient: A nurse midwife’s own birth story.”

The August 21, 2026 story about Kourtney B. Martin provides the human-interest foundation for this article and describes her experience moving from caregiver to patient.

American Medical Association — Physician burnout data.

The AMA's 2026 reporting shows physician burnout declining to 41.9%, while significant system and administrative challenges remain.

American Medical Association — Prior authorization burden.

AMA survey findings illustrate the continuing administrative burden associated with payer requirements and physicians' skepticism that recent insurer reforms will meaningfully reduce the problem.


One Last Question

Maybe we have been measuring healthcare incorrectly.

We measure what gets billed.

What gets collected.

What gets documented.

What gets coded.

What gets denied.

What gets paid.

But perhaps we should also measure:

How much time did we give back?

How many minutes did a physician spend with a patient instead of a payer portal?

How many hours did a nurse spend caring instead of chasing paperwork?

How many evenings did a clinic owner get back?

How many interruptions disappeared?

How many moments of human connection became possible?

Those numbers may never fit neatly into a revenue-cycle dashboard.

But patients notice them.

Physicians notice them.

Families notice them.

And perhaps that is the point.

The best healthcare technology may not be the technology patients notice.

It may be the technology that quietly gives their caregivers enough time to notice them.

#HealthcareAI #MedicalBilling #HealthcareAutomation #PhysicianBurnout #AdministrativeBurden #RevenueCycleManagement #MedicalPracticeManagement #HealthcareInnovation #HealthTech #AIinHealthcare #PhysicianLeadership #ClinicOwners #HealthcareOperations #DigitalHealth #PatientExperience #HumanCenteredHealthcare #MedicalTechnology #PhysicianEntrepreneur #HealthcareLeadership #OnnX

 

Friday, August 21, 2026

Haley Ashcom, Lindsay Clancy, and the Healthcare Signals We Keep Missing

What a mother’s recovery story—and a courtroom tragedy—can teach physicians about diagnosis, data, AI, and the hidden problems inside medical billing



“When you don't have a clear definition, and you have a very rare disorder, and there's a lot of stigma in society for folks disclosing some of these symptoms…” Dr. Katrina Furey, psychiatrist specializing in women's mental health


There is a sentence in healthcare that sounds almost too obvious to be controversial:

We need more data.

More data.

More dashboards.

More AI.

More analytics.

More interoperability.

More alerts.

More automation.

More information.

But what if we have been asking the wrong question?

What if healthcare doesn't primarily suffer from an information shortage?

What if we suffer from an information-connection problem?

Consider the story of Haley Ashcom.

After giving birth to her first son, Kane, in 2020, Ashcom began experiencing insomnia and anxiety. She was diagnosed with postpartum depression. But her symptoms progressed. She told CBS News that intrusive thoughts eventually began “turning into voices.” She ultimately sought psychiatric hospitalization and says she was diagnosed with postpartum psychosis. After treatment, she recovered and later had three more children without experiencing postpartum psychosis again.

Her story is remarkable for a simple reason:

The information changed.

And eventually, the interpretation changed with it.

Now put that story next to the name Lindsay Clancy.

Clancy, a former labor-and-delivery nurse from Duxbury, Massachusetts, is currently on trial over the 2023 deaths of her three children, Cora, Dawson, and Callan Clancy. Her defense argues that postpartum psychosis rendered her not criminally responsible. Prosecutors dispute that interpretation. As of August 21, 2026, the defense has rested its case.

These are not the same story.

They should not be treated as the same story.

Haley Ashcom's story is a story of illness, recognition, treatment, and recovery.

The Lindsay Clancy case is an unresolved criminal proceeding involving profoundly tragic deaths and competing medical and legal interpretations.

But there is a question connecting them.

And it is a question I think every physician, healthcare executive, and healthcare technology founder should be asking:

What happens when the signals are there—but nobody connects them soon enough?

That question goes far beyond postpartum mental health.

It reaches directly into the physician practice.

And eventually, into the billing office.


The Uncomfortable Truth

Here's my contrarian take:

Your practice may not have a billing problem.

It may have a signal-recognition problem.

The denial is just where the problem finally becomes visible.

That is an uncomfortable distinction.

Because if you call it a billing problem, you can hire another biller.

Buy another software platform.

Add another dashboard.

Create another work queue.

Outsource another function.

And congratulate yourself on being “proactive.”

Meanwhile, the same problem keeps coming back.

Like a sequel nobody asked for.


Start With Haley Ashcom

Ashcom's story deserves to be treated as a human story first.

Not as a metaphor.

Not as a marketing prop.

Not as evidence that some piece of technology would have magically solved everything.

She experienced a serious medical condition.

She sought help.

Her symptoms evolved.

Her clinical understanding evolved.

Treatment followed.

And she recovered.

That alone is worth telling.

CBS News reports that postpartum psychosis is rare, affecting approximately 1 to 2 women per 1,000 after delivery, but can be dangerous and requires urgent treatment.

ACOG similarly describes postpartum psychosis as a very rare and serious condition and recommends immediate psychiatric help.

But there is a subtle lesson here.

The important thing wasn't simply that information existed.

The important thing was that the meaning of the information changed as the story developed.

Insomnia.

Anxiety.

Intrusive thoughts.

Voices.

Escalation.

Hospitalization.

Diagnosis.

Treatment.

Recovery.

Healthcare is rarely one data point.

It is a sequence.

A pattern.

A story.


Now Think About Your Clinic

A patient arrives.

The front desk captures insurance information.

The eligibility response comes back.

The patient sees the physician.

The physician documents the encounter.

A diagnosis is recorded.

A procedure is performed.

A code is selected.

An authorization may or may not exist.

A claim is generated.

The claim is submitted.

Then:

DENIED.

The billing department gets the unpleasant little notification.

Someone opens the account.

Someone investigates.

Someone corrects it.

Someone resubmits it.

Someone waits.

Someone follows up.

Eventually, someone gets paid.

And everyone says:

“Good. We fixed the denial.”

Did you?

Or did you just repair the symptom?


The Denial Is Talking to You

This is the part I wish more healthcare leaders would take seriously.

A denial is not merely an administrative nuisance.

It is information.

It is telling you something.

Maybe:

The documentation didn't support the claim.

Maybe:

The authorization wasn't obtained.

Maybe:

Eligibility wasn't verified correctly.

Maybe:

The payer's rules changed.

Maybe:

The coding didn't match the service.

Maybe:

The information existed in the chart but wasn't available to the billing workflow.

Maybe:

Your staff has been compensating for a broken process manually for six months.

The denial is saying:

“Hey. Something happened upstream.”

And we're often responding:

“Thanks. We'll work the queue.”

That is the healthcare equivalent of putting a Band-Aid on the dashboard warning light.


The Question We Should Ask Instead

Don't ask:

“How do we work denials faster?”

Ask:

“Why did this claim become a denial?”

Then go one level deeper.

Why wasn't the problem detected before submission?

Then deeper:

Where did the necessary information exist?

Then:

Who had it?

Then:

When did they have it?

Then:

Why didn't the system connect it to the decision?

That is where things get interesting.


The Hidden Architecture of a Medical Practice

Most physician owners don't think of their practice as a data architecture.

They think:

Patients.

Staff.

Phones.

EHR.

Billing.

Insurance.

Payroll.

Maybe a little coffee.

But underneath all of that is an information system.

Information moves.

Or doesn't.

That distinction is worth money.

A patient's insurance information moves from registration to eligibility.

Clinical information moves from physician to documentation.

Documentation moves into coding.

Coding moves into claims.

Claims move to payers.

Payer responses move back into billing.

Denial information should move backward into the workflow.

But often it doesn't.

That last step is the problem.

The system forgets.

The biller learns.

The manager learns.

The physician learns.

The practice's spreadsheet learns.

But the system forgets.

So the same problem happens again.


Most healthcare organizations don't have a learning problem. They have a memory problem.

We learn something.

Then we lose it.

A biller discovers that a payer requires something unusual.

She remembers.

Then she leaves.

Knowledge leaves with her.

A staff member discovers that a certain workflow causes recurring denials.

He creates a spreadsheet.

Then the spreadsheet becomes obsolete.

A physician learns that documentation for a particular service needs additional detail.

She remembers.

Then six months later, the process changes.

The organization keeps relearning the same lesson.

That's expensive.


The Human Brain Is Doing the Work Your Software Should Be Doing

Your best employees probably have a mental model of your practice.

They know:

“That payer always does this.”

“That provider needs this.”

“Check this before submitting.”

“Don't forget that authorization.”

“Look at the old note.”

“This one is unusual.”

Those people are valuable.

But here's the problem.

You have turned your employees into biological middleware.

They are the integration layer.

They move information between systems.

They remember exceptions.

They translate one workflow into another.

They catch things the software doesn't.

And then we wonder why they're exhausted.


This Is Where AI Actually Gets Interesting

Not because AI can “replace the biller.”

That pitch is getting old.

And frankly, it's not particularly intelligent.

The better question is:

Can AI help the practice remember what it has already learned?

Can it recognize patterns across thousands of claims?

Can it identify recurring problems?

Can it compare current documentation against known requirements?

Can it flag missing information before submission?

Can it identify that five apparently different denials are actually the same problem?

Can it surface an exception for human review?

Can it explain why something was flagged?

That is much more interesting.


AI Should Not Be the Doctor

And it shouldn't be the biller either.

At least not in the simplistic sense.

Healthcare AI should not be built around:

“Let the machine decide.”

It should be built around:

“Let the machine notice.”

Notice patterns.

Notice inconsistencies.

Notice missing information.

Notice changes.

Notice exceptions.

Then:

Let humans decide.

That is a much healthier relationship between AI and healthcare.


The Clinical Lesson

This is exactly why Haley Ashcom's story is so powerful.

Her experience demonstrates why context matters.

A symptom is not a diagnosis.

A data point is not a conclusion.

A pattern can change the interpretation.

ACOG's guidance emphasizes screening and diagnosis across pregnancy and postpartum care and specifically calls for immediate medical attention when postpartum psychosis is present.

The clinical lesson is simple:

Don't just collect the signal. Understand the signal in context.

That principle belongs everywhere in healthcare.


And Then There's Lindsay Clancy

The Clancy case makes the question much more uncomfortable.

The current trial has featured conflicting expert testimony about her mental state, including testimony from defense expert Dr. Phillip Resnick and prosecution expert Dr. Avram Mack. Family members and clinicians have also offered different perspectives on her mental-health history and behavior.

This is precisely why healthcare professionals should be careful.

We don't know the final legal answer.

We shouldn't pretend we do.

We shouldn't use an active criminal case to make a simplistic point about mental illness.

And we certainly shouldn't say:

“If only someone had used AI…”

That would be irresponsible.

The appropriate lesson is much more modest:

Complex clinical situations require context, coordination, careful interpretation, and humility about what we do and do not know.

That is true in court.

It is true in the clinic.

It is true in the billing office.


Healthcare's Favorite Mistake

We confuse documentation with understanding.

If something is documented, we assume someone understands it.

Not necessarily.

The EHR may contain the information.

The payer portal may contain the information.

The authorization system may contain the information.

The billing system may contain the information.

The physician may know the information.

The patient may have told someone the information.

And somehow...

Nobody connects it.

That is not a data problem.

That's an architecture problem.


Your EHR May Be Full of Information and Still Be Blind

This sounds contradictory.

It isn't.

Imagine a warehouse filled with boxes.

Everything you need is inside.

But the labels are inconsistent.

Some boxes are in another warehouse.

Some are locked.

Some are written in shorthand.

Some are outdated.

Some are duplicated.

Some are only accessible to certain people.

And nobody has a map.

Technically:

You have everything.

Operationally:

You have nothing when you need it.

That's healthcare data today in miniature.


Why Physician-Owned Practices Feel This More

Large health systems can throw people at complexity.

Small and medium-sized practices can't.

A hospital might have:

coding specialists

revenue-cycle analysts

IT teams

data engineers

compliance departments

authorization teams

informatics specialists

practice administrators

A ten-provider clinic?

Maybe it has:

one office manager

two billers

a front desk

an outsourced service

and somebody named Linda who somehow knows everything.

Every practice has a Linda.

Don't make Linda your data architecture.


The Real Cost of Administrative Friction

People often ask:

“How much revenue are we losing?”

That's important.

But it is only half the question.

Ask:

How much human attention are we wasting?

Every unnecessary denial creates work.

Every missing authorization creates work.

Every eligibility problem creates work.

Every documentation correction creates work.

Every payer phone call creates work.

And every repeated problem creates work again.

The hidden cost is cognitive.

Your staff spends time remembering what your systems should remember.

Your physicians spend time navigating what your systems should connect.

Your practice manager spends time explaining what your dashboards should reveal.

That's expensive.


The Physician Tax Nobody Puts on the Invoice

There is another cost.

Physician attention.

When the practice is poorly designed, administrative problems eventually climb upstream.

A staff member asks the physician for clarification.

The physician answers.

Another question appears.

Another message.

Another chart.

Another documentation request.

Another payer issue.

Five minutes here.

Ten minutes there.

By Friday, the physician has spent hours solving problems that had nothing to do with practicing medicine.

We don't call that a revenue-cycle expense.

Maybe we should.


The New Metric: Cognitive Waste

Here's a metric I'd like healthcare leaders to experiment with:

Cognitive Waste

How many physician or staff minutes are spent resolving problems that could have been prevented with better information, workflow, or automation?

You could calculate it.

Track:

manual touches

repeated corrections

avoidable phone calls

avoidable chart reviews

duplicate data entry

repeated payer research

physician clarification requests

staff escalations

Then ask:

What percentage of this work actually needed a human brain?

That's the interesting number.


What OnnX Is Trying to Change

This is the problem I am working on with OnnX.

The goal isn't simply to process claims.

It is to create a more intelligent revenue-cycle operating layer for physician-owned practices.

The philosophy is straightforward:

Capture the right information.

Connect it.

Check it early.

Learn from what goes wrong.

Prevent the same problem from happening again.

That's very different from:

“Let's work the denial faster.”


Denial Management Is Not the Enemy

To be fair, denial management isn't bad.

You need it.

Claims will be denied.

Payers will make mistakes.

Rules will change.

Patients will change insurance.

Humans will make errors.

No serious operator believes in a zero-denial universe.

The problem is when denial management becomes the business model.

If your organization is getting better at working the same denial every month, congratulations.

You've become very efficient at being inefficient.

That's not transformation.


Denial Prevention Is a Different Game

Denial prevention asks:

Can we identify the failure before submission?

That means looking at:

Eligibility

Authorization

Documentation

Coding

Medical necessity

Provider information

Payer-specific requirements

Patient demographics

Referral requirements

Historical denial patterns

And then asking:

Does everything make sense together?

That's where contextual intelligence becomes useful.


Three Questions Every Clinic Owner Should Ask Monday Morning

Don't start with a six-month digital transformation project.

Start small.

Ask your team:

1. What problem do we fix every single week?

Write down the answer.

2. What do you check manually because you don't trust the system?

This answer may be even more valuable.

3. What do we discover only after the claim is denied?

That is where the money is hiding.


The 30-Day Challenge

Here's a practical experiment.

Week One: Find the Pain

Take your last 100 denials.

Categorize them.

Don't make 37 categories.

Start with five or ten.

Look for repetition.

 

Week Two: Trace the Crime Scene

For your top three denial categories, work backward.

Where did the problem originate?

Registration?

Eligibility?

Scheduling?

Clinical documentation?

Coding?

Authorization?

Payer configuration?

Nobody gets blamed.

You're mapping the crime scene.

 

Week Three: Move the Check Upstream

Take one recurring problem.

Create a check before the claim goes out.

Do it manually if you have to.

The goal is proving that prevention is possible.

 

Week Four: Automate the Boring Part

Once you understand the rule, automate what is predictable.

Keep humans involved where judgment matters.

Measure the result.

Then repeat.


What to Measure

Forget vanity dashboards.

Measure things that tell you whether the practice is getting smarter.

Preventable denial rate

Recurring denial rate

First-pass acceptance

Manual touches per claim

Average correction time

Days in A/R

Staff minutes per claim

Authorization failure rate

Eligibility failure rate

Documentation-related denials

Revenue leakage

And perhaps the most interesting:

How many times did we solve the same problem twice?

If the answer is “a lot,” your system isn't learning.


The Myth of the Perfect Dashboard

A dashboard can tell you:

“Your denial rate is 11.8%.”

Okay.

Now what?

The better system says:

“These three patterns account for 74% of your preventable denials.”

Even better:

“This one workflow change could prevent two of them before submission.”

That's the difference between reporting and intelligence.


The Myth of More Data

More data is not automatically better.

Sometimes more data is just more noise.

Physicians don't need another 47 notifications.

Billing staff don't need another 19 queues.

Clinic owners don't need another dashboard with seventeen shades of red.

They need:

the right information

at the right time

in the right context

with the right next action.

That's it.


The Myth of “AI Will Fix Healthcare”

No.

AI will not fix healthcare.

Neither will blockchain.

Neither will interoperability alone.

Neither will another EHR.

Neither will another billing vendor.

Technology doesn't fix poorly designed processes simply because it is newer.

AI can make a good process better.

It can also make a bad process faster.

That's why the first question should never be:

“Where can we use AI?”

Ask:

“Where are we repeatedly losing time, information, or money—and why?”

Then decide whether AI belongs there.


The Legal and Ethical Line

This matters enormously.

Healthcare AI must not become a machine for maximizing reimbursement at any cost.

Accurate coding is not aggressive coding.

Complete documentation is not manufactured documentation.

Revenue optimization is not justification for unsupported claims.

The standard should remain:

accurate clinical care

accurate documentation

accurate coding

accurate claim

appropriate reimbursement

Technology should strengthen that chain.

Not corrupt it.

And every automated recommendation should have appropriate governance, review, auditability, and human accountability.


The Most Dangerous AI Is the AI Nobody Questions

Here's another contrarian thought.

We spend a lot of time worrying about hallucinations.

We should.

But healthcare has another AI problem:

false confidence.

A system produces a recommendation.

It looks polished.

It has a confidence score.

Everyone assumes the machine knows.

But nobody asks:

What information did it not see?

That's the dangerous question.

Because context can change everything.


The Future Isn't Human vs. AI

That's yesterday's debate.

The real future is:

Human judgment + machine pattern recognition + better information architecture.

Let machines search.

Let machines compare.

Let machines detect.

Let machines prioritize.

Let machines remember.

Let humans interpret.

Let humans decide.

Let humans remain accountable.

That's a partnership worth building.


The Bigger Opportunity

I don't think the next great healthcare company will necessarily be the company with the most impressive AI model.

It may be the company that understands where information gets lost between one healthcare action and the next.

That's a much harder problem.

And probably a much more valuable one.

Because healthcare is full of gaps.

Between:

patient and provider

provider and EHR

EHR and billing

billing and payer

payer and practice

practice and patient

And every gap creates friction.


The Hidden Business Model of Healthcare

Here's the uncomfortable part.

A lot of healthcare technology is built around managing the consequences of fragmentation.

One company handles this.

Another handles that.

Another cleans up the first company's mistakes.

Another analyzes the cleanup.

Another sells you a dashboard showing the cleanup.

And somewhere at the bottom of the stack:

a human fixes everything.

We call this an ecosystem.

Sometimes it's just expensive plumbing.


What If We Designed From the Other Direction?

Instead of:

How do we manage the complexity?

Ask:

How do we remove the complexity?

Instead of:

How do we work more denials?

Ask:

How do we create fewer preventable denials?

Instead of:

How do we give staff more tools?

Ask:

How do we give staff fewer things to do?

Instead of:

How do we make AI smarter?

Ask:

How do we make the workflow smarter?

That's the contrarian shift.


The Human Story Comes Back

This is why I keep coming back to Haley Ashcom.

Her story isn't really about technology.

It's about something much more basic.

Pay attention to the story.

Listen when something changes.

Don't isolate one symptom from everything around it.

Don't assume yesterday's explanation still fits today's information.

And don't confuse the existence of data with understanding.

Those are clinical lessons.

But they're also leadership lessons.

And they're also technology lessons.


What Physicians Should Take Away

If you're a physician-owner, I would not ask you to become a revenue-cycle expert.

I would ask you to become curious.

Walk into your billing operation.

Ask:

What are we repeatedly fixing?

Ask:

What information are you missing?

Ask:

What do you know that the system doesn't know?

Ask:

What do we discover too late?

Then listen.

Don't defend the system.

Don't explain why the vendor can't do it.

Just listen.

You may discover that the biggest problem in your revenue cycle is hiding in plain sight.


What Founders Should Take Away

If you're building healthcare technology, resist the temptation to sell features.

Sell fewer problems.

That's harder.

But better.

Don't say:

“Our platform has AI-powered analytics.”

Say:

“We found a recurring problem that costs clinics money and staff time. Here's how we detect it earlier.”

Don't sell intelligence.

Demonstrate it.


What Healthcare Leaders Should Take Away

The future healthcare organization won't necessarily be the one with the most technology.

It will be the one that learns fastest from what happens inside the organization.

Every denial becomes a lesson.

Every exception becomes a pattern.

Every staff workaround becomes product feedback.

Every patient complaint becomes information.

Every operational failure becomes an opportunity to redesign the system.

That is a learning organization.

And that is where healthcare should be heading.


FAQ

Is this article suggesting that Haley Ashcom's experience could have been solved by technology?

No.

That would be an irresponsible conclusion.

Her story is fundamentally a human and clinical story about postpartum psychosis, recognition, treatment, and recovery. Technology may support healthcare, but it does not replace clinical judgment.

Why include Lindsay Clancy's case?

Because the current trial has renewed national attention to postpartum psychosis. But it is an active legal proceeding, and the article deliberately avoids making conclusions about Clancy's criminal responsibility.

Is postpartum psychosis the same as postpartum depression?

No. They are distinct conditions. ACOG describes postpartum psychosis as very rare and serious and says it requires immediate psychiatric help.

How common is postpartum psychosis?

CBS News reports approximately 1–2 cases per 1,000 women after delivery.

What does this have to do with medical billing?

The connection is not that psychiatric illness and billing are equivalent.

The connection is that both involve signals, context, interpretation, timing, and action.

Is denial management unnecessary?

No.

Denial management remains necessary.

The contrarian point is that organizations should not confuse being good at recovering from preventable failures with being good at preventing those failures.

Should clinics replace billers with AI?

No.

The better objective is to eliminate repetitive work and allow experienced people to spend more time on exceptions, judgment, communication, and complex cases.

What should clinics automate first?

Start with repetitive, measurable, rule-based work where errors are frequent and preventable.

What is the biggest AI mistake healthcare organizations make?

Using AI before fixing the workflow.

Garbage in, garbage out is still true—even when the garbage is processed by an expensive model.


Three Expert Perspectives

Dr. Uruj Kamal Haider — Perinatal Psychiatry

Haider's explanation of postpartum psychosis underscores how profoundly psychosis can affect perception and information processing.

Lesson for healthcare leaders: Context changes interpretation.

 

Dr. Catherine Birndorf — Reproductive Psychiatry

Birndorf has highlighted concern about postpartum psychosis being underdiagnosed.

Lesson for healthcare leaders: A problem can be serious, visible, and still systematically under-recognized.

 

Dr. Phillip Resnick — Forensic Psychiatry

Resnick testified for the defense in the Clancy trial and offered the opinion that Clancy was psychotic at the time of the killings. That is an expert opinion presented in an adversarial proceeding, not an established fact.

Lesson for healthcare leaders: Complex clinical situations can generate radically different interpretations of the same underlying information.

That should make us humble about automated conclusions.


Recent News

The timing of this conversation is important.

On August 21, 2026, CBS News published Haley Ashcom's account of postpartum psychosis as the Lindsay Clancy trial continues to draw attention to the condition.

The same day, AP reported that Clancy's defense had rested after presenting testimony centered on her mental state and the defense's argument that postpartum psychosis affected her criminal responsibility.

ACOG's guidance reinforces that postpartum psychosis is a medical emergency requiring immediate attention.

The news cycle gives us the hook.

But the lesson is evergreen:

Healthcare needs to get better at connecting signals before the consequences become irreversible.


Three References

1. CBS News — Haley Ashcom's postpartum psychosis experience
A current human-interest account of Ashcom's symptoms, diagnosis, treatment, recovery, and decision to speak publicly about postpartum psychosis.
Read the CBS News report

2. Associated Press — Lindsay Clancy trial
Current reporting on the defense resting its case and the competing medical interpretations presented during the trial.
Read the AP report

3. American College of Obstetricians and Gynecologists — Perinatal Mental Health
Clinical guidance covering screening, diagnosis, and the need for immediate medical attention in postpartum psychosis.
Read ACOG guidance


Final Thoughts

Maybe the biggest healthcare innovation isn't another app.

Maybe it's a healthcare system that actually remembers what it has learned.

A patient tells you something.

A nurse notices something.

A physician documents something.

A family member raises a concern.

A biller sees a recurring denial.

A staff member creates a workaround.

A payer sends a signal.

The information is already there.

The question is:

Who connects it?

That is the opportunity.

And perhaps the most provocative question of all is this:

How much of healthcare's waste exists not because we lack information, but because nobody connected the information soon enough?

Think about that the next time your billing department says:

“We have another denial.”

Maybe the denial isn't the problem.

Maybe it's finally telling you where the problem began.


Get Involved

What is one recurring problem in your practice that everyone has learned to work around—but nobody has actually fixed?

Tell me in the comments.

Share this article with a physician or clinic owner who needs to see this conversation differently.

And if you believe physician-owned practices deserve technology designed around less friction, better information, and fewer unnecessary administrative handoffs, join the conversation.

Raise your hand.

Challenge the conventional workflow.

Find the signal.

Fix the source.

Because healthcare doesn't need another system that makes the old system slightly faster.

It needs systems that make the old problems less necessary.


About the Author

Dr. Daniel Cham is a physician, healthcare technology consultant, and founder of OnnX, an AI-powered medical billing SaaS focused on reducing administrative friction for small and medium-sized physician-owned practices.

His work sits at the intersection of clinical medicine, healthcare operations, medical billing, artificial intelligence, and healthcare innovation.

He is particularly interested in a simple question:

How can technology help physicians spend less time fighting the system and more time practicing medicine?

Connect with Dr. Cham on LinkedIn:

linkedin.com/in/daniel-cham-md-669036285


Continue the Conversation

Healthcare is changing quickly.

The most useful ideas often appear where medicine, technology, operations, and human experience collide.

For additional perspectives, practical strategies, and conversations about healthcare innovation:

Visit Dr. Cham's website

Listen to the podcast on Spotify

Watch on YouTube

Follow Dr. Cham on X

Follow Dr. Cham on Facebook

Explore the ideas. Question the assumptions. Share what you're learning.

Because knowledge becomes useful when it changes what we do.


Free Resource

Looking for a practical next step?

Check the Featured section of my LinkedIn profile for a free resource.

No signup required.

Start there.

Then take one idea from this article and test it inside your own practice.


Disclaimer

This article is intended for general educational and informational purposes only. It does not constitute medical, legal, compliance, coding, reimbursement, financial, or other professional advice.

Clinical decisions should be made by qualified healthcare professionals based on the individual patient and applicable clinical guidance.

Questions involving billing, coding, reimbursement, contracts, privacy, compliance, or legal obligations should be reviewed with appropriately qualified professionals and the applicable requirements.

The discussion of the Lindsay Clancy criminal proceedings is provided for healthcare and educational context only and should not be interpreted as a determination of criminal responsibility, medical causation, or legal fact.


One More Thing

Don't ask whether your practice has enough data.

Ask whether your practice can see what the data is trying to tell you.

Don't ask how quickly you can work the next denial.

Ask why you keep receiving the same denial.

Don't ask where you can add AI.

Ask where better information could prevent unnecessary human work.

That's where the interesting healthcare problems are.

And that's where the next generation of healthcare innovation should begin.


#HealthcareAI #HealthcareInnovation #MedicalBilling #RevenueCycleManagement #RCM #DenialPrevention #HealthcareOperations #PhysicianLeadership #PhysicianOwnedPractices #HealthcareTechnology #HealthTech #MedicalTechnology #ClinicalData #HealthcareData #AIinHealthcare #HealthcareManagement #PracticeManagement #PhysicianEntrepreneur #DigitalHealth #HealthcareTransformation #RevenueCycle #MedicalPractice #HealthcareLeadership #OnnX

 

Kourtney Martin Spent Her Career Caring for Patients. Then She Became One.

She knew how healthcare worked. Then she experienced it from the other side. What she learned should make every healthcare leader rethink in...