Database Design for Emergency Room Case Study

Database Concepts
Name of the Students:
Name of the University:
Author Note

Reflection
This report contains the information about the database design for the Emergency Room
case study. Data is one of the most prominent factor of the current era and hence, storing them
has emerged as one of the topmost priority for the data owners. There are different options
available for proper data storage and one of them is the database. The database has cited
prominence adoption ratio. The reason behind the discussed adoption is the introduction of IT
and electrification of data. However, the development of database, migration of data from one
database to other and some other key aspects has emerged as one of the prominent concerning
factor. For the above discussed factors different tools and techniques have been availed such as
DBMS, ERD and other prominent tools and techniques. Hence to start with the design of the
database I have started with design of ER Diagram for the database. Also it should be noted that
for the assignment we were asked to implement the database on Microsoft access. The discussed
paper has focused in the linking procedure of the ERD and the Microsoft Access Database.
Hence, the following sections have offered an insight into the subject before discussing the
attempts and steps used for linking.
ERD abbreviation for Entity relationship diagram is a relationship diagram that cites
witness to the relationship between the noun (objects/entities) stored within a database. In simple
terms, it can be quoted as a component of the information/data which defines the logical
structure of a specific database. It was first introduced in 1976 by peter Chen which was latter
modified to ensure an enhanced diagram format. The ER diagram for the database that is to be
implemented contains the doctors, patients, nurses, receptionists, bed, medication and
appointment entities.

The core components of an ERD are the entities and attributes. Hence we have included a
number attributes in the above discussed entities. The connection between them are shown with
assistance of lines that are draw between the entities, attributes and the relationships. The
discussed diagram has proven to be of great vitality in database descriptions. It can also be used
in developing a system. The system development can take consideration of multiple scenarios
with assistance of the diagram before concluding with a finalized format of database. The
diagram is also used for understanding the operationalize of the database and manipulate the
functionality if needed. The ERD can be designed in different styles. The most prominent are the
IES (Information Engineering style), Chen Style, Bachman Style and Martin Style. We have
used the cross foot notation for the development for the ER diagrams.
We have implemented the database on Microsoft Access, and hence it is important that
we discuss the importance of Microsoft Access in this report. One of the globally adopted DBMS
(database management system) is Microsoft Access which is the co-subject of the discussed
paper. The offering by Microsoft is an integrated form of MJDE (Microsoft Jet Database
Engine), GUI (graphics user interface) and SDK (software development kit). The discussed
database management system offers prominent benefits and one of them is the capability to link
or import data and information that is stored in non-MS Access tools or database.
The database capabilities of MS access are not the limit for the discussed database
system. It can also act as a front-end program and allow other tools to operate in the background.
Additionally, there are template based database support from the discussed system which makes
it more significand and attractive for the users with limited knowledge of the system. These
templates are pre-installed in the system and for different options they can be downloaded from
the Microsoft’s official website. Another prominent feature of the discussed system is that it