Health & public health
OutbreakX
Map, inspect, and export disease reports in one geospatial workspace.
- Status
- Working product
- My role
- Full-stack and geospatial engineering
- Timeframe
- 2026
- Core technology
- React · FastAPI · PostGIS · Leaflet
01 / Context
The problem
Fragmented spreadsheets and manual maps make outbreak reporting difficult to validate, combine, and inspect spatially.
02 / Product
The implemented solution
OutbreakX centralizes case ingestion and geospatial exploration, with disease summaries, map markers, saved zones, location tools, and interoperable exports.
03 / System
Architecture, in plain language
FastAPI validates and persists georeferenced reports in PostgreSQL/PostGIS. A React and Leaflet client queries spatial records and renders interactive OpenStreetMap layers.
04 / Judgment
Important decisions
- Validated import rows before persistence so data-quality failures remain visible and recoverable.
- Used PostGIS rather than encoding geography as ordinary text fields.
- Kept the AI assistant informational and contextual instead of allowing it to alter surveillance records.
05 / Boundaries
Limitations and next work
The platform depends on the completeness and accuracy of imported reports. Its assistant is informational and must not be treated as medical or epidemiological advice.
06 / Implementation
Focused technology
React · FastAPI · PostGIS · Leaflet · SQLAlchemy · Gemini