General field guides

Read a WOAH disease reference without creating a local outbreak claim

A WOAH disease entry or chapter reference identifies an international reference topic; it does not establish an outbreak in a particular county. Preserve the exact document, edition and meaning of the code or identifier. A local occurrence claim needs its own dated evidence for the relevant place, population and event.

Updated 809 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.

Identify what the identifier actually names

Keep the surrounding title and document type with the code. A Code chapter, Manual chapter, database identifier and local event reference may use different numbering systems. Do not join records solely because two short identifiers look alike.

WOAH’s disease portal explains that listed diseases are adopted under Chapter 1.3 of the terrestrial or aquatic Codes. It also hosts additional nonlisted disease resources. Presence in the portal therefore should not be converted automatically into a claim that every topic has the same listing status.

Preserve the edition and supplied name

Record the document edition, relevant date and exact disease or agent wording. A renamed entry or moved chapter can change a reference link without creating a new biological event. Retain old-to-new mappings only when the source supports them.

If a database uses a shortened label, link it back to the full official entry. Keep uncertainty visible where a local term could refer to more than one condition. An editorial convenience should not create a false scientific identity or reportability conclusion.

Reference layer Evidence required
International topic Exact entry, document and edition
Listing status Actual supplied status and applicable version
Local event Dated authority record for that place
Local legal duty Applicable authority and jurisdiction
Site mapping Attributed relationship and unresolved ambiguity

Keep occurrence records in a separate stream

For a local claim, preserve the issuing authority, event identifier, location scope and relevant dates. A country-level statement should not become a county-level pin unless the source actually supplies that detail. Likewise, an historical occurrence should not be displayed as a current alert.

Do not use the absence of a local record in one consulted dataset as proof of freedom. State the dataset and period reviewed and its limitations. A reference article can explain a disease while making no assertion that it is present locally.

Work through a misleading map import

In this fictional data import, a disease reference is assigned to every county because each county page shares the same topic code. The mapping produces apparent outbreak markers without any event records. The code relationship describes topical relevance, not occurrence.

The correction keeps the reference links while removing the unsupported event interpretation. Any actual occurrence layer is built only from its own official records and dates. The example establishes no real jurisdiction’s status or reporting requirement.

Make the public distinction visible

Use labels such as reference topic, historical event or current official notice according to the evidence. Put the relevant scope and date beside the claim rather than relying on a distant general disclaimer. Check maps, answer text and download fields for the same interpretation.

When the official reference changes, update topic mappings without rewriting the event history. A later document edition does not change what an earlier notice said. Preserve both relationships so readers can follow the record.

Use reportability guidance, regional status interpretation and the Threat Atlas. A useful code explanation tells readers what the identifier names and what additional evidence is required before making a claim about their own locality.

Keep reference maintenance separate from occurrence updates

A changed chapter link or preferred topic name can require navigation and mapping repairs without establishing any new animal event. Record what changed in the reference document and preserve the event stream separately. A current edition describes the reference used now; an older official notice retains its actual wording and date.

In a second fictional catalogue, a topic identifier is reused as a field in both the reference table and event table. An import joins every reference topic to every locality page, creating apparent local records. Giving the entities separate identities and requiring actual event evidence for occurrence removes the unsupported map layer while retaining useful topic navigation.

Frequently asked questions

Does a WOAH reference establish local reportability?

Keep the international document's stated topic and listing scope separate from the applicable jurisdiction's legal or authority question. Use the responsible current source for that actual decision.

Does no matching local record prove freedom?

State which dataset and period were reviewed and retain its limitations. A missing match should not become a universal absence conclusion. A reference article may accurately explain a topic while making no local occurrence claim.

What should the reader see beside a code?

Give the document type, edition, supplied name and a readable explanation of what the identifier denotes. If a separate event is discussed, identify its actual dated source and geographic scope. That makes the distinction usable without requiring readers to infer whether a number is a chapter, topic or incident identifier.

Cite this reference

LivestockDefense. “Read a WOAH disease reference without creating a local outbreak claim.” Updated 2026-11-03. https://livestockdefense.com/guides/explaining-a-woah-disease-code-without-claiming-current-local-presence/

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. World Organisation for Animal Health: Animal diseases

    Source update: Not provided. Most recent check: 2026-10-29.

    Disease portal coverage and distinction between listed diseases and additional resources; not a local occurrence determination. Portal distinguishes listed diseases under Code chapter1.3 from additional nonlisted resources; a listing or chapter reference is not a local occurrence record.

Full source register ↗