SymptomX -AI-powered health helper for low-resource settings SymptomX is a lightweight web app that helps people in areas with limited access to doctors understand their symptoms, get self-care guidance, and find trusted reference information. It is not a medical diagnosis tool, but rather a reference and support platform to empower users with reliable health information.
- Problem and Motivation: What is the specific problem your project tackles? Why is it significant or challenging to address?
The problem we are addressing is the lack of accessible, reliable healthcare guidance for people living in remote or underserved areas. In many parts of rural China and developing countries, hospitals are far away, doctors are scarce, and internet searches often lead to misinformation. This delay in proper advice can turn minor illnesses into serious, preventable health crises. It’s significant because healthcare inequality remains one of the most pressing global challenges—affecting billions who cannot afford timely consultations. Tackling it is difficult because it requires bridging medical accuracy, cultural diversity, and technology usability in environments with poor infrastructure.
- Project Overview: Summarize your solution and explain how it directly addresses the identified problem. How is it different from existing solutions?
Our solution is SymptomX, an AI-powered health assistant website where users can: Enter symptoms in plain language and receive possible illness matches. Get safe self-care steps and medication guidance. Chat with an AI for additional questions.
Unlike existing symptom checkers, SymptomX is: Multilingual and culturally adaptable (starting with English and Chinese). Offline-first and lightweight, designed for low-resource settings. Transparent, showing confidence scores and clear triage advice. This combination of simplicity, trustworthiness, and accessibility makes it stand out.
- Technical Implementation: Highlight the innovative aspects of your solution and detail the technologies or methods you used. Be sure to describe how you considered accessibility and ensured a positive user experience.
We combined a keyword database + AI/NLP model to balance reliability with flexibility. 1.TF-IDF with cosine similarity matches symptoms to conditions. 2.FastAPI + Python backend serves responses quickly. 3.Frontend (HTML, CSS, JS, Tailwind) ensures mobile-first usability. 4.Pydantic validates data, ensuring safe outputs. 5.Dockerized deployment makes it portable.
Accessibility and UX were central: 1.Mobile-first design for rural users with phones. 2.Dark/light mode for readability. 3.Clear triage messages (“routine,” “urgent,” “emergency”) to reduce confusion.
- Impact and Scalability: What impacts does your solution have, and how can it scale effectively to reach more users or communities? What ideas do you have for potential future work on this project?
Impact: SymptomX empowers people with first-line health insights, reducing misinformation, anxiety, and preventable harm. It raises health literacy and supports health equity for underserved communities.
Scalability: 1.Expand database to include more illnesses, medications, and regional variations. 2.Add voice input/output for low-literacy populations. 3.Integrate telehealth connections with NGOs or local clinics. 4.Deploy on low-data servers or SMS gateways for regions without reliable internet. 5.Future work includes deeper AI integration, partnerships with global health organizations, and potential integration with wearable devices for continuous monitoring.
- Design Process and Collaboration: What were some challenges you faced over the course of the hackathon? How did you overcome those challenges? What did you learn about the design process? How did your team delegate tasks, resolve conflicts, and communicate with each in order to work together most effectively?
Challenges we faced: 1.Balancing accuracy and simplicity—too much detail confused users; too little risked safety. 2.Multilingual translation issues, especially for medical terminology. 3.Limited time to test across different devices and internet speeds.
How we overcame them: 1.Iterated with a feedback-first approach, simplifying UI after each test. 2.Used clear disclaimers to ensure safety while still offering guidance.
Split tasks: backend team handled logic, frontend team focused on UX, while AI integration was coordinated jointly.
Teamwork lessons: 1.Frequent check-ins kept us aligned. 2.Task delegation based on strengths improved efficiency. 3.We learned the importance of compromise and clarity in communication—especially 4.under hackathon time pressure.
- Health: A big consideration in the health industry is accessibility. What systemic barriers might limit access to your solution for certain groups, and what measures have you taken to ensure privacy, autonomy, and equity? What considerations need to be made in the implementation process of your solution in the real world to protect these aspects of patients and consumers?
Log in or sign up for Devpost to join the conversation.