ERD Diagram for Clinic Management: Database Systems Assessment 2

Desklib provides past papers and solved assignments for students. This project demonstrates ER diagram design for a clinic management system.

DATABASE SYSTEMS ASSESSMENT ITEM 2

Table of Contents
Assumptions....................................................................................................................................3
ER Diagram.....................................................................................................................................4
Conclusion.......................................................................................................................................5
References........................................................................................................................................6
2

Assumptions
The assumptions while creating ERD are:
 Total numbers of entities are seven where one-to-many and one-to-one relationships are
present.
 For every entity, there is a primary key that uniquely defines that entity like in
Clinic_history table h_id is a primary key that uniquely defines every history.
 In clinic_appointments table appointment_ID is the primary key, in table clinic_clients,
patient_id is the primary key, in table Bookings, booking_no, treatment_code in
Clinic_treatment, payment_id in session payment and therapist_ID in clinic_therapists.
All these are the primary keys that are considered.
 Now table “bookings” is created so that the many-to-many relationship among
appointment and treatment table can be avoided.
 Almost all the entities are connected with one-to-many relationship except the table
Clinic_history and Clinic_appointments, they are connected with the one-to-one
relationship because for the appointments there will be one single history not multiple.
 Foreign keys are also there in table Clinic_appointments, table Bookings and in table
Session_payment.
 These foreign keys take reference from other tables.
 The table Clinic_history consists of two primary keys.
3

ER Diagram
Figure 1 ERD
4

Conclusion
The given scenario is related to a clinic that provides different skin treatments and according to
that scenario, a cross foot notation is drawn or an ER diagram. This is created by using draw.io.
The diagram represents many relationships among the entities that are present and their attributes
are also there. All other constraints are also added like Foreign keys and Primary keys.
5

References
El-Halees, A. M., & Kehail, E. O. (2017). Integrate Database Design Techniques with Agile
Applications. Integrate Database Design Techniques with Agile Applications.
Gaikwad, A. S., Kadri, F. A., Khandagle, S. S., & Tava, N. I. (2017). Review on Automation
Tool for ERD Normalization. International Research Journal of Engineering and Technology
(IRJET)[Online], 4(2), 1323-1325.
6