sanjay-it008/hospital-

Purpose and Entry Points

This is a hospital-management system split into a Java backend and a JavaScript frontend. The backend entry point is hospital-backend/src/main/java/com/hospital/HospitalApplication.java; its runtime settings are in hospital-backend/src/main/resources/application.properties. The frontend bootstraps from hospital-frontend/src/index.js into hospital-frontend/src/App.js.

Backend API Layer

HTTP-facing resources are separated by domain and authentication:

• hospital-backend/src/main/java/com/hospital/controller/AuthController.java

• hospital-backend/src/main/java/com/hospital/controller/AppointmentController.java

• hospital-backend/src/main/java/com/hospital/controller/DoctorController.java

• hospital-backend/src/main/java/com/hospital/controller/PatientController.java

Controllers form the backend boundary for login/registration and patient, doctor, and appointment operations, delegating domain work rather than directly representing the persistence layer.

Domain and Persistence

The central persisted entities are users, patients, doctors, and appointments:

• hospital-backend/src/main/java/com/hospital/model/User.java

• hospital-backend/src/main/java/com/hospital/model/Patient.java

• hospital-backend/src/main/java/com/hospital/model/Doctor.java

• hospital-backend/src/main/java/com/hospital/model/Appointment.java

Repository interfaces isolate data access per entity, including hospital-backend/src/main/java/com/hospital/repository/AppointmentRepository.java and hospital-backend/src/main/java/com/hospital/repository/UserRepository.java. Service classes are the intended business-logic boundary between controllers and repositories, notably hospital-backend/src/main/java/com/hospital/service/AppointmentService.java and hospital-backend/src/main/java/com/hospital/service/AuthService.java.

Authentication and Request Security

JWT-based authentication is a defining cross-cutting backend flow. hospital-backend/src/main/java/com/hospital/security/JwtFilter.java likely intercepts incoming requests, while hospital-backend/src/main/java/com/hospital/security/JwtUtil.java creates or validates tokens. Security policy and cross-origin access are centralized in:

• hospital-backend/src/main/java/com/hospital/config/SecurityConfig.java

• hospital-backend/src/main/java/com/hospital/config/CorsConfig.java

The primary protected-request flow is frontend API call → CORS/security chain → JWT filter → controller → service → repository.

Frontend Application and Role Workspaces

The frontend is a single-page application organized around user journeys and role-specific views. Shared application state includes authentication and toast/notification concerns:

• hospital-frontend/src/context/AuthContext.js

• hospital-frontend/src/context/ToastContext.js

• hospital-frontend/src/components/Layout.jsx

Main workflows are represented by hospital-frontend/src/pages/Login.jsx, hospital-frontend/src/pages/Register.jsx, hospital-frontend/src/pages/BookAppointment.jsx, hospital-frontend/src/pages/PatientDashboard.jsx, hospital-frontend/src/pages/DoctorDashboard.jsx, and hospital-frontend/src/pages/AdminPanel.jsx. hospital-frontend/src/components/AppointmentCard.jsx is a reusable appointment presentation unit.

Client Data Boundaries and External Services

hospital-frontend/src/services/api.js is the likely HTTP boundary to the Java backend and should be the primary location for token attachment, request normalization, and backend URL handling. The frontend also contains alternate or supplemental client-side data integrations:

• hospital-frontend/src/services/localDB.js

• hospital-frontend/src/services/supabaseDB.js

• hospital-frontend/src/supabaseClient.js

Supabase is therefore an external service dependency present in the client architecture. Its relationship to the backend persistence layer is not determinable from the tree and should be clarified before treating either backend repositories or Supabase as the sole system of record.

Runtime and Delivery Boundaries

The backend is Maven-based (hospital-backend/pom.xml) and structured as a Java application with conventional controller/service/repository layers. The frontend is a separate Node-managed build (hospital-frontend/package.json) with Tailwind/PostCSS styling configuration. They can be deployed independently, with browser traffic crossing from the frontend runtime to the backend API and potentially to Supabase.