Scribd
Upload
27 views8 pages

Practical 2

Uploaded by

sanyamch333
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
27 views8 pages

Practical 2

Uploaded by

sanyamch333
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

PRACTICAL-02

ER Model of Hospital Management System.

REPRESENTATION OF ER DIAGRAM

ENTITIES and ATTRIBUTES

1ENTITIES and ATTRIBUTES

1. Patient

P-ID: Unique identifier for each Patient

Name: Name of the Patient

DOB: Date of birth of the Patient

Gender: Gender of the Patient

Mob-No: Contact number of the Patient

Age: Age of the Patient

Interactive Prompt:
How would you handle a situation where two patients have the same name? What
attributes could you use to ensure uniqueness in the database?

---

2. Employee

E-ID: Unique identifier for each Employee

Name: Name of the Employee

Salary: Salary of the Employee

Sex: Gender of the Employee

Mob-No: Contact number of the Employee

Address: Address of the Employee

State: State of the Employee

City: City of the Employee

Pin–no: Postal code of the Employee


Interactive Prompt:

Imagine the system must track employee shifts as well. Which attributes or new entities
could you introduce to manage shift schedules?

---

3. Doctor (inherits from Employee)

E-ID (Foreign Key referencing Employee)

Department: Department of the Doctor

Qualification: Qualification of the Doctor

Interactive Scenario:

A doctor is assigned to multiple departments on different days. How would you model
this scenario using the ER diagram?

---
4. Nurse (inherits from Employee)

E-ID: E-ID is a foreign key linking the Nurse to the Employee table through the
Employee ID.

Interactive Prompt:

What additional attributes might you need for nurses, such as certifications or specific
wards they are assigned to?

---

5. Room

R-ID: Unique identifier for each room

Type: Defines the quality of the room (e.g., deluxe, private, general)

Capacity: Number of people the room can accommodate

Availability: Shows the availability of the room

Interactive Question:
If you needed to track when a room is cleaned after each patient, where would you add
that information in the ER diagram?

---

6. Receptionist (inherits from Employee)

E-ID: Foreign key referencing Employee

Interactive Prompt:

Receptionists often handle multiple tasks such as appointment scheduling and billing.
What additional tables or attributes could you add to model their role?

---

7. Test Report

R-ID (Primary Key): Unique identifier for each test report

P-ID (Foreign Key referencing Patient): References the Patient table based on the
Patient ID
Test Type: Type of test performed

Result: Outcome of the test

Interactive Scenario:

Imagine multiple test results for the same patient. How could you structure your
database to manage this effectively?

---

8. Bill

B-ID: Unique identifier for each bill

P-ID (Foreign Key referencing Patient): Links the bill to a specific patient

Amount: The total amount the patient must pay

Interactive Scenario:

Sometimes patients may receive multiple bills (e.g., one for room charges and another
for tests). How would you modify the bill entity to handle this?
---

9. Records

Record-no: Unique number for each patient record

App-no: Appointment number for each patient

Interactive Thought:

If you needed to add historical data, such as a log of past treatments for each patient,
how would you expand the ER diagram to include this?

You might also like