How premchand338/re-move---healthcare-appointment-booking works
This repository implements a physiotherapy clinic website and API. Visitors explore clinical information, submit assessments, find therapists, and book appointments; patients and administrators can also authenticate, while administrators manage therapist records. The frontend route shell and server mounts are visible in sampled source. Several UI and backend modules are represented only by their paths, so links between those unsampled modules are omitted where their calls cannot be verified.
Main entry points: server.ts Express API server · App.tsx Routes and landing · db.ts Database connection · auth.ts Role authorization
Components 23
Clinic website
- Routes and landing
src/App.tsx - Clinical content
src/components/ClinicalModalities.tsx - Symptom assessment
src/components/AssessmentModal.tsx - Therapist discovery
src/components/TherapistListPage.tsx - Account access
src/pages/LoginPage.tsx - Patient registration
src/pages/RegisterPage.tsx - Admin dashboard
src/pages/AdminDashboard.tsx - Therapist management
src/components/TherapistListPage.tsx - Therapist API service
src/services/therapistService.ts - Appointment API service
src/services/appointmentService.ts - HTTP client
src/lib/api.ts
Clinic API
- Express API server
backend/src/server.ts - Authentication routes
backend/src/routes/authRoutes.ts - Assessment and matching
backend/src/routes/assessmentRoutes.ts - Appointment booking
backend/src/routes/appointmentRoutes.ts - Therapist records
backend/src/routes/therapistRoutes.ts - Patient records
backend/src/routes/patientRoutes.ts - Clinic services
backend/src/routes/serviceRoutes.ts - Contact inquiries
backend/src/routes/inquiryRoutes.ts - Role authorization
backend/src/middleware/auth.ts
Persistence and access
- Database connection
backend/src/db.ts - Clinic database
Other components
- Visitor or user
Connections 30
- Visitor or user → Routes and landing: opens
- Routes and landing → Clinical content: renders
- Routes and landing → Symptom assessment: opens
- Routes and landing → Therapist discovery: renders
- Routes and landing → Account access: routes to
- Routes and landing → Patient registration: routes to
- Routes and landing → Admin dashboard: routes to
- Admin dashboard → Therapist management: renders
- Therapist API service → HTTP client: requests through
- Appointment API service → HTTP client: requests through
- HTTP client → Express API server: sends HTTP
- Express API server → Authentication routes: mounts
- Express API server → Assessment and matching: mounts
- Express API server → Appointment booking: mounts
- Express API server → Therapist records: mounts
- Express API server → Patient records: mounts
- Express API server → Clinic services: mounts
- Express API server → Contact inquiries: mounts
- Assessment and matching → Role authorization: guards routes
- Appointment booking → Role authorization: guards routes
- Therapist records → Role authorization: guards routes
- Patient records → Role authorization: guards routes
- Assessment and matching → Database connection: queries
- Appointment booking → Database connection: queries
- Therapist records → Database connection: queries
- Patient records → Database connection: queries
- Clinic services → Database connection: queries
- Authentication routes → Database connection: queries
- Contact inquiries → Database connection: queries
- Database connection → Clinic database: connects to