Database Normalization and ERD for Patient Report System

Desklib provides solved assignments and past papers to help students succeed.

Table of Contents
A. Diagram for showing Dependencies:..................................................................................2
B. Normalization.....................................................................................................................2
1 NF........................................................................................................................................2
2 NF........................................................................................................................................3
3 NF........................................................................................................................................3
C. ERD....................................................................................................................................4
References..................................................................................................................................5
Table Of Figures
Figure 1 Diagram of Dependencies............................................................................................2
Figure 2 1 NF for Patient Report Table.....................................................................................2
Figure 3 Information_Patient Table...........................................................................................3
Figure 4 Information_clinic Table.............................................................................................3
Figure 5 Patient_Report Relations.............................................................................................3
Figure 6 Information_Patient Table...........................................................................................3
Figure 7 Information_clinic Table.............................................................................................3
Figure 8 Parameters_triAge Table.............................................................................................4
Figure 9 Patient_Report Relations.............................................................................................4
Figure 10 Patient_report ERD....................................................................................................4

A. Diagram for showing Dependencies:
For normalizing a database, the essential part is to understand the dependency of the
database. Dependencies are being based on various business rules which are as follows:
 The component which is being used as Primary Key should be underlined, bold and it
should be shaded according to different color scheme.
 The arrow which is above entities will indicate desirable dependencies, in this case,
dependencies which are based on the primary key is being displayed.
 Arrows below diagram of dependency having less desirable dependencies such as
partial or transitive dependency. (Coronel, C., & Morris, S. 2016)
Figure 1 Diagram of Dependencies

B. Normalization
Normalization can be defined as a process in which attributes will be assigned to entities. By
doing normalization data redundancy is being reduced and it will help to eliminate anomalies
of data in which deletions, updating, insertions took place. After performing the
normalization database is being logically correct.
1 NF
In 1 NF, key attributes whichever is present in the table is being defined. In 1 NF, no
repeating groups are allowed, and attributes are dependent on primary keys.
Figure 2 1 NF for Patient Report Table
In the above diagram, 1 NF form is being displayed for the patient report in which there are
multivalued attributes and composite attributes are present. So, 1 NF is being similar to
dependency diagram of the patient report table.
2 NF
A table should be in 2 NF if it is already in 1 NF and no partial dependencies are included in
the table. In 1 NF diagram of patient report, partial dependencies are present. So they will be
breakdown into different relations with no partial dependencies.
Figure 3 Information_Patient Table

Figure 4 Information_clinic Table
Figure 5 Patient_Report Relations
3 NF
A Relation will be said in 3 NF form when it is already in 2NF, and the attributes should not
have any transitive dependency. ( Hingorani, K et al., 2017)
Figure 6 Information_Patient Table
Figure 7 Information_clinic Table
Figure 8 Parameters_triAge Table

Figure 9 Patient_Report Relations

C. ERD
Figure 10 Patient_report ERD
The above image will be showing the Entity Relationship Diagram of the given relation
Patient_report. In the above image 4 different relations is being displayed which will be
showing that the above relations were in 3 NF normalized form in which there were no
transitive as well as partial dependency.

References
Hingorani, K., Gittens, D., & Edwards, N. (2017). REINFORCING DATABASE
CONCEPTS BY USING ENTITY RELATIONSHIPS DIAGRAMS (ERD) AND
NORMALIZATION TOGETHER FOR DESIGNING ROBUST DATABASES. Issues in
Information Systems, 18(1), 148-155.
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management.
Cengage Learning.