How danish-zaman-khan/opdpro_application works
OPDPro is a local outpatient-clinic management application: staff use its Django interface to register patients, book and document visits, then manage prescriptions, reports, and invoices. The Windows launcher initializes the local server and provides first-run administrator setup plus backup/restore controls; an optional Android WebView client is documented as requiring a separately deployed HTTPS backend. The graph preserves the README’s principal clinical and administrative areas. Edges reflect calls or model references shown in excerpts or documented setup; unshown routes and wiring are intentionally not inferred.
Main entry points: views.py Invoices and payments · desktop_launcher.py Desktop launcher · appointment/models.py Visit records · patients/models.py Patient profiles
Components 25
Local runtime
- Desktop launcher
desktop_launcher.py - Local data and backups
local_data.py - Android WebView
android/app/src/main/java/com/opdpro/mobile/MainActivity.kt
Clinic staff and patients
- Staff accounts
usermanagement/models.py - Staff administration
usermanagement/admin.py - Patient records
patients/views.py - Patient profiles
patients/models.py - Doctor profiles
doctors/forms.py
Visit care
- Appointments
appointment/views.py - Visit records
appointment/models.py - Prescriptions
prescriptions/views.py - Prescription catalogue
prescriptions/models.py - Lab and imaging reports
reports/views.py - Report records
reports/models.py
Clinic operations
- Invoices and payments
billing/views.py - Billing records
billing/models.py - Clinic configuration
settings/models.py - Staff notifications
user_notifications/context_processors.py - Notification records
user_notifications/models.py
Other components
- Clinic staff
- Clinic administrator
- Patient
- Local clinic database
- Windows user
- HTTPS backend
Connections 30
- Clinic administrator → Desktop launcher: sets up
desktop_launcher.py - Desktop launcher → Staff accounts: creates admin
desktop_launcher.py - Desktop launcher → Local data and backups: configures paths
desktop_launcher.py - Desktop launcher → Local clinic database: initializes
desktop_launcher.py - Local data and backups → Local clinic database: stores clinic data
- Windows user → Desktop launcher: opens
README.md - Clinic staff → Staff administration: manages accounts
README.md - Staff administration → Staff accounts: manages
usermanagement/admin.py - Patient → Patient records: registers
patients/views.py - Patient records → Patient profiles: reads and writes
patients/views.py - Clinic staff → Appointments: books visits
appointment/views.py - Appointments → Visit records: reads and writes
appointment/views.py - Visit records → Patient profiles: references patient
appointment/models.py - Doctor profiles → Staff accounts: edits profile
doctors/forms.py - Clinic staff → Prescriptions: creates and dispenses
prescriptions/views.py - Prescriptions → Prescription catalogue: reads and writes
prescriptions/views.py - Prescriptions → Patient profiles: selects patient
prescriptions/views.py - Prescriptions → Visit records: links visit
prescriptions/views.py - Clinic staff → Lab and imaging reports: uploads and reviews
reports/views.py - Lab and imaging reports → Report records: reads and writes
reports/views.py - Lab and imaging reports → Patient profiles: selects patient
reports/views.py - Lab and imaging reports → Visit records: links visit
reports/views.py - Clinic staff → Invoices and payments: manages billing
billing/views.py - Invoices and payments → Billing records: reads and writes
billing/views.py - Invoices and payments → Patient profiles: selects patient
billing/views.py - Invoices and payments → Visit records: links visit
billing/views.py - Invoices and payments → Clinic configuration: reads configuration
billing/views.py - Clinic staff → Staff notifications: views alerts
- Staff notifications → Notification records: queries unread
user_notifications/context_processors.py - Android WebView → HTTPS backend: connects to
README.md