How najhelybs/vacunacioncard-avance1 works
1. This is a Java/Spring Boot monolith for a “Sistema de Cartilla Digital de Vacunación” (digital vaccination record system). The entry point is VacunacioncardApplication.java, with Maven (pom.xml, Maven wrapper) handling build and dependency management.
2. The repository is currently structured as a layered application, but only the domain model is populated. The controller, service, service/impl, repository, and config packages exist as placeholders (.gitkeep), which means the architecture is intended to grow into a standard presentation–service–persistence stack.
3. The core of the system is the domain package, which is split by business capability rather than by technical layer. The major bounded contexts are:
- usuario for people using the system
- auth for account and access control concepts
- vacunacion for vaccines, records, and schedules
- cita for appointments
- campania for vaccination campaigns and centers
- salud for medical conditions and contraindications
- notificacion for reminders and system alerts
- comun for shared value objects and audit data
4. The user model appears central. Usuario is the base concept, with specialized roles/entities such as Paciente, Enfermero, and Administrador. SeguroMedico suggests patient insurance data is part of the domain, likely attached to or associated with a patient profile.
5. Access control is separated into its own domain slice. CuentaUsuario, Rol, Permiso, and SesionUsuario imply authentication/authorization and session tracking are modeled explicitly rather than embedded in generic user records.
6. The vaccination workflow is represented by several linked entities: Vacuna, EsquemaVacunacion, CartillaVacunacion, RegistroVacuna, AplicacionDosis, UbicacionAplicacion, and Laboratorio. Together these indicate the system tracks vaccine definitions, schedules, administered doses, where doses were applied, and the resulting patient vaccination card/history.
7. Appointment and campaign management are distinct subsystems. CitaVacunacion and Horario model booking and availability, while CampaniaVacunacion and CentroVacunacion model organized vaccination campaigns and physical sites. This suggests workflows for both individual appointments and broader public-health campaigns.
8. Clinical safety is modeled separately from vaccination records. Alergia, CondicionMedica, and Contraindicacion indicate pre-vaccination screening or eligibility checks are part of the domain, likely used before scheduling or administering doses.
9. Notification and audit concerns are isolated into their own packages. Notificacion, NotificacionRecordatorio, and NotificacionSistema cover patient/system messaging, while RegistroAuditoria captures traceability. This implies side effects such as reminders and compliance logging are treated as cross-cutting business features.
10. The comun package contains shared primitives/value objects like Calendario, Contacto, and Direccion, which are likely reused across users, centers, appointments, and campaigns. This is the main shared boundary to avoid duplicating address/contact/time concepts across the model.
11. There is no visible persistence or API implementation yet. Because the repository and service packages are empty, a diagram should show the intended flow rather than an implemented one: external client/UI would call controllers, controllers would delegate to services, services would operate on domain entities and repositories, and repositories would persist to a database.
12. Configuration is minimal at the moment. application.properties exists, but no concrete infrastructure classes are present, so current runtime behavior is basically the Spring Boot application shell plus the domain model. The test package contains only the default application startup test, reinforcing that the repo is still in an initial scaffolding phase.
Main entry points: controller/.gitkeep Controllers · service/.gitkeep Services · Contacto.java Común · VacunacioncardApplication.java VacunacioncardApplication
Components 15
Runtime
Spring Boot application shell and intended request flow
- VacunacioncardApplication · Application bootstrap
src/main/java/pe/utp/edu/vacunacioncard/VacunacioncardApplication.java - Controllers · Presentation layer intended for incoming requests
src/main/java/pe/utp/edu/vacunacioncard/controller/.gitkeep - Services · Business orchestration layer placeholder
src/main/java/pe/utp/edu/vacunacioncard/service/.gitkeep - Service Impl · Concrete service implementations placeholder
src/main/java/pe/utp/edu/vacunacioncard/service/impl/.gitkeep - Repositories · Persistence abstraction placeholder
src/main/java/pe/utp/edu/vacunacioncard/repository/.gitkeep
Domain
Business capabilities modeled in the monolith
- Usuario · Base user model and roles
src/main/java/pe/utp/edu/vacunacioncard/domain/usuario/Usuario.java - Acceso · Accounts, roles, permissions, sessions
src/main/java/pe/utp/edu/vacunacioncard/domain/auth/CuentaUsuario.java - Vacunación · Vaccines, schedules, cards and dose tracking
src/main/java/pe/utp/edu/vacunacioncard/domain/vacunacion/Vacuna.java - Citas · Appointments and availability
src/main/java/pe/utp/edu/vacunacioncard/domain/cita/CitaVacunacion.java - Campañas · Vaccination campaigns and sites
src/main/java/pe/utp/edu/vacunacioncard/domain/campania/CampaniaVacunacion.java - Salud · Conditions, allergies and contraindications
src/main/java/pe/utp/edu/vacunacioncard/domain/salud/Contraindicacion.java - Notificaciones · Reminders and system alerts
src/main/java/pe/utp/edu/vacunacioncard/domain/notificacion/Notificacion.java - Común · Shared contact, address, calendar and audit concepts
src/main/java/pe/utp/edu/vacunacioncard/domain/comun/Contacto.java
Infrastructure
Build and persistence scaffolding
- Maven Build · Dependency and lifecycle management
pom.xml - Config File · Spring application properties
src/main/resources/application.properties
Connections 19
- Maven Build → VacunacioncardApplication: builds · Maven compiles and packages the Spring Boot application
- VacunacioncardApplication → Controllers: starts · Application context hosts the web entry layer
- Controllers → Services: delegates · Controllers are intended to call application services
- Services → Service Impl: implements · Service contracts are expected to be realized by implementation classes
- Service Impl → Repositories: persists via · Services are expected to use repositories for storage access
- Controllers → Usuario: manages · User-facing flows center on patient and staff data
- Controllers → Vacunación: manages · Requests around vaccines, cards and dose history
- Controllers → Citas: manages · Appointment booking and availability flows
- Controllers → Campañas: manages · Campaign and site management flows
- Controllers → Notificaciones: manages · Reminder and alert flows
- Services → Acceso: coordinates · Access control is a separate business slice
- Services → Salud: coordinates · Eligibility and contraindication checks
- Vacunación → Usuario: belongs to · Vaccination records are anchored on the user/patient model
- Vacunación → Campañas: uses · Vaccination activity may occur through campaigns and sites
- Citas → Común: uses · Schedules and time/address primitives come from shared concepts
- Campañas → Común: uses · Campaigns and centers reuse shared contact/address data
- Usuario → Común: uses · People models reuse shared contact and address value objects
- Notificaciones → Común: uses · Notifications and audit traces share common primitives
- VacunacioncardApplication → Config File: configures · Application startup is driven by Spring properties