SENA Insights
Posted on November 2, 2026
By Anthony J. Wehbe, DO, MBA, FACOI | Founder & CEO, SENA Health | Practicing Internist, Senacare | Former Health-System Physician Executive
Why physician enterprises need to organize around patient intent, not organizational structure
There is something we have normalized in healthcare that makes less sense to me the longer I practice medicine.
We still ask patients — and often their families — to understand how our organizations work before they can get what they need.
A few months ago, one of my skilled nursing facility patients developed new atrial fibrillation and needed a cardiology consult. His daughter, who works full time an hour away, spent her entire lunch break on hold trying to figure out whether she should call the facility, the hospital that had seen her father last, the cardiology office, or me. She is more organized than most operations directors I’ve worked with in 20 years around this field, and it still took her forty minutes to get one appointment on the books. That is not a family navigating our health system. That is a family doing our organizational chart’s job for us, for free, on their lunch break.
We instruct patients to call this number for scheduling but use another one for referrals. We tell them to send a portal message for one issue, call the nurse line for another, contact the hospital for a third, and if the problem involves a specialist, start over with that office.
We call that access. From the patient’s perspective, it is often just work.
I see this from both sides. I still practice medicine — mostly for an elderly, home-bound, and long-term-care population through Senacare — and I founded SENA Health specifically because the gap between how we organize care and how patients experience it never closed, no matter which side of the table I sat on: bedside, or the C-suite at Jefferson Health and Kennedy Health System.
The organization sees scheduling, triage, referrals, prior authorization, portal messaging, call-center operations, and clinical escalation. The patient sees a problem. Their medication ran out. Their symptoms are worse. Their child is sick. They were discharged yesterday and are not sure what comes next.
Too often, we make the patient decide which part of our organization owns the problem.
That is the part I think we need to rethink.
The issue is not that patients use too many front doors. They will always call, text, use portals, visit websites, or talk directly with staff. The problem is that too many of those doors still lead into different workflows, different rules, and different silos.
A better model is not necessarily one front door. It is one operating logic behind the doors.
Channels are how patients enter. Intent is what the system needs to understand. Orchestration is what has to happen next.
That sounds straightforward. It requires far more than a better phone system or a more sophisticated chatbot.
I saw exactly why, working with one of our partner medical groups on cardiology referral leakage. The practice administrator’s first assumption was that the referral coordinators were understaffed, and the group added two more people as a stopgap. The backlog didn’t clear. The actual problem was that referral orders landed in three different work queues depending on which EHR module had generated them, and roughly half of those queues weren’t being worked at all, because no single role was accountable for closing them out. Nobody was lazy, and nobody was understaffed in the way anyone assumed. The workflow simply had no owner for the last mile and no amount of additional headcount was going to fix a queue nobody was responsible for.
If a patient says she needs to see a cardiologist, the first job is to understand what she actually needs. Is this a routine consultation, a worsening symptom, a post-discharge follow-up, or something that requires immediate clinical review?
The next question is whether the system can act on that information safely and intelligently. Can it apply the right clinical and operational rules, know when clinical judgment is required, see available capacity, account for insurance and location, offer a reasonable alternative, move the necessary information, and close the loop?
That is where navigation becomes an operating capability rather than a service function. It is also where the limitations become important.
Better navigation does not create physicians who do not exist. It does not manufacture appointment capacity. It does not eliminate payer restrictions or solve every referral rule.
Sometimes the problem really is supply.
But most physician enterprises cannot add meaningful clinical supply quickly. What they can often do is use the capacity they already have more intelligently, by understanding demand better, routing it more accurately, reducing avoidable hand-offs, and getting patients to the right next step with less friction.
That is a meaningful operating opportunity. It is also why SENA Health does not start with a channel or a piece of technology.
We start with the workflow. We look at what patients are trying to get done, where requests enter, what rules apply, where work stalls, which hand-offs add value, and which are simply artifacts of the way the organization evolved. Then we ask what the redesigned workflow requires.
Some steps can be automated. Some belong with trained staff. Some need clinical escalation. Some should disappear altogether.
The technology comes after the operating design, not before it.
AI can help enormously. It can understand language, identify intent, gather information, automate repetitive work, and make interactions more convenient. But AI does not, by itself, create orchestration.
Here is the uncomfortable version of that point: most of the “patient engagement” AI I see being deployed right now is being layered on top of exactly this kind of fragmented workflow, and I think that should worry boards more than it currently does. A chatbot that beautifully interprets a patient’s intent and then hands it into the same three broken queues hasn’t fixed wayfinding. It has automated the maze. We are at real risk, across this industry, of building extremely sophisticated technology whose main achievement is helping patients get lost faster and more pleasantly.
For that, the physician enterprise still needs shared rules, visibility into capacity, clear escalation protocols, enough data to act safely, and enough operational authority to move work across practices and departments. Without those things, we may make the front-end interaction more elegant while leaving the underlying fragmentation completely intact.
That distinction matters because every failed hand-off creates work. A patient calls back, or a referral is resent. A medical assistant follows up while a scheduler searches manually for an open slot. A physician receives another message in an already overflowing inbox because the first workflow never resolved the issue.
Patients experience that as friction. Offices experience it as labor cost. For physicians, it often shows up as one more piece of maddening complexity in an already overbooked day.
I think about this in the same five terms I use for every operating decision at SENA Health and Senacare: capacity utilization, leakage, clinician burden, patient retention, and margin. Wayfinding failures hit all five at once. Every patient who gives up mid-navigation is capacity that sat empty and demand that leaked to an urgent care or a competing system. Every family member acting as a human router is a physician’s inbox that will get the unresolved question anyway, usually at the worst possible time.
When we rebuilt referral and access workflows across that network — first at Kennedy Health System, then at Jefferson Health New Jersey after the 2017 merger — we were not running a patient-satisfaction project. We were closing a revenue leak. Over those six years, active unique patient lives grew from roughly 70,000 to more than 300,000, and medical group revenue grew fivefold. Acquiring practices and adding providers created the demand; fixing how patients moved between them is what let us keep it. Better wayfinding is not a courtesy line item. It is how you keep the demand you already paid to generate.
The goal should not be to make patients better navigators of our organizations. It should be to make the organization better at navigating on their behalf.
Leadership should be able to answer four questions:
The system should understand the complexity so the patient does not have to.
Want to talk through your organization’s front end? Schedule a conversation with Dr. Wehbe.