How valeaza710/tp_integrador_dao works
This is a Spanish-language medical-practice management web application. The principal workflow is patients booking appointments against doctors’ schedules; the backend manages appointment slots and persists records in SQLite. Other documented capabilities include patient/doctor administration, clinical histories and prescriptions, and reporting. The graph follows the sampled appointment flow and README capabilities; several subsystem links rely on the SOURCE INDEX, while frontend-to-API wiring is not shown in the excerpts.
Main entry points: main.py Application entry · connection.py SQLite database · agenda_turno_service.py Appointment workflow · receta_service.py Clinical records
Components 25
Web interface
- Appointment booking
frontend/static/js/agendarCita.js - Administration UI
frontend/static/js/gestorAdministrador.js - Clinical history UI
frontend/static/js/historialClinico.js - Reports UI
frontend/static/js/reportes.js - Page routes
frontend/views/frontend_routers.py
API workflows
- Application entry
main.py - Appointment endpoints
backend/routers/agenda_turno_routers.py - Patient endpoints
backend/routers/paciente_routers.py - Doctor endpoints
backend/routers/medico_routers.py - Prescription endpoints
backend/routers/receta_routers.py - Report endpoints
backend/routers/reportes_routers.py
Clinical operations
- Appointment workflow
backend/services/agenda_turno_service.py - Doctor schedules
backend/services/horario_medico_service.py - Patient management
backend/services/paciente_service.py - Clinical records
backend/services/receta_service.py - Report generation
backend/services/reportes_service.py - Doctor management
backend/services/medico_service.py
Persistence
- Appointment records
backend/repository/agenda_turno_repository.py - Schedule records
backend/repository/horario_medico_repository.py - Patient records
backend/repository/paciente_repository.py - Prescription records
backend/repository/receta_repository.py - Clinical history records
backend/repository/historial_clinico_repository.py - Report queries
backend/repository/reportes_repository.py - SQLite database
backend/data_base/connection.py
Other components
- Patient or staff
Connections 30
- Patient or staff → Appointment booking: books appointment
- Appointment booking → Appointment endpoints: submits booking
- Patient or staff → Administration UI: manages records
- Patient or staff → Clinical history UI: views history
- Patient or staff → Reports UI: views reports
- Application entry → Page routes: registers pages
main.py - Application entry → Appointment endpoints: registers routes
main.py - Application entry → Patient endpoints: registers routes
main.py - Application entry → Doctor endpoints: registers routes
main.py - Application entry → Prescription endpoints: registers routes
main.py - Application entry → Report endpoints: registers routes
main.py - Appointment endpoints → Appointment workflow: calls service
backend/routers/agenda_turno_routers.py - Patient endpoints → Patient management: calls service
backend/routers/paciente_routers.py - Doctor endpoints → Doctor management: calls service
backend/routers/medico_routers.py - Prescription endpoints → Clinical records: calls service
backend/routers/receta_routers.py - Report endpoints → Report generation: calls service
backend/routers/reportes_routers.py - Appointment workflow → Appointment records: reads and writes
backend/services/agenda_turno_service.py - Appointment workflow → Patient records: looks up patient
backend/services/agenda_turno_service.py - Doctor schedules → Appointment records: checks appointments
backend/services/horario_medico_service.py - Doctor schedules → Schedule records: manages schedules
backend/services/horario_medico_service.py - Patient management → Patient records: manages patients
backend/services/paciente_service.py - Clinical records → Prescription records: saves prescriptions
backend/services/receta_service.py - Clinical records → Clinical history records: uses history
backend/services/receta_service.py - Report generation → Report queries: requests reports
backend/services/reportes_service.py - Appointment records → SQLite database: queries SQLite
backend/repository/agenda_turno_repository.py - Schedule records → SQLite database: queries SQLite
backend/repository/horario_medico_repository.py - Patient records → SQLite database: queries SQLite
backend/repository/paciente_repository.py - Prescription records → SQLite database: queries SQLite
backend/repository/receta_repository.py - Clinical history records → SQLite database: queries SQLite
backend/repository/historial_clinico_repository.py - Report queries → SQLite database: queries SQLite
backend/repository/reportes_repository.py