What to Build 

Your solution should be concrete and usable, even if it’s early-stage. It can be an app, dashboard, predictive model, decision support tool, policy playbook or anything creative.
The goal is to demonstrate that your idea could work in the hands of clinicians, patients, operators, or policymakers if developed further. At minimum, your build should have two or more of the following:

• User-facing component — a dashboard, app, or interface that makes insights actionable.

• Data integration layer — one or more real-world datasets (climate, health, operations, etc.) clearly connected to the problem you’re solving.

• Analytics or intelligence — rules, models, or algorithms that transform raw data into useful signals.

• Impact framing — a way to show who benefits (patients, providers, facilities, communities) and how you’ll measure success (fewer ER visits, lower downtime, $/ton CO₂ saved, etc.).

• Scalability & governance plan — how it could plug into workflows while respecting privacy, compliance, and equity.

👉 Example (for illustration only):
A team building for Extreme Heat might submit a simple surge forecasting dashboard. It could pull weather + de-identified ER admissions, predict likely increases in heat-related cases, and recommend actions (e.g., staff shift alerts, open cooling centers). The interface might be a web app with an interactive chart and SMS alerts.

What to Submit

One submission per team.

• Repo link to include install/run steps.

• Solution demo video (≤3 min) to explain how your solution solves a problem.

• OPTIONAL - One-pager

  • Problem & users, data sources used, model/approach, and deployment plan.

  • Impact metrics (e.g., predicted ED visits avoided, downtime hours saved, $/ton CO₂e reduced).

  • Data governance (de-identification, PHI handling, licenses/ToS, model card, fairness checks).