CDC's current Bundibugyo page now gives the Democratic Republic of the Congo a number that no careful reader can simply lay over WHO's May 29 table. CDC says DRC has 321 confirmed cases and 48 confirmed deaths. It lists Uganda at 11 confirmed cases, one confirmed death, one probable case, and one probable death. WHO's disease-outbreak notice, dated May 29, uses a different and older public table: 906 suspected DRC cases, 223 suspected DRC deaths, 134 confirmed cases across DRC and Uganda, 18 confirmed deaths, and nine confirmed Uganda cases. [1] [2]

That is not a scandal by itself. It is a source-dating problem, and source dating is what makes this a lead. Monday's paper said CDC's four-airport and 21-day process turned Bundibugyo into service journalism. It also said WHO's contact lists made response capacity the hard number. Tuesday's question is the next one: when the public tables move at different speeds, which number should a traveler, clinician, or editor use? [1] [2]

The answer is not to pick the larger number because it sounds more urgent. It is to print the date, category, and institution beside the number. CDC's June 1 page is the latest U.S. current-situation page in the source stack. WHO's May 29 notice is the fuller international situation report, with suspected cases, sample analysis, health-worker infections, contact lists, and response constraints. They are different instruments. A thermometer and a hospital census can both be true; confusing them is bad medicine. [1] [2]

CDC's current page says there are no confirmed outbreak-linked U.S. cases. It also says the U.S. government continues to route affected air passengers through Washington-Dulles, Atlanta, Houston, and John F. Kennedy International Airport. The page keeps the 21-day entry-restriction period for affected travelers and says the public and traveler risk in the United States remains low. Those are service facts. They do not make the outbreak small. They make the U.S. operating rule narrow. [1]

WHO's notice makes the outbreak look less narrow because it is describing the outbreak, not the U.S. airport rule. It says DRC has suspected and confirmed cases, including health and care workers, and it names security incidents and community resistance among operational constraints. It also says Uganda listed contacts and that one U.S. doctor was receiving care in Germany after exposure in DRC. These facts belong near the CDC table because the U.S. screening system exists precisely because the source outbreak is not an abstraction. [2]

The public-health mistake would be to treat CDC and WHO as competing teams. The agencies are describing different parts of a chain. One end is the country-level outbreak, with suspected cases, confirmed cases, laboratories, contacts, burials, health workers, and community response. The other end is the traveler-service system that meets a defined class of passengers at four U.S. airports. The chain is only intelligible when the links stay labeled. [1] [2]

The count jump matters because confirmed cases carry a different practical meaning than suspected cases. A suspected case is a surveillance category. It can include people who later test negative or never get tested. A confirmed case has laboratory weight. WHO's May 29 notice is valuable because it includes both suspected and confirmed categories and says how many samples were collected and analyzed. CDC's June 1 page is valuable because it gives a later confirmed DRC count. Neither should be flattened into a single headline number. [1] [2]

This is why the article uses the word "past" carefully. CDC's confirmed DRC count has moved past the WHO confirmed table available in the memo stack, but that does not mean WHO was wrong. It means WHO's public notice is older and broader while CDC's current situation page has a newer confirmed DRC line. In outbreak journalism, a newer table can be more current without being more complete. A fuller table can be more instructive without being the freshest. [1] [2]

The reader-service part remains almost deliberately prosaic. Travelers from the affected region should follow CDC instructions if routed through the four named airports, monitor for symptoms during the 21-day period, and contact healthcare providers and public-health authorities as directed if symptoms develop. Clinicians should keep travel, exposure, symptoms, isolation, testing, and notification together. Everyone else should resist the temptation to turn any airport photograph into epidemiology. [1]

The vaccine and treatment caveat also remains essential. WHO says no approved vaccines or specific treatments currently exist for Bundibugyo virus disease, and response relies on case identification, isolation and care, contact tracing, safe burials, and community engagement. CDC's travel notices in the research stack carry the same distinction. A reader who hears "Ebola" may import assumptions from Zaire ebolavirus coverage. This outbreak requires subtype discipline. [2]

There is a moral temptation in outbreak writing to sound more certain than the institutions. Panic has certainty. Dismissal has certainty. Public health usually has dated tables and bounded instructions. CDC's no-U.S.-case line, low-risk assessment, four-airport routing, and 21-day period are bounded instructions. WHO's suspected-case totals, confirmed-case totals, contact lists, and operational constraints are dated response data. The paper's job is to keep the bounds visible. [1] [2]

That is also the divergence between the mainstream account and the X account. Mainstream coverage tends to print the agency update and move on. X discourse tends to turn any airport rule into proof of either a hidden crisis or bureaucratic theater. Both frames can miss the useful middle: official sources are not interchangeable, and the most practical question is often which public table has which date. [1] [2]

The airport rule can look dramatic because airports are theatrical places. They have lines, uniforms, signs, gates, cameras, and a built-in audience. But the rule is not general airport fear. It applies to a defined travel history. CDC's own page says no U.S. cases linked to the outbreak have been confirmed and that risk for the general public and travelers remains low. Low risk is not no system. It is a reason to keep the system precise. [1]

The WHO notice can look dramatic because the numbers are larger and the response constraints are harder. It describes suspected deaths, confirmed deaths, contacts, sample testing, and insecurity. Those are grave facts. They belong in the article because an outbreak with weak or pressured contact follow-up can move faster than a press cycle. But they still do not support the claim that casual U.S. airport contact is the central danger. [2]

The next useful update would be a reconciliation table from WHO, DRC, Uganda, Africa CDC, or CDC that aligns suspected and confirmed cases by date and country. The next practical update would be a change to travel notices, airport routing, or clinical guidance. The next scientific update would be a Bundibugyo-specific vaccine, treatment, or trial document. Until one of those appears, the paper should not make the outbreak larger or smaller than the documents make it. [1] [2]

There is a second reason source dating matters. Public-health counts are not only facts about patients; they are facts about capacity. A health ministry or WHO office may need time to classify suspected cases, confirm laboratory results, reconcile death reports, and separate one country's line from another's. A U.S. agency may update the traveler-facing page when the confirmed case count changes enough to affect its current-situation summary. Those are legitimate workflows. They become confusing only when a reader is asked to treat every update as the same kind of update. [1] [2]

The confirmed-death count illustrates the problem. CDC's June 1 current page puts DRC confirmed deaths at 48. WHO's May 29 notice puts confirmed deaths across DRC and Uganda at 18 while also listing 223 suspected DRC deaths. Those sentences cannot be responsibly merged into one death toll. A suspected death and a confirmed death answer different questions. A country-specific line and a cross-country line answer different questions. A newer current-situation page and an older disease-outbreak notice answer different questions. [1] [2]

The better habit is to make every number carry its passport. Institution: CDC or WHO. Date: June 1 or May 29. Geography: DRC, Uganda, or both. Category: suspected case, confirmed case, suspected death, confirmed death, listed contact, sample collected, sample analyzed. Once those labels are attached, the reader can see the pattern without being manipulated by it. The outbreak is serious. The U.S. traveler rule is bounded. The public tables are moving. All three statements can coexist. [1] [2]

This is also how the paper should cover future health alerts beyond Bundibugyo. The same discipline will apply to measles, recalls, heat, smoke, influenza, or any condition where agency tables update at different rhythms. The useful article is rarely the one that shouts first. It is the one that tells readers which document changed, what category changed, and what action, if any, follows. [1] [2]

This is why the lead belongs in Life rather than World. The story is not border panic, geopolitics, or a morality play about institutions. It is how ordinary readers navigate a dangerous disease when official documents do not update at the same pace. Date the table. Name the category. Keep the traveler rule separate from the outbreak count. That is not less serious than alarm. It is the serious part. [1] [2]

-- NORA WHITFIELD, Chicago