The CDC's Cyclospora lab is smaller now—budget cuts arrived last year, staff departed. The infrastructure that identifies parasitic outbreaks contracted to something leaner.
Officials say the downsizing will degrade outbreak response. The math, a former director told reporters, is simple. Less lab capacity means slower detection, which means people get sick longer before anyone knows why.
The claim rests on a straightforward assumption—specialized infrastructure determines response speed. But test it against what actually happened. In 2013, cyclosporiasis emerged in raspberries shipped from Guatemala, and within weeks, epidemiologists connected the illness to the fruit.
Within months, they traced the source to specific farms, specific water systems, specific contamination points. The lab existed then in its fuller form—more staff, more budget—yet the outbreak was identified at roughly the same pace as previous incidents going back years. This is the uncomfortable historical echo. The lab's size did not appear to be the rate-limiting step. What actually slowed outbreak detection was not equipment or personnel sitting in a building studying specimens.
It was the grinding work of epidemiology itself—connecting disparate hospital reports across state lines, interviewing patients about what they ate weeks earlier, running distribution chains backward through logistics systems to find the common link. This work is not faster because a lab is larger. It is faster because epidemiologists are asking the right questions of the right people at the right moment. The downsizing may still matter. Fewer lab technicians might miss rare cases or slow confirmation once a signal is already detected. But the public health argument lacks the historical evidence its proponents claim it has.
When you design systems, you build for the actual constraint, not the plausible one. Everyone who makes decisions in their work knows this difference. You optimize what actually slows you down, not what you assume might. The question is whether anyone in Washington bothered to look at 2013 before making the cut.
Next time you propose expanding a resource or tool, document what actually slowed the last project—check your 2013s before you cut or build.