Inspiration
Rare disease patients live in constant uncertainty. Symptoms fluctuate daily, appointments are brief and infrequent, and most patients struggle to accurately communicate weeks of complex health changes in a 15-minute consultation. Many also experience deep isolation because only a small number of people share their condition. We were inspired by a simple but powerful question: What if patients had an intelligent system that tracked, understood, and translated their daily experience into meaningful insights? Amelie was built to give rare disease patients clarity, structure, and confidence in managing their health.
What it does
Amelie is a full-stack web application designed specifically for rare disease patients. It provides: (a) Daily health check-ins (pain, energy, sleep, mood, mobility, red flags) (b) AI-generated personalized daily plans (c) A 7-day predictive risk forecast (d) Rosetta — an AI health companion (e) Smart safety alerts (f) Clinician-ready PDF health reports (g) Anonymous condition-specific community groups Unlike traditional health trackers that only show historical data, Amelie predicts risk trends and translates patient data into actionable insights. It helps patients prepare for appointments, recognize worsening patterns early, and connect with others who truly understand their condition.
How we built it
Frontend:
- React
- Vite
- Tailwind CSS
- Backend
- Node.js + Express
- Socket.io for real-time community chat
- JWT authentication with bcrypt
Database:
- sql.js (WebAssembly SQLite) for zero native setup
AI Features:
- OpenAI GPT-4o via streaming Server-Sent Events
- Personalized daily plan generation
- AI twin (Rosetta) with contextual system prompts
- GPT-generated clinical report PDFs
Custom Backend Logic:
- Rule-based alert engine
- Weighted mathematical 7-day risk forecast
- Linear regression trend calculations
- Risk dampening over time
The forecast and alert systems run purely on backend logic — no AI calls — ensuring speed and reliability.
Challenges we ran into
- Designing a risk prediction formula that felt medically conservative yet meaningful
- Ensuring AI responses were contextual, not generic
- Preventing over-medicalization or unsafe AI suggestions
- Balancing technical complexity with a clean, simple UI
- Making forecasts feel helpful — not anxiety-inducing
We had to carefully separate:
- AI-driven guidance
- Deterministic safety rules
- Predictive mathematical modeling
This architecture was critical for both safety and performance.
Accomplishments that we're proud of
- Building a real-time AI twin that understands personal health baselines
- Creating a backend-driven predictive forecast under 5ms response time
- Designing a rule-based alert engine independent of AI
- Generating clinician-ready PDF reports automatically
- Implementing anonymous peer communities with live messaging
Most importantly: We built something that feels empathetic — not just technical.
What we learned
- In health tech, safety > cleverness
- AI must be guided by strict boundaries
- Predictive modeling requires thoughtful dampening to avoid false certainty
- Simplicity in UI builds trust
- Real impact comes from reducing cognitive load for vulnerable users
We also learned how powerful structured data becomes when paired with intelligent interpretation.
What's next for Amelie
- Integrating wearable data (Apple Health, Garmin, Fitbit)
- Adding longitudinal analytics beyond 7 days
- Clinician dashboards for shared access
- HIPAA-compliant cloud deployment
- More rare-disease-specific forecasting models
- Expanding multilingual support
Long term, we envision Amelie becoming a structured intelligence layer between patients and providers—improving communication, early intervention, and quality of life.
Built With
- css
- express.js
- node.js
- openaiapi
- react
- tailwind
- vite
Log in or sign up for Devpost to join the conversation.