Skip to content

Clinical Case Definition

Operationalize surveillance or outbreak inclusion by specifying a reproducible combination of clinical, laboratory, person, place, and time criteria, often tiered as suspected, probable, and confirmed.

Version
v2 · 2026-09-06 · History
Domain-specific #
1481
Origin domain
medicine
Subdomain
epidemiology
Aliases
Case definition, Surveillance case definition, Outbreak case definition

Core Idea

A clinical or surveillance case definition is a rule set that determines which persons count as cases for a specified public-health investigation or surveillance system. It combines some subset of symptoms, signs, laboratory evidence, epidemiologic linkage, and person-place-time restrictions. Tiered definitions commonly distinguish suspected, probable, and confirmed cases as evidentiary certainty increases.

The definition standardizes counting and comparison; it is not necessarily the same as a clinician's diagnostic judgment or treatment threshold. Outbreak definitions can be deliberately sensitive early and narrowed as knowledge improves, while routine surveillance definitions prioritize stable comparability. Every count is therefore conditional on definition version, ascertainment system, testing availability, and population scope.

Scope of Application

Case definitions are literal in outbreak investigations, notifiable-disease surveillance, registries, and epidemiologic studies.

  • Outbreak investigation. Finding related illnesses within a person-place-time envelope.
  • Routine surveillance. Producing comparable incidence and prevalence series.
  • Notifiable conditions. Standardizing reports across jurisdictions.
  • Registries. Defining eligible disease or event records.
  • Epidemiologic research. Creating reproducible outcome or exposure classifications.
  • Emergency response. Tiering cases as evidence and testing capacity evolve.

Clarity

State purpose, condition, population, geography, onset window, clinical and laboratory criteria, linkage rule, tier logic, exclusions, version date, and authority. Distinguish report date from onset date and surveillance inclusion from clinical diagnosis. When comparing counts, map definition and testing changes before attributing differences to disease occurrence.

Manages Complexity

A case definition turns heterogeneous clinical narratives into a reproducible dataset and gives distributed investigators one inclusion interface. Tiering allows action before certainty is complete. Compression necessarily misclassifies some people and can create trend breaks when criteria or test access changes; versioned metadata and sensitivity analyses keep the count from being mistaken for the underlying disease population.

Abstract Reasoning

  1. Fix the surveillance or investigation purpose.
  2. Define the target event and person-place-time envelope.
  3. Choose clinical, laboratory, and linkage evidence available in practice.
  4. Combine criteria into explicit tiers and exclusions.
  5. Pilot sensitivity, specificity, timeliness, and workload.
  6. Train reporters and monitor ascertainment consistency.
  7. Version every substantive change and preserve crosswalks.
  8. Interpret counts jointly with testing and reporting processes.

Knowledge Transfer

The strict parent is Operationalization: an abstract target condition is lowered into observable criteria and executable inclusion logic under a correctness contract. Classification is related because cases are sorted into tiers, but operationalization explains the construct-to-rule bridge.

Operationalization is the strict parent because a latent or partly theoretical target is lowered into observable indicators and an executable classification rule. The portable structure is construct + purpose + observable evidence + scope + logic -> reproducible inclusion. The domain-specific residue is clinical presentation, laboratory evidence, epidemiologic linkage, outbreak time and place, tiered certainty, and public-health ascertainment.

Relationships to Other Abstractions

Local relationship map for Clinical Case DefinitionParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Clinical CaseDefinitionDOMAINPrime abstraction: Operationalization — is a kind ofOperationalizat…PRIME

Current abstraction Clinical Case Definition Domain-specific

Parents (1) — more general patterns this builds on

  • Clinical Case Definition is a kind of Operationalization Prime

    Operationalization is the strict parent because the definition converts an intended disease/event construct into an executable rule for observation and counting.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

Clinical Case Definition sits in a sparse region of the domain-specific corpus (97th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08