Designing Case Definitions for Veterinary Surveillance

By Dr. Zubair Khalid, DVM, MS, PhD · 2026-08-11

Key Takeaways

• Case definitions are epidemiological tools, not diagnostic protocols, requiring explicit criteria for classifying an animal, group, or sample as a case to ensure data interpretability and comparability across time and location, aligning with WOAH standards.
• The structure of a case definition is dictated by the surveillance objective (e.g., early detection requires high sensitivity, prevalence estimation requires high specificity) and must clearly define the unit of interest (individual animal, herd, or epidemiological unit).
• A comprehensive case definition integrates clinical signs (e.g., respiratory distress, fever thresholds), laboratory criteria (e.g., specific RT-PCR, ELISA results, sample types), epidemiological links, and temporal/spatial constraints to ensure operational clarity and repeatability.
• Validation against a reference standard (e.g., definitive laboratory test, expert panel) is crucial to estimate sensitivity, specificity, and predictive values, with a deliberate trade-off between sensitivity and specificity determined by the consequences of misclassification (e.g., missing a novel zoonosis vs. costly trade restrictions).
• Hierarchical case classifications (suspected, probable, confirmed) facilitate early detection using clinical or syndromic criteria while reserving confirmed status for definitive laboratory evidence, enabling real-time tracking and robust official reporting.
• Case definitions must be documented with version control, regularly reviewed and updated to reflect changes in diagnostic technology, disease epidemiology, or surveillance objectives, and supported by standardized data capture forms to ensure data quality and consistency.

A case definition is the set of standardized criteria used to decide whether an animal, a group of animals, or a biological sample is counted as a case in a surveillance system. This article provides a structured approach to developing and validating case definitions for veterinary surveillance, covering clinical, laboratory, and syndromic criteria across species. It is written for veterinary researchers, epidemiologists, and postgraduate students who design surveillance programs, analyze surveillance data, or interpret findings for disease control decisions. The central question addressed is how to construct a case definition that is repeatable, fit for purpose, and transparent about its limitations.

Surveillance data are only as interpretable as the case definitions that generate them. A poorly specified definition produces counts that cannot be compared across time or place, and it undermines the detection of emerging disease events. The WOAH animal health surveillance standards require member countries to report diseases using agreed case criteria, and the WOAH terrestrial animal health code provides the international framework within which those criteria operate. National veterinary services and research groups must therefore translate these international standards into operational definitions suited to local contexts, available diagnostic capacity, and the specific objectives of each surveillance system.

At a Glance

Conceptual Foundations of Case Definitions

A case definition is not a diagnostic protocol. It is an epidemiological instrument that classifies observations into a binary outcome, case or non-case, according to explicit rules. The same disease may require different definitions for different purposes. An outbreak detection system needs high sensitivity to catch early cases, whereas a prevalence survey needs high specificity to avoid inflating estimates. The CDC principles of epidemiology in public health practice describe this distinction in human surveillance, and the same logic applies directly to animal populations.

The definition must state the unit of interest. In production animal systems the unit is often the herd or flock, not the individual animal. A herd-level definition might count a herd as positive when at least one animal meets the clinical criteria, or when a specified number of animals test positive. Individual-level definitions suit companion animal surveillance and wildlife disease monitoring. The choice of unit changes the sensitivity and specificity of the system and affects how data can be aggregated for reporting.

Components of a Case Definition

A complete case definition contains five components: clinical criteria, laboratory criteria, epidemiological criteria, temporal constraints, and spatial constraints. Clinical criteria describe the signs, lesions, or history that qualify an animal. Laboratory criteria specify the tests, sample types, and interpretive thresholds. Epidemiological criteria capture links to confirmed cases, common exposures, or known risk factors. Temporal constraints define the period within which signs or test results are considered relevant. Spatial constraints limit the definition to a geographic area or production system.

Each component must be written in operational language. A phrase such as "respiratory distress" is insufficient unless the definition states how distress is recognized, by whom, and under what conditions. The MSD Veterinary Manual professional edition provides species-specific descriptions of clinical signs that can anchor these criteria, but the case definition must go further and specify measurement methods, such as respiratory rate thresholds or auscultation findings.

Classification Structures and Their Rationale

Surveillance case definitions commonly use a three-tier classification: suspected, probable, and confirmed. Suspected cases meet clinical or epidemiological criteria alone. Probable cases meet clinical criteria plus either epidemiological linkage or a non-definitive laboratory result. Confirmed cases meet laboratory criteria that provide definitive evidence of the agent, antigen, nucleic acid, or a validated serological response. This hierarchy allows a system to track suspect events in real time while reserving the confirmed category for cases that meet the highest evidentiary standard.

The tier structure serves two functions. It permits early detection because clinical and syndromic criteria can be applied at the point of care, and it preserves data quality because only confirmed cases are used for official reporting. The WOAH terrestrial animal health code specifies which laboratory tests are acceptable for confirmation of listed diseases, and national reference laboratories usually publish their own interpretive criteria. A case definition that cites these sources is more defensible than one that relies on unpublished local thresholds.

Syndromic Case Definitions

Syndromic surveillance uses case definitions based on clinical presentations instead of confirmed diagnoses. These definitions are deliberately broad. They capture conditions such as acute febrile illness, sudden death, or neonatal diarrhea without requiring a specific aetiological diagnosis. Syndromic definitions are valuable for early warning because they can be applied by non-specialist personnel and do not depend on laboratory turnaround times. Their weakness is low specificity, which generates many false positives that must be investigated.

A syndromic definition must specify the signs that constitute the syndrome, the minimum duration, and the population at risk. For example, a definition of acute respiratory syndrome in cattle might require coughing, nasal discharge, and elevated respiratory rate in at least two animals within a 48-hour period. The thresholds should be derived from baseline data for the target population so that normal variation is not counted as an event.

Validation Logic

Validation of a case definition requires comparison against a reference standard. The reference standard may be a definitive laboratory test, a combination of tests, or a panel of expert clinicians who review full case data. The validation process estimates sensitivity, the proportion of true cases detected by the definition, and specificity, the proportion of non-cases correctly excluded. Predictive values depend on prevalence and must be reported for the population in which the definition will be used.

The CDC principles of epidemiology in public health practice provide the standard framework for evaluating screening and surveillance tests, and the same measures apply to case definitions. Validation should also assess repeatability, the consistency of classification when the same case data are reviewed by different observers or on different occasions. Poor repeatability usually indicates ambiguous criteria that need rewording.

Trade-offs in Definition Design

The choice between sensitivity and specificity is a policy decision, not a statistical one. A surveillance system designed to detect a novel zoonosis in a wildlife reservoir should favour sensitivity, accepting that many false alarms will require follow-up. A system designed to certify freedom from disease for trade purposes must favour specificity, because a false positive triggers costly movement restrictions and quarantine actions. The WOAH animal health surveillance standards describe the obligations that follow from these choices, including the need to document the performance characteriztics of the definitions used.

Definitions should be reviewed periodically. Changes in diagnostic technology, vaccine availability, or disease epidemiology can render an existing definition obsolete. Each revision must be versioned and dated so that historical data can be interpreted correctly. A surveillance system that changes its case definition without documenting the change produces a break in the time series that can be mistaken for a true change in disease occurrence.

Operationalising a Case Definition in the Field

A case definition is only useful if it can be applied consistently by different observers under field conditions. The first operational decision is whether the definition will be applied prospectively, retrospectively, or both. Prospective application supports early detection and outbreak response, while retrospective application supports descriptive epidemiology and trend analysis. The same definition rarely serves both purposes equally well, and the surveillance objective should determine which mode takes priority.

The second decision concerns the unit of interest. Most veterinary case definitions apply to individual animals, but some surveillance objectives require definitions at the herd, flock, or premises level. A herd-level definition might specify a minimum number of animals meeting the clinical criteria within a defined period, or a single laboratory-confirmed case in a susceptible population. The WOAH terrestrial animal health standards distinguish between infection, clinical disease, and notification events, and these distinctions matter when the case definition determines reporting obligations.

The third decision is the data source. Definitions applied to passive surveillance data must rely on information that is routinely recorded during clinical consultations. Definitions applied to active surveillance can demand more detailed or standardized data collection. If the required data elements are not already captured in the practice management system or national database, the definition will generate incomplete records regardless of its intrinsic validity.

The Diagnostic Sequence and Decision Points

Applying a case definition in practice follows a structured sequence. The clinician first determines whether the animal meets the clinical criteria. If the clinical criteria are met, the case is classified as suspected or probable depending on the definition structure. Laboratory testing is then performed where available and appropriate, and the result determines whether the case is reclassified as confirmed.

Each step in this sequence has explicit decision points. The first is the threshold for clinical suspicion. A syndromic definition might require fever and respiratory signs, but the clinician must decide what constitutes fever in the target species and what respiratory signs are sufficiently specific. The MSD Veterinary Manual provides species-specific reference ranges and clinical descriptions that support these decisions, but the case definition itself should state the threshold explicitly instead of relying on the clinician's judgment.

The second decision point is the laboratory test and specimen type. The case definition should specify the preferred specimen, the timing of collection relative to clinical onset, and the test method. Where multiple tests are available, the definition should indicate whether any positive result confirms the case or whether a specific combination is required. The CDC principles of epidemiology in public health practice describe the distinction between screening and confirmatory tests, and this distinction should be reflected in the case definition's laboratory criteria.

The third decision point is the handling of discordant results. A clinically suspect animal with a negative laboratory result may be a false negative, a case of a different disease, or a true negative. The case definition should specify how such animals are classified, whether they remain as suspected cases, are reclassified as non-cases, or are subjected to repeat testing. Without this specification, the surveillance system will accumulate an indeterminate category that complicates analysis.

Species and Production System Modifications

The correct case definition varies with species, production system, and available diagnostic capacity. In companion animal practice, individual animal records are detailed and laboratory access is often immediate. Case definitions can therefore include specific laboratory criteria without imposing an unacceptable burden. In extensive livestock production, laboratory access may be delayed or absent, and case definitions must rely more heavily on clinical and epidemiological criteria. The WOAH terrestrial animal health code provides guidance on surveillance for trade-related diseases that recognizes these constraints.

Production system also affects the feasibility of certain criteria. A case definition requiring individual animal examination is impractical in a commercial broiler flock where the unit of observation is the flock instead of the bird. Similarly, a definition requiring serial sampling is feasible in a housed dairy herd but not in a transhumant pastoral system. The surveillance objective must be reconciled with the operational reality of the production system, and the case definition should be adjusted accordingly.

Patient status matters as well. A case definition developed for clinical disease may not capture subclinical infection, which is epidemiologically important in diseases such as bovine tuberculosis or porcine reproductive and respiratory syndrome. Where subclinical infection is the target, the case definition must incorporate laboratory testing of apparently healthy animals, and the sampling strategy must be specified in the surveillance protocol.

Documentation and Data Capture

The case definition should be accompanied by a standardized data capture form or electronic record template. The form should include the unique animal or premises identifier, the date of examination, the clinical signs observed, the laboratory tests performed and results, and the final case classification. Free-text fields should be minimized, and each data element should have a defined value set.

The documentation protocol should specify who completes each data element and when. The clinician completes the clinical criteria at the time of examination. The laboratory completes the test result when available. The surveillance coordinator or data manager updates the case classification when all results are received. Clear assignment of responsibility prevents gaps in the record.

Data quality should be monitored continuously. The AVMA practice resources emphasize the importance of accurate medical records for both clinical care and secondary uses such as surveillance. Completeness of the identifier field, timeliness of result entry, and consistency of classification should be reviewed at regular intervals. Where data quality is poor, the case definition may need simplification or additional training for data contributors.

Worked Example: Constructing a Definition for a Novel Respiratory Syndrome

Consider the task of constructing a case definition for a novel respiratory syndrome of unknown aetiology in cattle. The surveillance objective is early detection of emerging disease, so the definition should favour sensitivity over specificity in its clinical component.

The suspected case definition might require acute onset of fever and at least two of the following: nasal discharge, cough, dyspnoea, or reduced feed intake. The probable case definition might add a negative result for known respiratory pathogens. The confirmed case definition would require detection of the novel agent by a validated laboratory method, once such a method exists.

This structure allows the surveillance system to function before the aetiology is known. The suspected definition captures clinically compatible cases. The probable definition narrows the population for further investigation. The confirmed definition becomes available once laboratory capacity is developed. The Global Burden of Disease study methods demonstrate the value of standardized case definitions applied consistently across locations and time periods, and the same principle applies at the scale of a national veterinary surveillance system.

The definition should be reviewed at predetermined intervals, for example every six months during an emerging disease event. The review should assess whether the clinical criteria are capturing the expected case population, whether the laboratory criteria are achievable in practice, and whether the classification structure remains fit for purpose. Definitions are working tools, not fixed documents, and they should evolve as understanding of the disease improves.

Recognized Failure Modes and Early Detection

Case definitions fail in predictable ways, and most failures become visible only after data collection has begun. The most common failure mode is definition drift, where field staff apply progressively broader or narrower interpretations over time. Drift is detected by periodic re-testing of a sample of recorded cases against the original definition, and by monitoring the ratio of confirmed to suspected cases across reporting periods. A steady decline in that ratio often signals that the clinical criteria are being applied too liberally.

A second failure mode is misclassification between the case definition and the diagnostic test used for confirmation. When the laboratory test becomes the de facto case definition, the surveillance system loses sensitivity for cases that resolve before sampling or that present atypically. Early detection relies on comparing the number of laboratory-confirmed cases with the number of clinically compatible cases that were never sampled. A large gap indicates that the surveillance system is capturing only a fraction of true cases.

A third failure mode is temporal or geographic clustering of false positives. This occurs when a single clinician, clinic, or laboratory adopts an idiosyncratic interpretation of a criterion. Monitoring case counts stratified by reporting source will reveal such clusters. The discriminating check is to re-examine the original records for a sample of cases from the suspect source against the written definition.

A fourth failure mode is the use of a definition that is too complex for the data capture system in use. Definitions with many conditional criteria generate incomplete records because field staff omit fields they consider irrelevant. Early detection comes from reviewing the completeness of each data field in the case record, also the final classification.

Common Errors and Corrective Action

Less experienced clinicians often confuse the case definition with a diagnostic algorithm. A case definition is a standardized classification rule for surveillance, whereas a diagnostic algorithm is a clinical pathway for individual patient management. The corrective action is to keep the two documents separate and to state explicitly that the case definition does not replace clinical judgment.

A second common error is selecting criteria that are easy to measure instead of criteria that are fit for purpose. For example, using pyrexia as the sole clinical criterion because temperature is routinely recorded will produce a case definition with poor specificity for most pathogens. The corrective action is to return to the stated surveillance objective and to select criteria that reflect the biology of the target condition, not the convenience of the data source.

A third error is failing to define the population at risk precisely. A case definition that specifies clinical signs but not the species, age class, vaccination status, or production type will generate denominators that cannot be interpreted. The corrective action is to specify the target population in the definition itself, not in a separate protocol that may not be read.

A fourth error is treating the definition as fixed once validation is complete. Definitions require periodic review because the underlying disease may change, diagnostic tests may improve, or the surveillance objective may shift. The corrective action is to schedule a formal review at a defined interval and to document the rationale for any revision.

Limitations of the Evidence and Areas of Expert Disagreement

The evidence base for veterinary case definition design is thinner than for human surveillance. Much of the methodological literature derives from public health practice, and the CDC principles of epidemiology in public health practice describe frameworks developed for human populations. Veterinary applications require adaptation because of species diversity, production system variation, and the absence of standardized clinical coding in many settings.

Expert opinion differs on the appropriate balance between sensitivity and specificity for surveillance versus clinical purposes. Some authorities argue that surveillance definitions should favour sensitivity to avoid missing emerging threats, while others contend that low specificity generates an unacceptable burden of false alarms and follow-up investigations. The WOAH animal health surveillance standards emphasize the need for definitions that are fit for the stated purpose, but they do not prescribe a universal sensitivity threshold.

Disagreement also exists on the role of laboratory confirmation in case definitions. Some surveillance programs require laboratory confirmation for all reported cases, while others accept clinically compatible cases during outbreaks when laboratory capacity is overwhelmed. The WOAH terrestrial animal health code provides reporting standards that distinguish between suspected and confirmed cases, but the operational threshold for confirmation remains a matter of program-level judgment.

Referral, Consultation, and Regulatory Reporting

Referral to a specialist or laboratory is warranted when the case definition produces an unexpected classification, when clinical signs are ambiguous, or when the condition has trade or public health implications. Laboratory involvement is required when the case definition includes a laboratory criterion and the submitting practice lacks the capacity to perform the test. Consultation with an epidemiologist is appropriate when the case definition is being applied across multiple sites and consistency cannot be maintained.

Regulatory reporting obligations are triggered by the detection of notifiable diseases, regardless of whether the case meets the surveillance case definition. The surveillance definition and the statutory notification criteria are separate constructs, and a case that fails the surveillance definition may still be notifiable. Clinicians should consult the relevant WOAH animal health surveillance standards and national veterinary authorities to determine which conditions require reporting in their jurisdiction. When in doubt, report the case and seek guidance from the competent authority.

Frequently Asked Questions

How Do I Choose a Case Definition When Laboratory Confirmation Is Unavailable or Delayed?

Use a hierarchical approach. A clinical or syndromic definition should serve as the primary working case definition, with laboratory confirmation reserved for a subset of cases or for initial validation of the clinical criteria. Document the proportion of clinical cases that later receive laboratory confirmation, and report surveillance outputs using both the clinical and laboratory-confirmed counts. This dual reporting preserves sensitivity while allowing specificity to be assessed retrospectively. When laboratory access is intermittent, stratify results by diagnostic confidence and note the testing gap in the surveillance report. The WOAH animal health surveillance standards describe reporting frameworks that accommodate varying levels of diagnostic certainty.

What Is the Minimum Data Set I Should Record for Each Case?

Record the case identifier, species, breed, age, sex, geographic location, date of onset, date of reporting, and the specific criteria from the case definition that were met. Include the person who made the diagnosis and the diagnostic methods used. For syndromic definitions, record the clinical signs observed and their duration. For laboratory-confirmed cases, record the test type, sample matrix, and result. This minimum data set supports verification, deduplication, and trend analysis. The CDC principles of epidemiology in public health practice provide a framework for organizing surveillance data that applies across species and settings.

How Should I Handle Cases That Meet Only Part of the Case Definition?

Classify them explicitly as suspected or probable cases instead of excluding them silently. Record which criteria were met and which were absent. This partial classification preserves information for later re-analysis if the case definition is revised. In outbreak situations, partial cases may warrant enhanced monitoring or repeat sampling. In routine surveillance, they contribute to sensitivity estimates and help identify definition components that are poorly predictive. Maintain a separate category for cases that fail the definition but are clinically suspicious, and review this category periodically to detect emerging presentations that the current definition misses.

How Do I Adapt a Case Definition Developed for One Species to Another Species?

Start by mapping the clinical signs and laboratory parameters to the target species, then validate each component against species-specific reference ranges and disease presentations. Some criteria transfer directly, while others require substitution. For example, a respiratory rate threshold developed for cattle may not suit small ruminants or poultry. Consult species-specific references such as the MSD Veterinary Manual for normal physiological values and common differential diagnoses. Pilot-test the adapted definition on a small sample of known cases and non-cases before full deployment, and document all modifications so that comparisons across species remain interpretable.

How Do I Explain a Case Definition to a Client or a Non-Epidemiologist Supervisor?

Frame the definition as a standardized checklist that ensures consistent recognition and reporting. Explain that it reduces variability between observers and allows fair comparison of disease frequency over time and between locations. Use a concrete example from the species they work with, and emphasize that the definition is a screening tool, not a final diagnosis. Clarify that some cases will be missed and some will be false positives, and that this trade-off is intentional. The AVMA practice resources offer communication guidance that can be adapted for explaining surveillance concepts to practice teams and clients.

How Do I Budget for Case Definition Implementation in a Resource-Limited Setting?

Prioritize the criteria that are cheapest and most repeatable, and reserve expensive or specialised tests for a sampling subset. A purely clinical definition may be the only feasible option initially, but it should be validated against laboratory results whenever possible. Estimate the cost per case for data collection, sample submission, and follow-up, and compare this with the cost of missing cases. Consider whether passive reporting can be supplemented with periodic active surveillance sweeps. The WOAH terrestrial animal health code provides guidance on surveillance design that can be scaled to available resources.

Related Clinical & Scientific Guides

• Evaluating Veterinary Surveillance System Attributes
• Network Analysis for Infectious Disease Spread in Animal Populations
• Randomized Controlled Trials in Veterinary Field Settings

References and Further Reading

• Global, regional, and national age-sex-specific mortality for 282 causes of death in 195 countries and territories, 1980-2017: a systematic analysis for the Global Burden of Disease Study 2017.. 2018.
• Global, regional, and national age-sex specific mortality for 264 causes of death, 1980-2016: a systematic analysis for the Global Burden of Disease Study 2016.. 2017.
• Attributable deaths and disability-adjusted life-years caused by infections with antibiotic-resistant bacteria in the EU and the European Economic Area in 2015: a population-level modeling analysis.. 2019.
• Global, regional, and national deaths, prevalence, disability-adjusted life years, and years lived with disability for chronic obstructive pulmonary disease and asthma, 1990-2015: a systematic analysis for the Global Burden of Disease Study 2015.. 2017.
• Global, regional, and national comparative risk assessment of 84 behavioral, environmental and occupational, and metabolic risks or clusters of risks, 1990-2016: a systematic analysis for the Global Burden of Disease Study 2016.. 2017.
• WOAH Animal Health Surveillance Standards. WOAH.
• CDC Principles of Epidemiology in Public Health Practice. CDC.
• MSD Veterinary Manual, Professional Edition. MSD Veterinary Manual.
• American Veterinary Medical Association Practice Resources. American Veterinary Medical Association.

Related Articles

• Data Quality Assurance in Veterinary Surveillance Systems
• Designing and Implementing Animal Disease Surveillance Systems
• Designing Participatory Disease Surveillance in Livestock Systems
• Syndromic Surveillance in Veterinary Practice
• Risk-Based Surveillance in Animal Health

This article is educational professional reference material for veterinary audiences. It is not a substitute for veterinary diagnosis, individual clinical judgment, current product labeling, or applicable regulatory requirements.