EpiHack Arizona 2026 — Figures
Reference frameworks from
EpiHack Arizona (Ending Pandemics Academy · University of Arizona
Global Health Institute), converted from poster figures into structured
content suitable for ingestion into a DuckLake / DuckDB / Postgres knowledge
graph.
Figure 1 — Purpose for a One Health Participatory System
To detect the earliest signal of a potential epidemic or pandemic threat
emanating from humans, animals or the
environment by directly engaging the
community.
Figure 2 — Minimum Set of Key Data Parameters
A radial schema of the minimum data parameters for One Health
participatory surveillance, organized into eight color-coded classes.
| Legend | Category | Description |
| General | Demographic and contact attributes |
| Human | Symptoms and clinical signs |
| Severity markers | Severe-disease indicators within Human |
| Exposure | Risk-exposure events |
| Auxiliary | Supporting evidence (signals, images, lab) |
| Environmental | Environment / vector signals |
| Livestock | Domestic-animal incident attributes |
| Wildlife | Wildlife incident attributes |
General
- Age
- Sex
- Email
- Unique ID
- Occupation
- Date of report
- Postal code
- Phone number
- Household member ID
- Geographical coordinates
Human (symptoms / clinical)
- No symptoms
- Symptoms
- Date of illness
- Cough / congestion
- Nausea / vomiting
- Difficulty breathing
- Sore throat
- Rash
- Fever
- Chills
- Diarrhea
- Bleeding from body openings — severity marker
- Red eyes
- Muscle or body aches and pains
- Discolored or bloody urine — severity marker
- Loss of smell or taste
- Yellow skin / yellow eyes — severity marker
- Absent from work
- Absent from school
- Did you seek health care or treatment
Exposure
- Attending a recent mass gathering
- Tick or insect bite
- Animal bite
- History of travel
- Contact with live animals
- Contact with dead or sick animals
- Contact with sick individual / confirmed case
Auxiliary
- Digital biomarker signal
- Photo
- Diagnostic / lab confirmation
Environmental
- Date of environmental incident
- Location of vector spotting
- Unusual presence of vectors
- Density or number of vectors
- Flooding
- Water contamination
Livestock
- Date of livestock incident
- Location of livestock incident
- Number of sick animals
- Number of dead animals
- Species
Wildlife
- Date of wildlife incident
- Location of wildlife incident
- Species
- Number of dead animals
Figure 3 — Outbreak Timeliness Metrics
Timeliness metrics are the time intervals measured between two respective
outbreak milestones. Each milestone represents the date of key outbreak
activities. Milestones can apply to individual sectors or to a coordinated
One Health approach, integrating environmental, animal, and human health.
1PredictDate a reliable and valid predictive alert of a potential outbreak is available (e.g. increased rainfall leading to greater density of mosquitoes capable of disease transmission).
2PreventDate enhanced surveillance or other intervention is initiated in response to a predictive alert (e.g. mass vaccination in livestock; mosquito abatement).
3DetectDate symptom onset, death, or other evidence of pathogen circulation is observed or suspected in human(s) or animal(s).
4NotifyDate an outbreak in humans or animals is officially reported to relevant authorities (e.g. local to national; national to international; cross-sector).
5VerifyDate outbreak is confirmed by field investigation or other valid method.
6Diagnostic Test / Lab ConfirmationDate outbreak is confirmed by diagnostic or laboratory test in an epidemiologically-linked human or animal.
7RespondDate an intervention to control or manage the outbreak is initiated by a responsible authority (e.g. mass vaccination; quarantine).
8Public CommunicationDate of official release of information to the public by a responsible authority.
9Outbreak StartDate symptom onset or death occurs in the earliest epidemiologically-linked human or animal (often identified retrospectively or estimated based on available evidence).
10Outbreak EndDate outbreak is declared closed by a responsible authority.
11After Action ReviewDate after action review is jointly conducted by relevant One Health authorities.
The sequence of milestones may vary by outbreak. A single
action may represent more than one milestone. The After Action Review
milestone is included to inspire the necessary collaborations among
sectors for operationalizing One Health.
Figure 4 — Designing & Launching Participatory Surveillance
A 12-step lifecycle for designing, launching, and sustaining a
participatory surveillance system.
1Assess Needs of CommunityDesign
2Determine Purpose of SystemDesign
3Identify StakeholdersDesign
4Ascertain ResourcesDesign
6Test Prototypes & Finalize ProductBuild
9Create Awareness CampaignsOperate
10Train RecruitersOperate
11Incentivize & Retain UsersOperate
12Monitor, Evaluate & Adapt SystemOperate
Figure 5 — Worksheet: Designing a One Health Participatory Surveillance System
Breakout worksheet used at EpiHack Arizona to apply the 12-step lifecycle
to a concrete focus area. Each prompt below corresponds to one or more
steps from Figure 4.
| # | Prompt | Maps to lifecycle step |
| 1 | What is the purpose of your system? | 2 — Determine Purpose |
| 2 | Define the target population(s)? | 2 — Determine Purpose |
| 3 | What will you be giving back to the target population? (bi-directionality) | 1 — Assess Needs |
| 4 | Which parameters of the Minimum Dataset would you remove and/or add? | 5 — Co-Design |
| 5 | How will you ensure target-population access (barriers, literacy, awareness)? | 9 — Awareness |
| 6 | How frequently will participants report? | 5 — Co-Design |
| 7 | How long will a report take on average? | 5 — Co-Design |
| 8 | Who are key partners to develop, implement, promote, maintain? | 3 — Identify Stakeholders |
| 9 | How will you validate or verify the data? | 8 — Validate Data |
| 10 | 3–5 sentence elevator pitch for stakeholders. | 9 — Awareness |
Completed designs from breakout sessions
World Café Q4 — Examples of successful direct public engagement