PACE Organizations Are Scaling. Their Logistics Workflows Aren't.

There are now 202 PACE programs operating across 33 states, serving nearly 92,000 participants. Five years ago, that number was closer to 130 programs. The model is growing because it works: PACE keeps nursing home-eligible adults in their communities, coordinates their care through an interdisciplinary team of 11 mandated professions, and does it all under a single capitated payment. Medicare and Medicaid pay a per-member-per-month rate that ranges from roughly $2,700 to over $8,200 depending on geography and acuity. The PACE organization takes on the full financial risk.

That financial structure creates a powerful incentive to coordinate well. Every unnecessary hospital admission, every missed specialist appointment, every delayed equipment delivery eats directly into the margin. And as the U.S. population aged 65 and older is projected to nearly double from 52 million to 95 million by 2060, the PACE programs positioned to absorb that demand are the ones that figure out logistics coordination before they hit scale.

Most haven't figured it out yet.

The Coordination Ceiling

A typical PACE participant needs transportation to the day health center two or three times a week. They also need rides to specialist appointments, pharmacy pickups, and lab work. Many need durable medical equipment delivered and maintained. Most receive home health visits. Some require meal delivery. All of it has to be coordinated across a web of vendors, schedules, clinical orders, and participant preferences.

The interdisciplinary team meeting, held at least monthly for every participant, is supposed to keep this orchestrated. In practice, the logistics fall to care coordinators and transportation managers who spend their days on the phone. Industry data shows the average transportation scheduling call takes 31 minutes. Multiply that by the number of rides a 200-participant PACE program arranges each week, and you start to see where the staff hours go.

It gets worse as programs grow. A PACE organization expanding from one center to three doesn't just triple its participant count. It multiplies the number of vendor relationships, service zones, scheduling conflicts, and communication threads. The coordinators who held everything together at 100 participants can't hold it together at 400 without either hiring more people or finding a fundamentally different way to work.

Most programs hire more people. That's the coordination ceiling: the point where adding headcount is the only answer because the workflow can't absorb more volume.

Where the Fragmentation Lives

PACE logistics fragmentation isn't a single broken process. It's a collection of disconnected ones. Transportation lives in one system (or on a whiteboard). DME orders go through a vendor portal or a fax machine. Home health referrals happen over the phone. Pharmacy coordination is a separate workflow entirely. And the EHR, which should be the single source of truth for participant care, often doesn't know about any of it until someone types a note after the fact.

This creates three problems that compound as programs scale.

First, visibility. When a care coordinator can't see the status of a participant's ride, equipment delivery, and home health visit in one place, they spend time chasing down updates instead of managing exceptions. The phone becomes the primary coordination tool. That works at small scale. It collapses at large scale.

Second, data integrity. Manual documentation means logistics events are recorded inconsistently, late, or not at all. The interdisciplinary team makes decisions based on incomplete information. Audit readiness suffers. And the organization can't analyze its own logistics data to find patterns because the data doesn't exist in a structured form.

Third, vendor management. PACE organizations work with multiple transportation providers, DME suppliers, home health agencies, and pharmacies. Each has different scheduling systems, communication preferences, and performance standards. Managing these relationships through phone calls and email means there's no systematic way to track vendor performance, enforce service-level agreements, or shift volume when a provider underperforms.

What EHR-Embedded Logistics Changes

The PACE organizations breaking through the coordination ceiling are doing it by moving logistics into the EHR workflow instead of running it alongside the EHR in separate systems.

When a care coordinator can initiate a transportation request from within the participant's chart, and the request automatically pulls demographics, pickup location, destination, and clinical context through FHIR APIs, the scheduling process that took 31 minutes drops to under one. The ride is dispatched. Real-time tracking appears in the clinical record. And the entire transaction is documented without anyone typing a note.

That same architecture works for DME orders, home health referrals, and other logistics services. The participant's chart becomes the operational command center, not just the clinical record. Coordinators see all pending and in-progress logistics in one view. The interdisciplinary team has complete, current information when they meet. And the organization generates structured logistics data that can be analyzed for cost patterns, vendor performance, and operational bottlenecks.

This is the approach VectorCare was built around. The platform uses SMART on FHIR standards to embed transportation, DME, home health, and other logistics services directly into Epic workflows. For PACE organizations running on Epic, the care team stays in their existing environment. The logistics infrastructure runs in the background, connecting the vendor network, automating dispatch decisions, managing credentialing and compliance, and writing every event back to the medical record.

The result isn't just efficiency. It's a different operating model. Instead of hiring more coordinators as participant volume grows, the organization invests in infrastructure that absorbs the complexity. The coordination ceiling rises. And the margin that PACE programs need to remain financially viable stops eroding with every new enrollment.

The Scaling Math

Consider a PACE organization serving 300 participants across two centers. If each participant averages three logistics events per week (rides, deliveries, visits), that's 900 coordination events. At 31 minutes per phone-based scheduling interaction, the organization needs roughly 465 staff hours per week just to arrange services. That's nearly 12 full-time coordinators doing nothing but scheduling.

With EHR-embedded logistics, the same 900 events at under one minute each require roughly 15 staff hours per week. The difference isn't marginal. It's the difference between a cost structure that works and one that doesn't.

PACE capitation rates aren't increasing fast enough to cover unlimited hiring. The programs that scale profitably will be the ones that treat logistics coordination as infrastructure rather than staffing. They'll invest in platforms that automate the repeatable work so their clinical teams can focus on the work that actually requires human judgment: managing complex participants, navigating care transitions, and keeping people healthy enough to stay out of the hospital.

What Comes Next

The PACE model is expanding because the demographics demand it and the economics support it. But expansion without operational infrastructure is just growth without margin. The organizations that build logistics coordination into their EHR workflows now will be the ones positioned to absorb the wave of new participants that's coming over the next decade.

The ones that don't will hit the coordination ceiling. And the ceiling doesn't move on its own.

Learn more about how PACE organizations are modernizing logistics coordination at vectorcare.com.