TULSIRAMJI GAIKWAD-PATIL College of Engineering and Technology
Wardha Road, Nagpur - 441108
Accredited with NAAC A+ Grade
Approved by AICTE, New Delhi, Govt. of Maharashtra
(An Autonomous Institute Affiliated to RTM Nagpur University, Nagpur)
---------------------------------------------------------------------------------------------------------------------------------------
Department of Information Technology
---------------------------------------------------------------------------------------------------------------------------------------
Date: 09/04/2025
Session 2024-25
Programme: - B.Tech. (Information Technology)
Assignment -2
Course Name: - BIT32405: Database Management System
Name:- Triveni Naneshwar Patle
Semester:- Fourth
Roll No:- 40
Aim: - To enable students to design an Entity-Relationship (ER) Diagram for a Hospital Management
System, helping them understand the principles of database modeling and conceptual design.
Objective:-
a) To help students understand Entity-Relationship (ER) Diagrams.
b) To develop problem-solving and database design skills.
c) To encourage teamwork and creativity in designing ER models.
Methodology:-
a) Introduction & Conceptual Discussion
Briefly introduce the importance of ER diagrams in hospital database systems.
Explain key concepts:
Entities (Patient, Doctor, Appointment, Bill, Medicine, Room)
Attributes (Patient_ID, Name, Age, Specialization, Date, Amount, etc.)
Relationships (One-to-One, One-to-Many, Many-to-Many)
Primary & Foreign Keys (Unique identifiers and database connections) Use
real-world examples or an interactive Q&A session to engage students.
b) Brainstorming & Concept Mapping:
Students identifies essential hospital entities and their relationships.
They create a rough concept map on a whiteboard or paper before designing the ER diagram.
Drafting the ER Diagram using digital Platform
Er Diagram:
Entities and Their Attributes
1. Patient
• Attributes: o Name: The patient's full name.
o DOB: Date of birth. o Gender: Male, Female, etc.
2. Doctor
• Attributes: o Address: Where the doctor resides or can be
contacted.
o Specialization: Doctor's area of expertise (e.g., cardiologist, neurologist). o
Phone: Contact number.
3. Medical_Record
• Attributes: o Diagnosis: The diagnosis given to the patient. o
Treatment: The treatment provided for the diagnosis.
4. Admission
• Attributes:
o Admission_ID: Unique ID for each admission. o Admil_Date (typo, should be
Admission_Date): Date the patient was admitted.
o Bill_ID: Billing identification number. o Admlision_ifa (typo, should likely be
Admission_Info): Additional admission info. o Discharge_Date: Date the
patient was discharged. o Status: Admission status (e.g., active, discharged,
under treatment).
5. Room
• Attributes:
o Room_ID: Unique room number or identifier. o Type: Type of room (e.g.,
ICU, General, Private). o B’telog sc (typo, possibly Belongs to Section or
Belongs to Category): Refers to which section or department the room belongs
to.
Relationships Between Entities
1. Books (between Patient and Doctor)
• Indicates that a Patient books an appointment with a Doctor.
2. Has (between Doctor and Medical_Record)
• Shows that a Doctor has a Medical Record (likely of a Patient).
3. Admitted (between Admission and Medical_Record)
• Connects Admission to Medical_Record. A patient’s medical record is linked to their hospital admission.
4. Belongs to (between Medical_Record and Room)
• Specifies that the Medical_Record is associated with a Room—probably where the patient was treated
or admitted.
Additional Notes
• Duplicate Entity Box (Admission): The Admission entity appears twice in the diagram. This is most
likely for layout/clarity purposes to show separate sets of attributes and relationships (Admission Date vs
Billing Info).
• Typo Corrections:
o Admil_Date → Admission_Date o
Admlision_ifa → Admission_Info o Diagnos →
Diagnosis o B’telog sc → Possibly Belongs To
Section/Category
Summary of Workflow
1. A Patient books an appointment with a Doctor.
2. The Doctor creates a Medical_Record for the patient including diagnosis and treatment.
3. The Patient is Admitted (creates an Admission record) based on the treatment needs.
4. The Admission links to a Room, where the patient stays.
5. Billing, discharge date, and status are recorded under Admission.
Outcomes:
By the end of this activity, students will be able to:
✅ Understand ER diagram principles and how they apply to real-world hospital management systems.
✅ Effectively identify entities, attributes, and relationships in a database system.
✅ Create well-structured ER diagrams with correct primary keys, foreign keys, and cardinality.
✅ Develop teamwork, communication, and presentation skills through group collaboration.
✅ Apply database modeling concepts to future projects, such as designing SQL databases.
Course Coordinator HoD, (IT)
