π Lifeline: AI-Powered Health Support
π Inspiration
The idea for Lifeline was inspired by the growing need for accessible, real-time health support. In critical situations, seconds can make a difference β yet many patients, caregivers, and first responders lack instant access to reliable medical insights. We wanted to build something that bridges this gap: a tool that empowers users with information, triage, and decision support when it matters most.
π What We Learned
- How AI can be integrated with medical datasets while respecting privacy and ethical boundaries.
- The importance of human-centered design in health tech: clarity, trust, and simplicity are essential.
- Hands-on lessons with LLM prompting, embeddings, and contextual retrieval, especially for domain-specific knowledge.
- Team collaboration under tight time constraints β dividing roles between backend, frontend, and ML workflows.
π οΈ How We Built It
Backend (FastAPI + Python)
- Implemented an API for symptom input and triage recommendations.
- Integrated embeddings for context-aware retrieval of medical information.
- Implemented an API for symptom input and triage recommendations.
Frontend (React + Tailwind)
- Built a clean, minimal interface for users to quickly describe their situation.
- Added voice input and output for accessibility and speed.
- Built a clean, minimal interface for users to quickly describe their situation.
AI / Data Layer
- Used OpenAI for natural language understanding and generation.
- Embedded trusted healthcare resources for retrieval (triage guides, first-aid protocols, clinical FAQs).
- Ensured answers were contextualized + cited, avoiding hallucinations.
- Used OpenAI for natural language understanding and generation.
Deployment
- Deployed backend on Render and frontend on Vercel.
- Set up monitoring to handle scale during demo sessions.
- Deployed backend on Render and frontend on Vercel.
βοΈ Challenges We Faced
- Medical accuracy vs. AI creativity: ensuring responses were safe, reliable, and not misleading.
- Data privacy: designing a flow that works without storing sensitive user data.
- Time constraints: building a robust retrieval pipeline + frontend in under 36 hours.
- Edge cases: handling vague or ambiguous symptom descriptions gracefully.
π Whatβs Next
- Partner with healthcare providers for dataset validation.
- Expand to support multiple languages for global accessibility.
- Add integrations with emergency services APIs for faster response coordination.

Log in or sign up for Devpost to join the conversation.