How michelkas/while_health works
This is a Django healthcare-management application. Its visible patient workflow covers submitting patient and appointment information, checking appointment conflicts, and managing appointments; related domain modules model staff schedules and clinical records. The repository also has public hospital-content models, an API routing module, and asynchronous tasks for appointment emails and reports. The excerpts do not show the complete URL wiring or API behavior, so those connections are left out; the map uses only visible code and SOURCE INDEX references.
Main entry points: appointment/models.py Appointment rules · staff/models.py Staff and schedules · tasks.py Email and reports · views.py Portal views
Components 19
Web application
- Web routing
backend/config/urls.py - API routing
backend/config/api_urls.py - Portal views
backend/core/views.py - User accounts
backend/core/models.py
Patient care
- Patient workflow
backend/patients/views.py - Patient forms
backend/patients/forms.py - Patient records
backend/patients/models.py - Appointment form
backend/appointment/forms.py - Appointment rules
backend/appointment/models.py
Clinic operations
- Staff and schedules
backend/staff/models.py - Staff forms
backend/staff/forms.py - Hospital content
backend/data/models.py
Background services
- Appointment signals
backend/appointment/signals.py - Celery setup
backend/core/celery.py - Email and reports
backend/core/tasks.py
Other components
- Patient
- Clinic staff
- Application database
- Email service
Connections 26
- Patient → Patient workflow: uses portal
- Clinic staff → Portal views: uses portal
- Patient workflow → Patient forms: validates with
backend/patients/views.py - Patient workflow → Patient records: reads and saves
backend/patients/views.py - Patient workflow → Appointment rules: checks and saves
backend/patients/views.py - Patient workflow → Staff and schedules: looks up staff
backend/patients/views.py - Patient forms → Appointment form: uses
backend/patients/forms.py - Patient forms → Appointment rules: validates edits
backend/patients/forms.py - Appointment form → Appointment rules: forms model
backend/appointment/forms.py - Appointment rules → Patient records: references patient
backend/appointment/models.py - Appointment rules → Staff and schedules: references staff schedule
backend/appointment/models.py - Staff forms → Staff and schedules: forms model
backend/staff/forms.py - Hospital content → Staff and schedules: references department
backend/data/models.py - Portal views → Patient forms: uses
backend/core/views.py - Portal views → Patient records: reads records
backend/core/views.py - Portal views → Staff and schedules: reads staff
backend/core/views.py - Portal views → User accounts: uses
backend/core/views.py - Appointment signals → Email and reports: dispatches tasks
backend/appointment/signals.py - Celery setup → Email and reports: registers tasks
backend/core/celery.py - Email and reports → Patient records: reads patient data
backend/core/tasks.py - Email and reports → Appointment rules: reads appointments
backend/core/tasks.py - Email and reports → Staff and schedules: reads staff
backend/core/tasks.py - Email and reports → Email service: sends email
backend/core/tasks.py - Patient records → Application database: persists records
- Appointment rules → Application database: persists appointments
- Staff and schedules → Application database: persists schedules