1️⃣ Objective
The objective of this capstone is to design, develop, and implement a comprehensive Hospital Management System (HMS). This web-based platform will serve as a central system for managing crucial hospital operations, including Patient Records (EHR), appointment scheduling, billing, and staff management, aiming to improve administrative efficiency, reduce human error, and enhance patient care coordination.
Key Goals:
✨ Develop secure Patient Registration and EHR modules adhering to basic data privacy principles (e.g., mock HIPAA/GDPR compliance).
✨ Implement a dynamic Appointment Scheduling System for doctors and departments, including availability tracking.
✨ Create a Billing and Inventory Module for managing services rendered, generating invoices, and tracking pharmaceutical stock.
✨ Design role-based access control for different user types (Admin, Doctor, Receptionist, Patient).
✨ Provide a Reporting Dashboard for administrators to monitor hospital performance metrics (e.g., patient turnover, revenue).
2️⃣ Problem Statement
Many small to medium-sized hospitals and clinics still rely on inefficient, disjointed systems or manual, paper-based processes for critical functions like patient record-keeping, billing, and scheduling. This leads to long wait times, data redundancy, difficulties in tracking medication and inventory, and a high risk of medication and administrative errors.
This project addresses the fragmentation and inefficiency by consolidating all core operational data and workflows into a single, integrated digital platform. The HMS will provide a secure, real-time environment, ensuring that staff have immediate access to accurate patient history, appointments, and billing information, thereby improving throughput and data security.
3️⃣ Methodology
The project will be developed using an agile approach, focusing on modular development for clear separation of concerns:
✨ Phase 1 — Foundation & Authentication: Set up the database schema and implement a secure user authentication system with clear role definitions (Admin, Doctor, etc.).
✨ Phase 2 — Patient and EHR Module: Develop forms for patient registration and modules for securely viewing, creating, and updating patient medical history (diagnoses, prescriptions, notes).
✨ Phase 3 — Scheduling Module: Implement complex scheduling logic, allowing patients to book appointments, doctors to manage their availability, and receptionists to handle walk-ins and cancellations.
✨ Phase 4 — Billing & Inventory: Create a module that automatically generates a bill based on services rendered in the EHR, and a separate module for tracking pharmaceutical stock and expiry dates.
✨ Phase 5 — Testing & Deployment: Conduct unit and integration testing. Deploy the finalized application in a secure, containerized environment (Docker).
4️⃣ Dataset
Core Entities:
✨ Patients: Demographic data, contact info, unique medical ID.
✨ Staff: Login credentials, role (Doctor, Nurse, Admin), specialty/department.
✨ Appointments: Patient ID, Doctor ID, Date/Time, Status (Scheduled, Completed, Cancelled).
✨ Medical Records: Diagnosis (ICD-10 code mock), Prescriptions, Vitals, Notes (linked to Patient ID and Doctor ID).
Patient Records Table (Sample):
| Entity | Key Attributes | Relationship Focus |
|---|---|---|
| User | User ID, Email, Role (Student/Instructor) | One-to-Many (Orders, Progress) |
| Course | Course ID, Title, Instructor ID (FK) | One-to-Many (Modules, Enrollments) |
| Lesson/Quiz | Lesson ID, Module ID (FK), Content URL, Type | Hierarchy (Course → Module → Lesson) |
| Progress | User ID (FK), Lesson ID (FK), Completed (Boolean), Score | Many-to-Many (Tracking) |
| Enrollment | User ID (FK), Course ID (FK), Date Enrolled | Many-to-Many (Associative) |
5️⃣ Tools and Technologies
| Category | Tools / Libraries |
|---|---|
| Frontend & UI | React / Vue.js / Angular, HTML5, CSS (Tailwind or Bootstrap) |
| Backend & API | Node.js (Express) / Python (Django/Flask) / Java (Spring Boot) |
| Database & ORM | PostgreSQL / MongoDB (for content), Sequelize / JPA / Mongoose |
| Authentication/Security | JWT (JSON Web Tokens), OAuth 2.0, Password Hashing (Bcrypt) |
| Deployment & Tools | Docker, AWS EC2 / Vercel / Netlify, Git / GitHub |
6️⃣ Evaluation Metrics
✨ API Latency: Average time for content and progress retrieval (Target: $< 150$ ms).
✨ Progress Accuracy: Percentage of correctly tracked progress updates compared to expected completion.
✨ Quiz Grading Precision: Accuracy of the automated quiz grading engine.
✨ Security Validation: Successful implementation of RBAC, ensuring students cannot access instructor/admin resources.
✨ Code Quality & Coverage: Adherence to coding standards and test coverage for core business logic.
7️⃣ Deliverables
| Deliverable | Description |
|---|---|
| Deployed LMS Application | Live, functional web application with content, enrollment, and progress tracking. |
| RESTful API & Backend Services | Secure backend to manage users, courses, and handle progress updates. |
| Course Structure & Content Models | Database schema (DDL/ORM models) for the nested Course/Module/Lesson hierarchy. |
| Instructor/Admin Console | Dedicated interface for instructors to manage courses and view student metrics. |
| Technical Documentation | API reference, data model map, and deployment guide. |
8️⃣ System Architecture Diagram
Student / Learner Portal
Video consumption, course navigation, submitting quizzes/assignments.
Instructor / Creator Dashboard
Uploading content, creating tests, monitoring student analytics, grading.
Admin & Curriculum Console
User provisioning, managing course catalog, compliance and reporting.
Content Delivery & Streaming Service
Handles video encoding, adaptive bitrate streaming, and Digital Rights Management (DRM).
Assessment & Grading Engine
Executes quiz logic, handles submission processing, and calculates final scores.
Progress Tracking & Certification Service
Tracks lesson completion status, time spent, and issues verifiable certificates.
Media Asset Storage (e.g., Cloud Storage)
Securely hosts large files like course videos, PDFs, and high-resolution images.
Relational Database (e.g., PostgreSQL)
Stores structured data: course metadata, user profiles, and test results.
Payment Gateway Integration
Handles secure enrollment transactions, subscription billing, and refund processing.
Final Outcome: Scalable, Interactive, and Secure Learning Environment
Facilitates continuous learning, effective content monetization, and actionable pedagogical insights.
Student / Learner Portal
Video consumption, course navigation, submitting quizzes/assignments.
Instructor / Creator Dashboard
Uploading content, creating tests, monitoring student analytics, grading.
Admin & Curriculum Console
User provisioning, managing course catalog, compliance and reporting.
Content Delivery & Streaming Service
Handles video encoding, adaptive bitrate streaming, and Digital Rights Management (DRM).
Assessment & Grading Engine
Executes quiz logic, handles submission processing, and calculates final scores.
Progress Tracking & Certification Service
Tracks lesson completion status, time spent, and issues verifiable certificates.
Media Asset Storage (e.g., Cloud Storage)
Securely hosts large files like course videos, PDFs, and high-resolution images.
Relational Database (e.g., PostgreSQL)
Stores structured data: course metadata, user profiles, and test results.
Payment Gateway Integration
Handles secure enrollment transactions, subscription billing, and refund processing.
Final Outcome: Scalable, Interactive, and Secure Learning Environment
Facilitates continuous learning, effective content monetization, and actionable pedagogical insights.
9️⃣ Expected Outcome
✨ A fully operational, deployed LMS demonstrating proficiency in full-stack application development and complex data modeling.
✨ Demonstrated understanding of User Authentication, Role-Based Authorization, and State Management (progress tracking).
✨ A robust codebase with clear separation of concerns (Model, View, Controller) and strong emphasis on maintainability.
✨ An interactive user experience for both consuming and managing educational content.