How thangallapallysiddu-10/secure-storage-system-for-medical-image-data works
SecureMedicalImage is a Django medical-image vault for patients, doctors, and administrators. Patients register, await administrator activation, log in, upload image records, and review their own records; uploads are saved under media storage and recorded with blockchain-style transaction data. Doctors authenticate by mobile number plus an OTP and view records assigned to them. Administrators activate users, manage doctors, and inspect the audit log. The views and URL routing are sampled; the README describes verification and hash chaining, but the blockchain implementation and model definitions were not sampled, so their internals are not expanded.
Main entry points: users/views.py Patient actions · urls.py URL router · doctors/views.py Doctor actions · admins/views.py Admin actions
Components 19
Web entry
- URL router
SecureMedicalImage/urls.py - Site pages
SecureMedicalImage/views.py - Patient screens
assets/templates/users - Doctor screens
assets/templates/dctrs - Admin screens
assets/templates/admins - OTP screen
assets/templates/otpCheck.html
Identity and roles
- Patient actions
users/views.py - Doctor actions
doctors/views.py - Admin actions
admins/views.py - Registration form
users/forms.py - User accounts
users/models.py - Doctor records
users/models.py
Medical records
- Image records
users/models.py - Image files
media/files
Audit trail
- Chain logic
users/blkchain.py - Audit transactions
users/models.py
Other components
- Patient
- Doctor
- Administrator
Connections 24
- Patient → URL router: requests pages
- Doctor → URL router: requests pages
- Administrator → URL router: requests pages
- URL router → Site pages: dispatches pages
- URL router → Patient actions: dispatches actions
- URL router → Doctor actions: dispatches actions
- URL router → Admin actions: dispatches actions
- Site pages → Patient screens: renders pages
- Patient actions → Registration form: validates registration
- Patient actions → User accounts: reads and writes
- Patient actions → Doctor records: looks up doctors
- Patient actions → Image records: creates and reads
- Patient actions → Image files: saves uploads
- Patient actions → Chain logic: creates blocks
- Patient actions → Audit transactions: stores transactions
- Patient actions → Patient screens: renders pages
- Doctor actions → Doctor records: checks doctor
- Doctor actions → Image records: reads assigned records
- Doctor actions → Doctor screens: renders pages
- Doctor actions → OTP screen: renders challenge
- Admin actions → User accounts: activates users
- Admin actions → Doctor records: manages doctors
- Admin actions → Audit transactions: reads audit log
- Admin actions → Admin screens: renders pages