logo

Data Modelling: Entity Relationship Diagram for Auckland City Hospital

   

Added on  2023-01-19

6 Pages1172 Words45 Views
Infosys - data
modelling
Data Modelling: Entity Relationship Diagram for Auckland City Hospital_1
Table of Contents
INTRODUCTION...........................................................................................................................1
Overview of case.........................................................................................................................1
Some assumptions have been made:...........................................................................................2
Conclusion.......................................................................................................................................3
References........................................................................................................................................3
Data Modelling: Entity Relationship Diagram for Auckland City Hospital_2
INTRODUCTION
The process of creation of data model for storing data within database is referred to as
data modelling. In this data is formulated within well-configured as well as specified form which
presents data objects as well as associations with different data objects. Through this data can be
analysed in an effectual manner which further assists within acknowledgement of requirements
of business. Entity relationship diagram is defined as a data modelling technique which is used
for graphical illustration of entities of information systems along with relationship among those
entities. This assignment is based on Auckland City Hospital that is present within suburb of
Grafton. On the annual basis they have near about 80,000 patients.
Overview of case
Entity relationship diagram comprises of diverse connectors as well as symbols that are
liable for visualisation of crucial information. There exists four groups of people, they includes
physician, employees, volunteer and patients. Each have their own set of attributes and share
relationship among each other. They been specified below:
Patient: They can be either resident or outpatient depending on their requirements. Each
patient have their own unique_id which differentiates them from others present within the
hospital. This is often known as primary key. The special relational database table that is being
used for uniquely identifying all table records present within entity, it is known as primary key. It
comprises of unique value for data with row as well as do not have null values. Along with this,
other attributes are name, address, sex, age, contact number, date when they were admitted and
date related with their discharge. Contact number is within double dotted oval shape, the reason
for this is that patient can have multiple number through which contact can be made with them.
Employee: They lies within three categories which includes doctor and nurse. Again
each have different set of attributes which makes them different from other. Each employee have
their own id, type, name, email address, date of birth (dob), salary as well as address which
makes them different from others. Attributes of each employee has been illustrated below:
Doctor or physician: Each patient has unique physician assigned to them who is liable
for treating them in an appropriate manner. They have their unique id, qualification as well as
employee id which assists patients to identify their physician who is liable for providing them
treatment. Qualification makes each doctor different with respect to services they are being
1
Data Modelling: Entity Relationship Diagram for Auckland City Hospital_3

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Introduction to Data Modelling - Assignment
|6
|1270
|284

Development and Implementation Assignment
|12
|1025
|201

Enterprise Rules - Hospital Management System
|22
|1437
|45

Database Design and Development
|6
|968
|378

Science of Data Modelling and Database Design
|3
|593
|22

Information System for Healthcare: Applications, Tools, Challenges, and Developed System Modules
|14
|866
|201