Meet The Builder

Yashu.dev — Mon, 27 Jul 2026 06:27:32 +0000

Meet the Builders: Transforming Medical Reports into Dual-Engine Health Intelligence

How a team of hackathon builders turned isolated medical PDF lab reports into an AI-powered platform for individual health literacy and predictive public health surveillance using Google Gemini 2.5.

🌟 The Spark: A Two-Fold Problem
Every year, millions of people receive lab reports filled with dense medical jargon, obscure acronyms, and raw numerical values. Whether it’s an HbA1c of 6.8% or a Hemoglobin of 10.2 g/dL, most patients leave clinic visits anxious, confused, and forced to do unreliable web searches for answers.

At the same time, we noticed an even bigger systemic problem: Medical data exists in isolated silos. Thousands of medical lab PDFs sit on individual smartphones and clinic desks. No one sees the bigger picture. When 30% of patients in a specific neighborhood show elevated blood sugar markers, no alert goes off. When anemia rates spike among young demographics in a rural zone, it goes unnoticed until it becomes a community health crisis.

We asked ourselves a simple question: What if a single medical report upload could instantly empower the patient with clear, trustworthy answers while anonymously contributing to predictive public health intelligence?

That was the spark behind the Community Health Intelligence Assistant.

Phase 1: Building the Initial Prototype (v1.0)
We began by outlining a multi-agent RAG (Retrieval-Augmented Generation) pipeline designed to bridge both worlds:

Extraction & Parsing: Using Python and table extraction libraries, we parsed unstructured medical report text and mapped raw values against clinical reference ranges.
Patient Q&A (RAG): We stored text chunks in a vector store (ChromaDB) so patients could ask natural language questions about their reports.
Community Aggregation: We designed a basic SQLite database schema to store anonymized lab parameters grouped by demographic brackets (0-18, 19-30, 60+) and regional zones (Urban-Central, Rural-West).
Our initial proof-of-concept ran on a simple Streamlit interface. It worked, but we quickly realized it wasn't ready for production. Patients needed absolute trust in AI explanations, the UI needed to feel responsive, and community analytics required enterprise-grade privacy and security.

⚡ Phase 2: Overcoming Challenges & The Refinement Phase (v2.0)
During the refinement phase, we pushed our engineering to the next level:

Modernizing the User Experience (React 19 + Vite + SSE Streaming)
We completely replaced the single-script frontend with a production React 19 + Vite web application. To solve the problem of long wait times during AI generation, we implemented Server-Sent Events (SSE) live streaming (/api/chat/stream). Answers now stream in real time, token by token.
Solving AI Trust with Collapsible Source Grounding
In healthcare, AI hallucinations are unacceptable. To solve this, we engineered Collapsible Source Evidence Cards (ChatSourceEvidence). Alongside every AI response, users can toggle compact excerpts featuring explicit Page Number badges (Page 1, Page 2). Patients don't have to blindly trust the AI—they can verify every claim directly against their own uploaded report.
Upgrading the AI Engine (Google Gemini 2.5)
We upgraded our underlying model pipeline to Google Gemini 2.5 (gemini-2.5-flash for reasoning/explanations and gemini-embedding-001 for vector embeddings). By writing a lightweight direct REST API client, we eliminated heavy SDK dependencies and drastically reduced API response latency.
Enterprise Security & Mathematical Privacy
Healthcare applications demand strict data protection:

CodeQL Security Hardening: We systematically audited and hardened our backend code against CodeQL security vulnerabilities—implementing strict directory path normalization (os.path.normpath) to prevent path injections and creating dynamic credential masking (_mask_credentials) to ensure zero clear-text log leaks.
Differential Privacy: To ensure public health planners can query aggregate community metrics safely, we integrated calibrated Laplace Noise Differential Privacy (ϵ=0.5
ϵ=0.5), mathematically guaranteeing that single patient records can never be reverse-engineered from dashboard stats.

Predictive Outbreak Analytics Instead of just displaying static historical charts, we integrated Linear Regression Trend Analysis and CDC ESSENCE aberration detection. The platform now projects 30-to-90 day regional abnormal rate forecasts, enabling health officials to organize targeted medical screening camps before health spikes become crises.

How It Finished: A Production-Ready Architecture
What started as an idea is now a full-stack, containerized platform:

Frontend: Responsive React 19 + Vite UI with split-theme design system and multi-lingual support (English, Hindi, Spanish, etc.).
Backend: Asynchronous FastAPI server with health endpoints, CORS middleware, and static asset routing.
Deployment: Packaged with a multi-stage Dockerfile and automated Google Cloud Build config (cloudbuild.yaml) ready for serverless container deployment on Google Cloud Run.

Lessons Learned & What's Next
Building this platform taught us that Responsible AI isn't just a safety checklist—it's a core feature. Giving users transparent source citations, mathematical privacy guarantees, and instant plain-language clarity transforms AI from a scary "black box" into a trusted healthcare assistant.

Looking ahead, we plan to migrate our pipeline to Google Cloud native services—using Document AI for scanned report OCR, Vertex AI Embeddings, and BigQuery ML for enterprise-scale epidemiological modeling.

We want to thank the hackathon organizers, mentors, and the Google Gemini team for providing the AI tools that made this build possible!

GitHub Repository: Astroidkiller/medical-report-rag
Tech Stack: Google Gemini 2.5, React 19, Vite, FastAPI, Python 3.11, ChromaDB, SQLite, Docker

DEV Community: Yashu.dev

Meet The Builder