lokesh848-code/elder_guard

Purpose and Entry Points

ElderGuard AI is a multi-role elder-care platform: elder, caregiver, doctor, hospital, and pharmacy portals share healthcare records and operational workflows. The React/Vite client starts at frontend/src/main.jsx and routes through frontend/src/App.jsx. FastAPI starts from backend/app/main.py, exposing HTTP APIs plus elder-scoped WebSockets.

Client Application and Role Portals

The frontend maintains authentication and notification state, then presents role-specific dashboards and workflows. API service modules form the boundary to backend endpoints; hooks encapsulate connected/realtime data use.

• frontend/src/context/AuthContext.jsx

• frontend/src/components/layout/DashboardLayout.jsx

• frontend/src/pages/elder/ElderDashboard.jsx

• frontend/src/pages/caregiver/CaregiverDashboard.jsx

• frontend/src/services/api.js

Identity, Profiles, and Access Boundary

Authentication, role/profile management, and elder–caregiver links establish authorization. Connected records are owned by elder_id; caregiver reads and writes must be constrained by active caregiver links, while pending or view-only links do not grant equivalent access.

• backend/app/auth/routes.py

• backend/app/profiles/routes.py

• backend/app/profiles/links.py

• backend/supabase/migrations/013_connected_portals.sql

Connected Care Data and Realtime Fan-out

The connected subsystem is the cross-portal synchronization layer for medicines, vitals, check-ins, appointments, SOS, messages, notifications, and audit history. Backend mutations persist shared records, then publish named events to the elder:{elderId} WebSocket room; clients invalidate/refetch relevant cached data.

• backend/app/connected/routes.py

• backend/app/connected/realtime.py

• backend/app/connected/storage.py

• frontend/src/hooks/useConnectedPortal.js

Clinical Workflows

Appointments, medicine reminders, vitals, and emergency SOS are domain services with route/model/schema layers. Scheduler and queue modules imply time- or dispatch-oriented work beyond request handling. Emergency delivery is server-side: SOS persistence, linked-caregiver notification timing, notifications, and realtime broadcast.

• backend/app/appointments/service.py

• backend/app/appointments/queue.py

• backend/app/medicines/service.py

• backend/app/vitals/scheduler.py

• backend/app/emergency/service.py

Notifications and External Delivery

Notifications are modeled and dispatched centrally, with in-app, Firebase Cloud Messaging push, and Telegram channel adapters. These channels are downstream effects of care events rather than the source of authorization or record ownership.

• backend/app/notifications/service.py

• backend/app/notifications/channels/in_app.py

• backend/app/notifications/channels/push_fcm.py

• backend/app/notifications/channels/telegram.py

Persistence, Infrastructure, and Extended Services

The backend supports local SQLite fallback and PostgreSQL/Supabase migrations; database and security configuration are centralized in core. Docker Compose supports the full stack. Additional bounded domains include AI companion, OCR, reports/analytics, community events, doctor records, and hospital operations.

• backend/app/core/database.py

• backend/app/core/config.py

• backend/supabase/migrations/001_initial_schema.sql

• backend/supabase/combined_migrations.sql

• docker-compose.yml