How elis3o2/infancias works
This is a case-management application for receiving and processing requests concerning children/adolescents: users submit contact, institution, people, family, and supporting-document data; staff review and validate or reject requests, with person histories and reporting as adjacent workflows. The frontend route table exposes request, history, search, and report screens. Backend models represent requests, people, and locations, while integrations include external identity and clinical-history services. Evidence is limited to the supplied excerpts and SOURCE INDEX; several backend view-to-service and frontend-to-backend links cannot be verified here.
Main entry points: AppRoutes.tsx Application routes · models.py Request records · solicitud/serializers.py Request serializers · persona/serializers.py Person serializers
Components 22
User workflows
- Application routes
frontend/src/routes/AppRoutes.tsx - Request creation
frontend/src/pages/CreatePage/CreatePage.tsx - Submit request
frontend/src/pages/CreatePage/useSolicitudCreate.ts - Request review
frontend/src/features/solicitud/components/Cargados/validacion/useSolicitudValidacion.ts - Person workflows
frontend/src/features/persona/api.ts - Child history
frontend/src/pages/HistorialNinoPage.tsx - Reports
frontend/src/pages/ReportesPage.tsx
Request processing
- Request API client
frontend/src/features/solicitud/api.ts - Request operations
backend/src/apps/solicitud/services/Validacion.py - Request serializers
backend/src/apps/solicitud/serializers.py - Request records
backend/src/apps/solicitud/models.py - Report generation
backend/src/apps/solicitud/services/Reporte.py
People and records
- Person serializers
backend/src/apps/persona/serializers.py - Person records
backend/src/apps/persona/models.py - Location records
backend/src/apps/domicilio/models.py - Location serializers
backend/src/apps/domicilio/serializers.py
External services
- Clinical history lookup
frontend/src/features/api_externa/useHistoriasClinicas.ts - Clinical history client
frontend/src/features/api_externa/historiasClinicas.ts - Identity integration
backend/src/apps/api_externa/services/Renaper.py - External contracts
backend/src/apps/api_externa/clases.py
Other components
- Staff user
- MySQL database
Connections 21
- Staff user → Application routes: uses
frontend/src/routes/AppRoutes.tsx - Application routes → Request creation: routes to
frontend/src/routes/AppRoutes.tsx - Application routes → Child history: routes to
frontend/src/routes/AppRoutes.tsx - Application routes → Reports: routes to
frontend/src/routes/AppRoutes.tsx - Application routes → Request review: routes to
frontend/src/routes/AppRoutes.tsx - Request creation → Submit request: uses
- Submit request → Request API client: submits via
frontend/src/pages/CreatePage/useSolicitudCreate.ts - Request review → Request API client: validates via
frontend/src/features/solicitud/components/Cargados/validacion/useSolicitudValidacion.ts - Request serializers → Person serializers: uses
backend/src/apps/solicitud/serializers.py - Request serializers → Location serializers: uses
backend/src/apps/solicitud/serializers.py - Request serializers → Request records: serializes
backend/src/apps/solicitud/serializers.py - Person serializers → Person records: serializes
backend/src/apps/persona/serializers.py - Person serializers → Location serializers: uses
backend/src/apps/persona/serializers.py - Location serializers → Location records: serializes
backend/src/apps/domicilio/serializers.py - Request records → Location records: references
backend/src/apps/solicitud/models.py - Person records → Location records: references
backend/src/apps/persona/models.py - Clinical history lookup → Clinical history client: queries through
frontend/src/features/api_externa/useHistoriasClinicas.ts - Reports → Report generation: requests
- Request operations → Request records: updates
- Request records → MySQL database: stored in
- Identity integration → External contracts: uses contracts
backend/src/apps/api_externa/services/Renaper.py