MediLife

MediLife is a full-featured hospital management platform built on Java Jakarta EE, covering patient registration, doctor approval workflows, appointment scheduling, billing, medical records, and administrative control across three distinct roles. Access is split between Admin, Doctor, and Patient accounts, secured with BCrypt password hashing, session-based authentication, and an admin approval workflow that gates new doctor registrations before they can accept patients.

Booking supports two flows: a Request Appointment path where an admin assigns the best-fit doctor, and a Quick Consult path for direct booking, with admin reassignment and doctor-side rejection handling built into both. The Admin Panel centralizes platform oversight: real-time statistics, doctor approvals with license review, appointment management, user lock/unlock, department management, financial reports with CSV export, system logs, and broadcast announcements.

The Doctor Portal gives physicians a dashboard of today's appointments and earnings (both total and monthly), the ability to confirm or complete appointments, add diagnoses and prescriptions, review a patient's medical history, and reject appointments with a reason. The Patient Portal covers registration with medical details and profile image upload, booking through either flow, viewing upcoming and past appointments, cancelling pending ones, and accessing full medical history.

A real-time notification bell with unread counts fires on booking, confirmation, completion, billing, account actions, assignment, and rejection events, backed by a full history page. Doctors also get individual public portfolio pages (education timeline, experience, expertise, certifications, and publications) with a book-appointment call to action gated behind a login check.

The system is built on a strict MVC architecture end-to-end: JSP views handle display only, Servlets handle routing only, Services own all business logic and validation, a DAO layer owns all database queries, Filters enforce authentication and role-based access control, and Utils hold shared helpers, keeping every layer's responsibility non-overlapping.