Reporting question
Public data product · Public product
PopHealth Data Portal
I built a public portal to make population-health data easier to find, inspect, and reuse during community health assessment and planning.
- Data integration
- JavaScript
- Public APIs
- Supabase
- My role
- Product owner & developer
- Audience
- Population-health & policy teams
- Data
- Public agency datasets & APIs
- Delivery
- Public data directory & tables
Practical value
Brings indicator discovery, source links, and available county tables into one public product.
Working product
Explore the public product.
Purpose & ownership
The reporting need.
During the Community Health Needs Assessment process, finding the right indicator often meant repeating searches across agency sites, definitions, and downloads.
The portal brings indicator discovery, source links, and available county tables into one place. It is publicly accessible and supports data collection beyond the original CHNA workflow.
Technical approach
What I built.
- 01
Organize the evidence
Group indicators by health topic and geography. Preserve source links and metadata so readers can check where a figure came from.
- 02
Normalize the data
Use source-specific retrieval and extraction routines to prepare available county-level rows in a consistent format.
- 03
Separate refresh from use
Cache prepared data in Supabase. Public table reads use the cache instead of requesting every upstream source for each visitor.
- 04
Support reuse
Build source navigation and data views around how analysts collect evidence for assessments, reports, and policy review.
Quality & interpretation
How I check it.
- Test source retrieval and extraction paths.
- Check geographic coverage and indicator metadata.
- Test cache-only public reads and authenticated workspace boundaries.
- Review source freshness and availability.