Eric Cecava | What Running Three Facilities at Once Actually Teaches You

Each Entity Runs on Different Rules

Three facilities. One system. That description sounds straightforward until you try to operate it. Eric Cecava of Fort Gratiot spent six years running McLaren Port Huron's hospital, skilled nursing facility, and integrated medical group as a single organization. The coordination required is different in kind, not just degree, from running any one of them alone.

A hospital is driven by census and throughput. Beds need to be filled, cases need to move, and the metric that matters is length of stay against clinical appropriateness. A skilled nursing facility runs on staffing ratios and chronic care continuity. The residents are there for weeks, not days, and the financial model depends on Medicaid reimbursement in ways that acute care doesn't.

A medical group operates on a different clock entirely: physician satisfaction, appointment availability, referral patterns, and the long cycle times of ambulatory care. Cecava had to hold all three frameworks in his head simultaneously. The patient who leaves the hospital on day four doesn't disappear. If they transfer to the skilled nursing facility, they become someone else's census. If they follow up with a physician from the medical group, they become a different set of metrics.

The Seams Are Where the Problems Live

Most operational problems in an integrated system don't live inside the entities. They live between them. The handoff from the hospital to the skilled nursing facility requires coordination that neither unit has a direct incentive to prioritize. The hospital wants the bed. The SNF wants a complete clinical picture and a realistic care plan. The patient wants to not fall through the gap between those two priorities.

Cecava's manufacturing background gave him a specific way of seeing this. In Lean production, the constraints don't hide in the middle of a process. They sit at the transfers: where one step hands off to the next, where one team's output becomes another team's input. Healthcare transition points are exactly that. They look like handoffs. They function like chokepoints.

What Integration Actually Requires

Running an integrated system means building the connective tissue that the individual entities won't build for themselves. It means agreeing on shared metrics that cross entity lines. It means designing care pathways that assume a patient will move through multiple parts of the organization, not just one. It means having conversations that most administrators postpone because they require getting different cultures to agree.

At McLaren Port Huron, Cecava oversaw a hospital serving an acute care population, a skilled nursing facility managing post-acute recovery, and a medical group providing outpatient continuity across three Michigan counties. Getting those three entities to function as one required operational work that didn't show up on any single entity's dashboard.

The Leadership Implication

The leader of an integrated system needs to resist the pull of whichever entity is loudest. Hospitals tend to dominate internal conversations because they carry the most financial weight and generate the most urgent operational problems. That's understandable. It's also a trap. If the SNF and the medical group get treated as peripheral, the integration breaks down.

What Cecava of Fort Gratiot brought to that environment was a process engineer's instinct to look at the system before looking at the parts. The question isn't which entity is underperforming. The question is whether the connections between them are working. Usually, that's where the answer is.