Health systems continue to expand their advanced practice provider workforce in response to growing patient demand, physician capacity constraints and persistent recruitment challenges. Yet many organizations discover that adding APPs does not automatically translate into better access or improved operational performance.
When that happens, the natural response is often to look at the APP: Is productivity high enough? Is the schedule full? Is the provider seeing the right number of patients?
Those are reasonable questions but they start in the wrong place. An APP can be highly capable and appropriately staffed yet still work in a system that limits their effectiveness. If roles are poorly defined, responsibilities overlap, or routine work remains dependent on physician involvement, adding another clinician may simply add capacity to an inefficient workflow. Before concluding there is an APP productivity problem, leaders should consider a different possibility: The workflow may be the problem.
Staffing is not the same as integration
Many organizations approach APP workforce planning primarily as a staffing exercise. Demand increases, access deteriorates or physician schedules reach capacity, and an additional APP position is requested. That approach answers one important question: How many clinicians do we need? But it does not necessarily answer a more fundamental one: How should the work be performed?
Without intentional redesign, APPs are often inserted into workflows originally built around physicians. The result may be duplicate visits, unnecessary handoffs, inconsistent role expectations or APP schedules that simply replicate physician templates. An APP may have capacity, for example, while scheduling rules continue to direct appropriate patients to already constrained physician schedules. In these environments, what appears to be an APP utilization problem actually reflects a care-delivery model that has never been redesigned to incorporate APP capability.
Effective integration therefore requires organizations to move beyond headcount. The objective is not simply to add another provider. It is to design a system in which each member of the clinical team is doing the work most appropriate to their capabilities.
Start with the work, not the provider
Instead of beginning with the question, “What can the APP do?” leaders should first examine how patients move through the clinical system.
A simple approach is to map the patient journey:
Demand → Entry → Evaluation → Decision → Treatment → Follow-up
At each stage, leaders can ask several practical questions:
- What work is being performed?
- What level of clinical expertise does that work require?
- Who is best positioned to perform it?
- Where are patients handed from one clinician to another?
- Where does work stop while waiting for physician input?
- Which patients are routinely escalated to physicians, and why?
- Where does individual physician preference create variation?
- Where must the physician touch this workflow, and does the physician truly need to?
This exercise frequently reveals constraints that workforce planning alone does not. A perceived provider shortage, for example, may actually involve poorly differentiated visit types, unnecessary physician review, limited APP-controlled follow-up capacity or scheduling rules that do not direct patients to the first appropriate clinician. The principle is straightforward: Optimize the work before determining the workforce required to perform it.
Match clinical resources to clinical need
Workflow redesign should not be interpreted as simply transferring more work from physicians to APPs. The goal is not maximum APP autonomy, it is appropriate allocation of clinical resources. Instead of asking, “What can the APP take off the physician’s plate?” organizations can ask a more productive question “Which patients and clinical decisions require physician expertise, and which do not?”
One useful approach is to consider clinical work across three categories.
APP-led care may include predictable presentations, defined clinical pathways, routine follow-up and other care that can be managed independently within applicable scope-of-practice, credentialing and organizational requirements.
Collaborative care involves patients who can be primarily managed by an APP but have clearly defined triggers for physician consultation or escalation.
Physician-led care preserves physician capacity for clinical complexity, procedures and decisions requiring physician expertise.
This is more than role clarification. It allows organizations to intentionally match patient need with clinical capability rather than allowing historical patterns to determine who sees whom. APP integration should not diminish the physician role; it should concentrate physician expertise where it creates the greatest clinical value.
Measure the model, not just the APP
Redesigning the work also requires reconsidering how success is measured. Individual APP productivity remains an important operational measure, but it cannot fully describe the value of an integrated care model. If APP deployment allows physicians to see more new or complex patients, reduces avoidable handoffs, expands appointment availability or improves continuity, the benefit may be visible elsewhere in the system.
Leaders should therefore evaluate several dimensions of performance:
Access: Has appointment availability improved? Has time to appointment changed?
Physician capacity: Are physicians able to devote more capacity to new, complex or procedure-based care where appropriate?
Patient flow: Have unnecessary handoffs or delays been reduced?
Workforce: Are APPs consistently working within a clearly defined role? Does the model support sustainable physician and APP workloads?
Operational performance: Has team-level productivity or incremental clinical capacity improved?
The unit of analysis matters. If organizations evaluate only the APP, they may miss whether the care model itself is producing value.
Five questions to ask before adding the next APP
When considering additional APP staffing, leadership teams can begin with five questions:
- Demand: Where is unmet patient demand occurring?
- Work: What clinical work or process is creating the constraint?
- Capability: Which clinician is best positioned to perform that work?
- Dependency: Where does the workflow require physician involvement, and is that involvement necessary?
- Outcomes: What measures will determine whether the redesigned model creates value?
This changes workforce planning from a largely linear process of: volume → FTE request → hire into a more intentional, sequence with more predictable results: Demand → Workflow → Capability → Care Model → Workforce Requirement → Outcomes
APP optimization is care-model optimization
As health systems continue to expand their APP workforces, the next opportunity is not simply to employ more APPs or expect existing APPs to produce more. It is to design clinical systems that make better use of the entire care team. When APP utilization falls short of expectations, leaders should certainly evaluate staffing, competency and performance.
But they should examine workflow with equal rigor. The most important question may not be, “How productive is this APP?” It may be, “Have we designed a system in which this APP, and the physicians working alongside them, can be as effective as possible?” When organizations redesign the work first, improved access, physician capacity, patient flow and workforce sustainability can become outputs of the care model rather than expectations placed on individual clinicians.
Mr. Lahr is director of advanced practice providers at Orlando (Fla.) Health.
