Disease Surveillance

Part of Public Health

Systematic monitoring of disease frequency and distribution in a community to detect outbreaks early, identify trends, and guide public health responses.

Why This Matters

Disease surveillance is the community’s immune system against epidemics. Without surveillance, you learn about an outbreak when it is already large and difficult to control. With surveillance, you learn about it when it is a cluster of two or three cases — while it can still be stopped by quarantine and targeted intervention.

The distinction matters enormously. A cholera outbreak detected at one household can be contained by isolating cases and treating the water source. Detected at 40 households, it has already exceeded the capacity of any community health system to contain and becomes a mass casualty event.

Modern public health surveillance systems are elaborate — laboratory confirmation, electronic reporting, complex statistical analysis. What a post-collapse community needs is simpler: a systematic process for counting cases of important diseases, comparing those numbers to baseline expectations, and recognizing when something unusual is happening. This requires organized record-keeping, a designated responsible person, and a process for acting on what the data shows.

A community that maintains even basic surveillance will detect threats weeks before one that relies on passive information flow, and those weeks may mean the difference between a contained incident and a community-destroying epidemic.

What to Surveil

Not all conditions warrant equal attention. Focus surveillance resources on diseases that are:

• Highly transmissible (one case can lead to many)
• Potentially lethal (high case-fatality rate)
• Preventable by public health intervention

Priority reportable conditions — any healthcare provider seeing these must report immediately to the public health authority:

Condition	Priority	Why
Cholera or severe watery diarrhea	Emergency	Kills within hours; explosive spread
Measles or similar rash-fever	Emergency	Highly contagious; vaccine-preventable
Bloody diarrhea	Urgent	Dysentery; indicates fecal contamination
Meningitis (stiff neck, fever, altered mental status)	Urgent	High mortality; potentially epidemic
Fever with rash	Urgent	Many causes, some very serious
Jaundice (yellow eyes/skin)	Urgent	Hepatitis, yellow fever, other liver disease
Animal bite	Urgent	Rabies prevention window is short
Unusual cluster of any illness	Urgent	May signal common source exposure
Respiratory illness cluster	Routine	Influenza or other respiratory epidemic

Routine surveillance data (collected weekly or monthly):

• All-cause mortality (how many deaths, from what age groups?)
• Diarrheal disease cases (any increase is an early warning)
• Respiratory illness cases (seasonal patterns; deviations signal outbreaks)
• Maternal deaths and infant deaths (leading indicators of overall health system performance)
• Malnutrition assessments (weight for age in children under 5)

The Surveillance Reporting System

For surveillance to work, it must be easy to use and consistently applied.

Step 1: Designate reporters: Every regular source of patient contact — the main health practitioner, traditional healers operating in the community, birth attendants — is a mandatory reporter. They must report designated conditions by the following day.

Step 2: Simple reporting forms: Create a one-page weekly tally sheet. Every reporter fills it out on the same day each week and submits it to the public health authority.

Example weekly reporting form:

Reporter name: ___________
Location: ___________
Week of: [date]

EMERGENCY CONDITIONS (report immediately, also mark here):
  Severe watery diarrhea (possible cholera): [ ] cases
  Rash with fever (possible measles): [ ] cases
  Stiff neck with fever (possible meningitis): [ ] cases

ROUTINE CONDITIONS (tally for week):
  Diarrheal disease (any): [ ] cases
  Respiratory illness: [ ] cases
  Fever (no identified source): [ ] cases
  Wound infection: [ ] cases
  Deaths this week: [ ] total | Under 5: [ ] | Under 1: [ ]

UNUSUAL OBSERVATIONS: ___________

Step 3: Aggregation and review: The public health authority receives all forms, aggregates counts, and compares to previous weeks and seasonal baselines. This review should happen weekly — not monthly, not when convenient.

Step 4: Alert thresholds: Establish in advance the counts that trigger an alert response. This removes subjective decision-making under pressure.

Alert Thresholds

An alert threshold is a predetermined trigger level at which the public health system escalates its response. Define these thresholds before an outbreak, so that response is automatic rather than deliberated.

Immediate alert (emergency response):

• Even ONE confirmed or strongly suspected case of cholera, meningococcal meningitis, or suspected hemorrhagic fever
• Any cluster of two or more deaths in a short period from similar symptoms
• Any single suspected case of a disease thought to be eliminated from the region

Urgent alert (investigation within 24 hours):

• Two or more cases of the same serious illness with no epidemiological link
• A doubling of weekly case counts for any reportable condition compared to the same season in prior years
• Any pattern suggesting a common source exposure (multiple people from the same gathering developing the same illness)

Watch (increase monitoring frequency):

• A 50% increase in any illness category without identified cause
• Reports of unusual illness from multiple reporters
• A significant death of a young, previously healthy individual from unclear cause

The Outbreak Investigation Response

When a threshold is crossed, the surveillance system transitions to outbreak investigation mode:

Step 1: Confirm the cases — verify that reported cases meet the case definition (see below).

Step 2: Establish a case definition — a set of clinical criteria that define who counts as a case of this illness. Example case definition for cholera: “Acute watery diarrhea with rapid onset of dehydration, in a person who has had diarrhea for fewer than 5 days.”

Step 3: Count all cases systematically — go beyond passive reporting; actively search for cases meeting the case definition through community interviews.

Step 4: Describe time, place, and person — when did cases start? Where are cases located (map them if possible)? Who is affected (age, sex, occupation, household)?

Step 5: Form a hypothesis about the source — what do the cases have in common? Shared water source? Shared food? A gathering they all attended? Physical proximity?

Step 6: Test the hypothesis — interview cases and matched non-cases about their exposures. Are cases significantly more likely to have the suspected exposure than non-cases?

Step 7: Implement control measures — based on the most likely transmission route, implement the most appropriate intervention: water treatment, food source removal, isolation of cases, vaccination if available.

Step 8: Document and review — record the entire investigation, its conclusions, and the effectiveness of control measures. This is how your community improves its outbreak response over time.

Baseline Data Collection

Surveillance is only useful if you have a baseline to compare against. Begin collecting data before any outbreak occurs. In the first months of your surveillance system, you are establishing baseline rates. After 6-12 months, you will have seasonal patterns and can recognize deviations.

Keep summary statistics: average weekly counts of each condition by season. Review these annually. Over years, your baseline becomes more precise and your ability to detect anomalies improves.

This baseline data is also how you measure the impact of public health interventions. If you implement a hand-washing campaign and diarrheal disease rates fall by 30% in the following months, that is evidence the intervention worked.