Bachelor of Science in Computer Science
& Engineering
ER Diagram Report for HealthCare
Management System
by
Mahmudul Hasan
2204040
Amit Roy Antu
2204044
Avinandan Debnath
2204050
Sayanta Paul
2204052
Department of Computer Science and Engineering
Chittagong University of Engineering and Technology (CUET)
Chattogram-4349, Bangladesh
July, 2025
1
ER Diagram Report
Application for the Approval of [Link]. Engineering Project
Student Information
Name : Mahmudul Hasan
ID : 2204040
Name : Amit Roy Antu
ID : 2204044
Name : Avinandan Debnath
ID : 2204050
Name : Sayanta Paul
ID : 2204052
Session : 2022-2023
Supervisor Information
Name : Md. Atiqul Islam Rizvi
Designation : Assistant Professor
Department : Computer Science & Engineering
Project Details
Department : Computer Science and Engineering
Program : [Link]. Engineering
Tentative Title : HealthCare Management System
2
Table of Contents
Contents
Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
System Workflow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Background Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Issues with Existing Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
How DocAid Improves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3
Entity Descriptions
1.1 Users
• Stores login credentials and user roles (Admin, Doctor,Hospital, Patient).
• Attributes:user id, Email, Password, User type
1.2 Admin
• Responsible for managing doctors and moderating reviews.
• Attributes: admin id, First name, Last name
1.3 Patient
• Represents individuals booking appointments and giving reviews.
• Attributes: First name, Last name, Gender, Date of birth, Blood type, Address,
Contact no, Latitude, Longitude
1.4 Doctor
• Healthcare professional providing medical services.
• Attributes: First name, Last name, Gender, Consultation fee, Experience, Spe-
cialty, Bio, Address, Contact no, Latitude, Longitude
1.5 Hospital
• Healthcare facility offering medical services and tests.
• Attributes: Hospital name, Hospital type, Emergency phone, Address, Website,
Latitude, Longitude
1.6 Appointment
• Represents scheduled interactions between patients and doctors.
• Attributes: Patient id, Doctor id, Hospital id, Appointment date, Appointment time,
Status
4
1.7 Reviews
• Feedback given by patients about doctors.
• Attributes: Doctor id, Patient id, Rating, Comment, Review date
1.8 Doctor Schedule
• Weekly availability of doctors for appointments.
• Attributes: Doctor id, Visiting address, Visiting latitude, Visiting longitude, Vis-
iting day, Start time, End time
1.9 Specialties
• Represents medical specializations.
• Attributes: specialty id, Specialty name, Description
1.10 Medical Test
• Represents diagnostic or lab tests offered by hospitals.
• Attributes: Hospital id, Test name, Price, Description
Entity Relational Description
1. User–Admin/Doctor/Patient (IsA Relationship): Each user must be one
of Admin, Doctor, Hospital or Patient. This is a total and disjoint specialization
based on user type.
2. Admin–Reviews (Moderates): An admin can moderate many reviews. This
forms a one-to-many relationship.
3. Patient–Doctor–Reviews (Gives/Receives): A patient gives reviews to doc-
tors. Both entities have a one-to-many relationship with Reviews.
4. Patient–Appointment (Books): A patient can book multiple appointments.
One-to-many relationship.
5. Doctor–Appointment (Manages): A doctor can have multiple appointments.
One-to-many relationship.
6. Doctor–Doctor Schedule (Has): Each doctor has one scheduled visit slots.
One-to-one relationship.
5
7. Doctor–Specialties (Has Specialty): A doctor can have one [Link] mul-
tiple doctors can have one speciality. So it forms Many-to-one relationship.
8. Hospital–Medical Test (Offers): A hospital can offer multiple medical tests.
One-to-many relationship.