Explore 12 evidence-grounded Virginia app concepts across public health, climate resilience, rural access, school services, accessibility, and civic operations. Compare feasibility before committing months of development time.
Truthful positioning: these are project concepts—not claims that 12 completed AI systems already exist. The student should select one concept and implement a functioning, explainable product.
The strongest CAC idea is not necessarily the most complex one. It is the idea the student can explain, implement, test, and demonstrate confidently.
These are not five versions of the same app. Each emphasizes a different judging strength and student skill profile.
Every card identifies a primary user, demonstrable MVP, realistic data source, optional AI role, build window, and main implementation risk.
The original prototype mixed unrelated metrics and invented chart values. This revision uses a small set of clearly defined, source-linked facts instead.
Virginia has 95 counties and 38 independent cities. This administrative structure supports ideas that help residents find the correct local office, health district, or service boundary.
Commonwealth of Virginia source ↗VDH reports that 37.4% of pregnancy-associated deaths during 2018–2022 occurred 43–365 days after the end of pregnancy.
VDH maternal data ↗For the same 2018–2022 period, VDH separately reports that 40% of pregnancy-associated deaths were due to accidental overdose. This must not be combined with the 43–365-day statistic.
VDH maternal data ↗VDH’s heat-related illness dashboard covers emergency and urgent-care visits from May through September and updates on weekdays in July–August, with weekly Monday updates in May, June, and September or during heat events.
VDH heat surveillance ↗An idea should pass all five gates. A weak answer to any one gate is a signal to narrow or change the concept.
Name the person who will use the app first. Avoid simultaneously targeting clinicians, agencies, parents, students, and policymakers.
Confirm access format, update frequency, definitions, geographic level, and licensing before promising a feature.
The user journey should be understandable in one sequence: input → processing → useful result → action.
The student should be able to explain the API, data structure, algorithm, tests, errors, and design decisions without reading a generated script.
Do not claim HIPAA or FERPA compliance, real-time inventory, prediction accuracy, or clinical validation unless those claims are actually established.
Replace the original enterprise roadmap—Airflow, Kubernetes, multiple models, and statewide pilots—with a student-owned product plan that results in working code.
A source appearing here does not guarantee an API or unrestricted reuse. Check access terms, metadata, and update frequency during Week 1.