How mudiambat13/doctor works
MediConnect is documented as a patient–doctor teleconsultation platform with account roles and customizable profiles. The available source confirms patient registration/profile and appointment/consultation form stages, and settings configure SQLite persistence and JWT authentication. The views, URL configuration, and model definitions are present in the tree but were not sampled, so their runtime wiring and detailed consultation flow cannot be verified; the graph avoids asserting those links.
Main entry points: models.py Health records · views.py Request handlers · forms.py Account and profile forms · settings.py Django settings
Components 10
Access and roles
- Account and profile forms
core/forms.py
Care workflows
- Care forms
core/forms.py - Health records
core/models.py
Application platform
- Project routes
doctor_project/urls.py - Core routes
core/urls.py - Request handlers
core/views.py - Django settings
doctor_project/settings.py - SQLite database
doctor_project/settings.py
Other components
- Patient
- Doctor
Connections 5
- Patient → Request handlers: uses platform
- Doctor → Request handlers: uses platform
- Account and profile forms → Health records: creates patient
- Care forms → Health records: uses models
- Django settings → SQLite database: configures