General field guides

Read an animal-outbreak case definition before counting cases

Use the exact case definition supplied for the disease, surveillance program, jurisdiction and period under discussion. Keep classifications and the unit counted explicit. A record moving from one category to another is not automatically another affected animal, and a surveillance label should not be substituted for an individual veterinarian’s clinical assessment.

Updated 819 words · 4 min read1 source · scope listed below
Reading the sources

This reference uses the specific documents linked in the article and listed below. Check their scope, publication dates and the statements they support.

Locate the applicable definition

Capture the issuing authority, document title, version and relevant date. Check whether the material applies to this species, population and reporting purpose. Similar category names used by two programs do not establish identical criteria.

The APHIS reportable-disease resource links surveillance case definitions and reporting material. Use the specific applicable document rather than assuming its index page defines every event. Where applicability or authority is unclear, retain the uncertainty and consult the responsible official source.

Keep the classification attributed

Record the category actually supplied by the authority or designated reporting process. Do not promote an owner’s concern into “confirmed” because a symptom resembles an article description. Likewise, retain a negative or inconclusive result within its actual scope instead of converting it into a universal absence claim.

Separate the evidence received, the classification decision and the local publication time. If the official record changes category later, retain the earlier version and the basis of the change where supplied. Do not invent the missing diagnostic rationale.

Counting question Detail required
What is counted? Animal, premises, event or another supplied unit
Under which rule? Exact definition and version
Which category? Attributed classification, including uncertainty
During what period? Relevant event and reporting intervals
What changed? New unit, updated evidence or reclassification

Avoid adding categories that overlap over time

A cumulative list of all reports may contain several versions of the same event. Match stable identifiers before summing. If identifiers are unavailable, describe the deduplication limitation rather than merging records merely because their dates and place names look similar.

Keep denominators consistent with the supplied unit. A premises count cannot be divided by an animal population and presented as an animal-level proportion. If two sources use different units or inclusion criteria, display them separately until a justified comparison is possible.

Work through a reclassified record

In this fictional example, one premises is first listed under a provisional category and later under a confirmed category. An editor combines the two weekly files and initially counts two premises. The stable event identifier shows that the second row updates the first.

The revised account contains one premises with two recorded classification states. The event date, update date and local publication date remain distinct. The example does not prescribe any real disease’s confirmation criteria; those must come from its actual official definition.

Publish the rule beside the number

State the unit, period and classification in the caption or immediate explanation, with a link to the precise definition. Do not hide a meaningful change in criteria in a distant bibliography. If a revised definition changes comparability, explain that break before presenting a trend.

Check derived summaries, maps and answer text after reclassification. A corrected table next to an unchanged total still misleads readers. Use historical outbreak interpretation and reportability resources for related tasks. A useful count tells readers exactly which records qualified, under which rule, and how later updates were handled.

Explain a symptom cluster without upgrading its status

In this fictional herd, several similar observations prompt an owner concern, and reposts call it a confirmed outbreak. The available record contains the observations but no attributed confirmation or official incident declaration. Describe the concern under assessment and link any actual authority statement with its date and scope. Do not invent probable or confirmed categories for a program that has not supplied them. Prompt appropriate care and reporting can proceed while the public explanation preserves the unresolved status.

Questions before updating a map or total

Does reclassification create another affected premises?

Match the stable identity and inspect the actual update relationship. A record can move between categories over time while still representing one premises or event. Preserve the states without summing them as independent units.

Can a local editor supply missing confirmation criteria?

Use the exact applicable definition and attributed decision. A symptom cluster or familiar result word does not authorize invented categories for a programme that has not supplied them. Seek clarification where the actual applicability remains unclear.

What if a revised definition breaks the trend?

Explain the change beside the series and preserve which rule each period used. Do not smooth over incompatible inclusion criteria to create an uninterrupted-looking comparison. The counted unit and classification need to remain visible.

In a second fictional release, a current-status map and a cumulative document table display different totals. The editor initially forces them to agree. Reviewing the units reveals that one represents current classified premises while the other contains successive accounts. Both can be useful when labeled accurately. The repair clarifies their questions and version relationships rather than changing a valid count simply to produce matching numbers.

Cite this reference

LivestockDefense. “Read an animal-outbreak case definition before counting cases.” Updated 2026-11-03. https://livestockdefense.com/guides/interpreting-a-case-definition-during-an-animal-outbreak/

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.

  1. USDA APHIS: National List of Reportable Animal Diseases

    Source update: 2026-10-05. Most recent check: 2026-10-29.

    Document scope and recorded checks

    National reporting reference; state obligations and movement permissions require separate checks. Official reporting reference and distinctions among reporting statuses; page also identifies supplementary material for a proposed rule. Not treated as a blanket statement of effective state law. The inspected national page identifies supplementary material associated with a proposed rule and separately labels its current national list; no state reporting duty, deadline or movement permission is inferred. Reporting resources, surveillance case definitions and distinction between proposed rule material and applicable requirements. The inspected national page directs readers to the applicable case definition or PDF details for entries labelled Notifiable/Monitored. It separately identifies supplementary proposed-rule material. No individual disease classification, state duty, deadline, actual 2026 naming change or movement permission was established.

    Entries retain the date and scope of each recorded inspection.

    • 2026-10-29 — The inspected national page identifies supplementary material associated with a proposed rule and separately labels its current national list; no state reporting duty, deadline or movement permission is inferred.

      Exact official documentation inspected for the bounded publication or technical statements assigned to it; no clinical verification

    • 2026-10-29 — Reporting resources, surveillance case definitions and distinction between proposed rule material and applicable requirements.

      Exact publisher page or indexed publisher text inspected for the bounded facts identified; no independent veterinary review implied

    • 2026-10-29 — The inspected national page directs readers to the applicable case definition or PDF details for entries labelled Notifiable/Monitored. It separately identifies supplementary proposed-rule material. No individual disease classification, state duty, deadline, actual 2026 naming change or movement permission was established.

      Exact official webpage inspected for the stated document-identification claims only; linked definitions were not evaluated as case instructions

    • 2026-10-28 — Official reporting reference and distinctions among reporting statuses; page also identifies supplementary material for a proposed rule. Not treated as a blanket statement of effective state law.

      Exact publisher page or its indexed text inspected; bounded summary only

Full source register ↗