How roopaskumar7/gamuts-guru-intern works
Project type and purpose
• This is a full-stack Django web application named “Hospital Management System.”
• Purpose: Provide distinct interfaces and workflows for Admin, Doctor, and Patient roles to manage hospital operations (registration, appointment, discharge, billing).
File structure
• Top-level:
• manage.py – entry point for Django commands
• hospitalmanagement/ – Django project settings (ASGI/WSGI, settings.py, urls.py)
• hospital/ – Django app containing models, views, forms, admin config, migrations
• templates/ – Jinja2-style HTML templates for each user role
• static/ – CSS, images, profile pictures, screenshots
• requirement.txt – external Python dependencies
• Patterns:
• Follows Django’s MVC (Model-View-Template) pattern
• Single monolithic code base (no microservices)
• Separate templates per role under templates/hospital
• Uses Django ORM (models.py + migrations) for database interactions
• Uses xhtml2pdf for PDF invoice generation, SMTP for Contact Us email
Readme insights
• Three user personas with role-based approval workflows
• Email configuration for contact form in settings.py
• Steps to run: pip install, makemigrations, migrate, runserver
• Drawbacks: no admin approval, demo purpose only
Detailed element checklist
• “Forms” —> “Models” —> “Database”
• If generating invoice: “xhtml2pdf”
• If sending email: “SMTP Mail Server”
• Template Engine receives data from Views and returns “HTML + CSS”
• Static file server/network path to client