Illustrate an Entity-Relationship Diagram (ERD) model using Crow’s Foot notation Here we can have the following entities 1.patients:this entity will store the details of the patients and the attributes for this entity is id(which is unique for each patient and can be used as a primary key) name(this attribute will store the name of the patient and it is a composite attribute) address(this attribute will store the address of the patient and it is multi valued attribute. ) contact_num(this is also a multi valued attribute which will store the contact details of the patient). age(which is a derived attribute) 2.room:this entity will store the information about the details of the rooms. The attributes are. id(this is unique for each room and can be used as a primary key) room number(this will store the room number) Total_bed(this will store the total number of beds present in that room) 3. Bed:this entity will store the information regarding to each bed present in an room, and the attributes are id(this is unique for each bed and can be used as a primary key) Bed_num(this will store the bed number) patient_id(this will act as a foreign key which refers to the patient table) room_id(this will also act as a foreign key which refers to the room table) 4.physician:this entity will store the information of physician, and the attributes are id(this will unique for each physician and can be used as a primary key) Name(this is a composite attribute which store the first last name of the physician. contact_num(this is a multi valued attribute and store the contact number of the physician) email (this attribute will store the email address of the physician) 5.patient_record:this entity will store the medical record of the patient and have the following attributes. id(which is unique for each record and can be used as a primary key) title(this will store the title of the report) type(this will store the type of the report) description(this is a multi valued attribute and used to store the information of the report details) 6.bill:this entity will store the payment details for each patient and the attributes are id(which is unique for each payment and can be used as a primary key) patient_id(this will act as a foreign key and refers to the patient table) amount(total amount payed by the patient). date(this will store the date of payment. 7.method:this entity will store thr method of payment made by the patient, and the attributes are id(which is unique for each method and can be used as a primary key) type(this will store the method type of the payment) bill_id(this will act as a foreign key which refers to the bill table) 8.nurse:this entity will store the details of the nurse, and the attributes are id(this is unique for each nurse and can be used as a primary key) name(will store the name of the nurse) contact_num(this is a multy values attribute and store the contact number of the nurse.) Address(it is a composite attribute which store thr adress of the nurse)

Illustrate an Entity-Relationship Diagram (ERD) model using Crow’s Foot notation Here we can have the following entities 1.patients:this entity will store the details of the patients and the attributes for this entity is id(which is unique for each patient and can be used as a primary key) name(this attribute will store the name of the patient and it is a composite attribute) address(this attribute will store the address of the patient and it is multi valued attribute. ) contact_num(this is also a multi valued attribute which will store the contact details of the patient). age(which is a derived attribute) 2.room:this entity will store the information about the details of the rooms. The attributes are. id(this is unique for each room and can be used as a primary key) room number(this will store the room number) Total_bed(this will store the total number of beds present in that room) 3. Bed:this entity will store the information regarding to each bed present in an room, and the attributes are id(this is unique for each bed and can be used as a primary key) Bed_num(this will store the bed number) patient_id(this will act as a foreign key which refers to the patient table) room_id(this will also act as a foreign key which refers to the room table) 4.physician:this entity will store the information of physician, and the attributes are id(this will unique for each physician and can be used as a primary key) Name(this is a composite attribute which store the first last name of the physician. contact_num(this is a multi valued attribute and store the contact number of the physician) email (this attribute will store the email address of the physician) 5.patient_record:this entity will store the medical record of the patient and have the following attributes. id(which is unique for each record and can be used as a primary key) title(this will store the title of the report) type(this will store the type of the report) description(this is a multi valued attribute and used to store the information of the report details) 6.bill:this entity will store the payment details for each patient and the attributes are id(which is unique for each payment and can be used as a primary key) patient_id(this will act as a foreign key and refers to the patient table) amount(total amount payed by the patient). date(this will store the date of payment. 7.method:this entity will store thr method of payment made by the patient, and the attributes are id(which is unique for each method and can be used as a primary key) type(this will store the method type of the payment) bill_id(this will act as a foreign key which refers to the bill table) 8.nurse:this entity will store the details of the nurse, and the attributes are id(this is unique for each nurse and can be used as a primary key) name(will store the name of the nurse) contact_num(this is a multy values attribute and store the contact number of the nurse.) Address(it is a composite attribute which store thr adress of the nurse)

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Related questions

Concept explainers

Question

Illustrate an Entity-Relationship Diagram (ERD) model using Crow’s Foot notation

Here we can have the following entities

1.patients:this entity will store the details of the patients and the attributes for this entity is

id(which is unique for each patient and can be used as a primary key)
name(this attribute will store the name of the patient and it is a composite attribute)
address(this attribute will store the address of the patient and it is multi valued attribute. )
contact_num(this is also a multi valued attribute which will store the contact details of the patient).
age(which is a derived attribute)

2.room:this entity will store the information about the details of the rooms. The attributes are.

id(this is unique for each room and can be used as a primary key)
room number(this will store the room number)
Total_bed(this will store the total number of beds present in that room)

3. Bed:this entity will store the information regarding to each bed present in an room, and the attributes are

id(this is unique for each bed and can be used as a primary key)
Bed_num(this will store the bed number)
patient_id(this will act as a foreign key which refers to the patient table)
room_id(this will also act as a foreign key which refers to the room table)

4.physician:this entity will store the information of physician, and the attributes are

id(this will unique for each physician and can be used as a primary key)
Name(this is a composite attribute which store the first last name of the physician.
contact_num(this is a multi valued attribute and store the contact number of the physician)
email (this attribute will store the email address of the physician)

5.patient_record:this entity will store the medical record of the patient and have the following attributes.

id(which is unique for each record and can be used as a primary key)
title(this will store the title of the report)
type(this will store the type of the report)
description(this is a multi valued attribute and used to store the information of the report details)

6.bill:this entity will store the payment details for each patient and the attributes are

id(which is unique for each payment and can be used as a primary key)
patient_id(this will act as a foreign key and refers to the patient table)
amount(total amount payed by the patient).
date(this will store the date of payment.

7.method:this entity will store thr method of payment made by the patient, and the attributes are

id(which is unique for each method and can be used as a primary key)
type(this will store the method type of the payment)
bill_id(this will act as a foreign key which refers to the bill table)

8.nurse:this entity will store the details of the nurse, and the attributes are

id(this is unique for each nurse and can be used as a primary key)
name(will store the name of the nurse)
contact_num(this is a multy values attribute and store the contact number of the nurse.)
Address(it is a composite attribute which store thr adress of the nurse)

Expert Solution

Step by step

Solved in 2 steps with 1 images

SEE SOLUTION Check out a sample Q&A here

Knowledge Booster

Learn more about

Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.