This reference uses the specific documents linked in the article and listed below. Check their scope, publication dates and the statements they support.
Keep three dates instead of one
Record when an event occurred, when the authority reported it and when you retrieved the document. These dates can differ substantially. If an old notice is newly added to a website, its upload or retrieval date should not make the event appear current.
When the source gives only a range or an estimated onset, preserve that precision. Do not silently replace “during March” with March 1. A date field should be accompanied by a note explaining whether it represents onset, confirmation, publication or a later update.
Identify the unit being counted
An animal, a premises, a laboratory submission and a reported outbreak are different counting units. Before adding numbers, find the source’s definition and keep it with the table. Two reports can discuss the same event at different administrative levels.
WOAH’s data-collection explanation distinguishes event notifications from monitoring. The distinction matters when selecting records for a historical series. A notification is not automatically a measured rate in the whole animal population.
Preserve updates without counting them again
Create a stable event identifier and store each report version beneath it. Retain the original source URL, report identifier and the relationship between the initial and follow-up records. If a correction changes a count, show both the earlier value and the reason for using the newer one.
An illustrative archive contains one initial notice and four follow-up reports. A search returns five documents. Counting documents would produce five “outbreaks,” although the reports all concern one event. The event identifier resolves the duplication while keeping the full documentary history available.
Compare places only after checking coverage
Write down the hosts, surveillance approach, reporting period and geographic boundaries used in each source. If the boundaries or methods changed, flag the break in the series. A higher count after expanded testing may reflect improved detection, a real increase, or both; the count alone cannot separate those explanations.
| Comparison question | Information needed |
|---|---|
| Same disease concept? | Name, agent where relevant and case definition |
| Same population? | Species, production group and area covered |
| Same time basis? | Onset period versus notification period |
| Same unit? | Animals, holdings, submissions or events |
| Same reporting opportunity? | Known changes in surveillance or submission |
Do not turn a blank cell into zero. Use the source’s own absence or missing-information category, and preserve any definition supplied with it.
Write a bounded historical statement
A defensible sentence names its source, period and unit: “The authority’s archived reports list three premises for the stated period.” It does not automatically become “three farms are infected now,” “the area is safe,” or a probability of disease on a particular holding.
Before publishing a map, check that location precision is justified and does not disclose private premises unnecessarily. Save the query or extraction method alongside the output so another reader can reproduce the selection. Use the history reference for archive structure and the prevalence guide when the intended statement involves a rate rather than a list of reports.
Propagate a correction through derived summaries
In this fictional publication, an authority corrects one event record and the revised value affects a monthly total, a map label and a short answer. Link the correction to the stable event identifier, then check all three outputs against the revised source version. Preserve the earlier report and note which released version used it. A corrected chart beside an unchanged answer still presents two incompatible accounts. Do not describe the correction itself as a new event, and retain any official explanation of the change without inventing a cause.
Compare map editions before interpreting a missing marker
In a fictional archive, a marker appears in one saved map and is absent from the next. The second view uses a different reporting-period filter, while the underlying event record remains available. The missing marker does not establish that the event never existed or that the authority withdrew its account.
Retain the source edition, selected period, category filters and extraction date with each map. Compare event identifiers and any documented correction before explaining a display change. A screenshot without those settings may preserve the appearance while losing the reason two views differ. Do not invent a cause for the change when the source does not supply one.
Cite this reference
LivestockDefense. “Read historical animal-disease records in context.” Updated 2026-10-30. https://livestockdefense.com/guides/using-historical-outbreak-data-responsibly/
Add the date you accessed the page. This identifies the current reference; keep a permitted saved copy if your work depends on its exact wording. A citation alone does not establish support for a claim.
How to cite a page and its revision ↗Sources & boundaries
Read the evidence in context.
These documents support the statements identified in this reference. Check their scope and dates when deciding whether they answer your question.
- World Organisation for Animal Health: Disease Data Collection
Source update: Not provided. Most recent check: 2026-10-28.
WAHIS distinguishes event reporting and monitoring; official records include species, geography, tests and control measures. No event-count inference of prevalence.