How kaxarovv/rt-queue works
RT Queue supports clinical staff managing radiotherapy intake, prioritization, and scheduling. The main workflow is document upload and extraction, clinician review, case/queue management, then proposed start dates or machine-slot booking. Patient CRUD and dashboard reporting are additional capabilities. The graph includes the available frontend as well as the documented backend; some service relationships rely on the SOURCE INDEX or README rather than inspected implementation excerpts. README notes that several scheduling capabilities are demo-stage, and OCR for scanned PDFs is not implemented.
Main entry points: router.py Document endpoints · App.tsx Screen navigation · models.py Treatment cases · client.ts API client
Components 30
Clinical interface
- Screen navigation
frontend/src/App.tsx - Document review
frontend/src/features/document-upload/ReviewPanel.tsx - Patient management
frontend/src/features/patients/PatientsScreen.tsx - Queue view
frontend/src/features/queue/QueueScreen.tsx - Schedule view
frontend/src/features/scheduling/SchedulingScreen.tsx - Dashboard
frontend/src/features/dashboard/DashboardScreen.tsx - API client
frontend/src/shared/api/client.ts
Document intake
- Document endpoints
backend/app/domains/documents/router.py - PDF text extraction
backend/app/domains/documents/text_extraction_service.py - Regex extraction
backend/app/domains/documents/regex_extraction_service.py - Clinical extraction
backend/app/domains/documents/llm_extraction_service.py - Signal conflict detection
backend/app/domains/documents/conflict_detection.py - Document storage
backend/app/domains/documents/storage_service.py
Patients and queue
- Patient endpoints
backend/app/domains/patients/router.py - Treatment case endpoints
backend/app/domains/treatment_cases/router.py - Queue operations
backend/app/domains/treatment_cases/queue_service.py - Priority scoring
backend/app/domains/treatment_cases/priority_engine.py - Patient records
backend/app/domains/patients/models.py - Treatment cases
backend/app/domains/treatment_cases/models.py
Scheduling
- Scheduling endpoints
backend/app/domains/scheduling/router.py - Slot booking
backend/app/domains/scheduling/booking_service.py - Capacity service
backend/app/domains/scheduling/capacity_service.py - Displacement candidates
backend/app/domains/scheduling/displacement_engine.py - Slots and sessions
backend/app/domains/scheduling/models.py
Application platform
- HTTP application
backend/app/main.py - Database sessions
backend/app/core/database.py
Other components
- Clinical staff
- LLM service
- S3-compatible store
- PostgreSQL
Connections 42
- Clinical staff → Screen navigation: uses
frontend/src/App.tsx - Screen navigation → Document review: opens
frontend/src/App.tsx - Screen navigation → Patient management: opens
frontend/src/App.tsx - Screen navigation → Queue view: opens
frontend/src/App.tsx - Screen navigation → Schedule view: opens
frontend/src/App.tsx - Screen navigation → Dashboard: opens
frontend/src/App.tsx - Document review → API client: requests
frontend/src/features/document-upload/ReviewPanel.tsx - Patient management → API client: requests
frontend/src/features/patients/PatientsScreen.tsx - Queue view → API client: requests
frontend/src/features/queue/QueueScreen.tsx - Schedule view → API client: requests
frontend/src/features/scheduling/SchedulingScreen.tsx - Dashboard → API client: requests
frontend/src/features/dashboard/DashboardScreen.tsx - API client → HTTP application: calls endpoints
frontend/src/shared/api/client.ts - HTTP application → Document endpoints: registers
backend/app/main.py - HTTP application → Patient endpoints: registers
backend/app/main.py - HTTP application → Treatment case endpoints: registers
backend/app/main.py - HTTP application → Scheduling endpoints: registers
backend/app/main.py - Document endpoints → PDF text extraction: extracts text
backend/app/domains/documents/router.py - Document endpoints → Regex extraction: extracts entities
backend/app/domains/documents/router.py - Document endpoints → Clinical extraction: extracts fields
backend/app/domains/documents/router.py - Document endpoints → Signal conflict detection: checks conflicts
backend/app/domains/documents/router.py - Document endpoints → Document storage: stores files
backend/app/domains/documents/router.py - Document storage → S3-compatible store: reads and writes
backend/app/domains/documents/storage_service.py - Clinical extraction → LLM service: calls extraction
README.md - Patient endpoints → Patient records: queries
backend/app/domains/patients/router.py - Treatment case endpoints → Queue operations: delegates
backend/app/domains/treatment_cases/router.py - Treatment case endpoints → Priority scoring: computes score
backend/app/domains/treatment_cases/router.py - Queue operations → Priority scoring: scores cases
backend/app/domains/treatment_cases/queue_service.py - Queue operations → Treatment cases: queries
backend/app/domains/treatment_cases/queue_service.py - Patient records → Treatment cases: relates cases
backend/app/domains/patients/models.py - Scheduling endpoints → Slot booking: delegates booking
backend/app/domains/scheduling/router.py - Scheduling endpoints → Capacity service: checks capacity
backend/app/domains/scheduling/router.py - Scheduling endpoints → Displacement candidates: finds candidates
backend/app/domains/scheduling/router.py - Slot booking → Capacity service: checks capacity
backend/app/domains/scheduling/booking_service.py - Slot booking → Slots and sessions: books slots
backend/app/domains/scheduling/booking_service.py - Displacement candidates → Slots and sessions: queries sessions
backend/app/domains/scheduling/displacement_engine.py - Displacement candidates → Treatment cases: compares priority
backend/app/domains/scheduling/displacement_engine.py - Scheduling endpoints → Treatment cases: queries cases
backend/app/domains/scheduling/router.py - Treatment cases → Patient records: relates patient
backend/app/domains/treatment_cases/models.py - Treatment cases → Slots and sessions: relates sessions
backend/app/domains/treatment_cases/models.py - Document endpoints → Database sessions: uses sessions
backend/app/domains/documents/router.py - Patient endpoints → Database sessions: uses sessions
backend/app/domains/patients/router.py - Database sessions → PostgreSQL: connects
backend/app/core/database.py