A 1.5-year-old child in Kyegegwa District, western Uganda, has died of confirmed Marburg virus disease — in the same geographic response zone currently managing the largest active Ebola outbreak in Africa. [1] The World Health Organization published Disease Outbreak Notice DON612 confirming the case, adding a second hemorrhagic fever protocol to a region where response teams have been operating under Ebola isolation procedures for months. [2]

The Marburg confirmation on June 30 comes as this paper's July 1 edition named 1,270 confirmed Ebola cases and the absence of an approved vaccine for the Bundibugyo strain. The case count has since grown to 1,460 confirmed cases and 452 deaths in the Democratic Republic of Congo and Uganda combined. [3] The 190-case increase in five days is not the sharpest rate this outbreak has produced; it is a measure of how long this outbreak has been running and how much the diagnostic gap cost.

That gap is the upstream story. Standard GeneXpert assays — the molecular diagnostic tool deployed as the default in Ebola emergency response operations — were designed to detect Zaire ebolavirus, the strain responsible for the 2014-2016 West African outbreak and the 2018-2020 eastern DRC outbreak. They were not designed to detect Bundibugyo ebolavirus. [1] In a response that assumed GeneXpert could serve as the primary screening tool, samples from Bundibugyo-infected patients came back negative. Contacts were released. Transmission continued. Critical weeks passed before the diagnostic failure was identified.

On July 2, the WHO issued an Emergency Use Listing for the first diagnostic test specifically designed to detect Bundibugyo ebolavirus. [2] The EUL is the formal acknowledgment that no approved Bundibugyo test existed when the outbreak began — and that every GeneXpert-negative result during those weeks carried an unquantified false-negative rate for this specific strain. How many transmissions were seeded by contacts incorrectly cleared as negative is not fully calculable. The 1,460 confirmed case count is partly a receipt for that calculation's denominator being unknown. [2]

The Marburg case in Kyegegwa adds a second layer of operational complexity that the same response teams must now absorb simultaneously. Marburg and Ebola are both filoviruses; they spread through direct contact with bodily fluids of infected individuals and require strict isolation and personal protective equipment. But the protocols are not identical. [3] Marburg contact tracing follows a 21-day monitoring period, the same as Ebola; but Marburg does not respond to any of the Ebola-specific experimental therapeutics that have been part of the DRC response. The contact network for the Kyegegwa child requires independent investigation: who cared for the child, who they have been in contact with, whether any of those contacts have been in proximity to the Ebola response population, and whether any Marburg exposure occurred through the response workforce itself. [1]

None of those questions have public answers yet. The 1.5-year-old's contacts in Kyegegwa were reportedly being traced as of the WHO DON's publication. [2] Whether additional Marburg cases have appeared among contacts or response workers has not been reported. Whether DRC has assessed potential Marburg exposure predating the Ebola response's presence in the region also has no public record.

The operational picture for a response team managing both pathogens in overlapping geography is demanding in ways that standard emergency operations planning does not anticipate. Two separate contact-tracing databases. Two PPE protocols with different doffing sequences. Two sets of laboratory result turnaround times. Two community communication messages that must not contradict each other. Any response worker exposed to both pathogen environments requires isolation monitoring under both protocols simultaneously. [3]

CIDRAP reported the Ebola death toll crossing 400 in the same window as the Marburg confirmation. [3] The international health community covers both as parallel case-count stories. The structural reading is different: a diagnostic tool failure enabled a filovirus outbreak to reach 1,460 confirmed cases before a purpose-built test existed, and now the same response zone is managing a second filovirus simultaneously. The July 2 EUL for the Bundibugyo test is a corrective. It arrives 1,460 confirmed cases late.

-- KENJI NAKAMURA, Tokyo