Q4 — How can wildlife diseases be better tracked using Participatory Surveillance?

How can wildlife diseases be better tracked using Participatory Surveillance?

A draft design that applies the 12-step lifecycle and the worksheet template to wildlife and vector-borne disease in Arizona.

1. Purpose

Capture community reports of (a) sick or dead wildlife, (b) unusual vector abundance or biting activity, and (c) suspected zoonotic exposures, and fuse them with AZGFD wildlife-health data, ADHS zoonotic case data, and NEON longitudinal ecological data to shorten the Detect → Verify interval for spillover events.

2. Target populations

3. What we give back (bi-directionality)

4. Parameters (delta vs. Minimum Dataset)

Keep: date of incident, geographical coordinates, species, number of sick/dead animals, photo, contact-with-animal exposure parameters.

Add for this focus:

De-emphasize: human clinical-symptom parameters (handled in human surveillance designs).

5. Access

6. Frequency

“See something, report something.” No required cadence — but a monthly nudge to active reporters keeps engagement.

7. Time per report

~2 minutes for a photo + tap-through; up to 10 minutes for a structured mortality investigation by a power user.

8. Key partners

9. Validation

10. Elevator pitch

Arizona’s wildlife and vector surveillance lives in silos — AZGFD watches game, ADHS watches arboviruses, NEON watches the ecology, and the people closest to the land have nowhere to send what they see. We are building a participatory-surveillance front door for wildlife and vector-borne disease in Arizona that lets hunters, hikers, ranchers, tribal members, and rehabbers report sick or dead wildlife and unusual vector activity in two minutes, routes the report to the right agency, and gives the community back a live map of what is happening in their county. Built on the One Health Minimum Dataset and a DuckLake knowledge graph that fuses agency, research, and community data.

See also