Wednesday, October 21, 2026

Stephanie Johnson and Marcus Brown: A Brother’s Liver Donation, a Sister’s Second Chance, and the Healthcare Problem Nobody Should Accept

One family’s extraordinary journey raises an uncomfortable question: If healthcare exists to help people reclaim their lives, why do we tolerate systems that repeatedly take physicians away from the people they are trying to help?



“They all go back to the importance of the patient-physician interaction, which is really just a human connection that's part of delivering good-quality care and getting good outcomes.” — Dr. Gary Price, President of The Physicians Foundation, speaking to Medical Economics


A brother stepped forward before his sister asked

Stephanie Johnson lived with polycystic liver disease. Her liver had enlarged so dramatically that everyday activities became difficult. Eating was uncomfortable. Climbing stairs left her breathless. Strangers sometimes mistook her enlarged abdomen for pregnancy.

Her younger brother, Marcus Brown, wanted to help.

Stephanie was reluctant to ask family members to donate an organ. She believed other people on the transplant waiting list might need a liver more urgently.

Marcus saw it differently.

He raised the possibility of donating part of his liver with their mother before Stephanie knew what he was considering.

In February 2026, Marcus donated part of his liver to his sister at VCU Health’s Hume-Lee Transplant Center in Richmond, Virginia.

The operation involved a multidisciplinary medical team, including transplant surgeon Dr. Seung Duk Lee, M.D., Ph.D., and Dr. David Bruno, M.D., FACS. During Stephanie’s recovery, doctors also discovered a cancerous growth in her colon. Surgical oncologist Dr. Leopoldo Fernandez subsequently removed it.

Stephanie endured a prolonged hospitalization before finally returning home.

Then came a small moment with enormous meaning.

She found herself running up the stairs.

Previously, climbing them had left her struggling for breath. Now, she could move more freely, eat more comfortably, and begin reclaiming ordinary parts of life.

She could buy clothes in her own size. She could focus more of her energy on her two sons.

The medical procedures were extraordinary. The victories that mattered to Stephanie were wonderfully ordinary.

Eating a meal. Climbing stairs. Wearing a shirt without trying to hide. Getting more of your life back.

Her story is about family, medical expertise, difficult decisions, and the possibility of recovery.

It is not a story about medical billing, and there is no evidence that billing problems caused or affected her outcome.

But it reminds us of a principle that should guide every part of healthcare:

The system exists to serve the patient. The patient does not exist to serve the system.

That sounds obvious.

So why is it so easy to lose sight of it?


The uncomfortable question: What is healthcare optimizing for?

Healthcare can perform extraordinarily complex operations. Surgeons can remove diseased organs and transplant donated tissue. Clinical teams coordinate medications, imaging, laboratory results, intensive monitoring, and recovery.

Yet many physicians and their staff still spend hours tracking down missing information, correcting preventable errors, checking authorization requirements, and trying to understand why a claim has become another administrative project.

We can perform miracles in the operating room and still struggle to get the right information to the right person at the right time.

That is not an argument against technology, administration, or necessary safeguards.

It is a question about priorities.

Are we optimizing healthcare for the delivery of care—or for the processing of everything that surrounds it?

There is a difference.

A system can become extremely efficient at processing paperwork while leaving the underlying reasons for that paperwork untouched.

It can generate a dashboard showing yesterday’s failures without preventing tomorrow’s.

It can automate a process that should have been simplified.

It can even use artificial intelligence to make a bad workflow faster.

Congratulations. We have successfully taught the machine to run in circles.

The harder question is whether the circle needed to exist.


The contrarian thesis: Some billing problems begin before billing

As a physician and founder of OnnX, I have become increasingly interested in a question that sits upstream of traditional revenue-cycle management.

What if some of the work we call billing is actually the work of reconstructing information that should have been complete, connected, and usable much earlier?

Consider a typical patient encounter.

A patient schedules an appointment. The practice collects demographic and insurance information. Staff check eligibility and determine whether a referral or authorization is required. The physician evaluates the patient and documents the encounter. Coding and charge capture follow, and a claim is submitted.

Each stage depends on information from earlier stages.

A missing detail may not be obvious when it first appears. The workflow continues. Someone else assumes the information is complete. The problem becomes visible only when the next step fails.

Now someone must investigate.

Was the insurance information correct? Was authorization required? Did the referral arrive? Does the documentation support the intended service? Was a payer-specific requirement overlooked? Did the information exist in another system but fail to reach the person who needed it?

The claim becomes the crime scene.

The actual cause may be several steps away.

This is why I believe healthcare should investigate the origin of recurring errors, not simply optimize the department that discovers them.

A denial is an event. It is not always an explanation.

A coding query is a task. It does not automatically reveal why the documentation was unclear.

A delayed payment is an outcome. It does not tell us whether the original problem began with registration, coverage, authorization, documentation, coding, or payer processing.

The location where a problem appears is not necessarily where it began.

That distinction can change how a practice measures performance, allocates staff, selects technology, and decides which problems deserve attention first.


The hidden tax of administrative rework

Imagine a hypothetical physician-owned practice.

A physician sees a patient, makes a clinical decision, and documents the encounter. The practice expects to submit an appropriate claim.

But the insurance information is incomplete. A referral requirement was overlooked. The documentation needs clarification.

Each issue appears manageable.

Together, they create a chain of additional work.

A staff member must identify the problem, determine what is missing, contact someone, retrieve information, and correct the record. The physician may need to clarify documentation. The claim may be delayed, corrected, or denied.

The practice has now paid for the encounter in operational terms twice: once to deliver care and again to repair the process around it.

Sometimes more than twice.

There may be staff time, physician interruptions, additional communication, delayed cash flow, and patient frustration.

These costs are scattered across departments. Because no single line item captures the entire burden, the practice may underestimate what recurring information failures actually cost.

The hidden tax is the labor required to reconstruct information that was missing, disconnected, misunderstood, or not preserved in context.

Not every billing problem originates upstream. Some result from payer decisions, contractual disputes, changing rules, genuine coding disagreements, or other causes outside a practice’s direct control.

But that makes root-cause analysis more important, not less.

If the practice does not distinguish between problems it can prevent and problems it must resolve, it may spend money trying to fix the wrong thing.


The numbers: Administrative burden is not imaginary

The American Medical Association’s 2024 prior authorization survey reported that physicians and their staff spent an average of approximately 13 hours per week completing prior authorization work, with physicians completing an average of 43 prior authorizations weekly.

The survey also found that physicians overwhelmingly viewed prior authorization as contributing to burnout and delaying necessary care.

These figures describe a specific survey and should not be treated as universal measurements for every practice. But they illustrate the scale of the challenge.

Thirteen hours is not a rounding error.

It is more than a working day every week.

And the cost is not simply the salary of the person completing the authorization. It includes the opportunity cost of what that person could have done instead.

Could a coordinator have helped a patient understand the next step in treatment? Could a medical assistant have supported follow-up? Could a physician have reviewed a complex case without another interruption?

We should not assume that every saved administrative hour automatically becomes a clinical hour. Staffing, scheduling, and practice economics are complicated.

But we should ask a straightforward question:

If a process consumes hours every week, what evidence tells us that those hours are being spent in the best possible way?


A timely warning from Dr. Gary Price

In an interview published October 20, 2026, Medical Economics spoke with Dr. Gary Price, president of The Physicians Foundation, about misinformation, burnout, and declining trust between patients and physicians.

Price emphasized the importance of preserving time for the patient-physician relationship. He also discussed how fragmentation, insurance barriers, prior authorizations, and denials can interfere with that relationship.

His argument is important because it moves the conversation beyond physician dissatisfaction.

Time with patients is not a luxury feature of healthcare. It is part of how healthcare works.

A physician who has enough time to listen may discover something that changes a diagnosis or treatment plan. A physician who can explain uncertainty may help a patient make a better-informed decision. A physician who knows the patient's history may recognize a change that a fragmented encounter obscures.

The human connection is not separate from clinical quality.

Yet administrative systems can consume the very time that helps make clinical care effective.

This is not a call to eliminate every administrative requirement. Some protect patients, support appropriate utilization, and establish accountability.

The challenge is to distinguish necessary controls from avoidable friction—and then design the necessary controls as well as possible.

The objective should not be to eliminate administration at any cost. It should be to eliminate the administration that exists because the system repeatedly fails to work as intended.


Three perspectives that belong in the same conversation

1. Dr. Gary Price: Protect the human connection

Price’s recent comments emphasize that physician-patient interaction and trust are fundamental to good care.

The operational implication is clear: administrative processes should support the clinical relationship, not compete with it unnecessarily.

A technology that saves time is valuable only if it produces a meaningful improvement in the work or experience that matters.

2. The American Medical Association: Measure the administrative burden

The AMA’s prior authorization research gives physicians a way to discuss the burden using more than anecdotes.

The implication is that practices should measure the time spent on repetitive administrative tasks, identify where delays originate, and evaluate whether interventions actually reduce the burden.

“Everyone feels overwhelmed” is a reason to investigate.

It is not yet a diagnosis of the operational problem.

3. CMS: Improve information exchange and standardization

The Centers for Medicare & Medicaid Services has established interoperability and electronic prior authorization requirements for certain impacted payers through its CMS Interoperability and Prior Authorization Final Rule.

These changes aim to improve information exchange and make prior authorization processes more transparent and efficient. Requirements and implementation timelines vary by provision and organization.

The implication is that electronic exchange matters—but digitization alone is not the finish line.

An electronic form can still request redundant information. An automated process can still depend on incomplete data. A faster transaction can still fail if the underlying requirement is misunderstood.

Digitization changes the channel. Better information structure can change the quality of the exchange.

 

These perspectives are not endorsements of OnnX. They represent different parts of the healthcare landscape that converge on a common question: how do we make the system support care more effectively?


The OnnX thesis: Fix the signal before repairing the noise

OnnX is an upstream intelligence platform for healthcare, built by physicians and medical billers to reduce downstream administrative and billing noise so physicians can focus on clinical care.

Our premise is that some recurring billing problems begin with fragmented information, unclear requirements, or disconnected decisions before a claim is submitted.

The working process is:

Capture → Structure → Preserve → Propagate → Act → Learn

  • Capture: Collect relevant information where it first becomes available.
  • Structure: Organize the information so its meaning and relationships are clear.
  • Preserve: Retain the context needed to interpret it correctly.
  • Propagate: Make the relevant information available to the next appropriate step.
  • Act: Identify gaps, inconsistencies, or requirements that need attention.
  • Learn: Review outcomes and use verified patterns to improve future decisions.

The objective is not to replace medical billers or promise that every denial will disappear.

It is to test whether better information continuity and earlier decision support can prevent some of the rework that practices currently resolve downstream.

Think of a recurring billing error as a smoke alarm.

One option is to hire someone to reset it every time it sounds.

Another is to investigate whether something is repeatedly causing the alarm to activate.

The first task may still be necessary. But if nobody investigates the cause, the practice has created a very efficient alarm-resetting department.

That is not the same as solving the problem.


Seven practical steps for physician-owned practices

A practice does not need to purchase another platform tomorrow to start improving its information quality.

Begin with one recurring problem.

1. Pick a specific failure.
Choose something measurable, such as recurring eligibility errors, missing authorization information, documentation clarification requests, or claims returned for incomplete data. “Fix billing” is not a useful project definition.

2. Map the information journey.
Document where the information originates, who handles it, where it is stored, and when it is needed. Ask frontline staff where the process repeatedly breaks down.

3. Identify the earliest controllable cause.
Separate missing information from misunderstood requirements, unclear responsibilities, software limitations, and payer-side constraints. These problems require different interventions.

4. Establish a baseline.
Measure frequency, staff time, recurrence, and impact on claims or patient services. Without a baseline, a team can mistake a busy month for an improvement.

5. Fix the source where possible.
Improve the relevant registration field, documentation prompt, authorization process, responsibility assignment, or information exchange. Do not automatically send every problem to billing for repair.

6. Use technology for a defined purpose.
Automation may help flag missing fields, compare information, route exceptions, or surface relevant requirements. It should not invent clinical facts or silently make consequential decisions without appropriate oversight.

7. Evaluate honestly.
Check whether the intervention reduced the original problem, created new work, increased false alerts, or shifted the burden to another department. Expand only when the evidence supports it.

This approach is less glamorous than buying a platform with a futuristic name.

It is also more likely to reveal what the practice actually needs.


Metrics that matter more than a shiny dashboard

A useful operational improvement should be measurable.

Depending on the problem, consider tracking:

  • First-pass claim acceptance: The proportion of claims accepted without correction, using a clearly defined measure.
  • Preventable denial rate: The share of denials linked to causes the practice can reasonably address.
  • Rework time: Staff time spent investigating, correcting, resubmitting, or escalating recurring issues.
  • Missing-information rate: How often a workflow reaches a point where required information is absent or inaccessible.
  • Authorization turnaround: The time required for practice-side processing, distinguished from payer processing time.
  • Repeat-error rate: How frequently the same underlying issue returns after it has been corrected.
  • Exception rate: How often an automated process needs human intervention.
  • Patient communication burden: How often patients must contact the practice to clarify an administrative delay.

No single metric tells the whole story.

A lower denial rate might coincide with slower claim submission. An automated system might appear efficient because it fails to identify difficult cases. A new checking process might improve accuracy while increasing staff workload.

Pair efficiency measures with quality, safety, and workload measures.

The goal is not to make the dashboard green.

The goal is to make the underlying work better.


Five myths worth challenging

Myth 1: We just need better billers.

Good medical billers are essential. But even excellent staff cannot reliably compensate for every upstream information gap. When the same error recurs, investigate the process as well as the performance of the people working within it.

Myth 2: More automation means less work.

Automation can move work from one department to another, generate false alerts, or create new exception queues. Measure the entire workflow before and after implementation.

Myth 3: AI can solve documentation problems by generating more text.

More text does not necessarily mean better documentation. Accurate, relevant, clinically appropriate information matters more than note length. Clinicians remain responsible for ensuring that the record reflects the encounter truthfully.

Myth 4: Denials are simply part of doing business.

Some disputes and denials are unavoidable. That does not make every recurring denial inevitable. Classify the reasons, investigate the preventable portion, and track whether interventions reduce recurrence.

Myth 5: The newest platform must be the best solution.

Sometimes the right answer is software. Sometimes it is clearer training, a better template, a defined responsibility, or a simpler process. Buy technology to address a demonstrated problem—not to avoid diagnosing it.


The risks of getting it wrong

An upstream intelligence platform can create value, but it can also introduce new risks.

Clinical integrity: Never fabricate symptoms, findings, medical necessity, or other clinical information to satisfy a billing requirement.

Human oversight: Make recommendations understandable and provide a clear process for review, correction, and escalation.

Privacy and security: Apply appropriate safeguards, access controls, auditability, and agreements governing the use of patient information.

Bias and reliability: Test performance across specialties, payer arrangements, practice sizes, and patient populations. A system that works in one setting may fail in another.

Transparency: Users should understand why a system raised an alert and what evidence supports its recommendation.

Compliance: Practices should assess applicable HIPAA obligations, business associate arrangements, coding standards, payer contracts, and other requirements with qualified advisers.

Appropriate incentives: Do not encourage unnecessary services, unsupported diagnoses, or inflated coding in pursuit of better reimbursement.

There is a subtler risk: a system can make a bad process harder to question because it now has an algorithm.

An automated recommendation is not automatically correct. A workflow is not automatically appropriate because it is digital.

Technology should help people make better decisions—not obscure responsibility for those decisions.


A 30-day experiment

For a physician-owned practice, meaningful improvement can begin with a small, disciplined test.

Week 1 — Find the recurring problem. Choose one issue, gather examples, interview the staff handling it, and measure the baseline.

Week 2 — Trace it upstream. Identify where the information first becomes incomplete, inconsistent, inaccessible, or misunderstood. Separate internal causes from external constraints.

Week 3 — Test one intervention. Change a specific step, train the affected team, and define who handles exceptions. Keep the experiment limited enough to monitor safely.

Week 4 — Evaluate the evidence. Compare results with the baseline. Did the problem decline? Did workload actually fall? Did another error increase? Should the practice expand, modify, or abandon the intervention?

No giant transformation budget is required.

No presentation needs the phrase “paradigm shift.”

Just a real problem, a measurable test, and the willingness to discover that the original assumption may have been wrong.


What the future should look like

The future should not be a clinic where every employee spends the day supervising an endless parade of alerts.

Nor should it be a clinic where AI makes consequential decisions that nobody understands or checks.

A better future would allow relevant information to be captured appropriately, structured consistently, preserved with context, and made available to the people who need it.

Missing information would be identified earlier. Exceptions would reach the right person. Physicians would not repeatedly reconstruct details that already existed elsewhere. Medical billers could spend more time applying their expertise and less time chasing basic information.

Automation would handle appropriate routine tasks while people retained responsibility for decisions requiring judgment.

Success would be measured not by how many tasks software completed, but by whether accuracy improved, rework declined, operations became more predictable, and patients and staff had a better experience.

That is the direction behind OnnX: upstream billing intelligence.

The ambition is to investigate whether better information continuity and earlier decision support can reduce preventable downstream problems for physician-owned practices.

That is a hypothesis to validate through real workflows, measurable outcomes, and honest testing—not a promise that one platform can eliminate every problem.

Healthcare needs fewer confident promises and more disciplined investigations into where its problems begin.


The lesson Stephanie and Marcus leave us

Stephanie Johnson’s recovery is measured in things many healthy people rarely think about: eating a full meal, climbing stairs, buying clothes in her own size, and having more energy for her children.

Marcus Brown made an extraordinary personal decision to help his sister regain those ordinary freedoms.

Their family relied on a specialized medical team whose work demanded precision, coordination, and careful attention to both donor and recipient.

Their story reminds us that the purpose of healthcare is not merely to complete procedures, submit claims, or close tasks.

It is to help people live healthier lives.

Complex medicine will always require expertise, safeguards, and coordination. Not every administrative requirement can or should disappear.

But we should question avoidable friction wherever it repeatedly consumes the time, attention, and resources that patient care requires.

If a process is necessary, make it reliable.

If information is needed, make it available.

If an error keeps recurring, investigate its origin.

If technology is introduced, measure whether it improves the outcome.

And if physicians and staff are repeatedly asked to reconstruct information that was lost, duplicated, or poorly structured, ask whether the process needs to work that way at all.

The future of healthcare may depend not only on what we teach machines to do, but also on what we finally stop asking people to do over and over again.


A question for physicians, practice owners, and healthcare operators

If you could eliminate one recurring administrative problem from your practice tomorrow, which would give your team the most time back for patient care?

Prior authorization? Missing information? Documentation rework? Eligibility errors? Preventable denials?

Tell me in the comments. The most useful answers may come from the people who encounter these problems every day.

If this perspective resonates with you, share or repost it so more physicians and practice teams can join the conversation.

The goal is not to make administration disappear. It is to make unnecessary administration harder to justify.


Frequently asked questions

1. What is upstream billing intelligence?
It focuses on information quality, context, and decisions before a claim is submitted, with the aim of identifying gaps early enough to reduce avoidable downstream rework.

2. Is every medical billing denial preventable?
No. Denials can result from coverage limitations, payer decisions, contractual disputes, coding issues, incomplete information, and other causes. Practices should distinguish preventable problems from those requiring appeal or external resolution.

3. Does better documentation guarantee reimbursement?
No. Reimbursement also depends on coverage, applicable rules, authorization requirements, coding, contracts, and payer adjudication. Documentation must remain accurate and clinically appropriate.

4. Can AI eliminate prior authorization?
AI may help organize information, identify requirements, prepare submissions, and support status monitoring. It cannot eliminate payer requirements or guarantee approval.

5. How can a small practice begin reducing administrative burden?
Choose one recurring problem, measure its frequency and impact, trace it to its earliest controllable cause, and test a targeted improvement before expanding.

6. What should a practice measure?
Depending on the problem, measures may include first-pass claim acceptance, preventable denial rate, rework time, missing-information rate, authorization turnaround, repeat-error rate, and staff workload.

7. Does upstream intelligence replace medical billers?
It should not be framed as a replacement for billing expertise. Better information systems can help billers spend less time repairing avoidable gaps and more time applying their knowledge.

8. How is OnnX different from a traditional revenue-cycle management service?
OnnX is being developed around an upstream intelligence thesis: improve how information is captured, structured, preserved, and acted upon before it creates downstream billing problems.

9. Should every administrative process be automated?
No. Some processes protect safety, accountability, and compliance. The goal is to reduce unnecessary friction while preserving accuracy, privacy, appropriate review, and patient protections.

10. What is the first question to ask about recurring errors?
Where did this problem first become possible, and what information or decision would have prevented it?


About the author

Dr. Daniel Cham, MD, is a physician, entrepreneur, and founder working at the intersection of clinical care, healthcare operations, and technology. Through OnnX, he is exploring how upstream information quality and decision support can reduce administrative and billing friction for physician-owned practices.

Connect with Dr. Cham on LinkedIn.

Continue the conversation

·       Visit Dr. Cham's website

·       Dr. Daniel Cham on LinkedIn

·       Subscribe and watch on YouTube

Knowledge creates possibilities. Start by questioning one process, measuring one problem, and learning what could work better.

For a free resource, visit the Featured section of my LinkedIn profile. It is available without a signup.


Disclaimer

This article is for general educational and informational purposes. It is not medical, legal, coding, reimbursement, compliance, or financial advice. Requirements vary by payer, jurisdiction, specialty, and practice. Consult qualified professionals for guidance on specific circumstances.


References and further reading

  1. VCU Health: A brother’s liver donation gives his sister a new lease on life — the original account of Stephanie Johnson and Marcus Brown.
  2. Medical Economics: Misinformation, burnout and lost trust are “incredibly interrelated” — October 20, 2026, interview with Dr. Gary Price.
  3. American Medical Association: Prior Authorization — research and resources on prior authorization and physician burden.
  4. Centers for Medicare & Medicaid Services: CMS Interoperability and Prior Authorization Final Rule — federal requirements and implementation information.

#Healthcare #MedicalBilling #PhysicianEntrepreneur #HealthcareInnovation #PracticeManagement #HealthTech #PriorAuthorization #RevenueCycle #PhysicianOwnedPractices #PatientCenteredCare #OnnX

 

Tuesday, October 20, 2026

Katherine Screws Waited Three Years for a Transplant. What If Healthcare Is Solving the Wrong Problem?

A patient’s search for answers reveals an uncomfortable truth about complex systems: when information is fragmented, people can follow the process and still get stuck. From transplant care to medical billing, are we fixing problems—or simply getting better at cleaning up the mess?

 


“Whatever the organ, most patients don’t know what to ask,” said Dr. Allyson Hart, a researcher at Hennepin Healthcare Research Institute, in Associated Press

 

It is a simple observation with a much bigger implication.

What happens when people must navigate a complicated system without understanding how it works, which options are available, or what is standing in their way?

Sometimes, the problem is not a lack of effort.

Sometimes, it is not a lack of expertise.

And sometimes, it is not even a lack of technology.

Sometimes, people simply cannot see the information they need to make their next move.

That is the question raised by the experience of Katherine Screws, a Phoenix woman whose three-year wait for an intestine transplant illustrates the human consequences of navigating a complicated healthcare system.

Her story also raises a question for physician-owned practices: How much administrative frustration could be avoided if the right information became visible before the next step went wrong?

Because healthcare has an impressive collection of software, portals, databases, dashboards, and artificial intelligence.

Yet somehow, people still end up asking the digital equivalent of, “Has anyone seen the paperwork?”

Apparently, the paperwork has achieved interoperability with everyone except the person who needs it.


A six-month expectation became a three-year wait

In May 2022, one month after marrying her husband, Stephen Gerrish, Katherine Screws was involved in a car crash that destroyed her small intestine.

She could no longer absorb nutrition normally. She depended on overnight intravenous nutrition, often felt too sick to get out of bed, and could not return to her engineering career or pursue her plans to start a family.

She had been told that a transplant might be possible within approximately six months.

Instead, she waited three years.

During that time, Screws faced more than a medical challenge. She was trying to understand a system whose options, processes, and decisions were not always clear to her.

The turning point came when she connected with Lisa Stocks, a nurse at California's organ procurement organization, OneLegacy.

Stocks helped Screws understand that transplant centers can differ in their practices and in which donor organs they are willing and able to accept. Screws also learned about publicly available information that could help her compare transplant centers.

She explored the Scientific Registry of Transplant Recipients database and registered at MedStar Georgetown University Hospital in Washington, D.C., in addition to her original center, UCLA Health.

In June 2025, just weeks after registering at Georgetown, she received her intestine transplant.

Dr. Cal Matsumoto, a transplant surgeon at MedStar Georgetown University Hospital, and his team performed the procedure. The donor intestine was longer than usual, but it fit successfully.

The story also features Dr. Syed Ali Husain of NYU Langone Health, who researches differences in transplant practices, and Dr. Allyson Hart, who helped develop patient-friendly tools for comparing transplant centers.

UCLA Health declined to comment on Screws's individual care, citing patient privacy rules, but said it follows federal transplant guidelines and continually strives to improve its processes.

Screws was careful to explain that her frustration was not simply directed at her original physicians. She was troubled by the lack of clear, centralized information about what to expect and what might be holding up progress.

Her experience does not prove that every transplant delay is avoidable or that one hospital's decisions are inherently better than another's. Transplantation involves difficult clinical judgments, complex logistics, and time-sensitive matching.

But it does demonstrate the importance of understanding how a system works and knowing what questions to ask.

The most important question may not be, “Why is this taking so long?” It may be, “What is actually holding this up—and what can I do about it?”

That question belongs in many more places across healthcare.


The contrarian argument: Maybe healthcare doesn't need another dashboard

When something goes wrong, the instinct is often to add something.

Another application. Another workflow. Another reporting tool. Another automated notification. Another dashboard showing that the other dashboard has a problem.

Before long, the organization has a dashboard for the dashboard.

But what if the underlying problem is not always the absence of a tool?

What if the information already exists somewhere—but is incomplete, disconnected, outdated, difficult to interpret, or unavailable to the person who needs it?

Consider how a medical practice operates.

The physician understands the patient's clinical circumstances. The front office manages registration. The authorization team works with payer requirements. The scheduler coordinates appointments. The medical biller needs the documentation and information required to submit an accurate claim.

Each person may be doing their job correctly.

Yet the overall process can still fail if important information does not reach the next person at the right time.

A patient's coverage may have changed. A referral may be missing. An authorization may still be pending. A documentation requirement may not have been identified until after the encounter.

The practice discovers the problem later, when correcting it is more expensive and disruptive.

This is the distinction between optimizing a task and improving the system that connects the tasks.

A faster process can still be a bad process. An automated error is still an error. And an AI-generated answer cannot make missing information magically appear.

Technology can improve healthcare enormously. But adding technology without addressing the quality and continuity of information may simply help an organization process its existing problems more efficiently.

That is progress of a sort.

It is just not necessarily the progress we need most.


What Katherine's experience can teach us—and what it cannot

An intestine transplant and a rejected medical claim are not equivalent.

The medical stakes, ethical considerations, clinical decisions, and consequences are fundamentally different. Katherine's story should not be used to suggest that a billing platform could have shortened her transplant wait, nor should it be interpreted as an accusation of negligence against the professionals involved.

The connection is more specific.

People need understandable, timely information to navigate complex systems and make informed decisions.

For a transplant patient, that may mean understanding how centers differ, which options are available, and what questions to discuss with a transplant team.

For a physician-owned practice, it may mean knowing whether a referral is complete, whether authorization is confirmed, whether coverage information is current, and whether documentation supports the service being billed.

Different situations. Different stakes. A shared challenge: information must be available and understandable before it can guide action.

In both settings, the existence of a process does not guarantee that the people navigating it can see how it works.

That is why information transparency matters.


The hidden cost of discovering problems too late

Imagine a physician evaluating a patient and determining that a procedure is medically appropriate.

The appointment is scheduled. The clinical note is written. The patient expects the next step to happen.

But several administrative questions remain:

  • Is the insurance information current?
  • Does the patient's plan cover the service under the applicable conditions?
  • Is prior authorization required?
  • Is a referral necessary?
  • Does the documentation contain the information required to support the request?
  • Has the authorization status reached the scheduling team?
  • Will the eventual claim accurately reflect the service provided and documented?

These questions may involve different staff members, systems, and payer requirements.

If one requirement is missed, the problem might not become visible until the procedure is scheduled, the service is performed, or the claim is submitted.

Then the practice must investigate.

Someone retrieves the documentation. Someone contacts the payer. Someone follows up on the authorization. Someone corrects the claim. Someone explains the delay to the patient. Someone tries to determine why the process failed.

And the physician may be asked to clarify a note weeks after the encounter.

The organization has now paid for the work twice: once to perform the original task and again to repair the process.

This is where administrative friction becomes a financial and operational problem.

A denied claim is not just a line in a report. It can represent staff time, delayed reimbursement, additional patient communication, and work that could have been directed elsewhere.

The critical question is not merely, “How do we fix this claim?”

It is:

“What happened before the claim that made this problem possible?”

That is the upstream question.


The prior authorization problem is not just paperwork

The American Medical Association's prior authorization research has documented substantial administrative burdens for physicians and patients.

Its 2025 physician survey, reported in 2026, found that:

  • 95% of surveyed physicians said prior authorization delays access to necessary care.
  • 92% said it negatively affects clinical outcomes.
  • 79% said patients abandon treatment because of authorization challenges.
  • 94% said prior authorization contributes to physician burnout.
  • Physicians and staff reported spending an average of 13 hours per week dealing with prior authorization.

These are survey findings, not proof that every delay causes harm or that one technology solution can eliminate the burden. But they illustrate how much effort the process can consume.

For a small practice, 13 hours a week is substantial.

That time has to come from somewhere: patient communication, referral coordination, follow-up, documentation, or other work that also matters.

And the irony is hard to miss. Healthcare continues to invest in digital transformation while physicians and staff spend hours navigating administrative requirements across fragmented systems.

We have digitized many processes.

We have not necessarily connected them.


Three lessons from the people in Katherine's story

1. Katherine Screws: People cannot act on options they cannot see

Screws's experience shows why accessible information matters.

For practices, the equivalent question is whether each authorized team member can see the information needed to move work forward.

Can the scheduler see that authorization is pending?

Can the physician understand which documentation requirement remains unresolved?

Can the biller distinguish a genuine coding question from an eligibility issue?

Can the practice owner identify recurring problems without manually reconstructing events from multiple systems?

The answer is not to give everyone unrestricted access to everything. Privacy, security, and role-based access are essential.

The objective is to make relevant information available to the right person at the right time.

2. Lisa Stocks: Experience is valuable—but it should not live only in someone's memory

Stocks helped Screws understand the transplant system and explore additional options.

Medical practices also depend on people with experience. A skilled biller may know that a particular payer repeatedly requests certain documentation. A referral coordinator may understand which records a specialist requires. A front-office employee may recognize a recurring eligibility problem.

That knowledge is valuable.

But if it exists only in someone's memory, a personal spreadsheet, or an old email thread, the organization cannot reliably apply it across future encounters.

The solution is not to replace experienced employees.

It is to preserve useful knowledge, make recurring requirements visible, and reduce dependence on memory alone.

Even an outstanding employee cannot simultaneously be the practice's database, notification system, and institutional memory.

3. Dr. Syed Ali Husain, Dr. Allyson Hart, and Dr. Cal Matsumoto: Context changes how information should be interpreted

The transplant reporting describes differences among centers and the clinical judgment involved in evaluating donor organs.

That reinforces a broader principle: A decision cannot be understood simply by looking at its outcome without considering the circumstances behind it.

The same is true of medical billing.

A denial does not automatically mean a coder made a mistake. A missing authorization does not necessarily mean a scheduler was careless. A documentation gap does not automatically mean a physician failed to provide appropriate care.

The cause could involve changing payer requirements, incomplete registration, a communication breakdown, a documentation issue, or a process that failed to make an important requirement visible.

Counting failures tells us what happened. Understanding their causes tells us what to change.

That is the difference between reporting a problem and learning from it.


The myth: More AI automatically means less administrative work

AI can help identify patterns, summarize information, flag potential inconsistencies, and support routine tasks.

But AI is not a substitute for good data, appropriate clinical judgment, or a well-designed process.

Imagine an automated system submitting an authorization request with incomplete information. It can submit the request quickly, but the payer may still return it for missing details.

Imagine an AI tool generating a polished clinical note that omits a fact necessary to explain the service. The language may sound excellent while the underlying problem remains.

Imagine a denial-management platform that helps staff categorize rejected claims. That may be valuable, but categorizing the same recurring problem does not necessarily prevent it from happening again.

None of these tools is inherently bad. Each may address part of the problem.

The mistake is assuming that automating one step automatically improves the entire process.

In a September 30, 2026, joint statement, six major physician organizations—including the American Medical Association, the American College of Physicians, and the American College of Surgeons—warned against treating AI as a replacement for physician expertise. They emphasized that clinical context, professional judgment, patient safety, and accountability must guide the development and use of AI.


The lesson for healthcare administration is equally important: Technology should support better decisions, not simply accelerate activity.

Before adopting an AI tool, ask:

  • Does it help identify the underlying issue?
  • Does it use reliable, relevant information?
  • Does it explain what remains unresolved?
  • Does it help the appropriate person take the next step?
  • Can the practice audit its outputs and correct mistakes?
  • Does it preserve human oversight where judgment is required?

If the tool only makes the existing queue move faster, it may still be useful. But it is solving a different problem from preventing avoidable work.


What upstream billing intelligence looks like in practice

Upstream billing intelligence starts with the idea that many preventable billing problems have contributing conditions that exist before a claim is submitted.

Those conditions can arise during registration, eligibility verification, scheduling, referral management, authorization, documentation, coding, or charge capture.

A practical framework is:

Capture → Structure → Preserve → Propagate → Act → Learn

Capture: Collect relevant information when it becomes available.

Structure: Organize it so people and systems can interpret it consistently.

Preserve: Retain the context behind important decisions, requirements, and exceptions.

Propagate: Make the information available to authorized people and downstream systems that need it.

Act: Flag unresolved requirements and help the responsible person determine the next appropriate step.

Learn: Analyze recurring patterns and improve the process based on evidence.

For example, if a procedure requires authorization, the practice should be able to distinguish an authorization that is requested from one that is approved or confirmed as unnecessary.

If documentation appears to be missing a required element, the system should flag the issue for appropriate review rather than silently assuming the record is complete.

If a payer repeatedly requests the same information, the practice should investigate whether a template, training, handoff, or process needs improvement.

This does not mean every denial can be prevented. Some result from payer decisions, clinical disagreements, changing rules, or circumstances outside the practice's control.

It means the practice should identify and address the preventable conditions it can influence.

The best time to discover a missing requirement is generally before additional work depends on it.


Seven metrics that reveal whether the process is improving

A practice does not need 47 dashboard widgets to start making progress. It needs a few consistent measures that lead to useful decisions.

  1. First-pass claim acceptance: How often do claims pass initial submission checks without preventable errors? Distinguish clearinghouse acceptance from payer adjudication.
  2. Denial rate by root cause: Separate authorization, eligibility, coding, documentation, and other relevant causes rather than relying only on the overall rate.
  3. Rework hours: Measure staff time spent correcting preventable errors, retrieving information, and resubmitting claims.
  4. Authorization lead time: Track the time required to move from a complete request to a documented decision, separating payer delays from internal delays.
  5. Missing-information rate: Measure how often work reaches a critical step without the information required to proceed.
  6. Repeat-error rate: Determine how frequently the same underlying problem recurs after it has been addressed.
  7. Patient-impact indicators: Where appropriate, monitor avoidable rescheduling, care delays, unexpected financial communications, and related outcomes.

Establish a baseline, define each measure consistently, and review the results regularly.

The goal is not to make the dashboard prettier.

It is to answer a more important question:

Are we preventing more problems—or merely getting better at cleaning them up?


A four-week experiment for a small medical practice

Improving a process does not necessarily require purchasing a new platform.

Start with one recurring problem.

Week 1: Find the pattern.

Review a sample of recent denials, authorization delays, or claim corrections. Identify where the issue first appeared.

Week 2: Map the information.

Determine where the required information originates, who verifies it, where it is stored, who needs it next, and how the current process fails.

Week 3: Test one change.

Try a targeted checklist, a standardized field, a clearer handoff, or an appropriate alert. Avoid adding steps that do not address a defined problem.

Week 4: Measure the result.

Compare the results with the baseline. Review error frequency, rework hours, delays, and staff feedback. Check for unintended consequences.

If the change helps, refine it. If it does not, investigate why before automating it.

This is not the most glamorous AI demonstration. Nobody is going to make a viral video about a missing authorization field that was completed correctly the first time.

But that is precisely the point.

A problem prevented is often less visible than a problem repaired.

It is also frequently less expensive to deal with.


Where OnnX 2.0 fits

This is the problem OnnX 2.0 is being developed to address.

OnnX is an upstream intelligence platform for healthcare, built by physicians and medical billers to reduce downstream administrative and billing noise so physicians can focus on clinical care.

Built by physicians and medical billers since 1995, the OnnX 2.0 concept focuses on the information and decisions that influence billing before a claim becomes a problem.

Clinical context, patient information, coverage, authorization requirements, referrals, documentation, and operational decisions can become fragmented across people and systems.

When the relevant information does not travel with the work, downstream teams must reconstruct it.

OnnX 2.0 is being developed around a different approach: make important context more structured, visible, and actionable so physician-owned practices can recognize information gaps earlier and investigate risks before they become avoidable rework.

The objective is not to promise zero denials or claim that every billing problem can be eliminated. It is to focus on upstream causes that a practice may be able to identify and address.

That means asking different questions.

Instead of only asking how to process a denial faster, ask what created the conditions for it.

Instead of only asking how to chase missing information, ask why it was missing when it was needed.

Instead of buying another dashboard, ask which decision the dashboard should help someone make.

The aim is to move from reactive billing toward more predictable, informed revenue-cycle operations.

That is a development vision, not a claim that every capability has already been validated in practice. The value must ultimately be demonstrated through real workflows, measurable results, and appropriate safeguards.

But the principle is worth pursuing: Better information upstream can create better opportunities to prevent problems downstream.


The future of healthcare may depend on what we stop having to fix

Katherine Screws's experience reminds us that navigating a complicated system can be difficult even when the people inside it are working hard.

Her story does not prove that every delay is avoidable. It does show why accessible information, clear explanations, and an understanding of available options matter.

For physician-owned practices, the parallel is not the severity of the outcome. It is the importance of visibility and informed action.

A patient should not have to guess what question to ask next.

A physician should not repeatedly reconstruct the context behind a clinical decision.

A medical biller should not have to become a detective because essential information is scattered across disconnected systems.

And a practice owner should not have to wait until the end of the month to discover a recurring problem that could have been visible much earlier.

Healthcare does not need technology for technology's sake.

It needs systems that help people do the right work with the right information at the right time.

We have spent years teaching technology to process more work.

Perhaps the next breakthrough will come from designing systems that recognize which problems should never have reached the next step in the first place.

And if that sounds less exciting than another AI announcement, consider this:

Sometimes, the best result is a claim that never needed correcting, an authorization that did not stall, or a patient who did not have to make five phone calls to discover what happens next.

No dramatic alert. No heroic spreadsheet. No billing department operating like a crime-scene investigation unit.

Just a process that works better.

That may not be flashy. But for physicians, staff, and patients, it could be far more valuable.


Frequently asked questions

What is upstream billing intelligence?

It is an approach to identifying and addressing information gaps, requirements, and operational risks before they contribute to claim errors, denials, or rework.

Why do billing problems begin before a claim is submitted?

Claims depend on information collected across registration, eligibility, referrals, authorization, documentation, coding, and charge capture. Errors or omissions at earlier stages can affect the claim later.

Can AI prevent medical billing denials?

AI may help identify patterns, missing information, and potential inconsistencies. It cannot guarantee payment or eliminate every denial. Results depend on data quality, payer rules, workflow integration, and appropriate human oversight.

What should a small practice do first?

Choose one recurring problem, identify where it originates, map the information and handoffs involved, test one targeted improvement, and measure whether the change reduces errors or rework.

Is OnnX 2.0 a traditional medical billing service?

OnnX 2.0 is being developed as an upstream intelligence platform focused on helping physician-owned practices improve the information and decisions that affect billing. Its intended positioning emphasizes prevention and intelligence rather than outsourced billing services.


Join the conversation

Katherine Screws's story raises a question that reaches far beyond transplant medicine:

Are we building smarter healthcare systems—or simply getting better at managing the problems our systems keep creating?

Physicians, practice owners, administrators, and medical billers: Where does the most avoidable rework begin in your experience—registration, eligibility, authorization, documentation, coding, or the handoffs between them?

Share your perspective in the comments. If this challenges how we think about healthcare administration, share or repost it so others can join the discussion.


About the author

Daniel Cham, MD is a physician, entrepreneur, and healthcare technology founder developing OnnX 2.0, an upstream intelligence platform for healthcare built by physicians and medical billers since 1995. His work focuses on improving the quality and continuity of information across clinical and administrative processes so physician-owned practices can reduce preventable billing problems and focus more attention on patient care.


Disclaimer: This article is for educational and informational purposes only and does not provide medical, legal, coding, billing, or reimbursement advice. Katherine Screws's experience is discussed based on public reporting and should not be interpreted as an allegation of wrongdoing by any individual or organization. The comparison with medical billing concerns information and coordination, not equivalence between clinical outcomes and administrative delays.


References

  1. Associated Press, October 20, 2026: Arizona woman's three-year wait for an intestine shows the US organ transplant system's complexity.
  2. Associated Press, October 20, 2026: How the US organ transplant system works and what to ask to improve your chances.
  3. American Medical Association: Survey: Prior authorization reform pledge falls short for physicians.
  4. American Medical Association, September 30, 2026: Statement from leading physician organizations on the role of augmented intelligence in healthcare.
  5. Agency for Healthcare Research and Quality: Care Coordination.

Connect with Daniel Cham, MD

Visit Dr. Cham's website

Dr. Daniel Cham on LinkedIn

Subscribe and watch on YouTube

Explore the free resource in my LinkedIn Featured section. No signup required.


#Healthcare #PhysicianOwnedPractices #MedicalBilling #HealthcareAdministration #RevenueCycleManagement #PriorAuthorization #ClaimDenials #HealthcareAI #HealthTech #OnnX2.0 #UpstreamIntelligence #PhysicianBurnout

 

Monday, October 19, 2026

Polly Comforted a Child With Cancer. Meanwhile, Healthcare Is Still Paying People to Fix Preventable Problems.

What a Labrador at a Bronx children's hospital can teach physicians, clinic owners, and healthcare innovators about patient experience, administrative waste, and the contrarian idea that healthcare's next breakthrough may come from preventing work, not automating more of it.

 


“First, experience – and patient experience in particular – is not a survey or score. Rather, it is something a patient, family members or care partners live through.”

That is Jason A. Wolf, president and CEO of The Beryl Institute, in Healthcare IT News on October 19, 2026. His point is simple: healthcare is not just what organizations measure. It is what people actually experience.

And sometimes, that experience is shaped by a four-legged healthcare worker who has never attended medical school, never opened an electronic health record, and probably has no opinion about artificial intelligence.

Her name is Polly.


A Dog Named Polly, a Child With Cancer, and an Uncomfortable Healthcare Question

At Children's Hospital at Montefiore Einstein in the Bronx, New York, a four-year-old Labrador named Polly helps bring comfort to hospitalized children.

According to a New York Post report published October 19, 2026, Polly visited an eight-year-old cancer patient who was experiencing tremors after doctors removed the child's breathing tube and reduced sedative medications.

Polly works with Katy Dessick, a certified child life specialist. Dessick reportedly observed that the child's tremors became less frequent when Polly was present.

It is an affecting story, but accuracy matters. This observation does not establish that Polly caused the change in tremors, and it does not mean a facility dog can replace medical treatment. It reminds us that the experience of being ill includes more than clinical procedures.

The report also describes Dr. Adit L. Tal, a pediatric hematologist-oncologist at Children's Hospital at Montefiore Einstein, discussing the role facility dogs can play in helping young patients feel more comfortable.

Another Labrador, Lev, age seven, visits children at Maimonides Medical Center in Brooklyn, New York. His handler is identified in the report by the first name Gabriel.

These are different people doing different jobs in different hospitals. Yet their stories point toward an important principle: the human experience of healthcare deserves attention alongside clinical treatment.

Now, let's move from a children's hospital to a small independent medical practice.

A patient arrives for an appointment. The clinician is ready. The patient is ready.

Then someone discovers the referral is missing.

The authorization status is unclear. The insurance information in one system does not match the information in another. A document that should have been available yesterday now requires three phone calls, two portal logins, and a heroic amount of patience.

Suddenly, the appointment has a supporting cast of administrative problems.

Healthcare has become remarkably good at turning one missing piece of information into a multi-department investigation.

What if the real innovation is not getting better at fixing these problems, but preventing more of them from happening in the first place?

That is the question I believe physicians, clinic owners, and healthcare technology founders should be asking.


My Contrarian Take: Healthcare Does Not Need Another Tool for Every Problem

I am a physician-entrepreneur and founder of OnnX, an AI-powered medical billing software initiative focused on small and medium-sized medical practices.

My perspective is increasingly shaped by one distinction:

Automating work is not the same as eliminating the need for that work.

Suppose a claim is rejected because required information is missing.

One solution is to identify the problem, locate the information, correct the claim, resubmit it, and monitor the outcome.

That may be necessary. But it is not the end of the investigation.

Why was the information missing? Was it never collected? Was it entered inconsistently? Did a handoff fail? Was the requirement misunderstood? Did the information exist but remain inaccessible to the person who needed it?

If the same cause produces the same correction week after week, making the correction faster may improve productivity without solving the underlying problem.

It is a bit like buying a faster mop while ignoring the leaking pipe.

The mop may be excellent. The floor may look better. The water bill remains a mystery.

Healthcare should absolutely improve necessary work. It should also challenge unnecessary work.

Not every denial is preventable. Not every administrative step is waste. Documentation, authorization, compliance, and appropriate review can be essential to safe and accountable care.

The opportunity is to distinguish necessary complexity from preventable rework.

The goal should not be to automate every problem. It should be to make fewer preventable problems occur.


The Administrative Burden Is Not Just an Annoyance

For independent physicians, administrative complexity is a business problem, a workforce problem, and sometimes an obstacle to timely care.

The American Medical Association's 2025 prior authorization survey, reported in May 2026, surveyed 1,000 practicing physicians. The findings are sobering:

  • 95% said prior authorization delays access to necessary care.
  • 79% reported that patients abandon treatment because of authorization challenges.
  • 26% said prior authorization had contributed to a serious adverse event involving a patient in their care.
  • Physicians reported completing an average of 40 prior authorizations per week.
  • Prior authorization consumed an average of 13 hours of physician and staff time each week.
  • 94% said prior authorization contributes to physician burnout.
  • 88% reported that prior authorization increases overall healthcare utilization.

These are physicians' reported experiences, not proof that every practice faces the same circumstances or that one software product can resolve them. But the findings make one thing difficult to ignore: administrative processes can consume resources that healthcare teams need elsewhere.

Imagine reclaiming even a portion of the time spent chasing information, checking status, and repeating work. What would a practice do with those hours?

More patient communication? Better follow-up? Less overtime? More time for complex cases?

Those are worthwhile questions. But the answers should be measured, not assumed.


Three Perspectives on the Human Side of Healthcare

1. Jason A. Wolf: Patient Experience Is What People Live Through

In his October 19, 2026, Healthcare IT News interview, Jason A. Wolf argued that patient experience extends beyond surveys and scores. It includes the experiences of patients, families, care partners, and the workforce.

The implication for clinic owners is that patient experience cannot be delegated entirely to a satisfaction survey.

A patient who repeatedly supplies the same information, waits for an unresolved referral, or receives confusing instructions is experiencing the system, too.

So is the staff member who spends half the morning tracking down a document that should already be available.

The practical question is not simply, “How satisfied are our patients?”

It is also, “Where does our process create avoidable friction, and what are we doing about it?”

2. Katy Dessick: Pay Attention to the Person, Not Just the Task

Katy Dessick's work with Polly offers a reminder that care happens in the context of human emotion and vulnerability.

A child facing cancer is not simply a diagnosis, a treatment plan, or a series of clinical measurements. The child's experience matters.

Likewise, an administrative problem is not merely a line item in a work queue. It may affect a patient's next appointment, a staff member's workload, or a clinician's ability to complete a task efficiently.

The lesson is not that every practice needs a therapy dog. It is that healthcare teams should understand the people affected by the processes they design.

3. Researchers: Good Ideas Still Need Evidence

A randomized clinical trial published in JAMA Network Open in March 2025 examined therapy dogs added to standard child-life support in a pediatric emergency department.

The study included 80 children. At 45 minutes, the group that received therapy-dog support experienced a greater reduction in reported anxiety than the comparison group. At 120 minutes, the difference in child-reported anxiety was not statistically significant.

The study supports a measured conclusion: therapy dogs may help reduce anxiety in this setting, but the results should not be exaggerated beyond the evidence.

Healthcare technology deserves the same standard.

A compelling demonstration is not proof of sustained operational improvement. A promising AI feature is not proof of lower costs. A faster workflow is not automatically a better outcome.

Measure the result. Check the limitations. Keep what works. Change what does not.

These individuals and researchers are included for their relevant perspectives; their inclusion does not imply endorsement of OnnX.


OnnX: Move Intelligence Upstream

OnnX is being developed around an idea: many administrative problems should be addressed before they create downstream work.

Medical billing does not begin when a claim is submitted. The eventual claim depends on information gathered, documented, checked, and transferred throughout the patient's journey.

A problem that starts upstream can become a correction downstream.

For example, consider a service that requires prior authorization. A practice may need to identify the requirement, collect supporting information, submit the request, track its status, verify the response, and ensure the result is available to the people who need it.

An upstream approach would focus on making those steps visible and reliable before the service or claim reaches a point where missing information causes avoidable disruption.

That means distinguishing a request that has been submitted from an authorization that has actually been approved. It means flagging gaps without inventing answers. It means routing unresolved issues to an accountable person.

The same principle may apply to referral status, insurance eligibility, documentation completeness, coding checks, and claim preparation.

The OnnX design philosophy follows six steps:

Capture → Structure → Preserve → Propagate → Act → Learn

  • Capture relevant information at the appropriate point.
  • Structure it so it can be interpreted consistently.
  • Preserve context rather than losing it between systems.
  • Propagate it to authorized people and workflows that need it.
  • Act through appropriate, clearly assigned next steps.
  • Learn from outcomes and recurring failures.

The ambition is not to replace every system or automate every decision. It is to explore how upstream intelligence can help practices identify information gaps earlier and reduce avoidable administrative work.

This is a product direction under evaluation, not a claim that every capability is already available or that specific savings have been demonstrated.

A responsible healthcare founder should be able to distinguish a vision from a validated result.


Seven Steps Clinic Owners Can Take Now

You do not need a large AI budget to begin improving a process. Start with a problem that is specific, recurring, and measurable.

Step 1: Identify the recurring headache.

Ask staff which administrative issue interrupts their work most often. Look for missing referrals, unclear authorization status, inconsistent insurance details, repeated documentation requests, or preventable claim corrections.

Step 2: Map what really happens.

Document the actual workflow, including handoffs, systems, exceptions, and follow-up. The official process may have three steps. The staff's spreadsheet, phone calls, and workarounds may reveal ten.

Step 3: Establish a baseline.

Count how often the problem occurs, how long it takes to resolve, and what consequences follow. Record staff time and relevant operational outcomes where practical.

Step 4: Investigate the root cause.

Ask why the problem happened, not just who fixed it. Was information never collected? Was ownership unclear? Did a transfer fail? Was a requirement misunderstood?

Step 5: Standardize the process.

Define what information is needed, where it belongs, who verifies it, and how completion is confirmed. Do not remove safeguards or clinically important exceptions merely to make the workflow look simpler.

Step 6: Pilot a narrow improvement.

Try a structured checklist, clearer ownership, a validated integration, or a carefully scoped automation. Involve the staff who will use it. Keep human review for consequential decisions.

Step 7: Compare results and adjust.

Did the problem happen less often? Did resolution time fall? Did the change create new errors? Did staff find the process easier to use?

If the evidence is weak, do not declare victory because the software has a nice interface.


Six Ways Automation Can Make Things Worse

1. Automating a broken process. A faster bad process is still a bad process.

2. Adding alerts without responsibility. If nobody owns the next action, another notification is just digital confetti.

3. Trusting AI output without verification. AI can miss context, misinterpret data, or produce plausible but incorrect answers.

4. Measuring activity instead of results. The number of tasks automated tells you little about whether the practice improved.

5. Ignoring staff feedback. A tool that looks efficient to management may create extra work for the people using it.

6. Promising savings before measuring them. Claims about reduced denials, recovered revenue, or time saved should be supported by appropriate evidence.

The underlying principle is simple: buy technology to solve a defined problem, not to prove that your organization is keeping up with technology.


Five Myths Worth Challenging

Myth 1: Every denial can be prevented.

Reality: Some denials arise from correctable administrative problems; others involve coverage, clinical documentation, medical necessity, contractual terms, or payer decisions. Diagnose the cause first.

Myth 2: More automation always means lower costs.

Reality: Automation can introduce implementation, oversight, exception handling, and correction costs. Measure the net result.

Myth 3: Billing is only the billing department's responsibility.

Reality: Billing outcomes can depend on information collected during scheduling, registration, clinical documentation, referral management, and authorization.

Myth 4: AI can replace professional judgment.

Reality: AI may assist with information retrieval, prioritization, and consistency checks. It does not eliminate accountability for clinical decisions, coding, or appropriate oversight.

Myth 5: Patient experience and operational efficiency are separate goals.

Reality: Clearer information and fewer avoidable handoffs may support both, but the benefits should be tested rather than presumed.


Legal and Ethical Guardrails

Healthcare automation must respect applicable privacy, security, billing, coding, and contractual requirements.

Before using a new tool, practices should evaluate access to protected health information, vendor responsibilities, security controls, applicable business associate agreements, auditability, and procedures for handling errors or incidents.

An automated system must not invent clinical documentation, misrepresent authorization status, or submit unsupported claims. AI-generated content should be reviewed at a level appropriate to its intended use and potential consequences.

Ethical implementation also requires attention to fairness, transparency, privacy, and accountability. A tool that saves time but introduces hidden errors is not a success.

Consult qualified compliance, legal, coding, and security professionals where appropriate. This article is educational, not legal or billing advice.


Seven Measures That Matter More Than a Flashy Dashboard

Start small. Choose a handful of measures that reflect the problem you are trying to solve:

  • Rework frequency: How often does the same issue recur?
  • Resolution time: How long does it take to close the loop?
  • First-pass claim acceptance: What share of claims are accepted without initial rejection or correction, using a consistent definition?
  • Denial rate by cause: Which causes are within the practice's control?
  • Days in accounts receivable: How long does it take to collect outstanding balances?
  • Administrative time: How much staff time goes toward repetitive work?
  • Patient impact: Are avoidable delays, repeated requests, or communication failures decreasing?

Interpret changes carefully. Payer mix, claim volume, staffing, and policy changes can affect results. A pilot should be evaluated against a credible baseline, not a convenient story.


What the Future of Healthcare Should Look Like

Healthcare will never be free of complexity. Patients have different needs. Clinical judgment remains essential. Payer requirements and exceptional circumstances will continue to exist.

But complexity is not a reason to accept every source of rework as inevitable.

The next generation of useful healthcare systems may not be defined by how many tasks they automate. It may be defined by how well they preserve information, identify gaps, coordinate handoffs, and support the right action at the right time.

For physicians, that means demanding evidence from vendors.

For clinic owners, it means understanding the problem before buying a solution.

For founders, it means building around real operational needs rather than adding AI because AI is fashionable.

For patients, the hoped-for result is straightforward: less avoidable confusion, fewer preventable delays, and more attention from the people caring for them.

And that brings us back to Polly.

A facility dog cannot repair a broken data handoff. An AI platform cannot replace human compassion. A billing system cannot solve every problem in healthcare.

But each has a role when it serves the people who depend on the system.

Polly's story reminds us to look beyond the procedure and see the person. The administrative burden reminds us to look beyond the rejected claim and investigate the process that produced it.

Perhaps healthcare's next breakthrough is not doing everything faster. Perhaps it is needing to fix fewer things in the first place.

Your Turn: What Work Should Never Have Existed?

If you own or operate a medical practice, consider this question:

What is one recurring administrative task in your practice that should be prevented rather than automated?


Share your experience in the comments. Your answer may help another practice recognize a problem it has accepted as normal.

If this perspective resonates with you, repost the article to start a conversation among physicians, clinic owners, medical billers, and healthcare innovators.

I am exploring these questions through OnnX and welcome thoughtful perspectives from people doing the work every day.

PS: Visit the Featured section of my LinkedIn profile for a free resource. No signup is required.


References and Further Reading

1. Patient experience and leadership

Jason A. Wolf, president and CEO of The Beryl Institute, discusses why patient experience should be part of organizational culture and strategy, not merely a score.

Healthcare IT News, October 19, 2026: Patient experience is not a score – it's a leadership strategy

2. The administrative burden of prior authorization

The American Medical Association's 2025 physician survey, reported in May 2026, describes physicians' experiences with delays, workload, and prior authorization reform.

American Medical Association, May 13, 2026: Prior authorization reform pledge falls short with physicians

3. Research on therapy dogs and pediatric anxiety

A randomized clinical trial evaluated therapy dogs alongside standard child-life support in a pediatric emergency department.

Kelker et al., JAMA Network Open, March 3, 2025: Therapy Dogs for Anxiety in Children in the Emergency Department

4. The original human-interest story

The report describing Polly, Katy Dessick, the child, and facility dogs working at New York hospitals.

New York Post: How dogs at NYC hospitals are helping sick kids heal


About the Author

Dr. Daniel Cham is a physician, medical consultant, and entrepreneur working at the intersection of healthcare technology, practice management, and medical billing. He is the founder of OnnX, an initiative exploring how upstream intelligence may help independent medical practices identify and reduce preventable administrative work.

His focus is on translating healthcare's operational challenges into practical questions, evidence-informed improvements, and better experiences for physicians, staff, and patients.

Connect on LinkedIn.

Continue the Conversation

Knowledge drives progress when we challenge accepted practices, learn from evidence, and turn useful insights into better healthcare operations.


Disclaimer: This article is for general educational and informational purposes only. It is not medical, legal, billing, coding, compliance, or financial advice. Requirements and circumstances vary. Consult qualified professionals for advice on specific situations.


#Healthcare #MedicalBilling #HealthcareAI #RevenueCycleManagement #PhysicianEntrepreneur #PracticeManagement #PatientExperience #HealthTech #HealthcareInnovation #OnnX #IndependentPractice #AdministrativeBurden #PatientCenteredCare

 

Stephanie Johnson and Marcus Brown: A Brother’s Liver Donation, a Sister’s Second Chance, and the Healthcare Problem Nobody Should Accept

One family’s extraordinary journey raises an uncomfortable question: If healthcare exists to help people reclaim their lives, why do we tole...