When public health agencies respond to an emerging outbreak, one of their most important tools is a screen. A design case study on how dashboards, maps, and case counts turn a frightening threat into something the public can actually understand.
When public health agencies respond to an emerging infectious-disease event, one of their most important tools isn't a vaccine or a lab — it's a screen. The dashboards, maps, case counts, and risk statements that organizations like the CDC and WHO publish are how a frightening, abstract threat becomes something the public and clinicians can actually understand and act on. The 2026 hantavirus outbreak — a cluster of Andes virus infections linked to the MV Hondius expedition cruise ship, first reported to the WHO on May 2, 2026 — offers a clear, real example of the kind of event these communication systems are built for, and a useful lens for examining how outbreak data should be designed.
This is a data-visualization and information-design case study, written with care for the subject. The facts of the disease here come from public health authorities: hantavirus can cause hantavirus pulmonary syndrome (HPS), the 2026 outbreak involved the Andes virus, and as of mid-May the WHO had reported a small number of cases including several deaths, with agencies assessing the risk to the general public as very low. This article offers no medical advice; for that, readers should consult the CDC, WHO, or a clinician. Our focus is narrower and purely about design: how do you visualize an outbreak so that people understand the true situation — neither panicking nor dismissing it — when the underlying data is incomplete, evolving, and emotionally charged?
The Hardest Design Brief: Inform Without Inflaming
Every outbreak dashboard faces a brief unlike almost any other in design: communicate a genuine health threat accurately while neither understating the danger nor triggering disproportionate fear. This is a razor's edge. Underplay a hantavirus situation and you fail people who need to take it seriously; overplay it and you cause panic, erode trust, and crowd out attention that other risks deserve. The 2026 outbreak is a textbook example of why this balance is so delicate — it involved a serious disease with fatalities, yet the assessed risk to the general public was very low, two facts that are both true and easy to misrepresent in either direction.
The design has to hold both truths simultaneously. A dashboard that screams about a deadly hantavirus without contextualizing the actual exposure risk is technically accurate and practically harmful. One that buries the seriousness to avoid alarm fails the people genuinely at risk. The entire craft of outbreak visualization lives in that tension: presenting the gravity of the disease and the proportionality of the risk in the same breath, so a reader comes away neither terrified nor complacent but appropriately informed. This is arguably the highest-stakes information-design problem there is, because the cost of getting the emotional register wrong is measured in real public behavior.
The Risk-Level Statement: The Most Important Element
If a single element matters most on an outbreak page, it's the risk-level communication — the plain statement of how much the audience should actually worry. For the 2026 hantavirus event, the central message from agencies was that the risk to the general public was very low, even as the outbreak itself was serious for those exposed. How that statement is designed and positioned shapes the entire public response.
The instinct might be to lead with case counts and dramatic maps, but the most responsible design leads with calibrated context. A reader arriving at a hantavirus page is often anxious, and the first thing they need is an honest answer to "should I be worried?" Putting a clear, prominent, plainly-worded risk assessment up top — "risk to the general public is very low" — does more to inform than any chart, because it frames everything that follows. Without that frame, raw numbers invite catastrophizing; a count of cases with no context reads as scarier than it is. The risk statement is the lens through which the data should be read, and design decisions about its prominence, wording, and placement are therefore the most consequential on the entire page.
Crucially, this statement must be honest in both directions. "Very low risk to the general public" should sit alongside, not instead of, an acknowledgment that the disease is serious and that specific groups face higher exposure. The 2026 hantavirus messaging worked precisely because it distinguished between the general public (very low risk) and people with direct exposure to the source (a real concern). Designing that distinction clearly — who is and isn't at elevated risk — is what separates honest risk communication from either fearmongering or false reassurance. A good outbreak dashboard never makes the reader guess which category they fall into.
Case Counts: Numbers That Carry Weight
Case and fatality counts are the spine of any outbreak dashboard, and they demand unusual care because each number represents a person. For the 2026 hantavirus outbreak, the figures were small — on the order of ten cases and a few deaths as of mid-May — and that smallness is itself information that the design must convey accurately rather than inflate.
The first design challenge is conveying scale honestly. A large, red, full-screen "3 DEATHS" treatment communicates something very different from the same number presented soberly in context, even though both are factually correct. For a hantavirus outbreak where the absolute numbers are small and the public risk low, design choices that visually amplify the figures — oversized type, alarming color, dramatic animation — distort the reality even without changing the data. The honest approach sizes the presentation to the actual situation: serious, clearly stated, but not sensationalized. The numbers should be findable and precise, not weaponized for attention.
The second challenge is honesty about what the numbers mean and don't mean. Outbreak counts are provisional and lag reality — a hantavirus case count reflects what's been confirmed and reported, not the true current state, and confirmed-versus-suspected cases are meaningfully different. A well-designed dashboard distinguishes these clearly: confirmed cases, probable cases, and deaths shown as distinct categories rather than blended into one impressive-looking total. It also timestamps everything, because an outbreak number without a "data as of" date is misleading by omission. The design's job is to let the figures carry their real weight — neither more nor less — and to be transparent about their inherent uncertainty.
Mapping an Outbreak: Geography That Helps, Not Frightens
Maps are powerful in outbreak communication and dangerously easy to misuse. A map showing where hantavirus cases have appeared can orient and inform, or it can mislead — and the difference is entirely in the design. The 2026 outbreak is an instructive case because its geography was unusual: a cruise ship that departed Argentina and traveled across the South Atlantic, with exposed individuals later dispersing to many countries. That's a genuinely hard thing to map honestly.
The core danger is that a map can imply spread that isn't happening. Plotting a dot in every country where an exposed passenger returned can make a hantavirus outbreak look like it's sweeping the globe, when in reality those are isolated, monitored individuals from a single source event, not evidence of community transmission. A responsible map distinguishes the source of an outbreak from the residences of exposed people, and transmission hotspots from mere case locations. Color, clustering, and annotation all have to work to prevent the eye from inferring a pandemic where there's a contained cluster. For a person-to-person-capable virus like the Andes type behind the 2026 hantavirus event, conveying how and where transmission actually occurs — close, prolonged contact, largely within the ship environment — matters enormously, and a naive dot map erases that nuance.
The lesson is that geographic visualization carries implicit narrative. A reader doesn't just see where the dots are; they infer a story about how the disease moves. The designer's responsibility is to make sure that inferred story is the true one. A hantavirus map that accurately shows a single-source shipboard cluster with monitored contacts tells a calming, accurate story; the same data plotted carelessly tells a false story of uncontrolled spread. Geography is never neutral in outbreak design, and the choices about what to plot and how are choices about what the public will believe.
Contact Tracing Visualizations: Showing the Web Without Exposing People
Contact tracing — mapping who may have been exposed through whom — is central to outbreak response, and visualizing it presents a distinctive design tension between clarity and privacy. For the 2026 hantavirus outbreak, agencies were tracing and monitoring passengers and their travel contacts across multiple countries, exactly the kind of network that benefits from visualization but also risks exposing individuals.
The design value of a contact-tracing visualization is that it can show the structure of an outbreak: how cases connect, where the chains of transmission run, which clusters are contained and which are still propagating. For a virus like the one behind the 2026 hantavirus event, which can spread person to person through close contact, understanding the network is understanding the threat. A well-designed view can convey "these cases are all linked to one source and the contacts are accounted for" — a profoundly reassuring message when it's true — far better than a list of numbers can.
But the same visualization handles real people, and here privacy is a hard design constraint, not an afterthought. The chart must convey the epidemiological structure without revealing identities — using aggregation, abstraction, and anonymization so the public learns the shape of the hantavirus outbreak without any individual becoming identifiable. This is a genuine design problem: too much detail and you violate privacy and potentially stigmatize people; too little and the visualization says nothing useful. The balance, struck well, lets the public understand the connectedness and containment of an outbreak while protecting the dignity and privacy of everyone in the network. Designing for that boundary — informative structure, invisible individuals — is one of the more ethically loaded tasks in the whole field.
Designing for Uncertainty and Change
An outbreak is a moving target, and a dashboard built as if the data were final is fundamentally dishonest. The 2026 hantavirus situation evolved over weeks — cases were confirmed, suspected cases reclassified, contacts traced, the picture continually updated — and the design has to communicate that it is a living snapshot, not a settled fact.
This means several things in practice. Every figure needs a clear timestamp and an honest label about its provisional nature, so a reader understands a hantavirus count is "what we know as of now," not a final tally. The distinction between confirmed and suspected cases must stay visible as numbers shift. And the design should set expectations about incubation and reporting lags — because a disease where symptoms can take weeks to appear means today's count understates a situation that is still unfolding, and a dashboard that doesn't convey that invites misreading. Honesty about uncertainty isn't a weakness in outbreak design; it's the core of trustworthiness. A dashboard that pretends to more certainty than exists will eventually be contradicted by reality, and each contradiction erodes the credibility the whole system depends on.
There's a deeper principle here that applies to all high-stakes data visualization: showing uncertainty honestly is more trustworthy than projecting false confidence. A hantavirus dashboard that says "these numbers are provisional and will change" earns more long-term trust than one that presents evolving estimates as fixed truth and then has to walk them back. Designing the uncertainty into the presentation — rather than hiding it for the sake of a cleaner look — is what makes a dashboard credible across the full arc of an outbreak.
Accessibility and Plain Language
Outbreak information must reach everyone, which makes accessibility and plain language non-negotiable rather than optional polish. A hantavirus dashboard that only the epidemiologically literate can parse has failed a large part of its audience precisely when clear understanding matters most. The 2026 outbreak, with exposed individuals from many countries, underscores how broad and varied the real audience for outbreak communication is.
Plain language is the foundation. Terms like "hantavirus pulmonary syndrome," "zoonotic," or "person-to-person transmission" carry precise meaning to clinicians but can confuse or frighten a general reader. A well-designed public dashboard translates the clinical into the comprehensible without dumbing it down — explaining what a hantavirus is, how exposure actually happens, and what "very low public risk" concretely means, in words a worried non-expert can absorb quickly. Layering helps: a plain-language summary on top, with technical depth available beneath for clinicians and the curious, serves both audiences from one design.
Beyond language, the usual accessibility disciplines apply with extra urgency because the stakes are health and safety. Information encoded only in color fails people who can't perceive it; a risk level shown solely as a red/green indicator must also be stated in text. The dashboard has to work on modest devices and slow connections, because an outbreak doesn't restrict itself to people with fast phones. And critical guidance — what the situation is, who's at risk — must be reachable by screen readers and assistive technology. Accessibility in outbreak design isn't a compliance checkbox; it's a determinant of whether the public actually receives information that may bear on their health, which is why it sits at the center of the responsibility rather than its margins.
The Source-Authority Problem
A final design challenge unique to this domain is establishing trust in the information itself. In an environment full of rumor and misinformation, an outbreak dashboard has to visibly signal that it is authoritative — that this hantavirus information comes from the CDC, the WHO, or another credible health authority, not from a content farm or a speculative post. Design carries much of that signal.
Clear sourcing, official identity, transparent methodology, and visible "last updated" timestamps all contribute to perceived authority. A reader encountering official numbers needs to immediately understand where they come from and how current they are, because in a fast-moving situation the provenance of a figure is part of its meaning. Design that obscures sourcing — numbers floating without attribution — invites the reader to distrust them or to mistake an unofficial estimate for an official one. The visual establishment of credibility is itself a design task, and a crucial one when the alternative sources of information are often louder, faster, and wrong.
This matters because the competition for an anxious public's attention during a hantavirus scare is fierce, and the trustworthy source is frequently not the most sensational. An official dashboard wins that competition not by being louder but by being clearly, visibly reliable — sober, sourced, current, and honest about what it doesn't yet know. The credibility has to be designed in, because it's the quality that distinguishes the signal from the noise precisely when getting that distinction right matters most.
The Epidemic Curve: Visualizing Time Honestly
One of the most recognizable outbreak visuals is the epidemic curve — cases plotted over time — and it deserves attention because it's both powerful and easy to misread. An epi curve can show whether an outbreak is growing, plateauing, or receding, which is often the single most important question the public has. For a contained, single-source event like the 2026 cluster, a well-built curve tells a reassuring story: a burst of linked cases from one exposure, not an accelerating climb.
The design subtleties are real. The choice of axis scaling can make a handful of cases look like an explosion or a blip; a sharply rising line on a zoomed-in axis manufactures alarm that the underlying data doesn't support. Binning matters too — grouping cases by day versus by week changes the visual shape entirely. And the reporting lag that affects counts also affects curves: the most recent days almost always look artificially low because cases haven't been reported yet, and a curve that doesn't flag this "right-truncation" misleads the reader into seeing a decline that may not be real. A responsible epidemic curve annotates these limitations directly, so the viewer reads the trend correctly rather than inferring a false trajectory. As with every other element, the honest version sizes and frames the visual to the truth of the situation, resisting the pull toward a more dramatic shape.
What This Teaches Beyond One Outbreak
Strip away the specifics and outbreak dashboard design is a master class in communicating high-stakes, uncertain, emotionally-charged data responsibly — a challenge that recurs far beyond public health, in everything from financial risk to climate data to safety reporting. The principles the 2026 hantavirus response illustrates generalize cleanly.
Lead with calibrated context, not raw alarm: the risk statement frames everything, and getting its register right matters more than any chart. Size the presentation to the reality, so design choices don't inflate or minimize the true situation. Treat every number as provisional and timestamped, distinguishing confirmed from suspected and being honest about lag. Map carefully, because geography implies a narrative and a careless map can manufacture a false story of spread. Visualize networks to show structure while rigorously protecting the privacy of the people within them. Make uncertainty visible rather than hiding it, because honesty about what you don't know is the foundation of lasting trust. Write in plain, accessible language so the information reaches everyone, not just experts. And establish authority visibly, because in a sea of misinformation, looking credible is part of being useful. The hantavirus outbreak of 2026 is a sober reminder that behind every clean dashboard is a set of profound design decisions, and that getting them right is, in the most literal sense, a matter of public well-being.
In the end, the goal of an outbreak dashboard is the same as the goal of all good information design, just with the stakes raised to their highest: to leave a person genuinely understanding their situation. For a hantavirus outbreak, that means understanding that a serious disease has caused real harm to a small number of people, that the risk to most of the public is very low, and that credible authorities are tracking it closely — all at once, without panic and without dismissal. Achieving that clarity, with respect for both the gravity of the disease and the people affected by it, is the quiet, essential work that outbreak visualization exists to do.