How 2minstudio/fuel-backend works
This is a Django clinic-management application centered on patient and staff accounts, clinic schedules, appointment booking, invoicing and payment collection, with reporting and appointment communications as supporting capabilities. The principal workflow is an API request handled by the application views, which validate or serialize domain data and persist it through Django models; payment and reporting have their own view-to-domain layers. The README documents PostgreSQL and Celery operation, but sampled evidence does not establish all URL routing or asynchronous dispatch, so uncertain links are omitted or marked unverified.
Main entry points: appointment/views.py Appointment API · serializers.py Appointment serializers · models.py Appointment catalog · payment/views.py Payment API
Components 24
People and clinics
- Account API
user/views.py - Account serializers
user/serializers.py - User records
user/models.py - Clinic API
clinic/views.py - Clinic serializers
clinic/serializers.py - Clinic and hours
clinic/models.py
Appointments
- Appointment API
appointment/views.py - Appointment serializers
appointment/serializers.py - Appointment catalog
appointment/models.py
Billing and payments
- Payment API
payment/views.py - Payment serializers
payment/serializers.py - Invoices and payments
payment/models.py - Payment utilities
payment/utils.py
Communications
- Scheduled tasks
base/tasks.py - Appointment messaging
base/utils.py - Email delivery
base/helpers/email.py - SMS delivery
base/helpers/sms.py - Notification API
notification/views.py - Notifications
notification/models.py
Reporting
- Report API
report/views.py - Report calculations
report/utils.py - Report pagination
fuelapp/pagination.py
Other components
- Patient or staff
- Email service
Connections 33
- Patient or staff → Account API: sends request
- Patient or staff → Appointment API: books appointment
- Account API → Account serializers: uses
user/views.py - Account serializers → User records: validates records
user/serializers.py - Clinic API → Clinic serializers: uses
- Clinic serializers → Clinic and hours: serializes
clinic/serializers.py - Appointment API → Appointment serializers: uses
appointment/views.py - Appointment API → Appointment catalog: reads and writes
appointment/views.py - Appointment API → Account serializers: uses
appointment/views.py - Appointment API → Clinic and hours: reads
appointment/views.py - Appointment API → Payment API: calls
appointment/views.py - Appointment serializers → Appointment catalog: serializes
appointment/serializers.py - Appointment serializers → Account serializers: uses
appointment/serializers.py - Appointment serializers → Clinic serializers: uses
appointment/serializers.py - Appointment serializers → Payment utilities: uses
appointment/serializers.py - Payment API → Payment serializers: uses
payment/views.py - Payment API → Invoices and payments: reads and writes
payment/views.py - Payment API → Payment utilities: uses
payment/views.py - Payment API → Appointment catalog: reads
payment/views.py - Payment serializers → Invoices and payments: serializes
payment/serializers.py - Payment serializers → Appointment catalog: reads procedures
payment/serializers.py - Payment serializers → Clinic serializers: uses
payment/serializers.py - Report API → Report calculations: calculates reports
report/views.py - Report API → Appointment catalog: queries
report/views.py - Report API → Invoices and payments: queries
report/views.py - Report calculations → Report pagination: uses
report/utils.py - Scheduled tasks → Appointment catalog: reads appointments
base/tasks.py - Scheduled tasks → Appointment serializers: uses
base/tasks.py - Scheduled tasks → Appointment messaging: calls
base/tasks.py - Appointment messaging → Email delivery: uses
base/utils.py - Appointment messaging → SMS delivery: uses
base/utils.py - Email delivery → Email service: sends email
base/helpers/email.py - Notification API → Notifications: reads and writes
notification/views.py