How riya281106/agentic-healthcare-assistant works
This is an early-stage healthcare-assistant web app: users can navigate a React frontend with landing, login, registration, chat, and profile routes, while a separate FastAPI backend currently exposes only a health-check-style root response. The landing page advertises conversational AI, trusted sources, symptom tracking, emergency detection, privacy, and shareable reports, but the README says the AI layer is still to be added. The sampled frontend contains no backend requests, so no frontend-to-backend workflow is shown.
Main entry points: App.jsx App routes · HomePage.jsx Home page · main.jsx Frontend entry · Navbar.jsx Navigation bar
Components 14
React frontend
- Frontend entry
frontend/src/main.jsx - App routes
frontend/src/App.jsx - Navigation bar
frontend/src/components/Navbar.jsx - Home page
frontend/src/pages/HomePage.jsx - Hero section
frontend/src/components/Hero.jsx - Feature cards
frontend/src/components/Features.jsx - Footer
frontend/src/components/Footer.jsx - Login page
frontend/src/pages/LoginPage.jsx - Registration page
frontend/src/pages/RegisterPage.jsx - Chat page
frontend/src/pages/ChatPage.jsx - Profile page
frontend/src/pages/ProfilePage.jsx - Not-found page
frontend/src/pages/NotFoundPage.jsx
FastAPI backend
- Root API
backend/main.py
Other components
- User
Connections 12
- User → Frontend entry: opens app
- Frontend entry → App routes: renders
- App routes → Navigation bar: renders
- App routes → Home page: routes to
- App routes → Login page: routes to
- App routes → Registration page: routes to
- App routes → Chat page: routes to
- App routes → Profile page: routes to
- App routes → Not-found page: routes to
- Home page → Hero section: renders
- Home page → Feature cards: renders
- Home page → Footer: renders