How cha4stre/esanar works
Project Type and Purpose
• eSanar is a monolithic, full-stack web application built with Spring Boot in Java.
• It follows the traditional MVC pattern to manage medical patient records, role-based access, consultations, and report generation (PDF/Excel).
File Structure Analysis
• Top-Level Artifacts
• pom.xml, Maven wrapper, Dockerfile – build and containerization.
• src/main/java/cj/esanar – Java code organized into packages: config, controller, persistence, service, util.
• src/main/resources – Spring Boot properties, static assets (JS/CSS/images), Thymeleaf templates.
• Architectural Layers
• config – Spring Security, data initialization, success handlers, role conversion.
• controller – MVC controllers handling HTTP requests and returning views or JSON.
• service & service/implement – Business logic interfaces and implementations.
• persistence/entity & repository – JPA entities and Spring Data repositories.
• util – pagination utilities and report exporters (PDF/Excel).
• External Integrations
• OMS CIIE API consumption module (in service or util).
• Deployment/Build
• Dockerfile for container image; Maven for build lifecycle.
README Insights
• Emphasizes MVC, role-based security, CRUD operations on users/patients/consultations, export to PDF/Excel, external WHO API consumption.
• Targets academic requirements for Software Architecture course; real-world clinic collaboration.
a. Main Components
1. Web Client (Browser) – HTML/JS static assets, interacts over HTTP/S.
2. Spring Boot Application – orchestrates MVC flow.
3. MVC Layers
– Controllers: AuthController, AdminController, ConsultaController, EnfController, WelcomeController
– Services: ConsultaService, PacienteService, HistoriaService, PermissionsService, UserDetailsService
– Repositories: UserRepository, PacienteRepository, ConsultaRepository, etc.
4. Database – relational store (configured in application.properties).
5. External API – WHO CIIE REST service.
6. Reporting Modules – PDF exporter, Excel exporter.
b. Relationships and Data Flow
• Browser → HTTP Request → SecurityFilterChain (SecurityConfig, CustomSuccessHandler)
• Authenticated → Controller
• Controller → Service → Repository → Database
• Service → util/reports → generate PDF/Excel → HTTP Response (download)
• Service → HTTP Client → External WHO API → enrich data → Controller → View
• Controller → Thymeleaf templates → HTTP Response → Browser
c. Architectural Patterns & Principles
• Layered Architecture (Controller → Service → Repository)
• MVC (views with Thymeleaf, controllers handling input, models via entities)
• Dependency Injection via Spring
• Role-based Access Control using Spring Security
• External integration via REST client
d. Key Technologies
• Java 11+, Spring Boot, Spring MVC, Spring Security, Spring Data JPA
• Thymeleaf templates, static JS/CSS
• Maven, Docker
• Apache POI (Excel), iText or Jasper (PDF)
• REST template or WebClient for WHO API