Eric Cecava | What Running Three Hospitals Reveals About Healthcare Quality

Eric Cecava in the pharmacy


Managing quality across multiple facilities exposes the gap between system averages and what is actually happening on the ground

Quality in healthcare is often measured at the system level and managed at the facility level, which creates a specific kind of problem. The system-level metric looks one way. The facility-level reality looks another. Eric Cecava of Fort Gratiot, Michigan, who progressed from System Director of Process Excellence to VP of Regional Operations and Quality to Chief Operating Officer at Adena Health System in Ohio before taking on executive leadership at McLaren Port Huron in Michigan, has spent his career navigating exactly this gap.

System Averages Hide Site-Level Problems

When quality metrics are aggregated at the system level, what gets reported is an average. That average can look acceptable when one facility is performing well and another is underperforming, because the strong site compensates for the weak one in the aggregate number. That situation is invisible from the system dashboard and visible only to someone who is looking at performance by site.

Cecava's work in business intelligence and data systems at Adena Health System gave him a specific orientation toward this problem: the data infrastructure matters, but how the data is presented and to whom is what determines whether it drives action. A quality metric reported monthly to a system-level committee is not the same management tool as a quality metric reported weekly to the clinical team at the site where the problem is occurring.

Standardization Without Accountability Is Just Policy

Health systems with multiple facilities tend to develop quality standards that apply across all sites. Those standards make sense: consistent protocols, consistent documentation requirements, consistent expectations for clinical performance. But a standard that is written and not monitored is a policy. A standard that is monitored and enforced is a management system. The difference between those two things is what determines whether quality is consistent across sites or just consistently described.

The Lean Six Sigma deployment that Cecava led at Adena was concerned with this distinction. Process standards that were implemented without ongoing monitoring tended to drift back toward pre-implementation behavior. The discipline of maintaining improvement after the initial project is complete is where most process improvement efforts lose their gains.

Regional Operations Is Different From System Strategy

Cecava's title at Adena, VP of Regional Operations and System Quality, named the tension that exists in every multi-facility health system: the regional reality is different from the system strategy. Facilities in different communities, serving different patient populations, with different physical infrastructure and different medical staff cultures, require management attention that accounts for those differences rather than pretending they do not exist.

The operational work in regional roles is largely about understanding the specific context of each facility well enough to make management decisions that work in that context, while maintaining the alignment with system standards and objectives that makes operating as a system worthwhile. It is a balance that has to be actively managed rather than structurally solved.

Quality Performance and Financial Performance Are Connected

The relationship between quality outcomes and financial performance in healthcare is real but operates on a longer timeline than most financial planning cycles accommodate. Facilities that consistently perform well on clinical quality metrics tend to have lower readmission rates, fewer adverse events, shorter length-of-stay for appropriate cases, and better patient experience scores. Each of those outcomes has a financial consequence.

The organizations that invest in quality infrastructure, including the staffing, the data systems, and the leadership attention required to maintain quality performance, are making a long-term financial argument that is difficult to demonstrate in a single budget cycle. The executives who can make that argument credibly, with data that connects quality performance to operational and financial outcomes, are the ones who can sustain quality investment in an environment of competing budget priorities.

The COO View on Quality Is Operational, Not Aspirational

Cecava's view of quality in health systems is grounded in his operational background: quality is not a program or an initiative. It is the output of an operational system that is designed to produce consistent clinical results and managed to maintain those results over time. The language of aspiration, the culture of excellence, the commitment to quality as a value, is not wrong. But it is not sufficient.

What is sufficient is the operational infrastructure: the data systems that make performance visible, the management processes that hold people accountable for results, the improvement methodology that addresses problems when they appear, and the leadership attention that signals to the organization that quality is a real priority rather than a stated one. That is the work that produces quality outcomes across multiple facilities, and it is operational work through and through.


Comments

Popular posts from this blog

Eric Cecava | What Changes When You Become Accountable for Everything

Eric Cecava | Why Geography Shapes Healthcare More Than Most Leaders Admit

Eric Cecava | Why the COO Job and the CEO Job Are Not the Same Job