How sant1jmnz/proyect-berea works
Dermalia combines a Qt terminal for patients, a Qt reception/management app, and a web booking site, backed by MySQL with local fallback in the desktop apps. The principal workflow is choosing protocols, finding an available time, confirming a booking with an optional simulated deposit, then looking up or cancelling the appointment. Management adds patient, professional, protocol, schedule, and business-record capabilities. The README also describes reminders, price search, AI assistance, coupons, and gift cards; some are documented capabilities whose implementation links are not shown in the excerpts.
Main entry points: gestion Management pages · ventanacliente.cpp Patient terminal · ventanagestion.cpp Management app · reservar.js Web booking
Components 23
Booking channels
- Patient terminal
frontend/cliente/ventanacliente.cpp
Shared services
- Protocol catalogue
web/src/datos/protocolos.js - Database connection
frontend/comun/basedatos.cpp - Stored procedure repository
frontend/comun/repositorio.cpp - MySQL database
- Connection and fallback
frontend/comun/conexionapp.cpp - Local JSON store
frontend/gestion/almacenlocal.cpp - Appointment reminders
frontend/comun/recordatorios.cpp
Reception management
- Management app
frontend/gestion/ventanagestion.cpp - Management pages
frontend/gestion - Coupons and gift cards
frontend/gestion/paginacupones.cpp - Patient records
frontend/gestion/paginapacientes.cpp - Professional schedules
frontend/gestion/paginaprofesionales.cpp - Protocol management
frontend/gestion/paginaprotocolos.cpp - Reports and evaluations
frontend/gestion/paginareportes.h
Web experience
- Web booking
web/src/js/paginas/reservar.js - Booking API client
web/src/datos/api.js - Web API server
web/api/servidor.js - Local reservations
web/src/datos/reservas.js - Price and protocol search
web/src/js/paginas/protocolos.js - Institute information assistant
Other components
- Patient
- Reception staff
Connections 26
- Patient → Patient terminal: uses
- Patient → Web booking: books through
- Reception staff → Management app: records bookings
- Patient terminal → Stored procedure repository: queries and saves
- Patient terminal → Connection and fallback: connects through
frontend/cliente/ventanacliente.cpp - Patient terminal → Local JSON store: uses offline
- Management app → Management pages: creates
frontend/gestion/ventanagestion.cpp - Management app → Stored procedure repository: uses
frontend/gestion/ventanagestion.cpp - Management app → Connection and fallback: connects through
frontend/gestion/ventanagestion.cpp - Management app → Local JSON store: uses offline
- Management pages → Patient records: includes
- Management pages → Professional schedules: includes
frontend/gestion/paginaprofesionales.cpp - Management pages → Protocol management: includes
- Management pages → Coupons and gift cards: includes
- Management pages → Reports and evaluations: includes
frontend/gestion/ventanagestion.cpp - Web booking → Booking API client: requests availability
web/src/js/paginas/reservar.js - Web booking → Booking API client: submits booking
web/src/js/paginas/reservar.js - Web booking → Local reservations: saves fallback
web/src/js/paginas/reservar.js - Web booking → Protocol catalogue: reads protocols
web/src/js/paginas/reservar.js - Booking API client → Web API server: calls
- Stored procedure repository → Database connection: executes procedures through
- Database connection → MySQL database: connects and queries
- Connection and fallback → Database connection: manages connection
- Patient terminal → Appointment reminders: uses
- Patient → Price and protocol search: searches
- Patient → Institute information assistant: asks