How mrnobody23-cloude/ai-healthcare-system works
MedVault is a patient-and-doctor healthcare portal for account access, doctor discovery and appointments, health-data and medical-record management, access requests, and disease-risk analysis. Users enter through the React application; its role-specific pages use the API service to reach the Flask backend, which coordinates persistence and, for analysis, disease models. The database supports MongoDB or in-memory storage, and the frontend also has localStorage utilities. Source excerpts are partial, so uncertain route-to-model and page-to-endpoint wiring is not asserted.
Main entry points: app.py HTTP API · App.jsx App shell · api.js API client · patient Patient pages
Components 20
Web application
- App shell
frontend/src/App.jsx - Sign in
frontend/src/pages/Login.jsx - Patient pages
frontend/src/pages/patient - Doctor pages
frontend/src/pages/doctor - API client
frontend/src/services/api.js - Browser storage
frontend/src/utils/storage.js - AI analysis page
frontend/src/pages/patient/AIAnalysis.jsx
Backend services
- HTTP API
backend/app.py - Encryption
backend/encryption.py - Prediction API
backend/app.py
Health data
- Data access
backend/database.py - MongoDB
- Memory store
backend/database.py - Medical records
backend/app.py - Appointments
backend/app.py - Health data
backend/app.py - Access requests
backend/app.py
AI analysis
- Disease models
backend/ml_models
Other components
- Patient
- Doctor
Connections 23
- Patient → App shell: uses
- Doctor → App shell: uses
- App shell → Sign in: renders
- App shell → Patient pages: renders
- App shell → Doctor pages: renders
- Sign in → API client: authenticates through
- App shell → API client: syncs through
- App shell → Browser storage: reads and writes
- Patient pages → API client: requests data
- Doctor pages → API client: requests data
- API client → HTTP API: sends HTTP requests
- HTTP API → Data access: reads and writes
- Data access → MongoDB: uses when configured
- Data access → Memory store: falls back to
- HTTP API → Encryption: encrypts and decrypts
- HTTP API → Medical records: handles record routes
- HTTP API → Appointments: handles appointment routes
- HTTP API → Health data: handles health routes
- HTTP API → Access requests: handles access routes
- Patient pages → AI analysis page: includes
- AI analysis page → API client: requests analysis
- HTTP API → Prediction API: serves prediction routes
- Prediction API → Disease models: runs predictions