How indhumathi2906/medivault-prescription-for-healthcare-systems works
MEDIVAULT is a role-based healthcare platform for patient records, appointments, consultations, prescriptions, and longitudinal health tracking. The principal workflow is a doctor reviewing a patient and recording a progress assessment; the patient then views comparisons and trends. The graph also covers doctor discovery and booking, clinical records, notifications, and administration. Controller/service links are shown where supported by sampled code; other feature branches follow the documented route and module structure, so their internal wiring is not expanded.
Main entry points: server.ts API host · App.tsx Routes and roles · db.ts Application data store · api.ts HTTP client
Components 32
Role-based client
- Routes and roles
src/App.tsx - Patient pages
src/pages/patient - Doctor pages
src/pages/doctor - Admin pages
src/pages/admin - Public access
src/pages/public - HTTP client
src/services/api.ts
Healthcare API
- API host
server.ts - Patient routes
server/routes/patientRoutes.ts - Doctor routes
server/routes/doctorRoutes.ts - Progress routes
server/routes/progressRoutes.ts - Appointment routes
server/routes/appointmentRoutes.ts - Consultation routes
server/routes/consultationRoutes.ts - Prescription routes
server/routes/prescriptionRoutes.ts - Notification routes
server/routes/notificationRoutes.ts - Admin routes
server/routes/adminRoutes.ts - Auth routes
server/routes/authRoutes.ts
Clinical workflow
- Patient records
server/controllers/patientController.ts - Doctor directory
server/controllers/doctorController.ts - Appointment booking
server/controllers/appointmentController.ts - Consultations
server/controllers/consultationController.ts - Prescriptions
server/controllers/prescriptionController.ts - Progress reviews
server/controllers/progressController.ts - Metric analysis
server/services/progressService.ts - Notifications
server/controllers/notificationController.ts
Identity and oversight
- Authentication
server/controllers/authController.ts - Access controls
server/middleware/auth.ts - Platform oversight
server/controllers/adminController.ts - Application data store
server/config/db.ts
Other components
- Patient
- Doctor
- Administrator
- Supabase PostgreSQL
Connections 42
- Patient → Routes and roles: opens
- Doctor → Routes and roles: opens
- Administrator → Routes and roles: opens
- Routes and roles → Patient pages: routes
- Routes and roles → Doctor pages: routes
- Routes and roles → Admin pages: routes
- Routes and roles → Public access: routes
- Patient pages → HTTP client: requests
- Doctor pages → HTTP client: requests
- Admin pages → HTTP client: requests
- Public access → HTTP client: requests
- HTTP client → API host: HTTP requests
- API host → Patient routes: mounts
- API host → Doctor routes: mounts
- API host → Progress routes: mounts
- API host → Appointment routes: mounts
- API host → Consultation routes: mounts
- API host → Prescription routes: mounts
- API host → Notification routes: mounts
- API host → Admin routes: mounts
- API host → Auth routes: mounts
- Patient routes → Patient records: dispatches
- Doctor routes → Doctor directory: dispatches
- Progress routes → Progress reviews: dispatches
- Appointment routes → Appointment booking: dispatches
- Consultation routes → Consultations: dispatches
- Prescription routes → Prescriptions: dispatches
- Notification routes → Notifications: dispatches
- Admin routes → Platform oversight: dispatches
- Auth routes → Authentication: dispatches
- Progress reviews → Metric analysis: calculates
- Patient records → Metric analysis: compares progress
- Doctor directory → Metric analysis: reads progress
- Patient records → Application data store: reads records
- Appointment booking → Application data store: reads and writes
- Progress reviews → Application data store: appends reviews
- Metric analysis → Application data store: reads reviews
- Authentication → Application data store: reads and writes
- Access controls → Auth routes: guards
- Access controls → Patient routes: guards
- Access controls → Progress routes: guards
- Application data store → Supabase PostgreSQL: optional persistence