How akshaya-ravichandran2712/infosys_springboard_internship_batch_2 works
MediSphere is a healthcare management platform for patient records, monitoring, and role-based access. The main user workflow is navigating the React application, registering or viewing patient records, and accessing clinical modules for twin completeness and vital validation. Backend controllers handle patient, authentication, alert, and clinical-outcome approval operations; repositories persist domain records. The README also describes predictions, care plans, reports, and RBAC. Those frontend capabilities appear in routing, but their backend connections are not established by the sampled evidence.
Main entry points: AppRoutes.jsx Application routes · Dashboard.jsx Patient dashboard · PatientController.java Patient API · PatientRepository.java Patient repository
Components 28
Frontend experience
- Application routes
frontend/src/routes/AppRoutes.jsx - Patient dashboard
frontend/src/pages/Dashboard.jsx - Patient telemetry card
frontend/src/components/PatientCard.jsx - Navigation sidebar
frontend/src/components/Sidebar.jsx
Identity and access
- User registration
frontend/src/pages/Register.jsx - Access roles
frontend/src/pages/RBAC.jsx - Authentication API
medisphere-backend/src/main/java/com/medisphere/controller/AuthController.java - JWT service
medisphere-backend/src/main/java/com/medisphere/service/JwtService.java
Patient records
- Patient registry
frontend/src/pages/Patients.jsx - Patient API
medisphere-backend/src/main/java/com/medisphere/controller/PatientController.java - Patient repository
medisphere-backend/src/main/java/com/medisphere/repository/PatientRepository.java - Patient record
medisphere-backend/src/main/java/com/medisphere/entity/Patient.java
Clinical workflows
- Digital twins
frontend/src/pages/Twins.jsx - Twin completeness
frontend/src/pages/TwinCompleteness.jsx - Vital validation
frontend/src/pages/VitalValidation.jsx - Predictions
frontend/src/pages/Predictions.jsx - Alert inbox
frontend/src/pages/Alerts.jsx - Care plans
frontend/src/pages/CarePlans.jsx - Reports
frontend/src/pages/Reports.jsx - Alert API
medisphere-backend/src/main/java/com/medisphere/controller/AlertController.java - Alert handling
medisphere-backend/src/main/java/com/medisphere/service/AlertService.java - Alert repository
medisphere-backend/src/main/java/com/medisphere/repository/AlertRepository.java - Alert record
medisphere-backend/src/main/java/com/medisphere/entity/Alert.java - Outcome approval API
medisphere-backend/src/main/java/com/medisphere/controller/OutcomeApprovalController.java - Outcome approval
medisphere-backend/src/main/java/com/medisphere/service/OutcomeApprovalService.java - Approval repository
medisphere-backend/src/main/java/com/medisphere/repository/OutcomeApprovalRepository.java - Approval record
medisphere-backend/src/main/java/com/medisphere/model/ClinicalOutcomeApproval.java
Other components
- Healthcare user
Connections 25
- Healthcare user → Application routes: uses
frontend/src/routes/AppRoutes.jsx - Application routes → Patient dashboard: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → Patient registry: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → User registration: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → Access roles: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → Digital twins: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → Twin completeness: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → Vital validation: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → Predictions: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → Alert inbox: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → Care plans: routes to
frontend/src/routes/AppRoutes.jsx - Application routes → Reports: routes to
frontend/src/routes/AppRoutes.jsx - Patient dashboard → Patient telemetry card: renders
frontend/src/pages/Dashboard.jsx - Patient dashboard → Patient API: fetches records
frontend/src/pages/Dashboard.jsx - Patient registry → Patient API: submits patient
frontend/src/pages/Patients.jsx - Authentication API → Patient repository: looks up patient
medisphere-backend/src/main/java/com/medisphere/controller/AuthController.java - Authentication API → JWT service: generates token
medisphere-backend/src/main/java/com/medisphere/controller/AuthController.java - Patient API → Patient repository: accesses records
medisphere-backend/src/main/java/com/medisphere/controller/PatientController.java - Patient repository → Patient record: stores
medisphere-backend/src/main/java/com/medisphere/repository/PatientRepository.java - Alert API → Alert handling: delegates
medisphere-backend/src/main/java/com/medisphere/controller/AlertController.java - Alert handling → Alert repository: saves and queries
medisphere-backend/src/main/java/com/medisphere/service/AlertService.java - Alert repository → Alert record: persists
medisphere-backend/src/main/java/com/medisphere/repository/AlertRepository.java - Outcome approval API → Outcome approval: delegates
medisphere-backend/src/main/java/com/medisphere/controller/OutcomeApprovalController.java - Outcome approval → Approval repository: reads and saves
medisphere-backend/src/main/java/com/medisphere/service/OutcomeApprovalService.java - Approval repository → Approval record: persists
medisphere-backend/src/main/java/com/medisphere/repository/OutcomeApprovalRepository.java