Annexure –I

PART A – Micro-Project Proposal

Title of Micro-Project: --- Design E-R diagram of Hospital Management System and
Normalize upto 3NF.

1.0 Brief Introduction

Entity is a real thing or object in the real world that is distinguishable from all other objects.
An entity set is a set of entities of the same type that share the same properties, or
attributes. Attributes are disruptive properties possessed by each member of an entity set.

An entity relationship diagram shows the visual representation of different entities within a
system and how they relate to each other. ER diagram illustrate the logical structure of the
databases. ER diagram constitute a very useful framework for creating and manipulating
databases.

Normalization: Normalization can define as process of decomposition of database tables to

avoid the data redundancy. ERD (Entity-Relationship Diagram) is the conceptual model. It
represents relationship between entities. ERD is converted into Relation model (tables) using
concepts of normalization (rules to prepare tables to store data). Any application which
requires data to be stored into database (tables) could be considered as application of ERD
and Normalization. For example, Hospital Management system.

2.0 Aim of the Micro-Project

This Micro-Project aims at:
1. Draw the ER diagram of Hospital management system.
2. Normalize the Hospital management system ER diagram up to 3NF.

3.0 Intended Course Outcomes

After completion of this project students will be able to:
1. Use Boolean expressions to realize logic circuits.
2. Build Simple combinational circuits.
3.0 Intended Course Outcomes

a) Design normalized database on given database.

4.0 Literature Review

Malik A. M., Khan R. H., 2009. Understanding the Implementation of an electronic hospital
information system in a developing country.

Hospital Information System (HIS) is a comprehensive, integrated information system

designed to manage the administrative, financial and clinical aspects of a hospital. This study
is to describe those aspects of the implementation of hospital information system in three
tertiary hospitals in Klang Valley; Serdang Hospital, Selayang Hospital and University
Kebangsaan Malaysia Medical Centre (UKMMC). A qualitative study was conducted to obtain
views on information system development and implementation in the hospitals mentioned
above. In-depth interviews with personnel representing both the system providers and the

1
end-users were done guided by a questionnaire. The results of the interviews were
categorized into few themes namely the system development, human resource, scope of
implementation, support system, user-friendly, training, hardware and security. There were
differences in hospital information system development and implementation in the three
hospitals. Each system has its own strengths and weaknesses that make it unique. In
developing HIS, its important to ensure the system can work effectively and efficiently.
Quality human resource, good support system, user-friendly and adequate training of the
end-user will determine the success of implementation of HIS. Upgrading of hardware and
software as needed is the basis to keep up with the pace of technology advancement and
increasing number of patients. It is hoped that HIS will be implemented in all other hospitals
with effective integration and networking

Asabe.S.A., Oye, N. D., Monday Goji, “HOSPITAL PATIENT DATABASE MANAGEMENT

SYSTEM”, COMPUSOFT An International journal of Advance Computer Technology.

Health care in India as in many other countries is confronted with growing demand for
medical treatment and services. The medical records must appropriately have all of the
patients’ medical history. Physicians must maintain flawless records, because this document
serves a number of purposes. This study on hospital management system is design to
transform the manual way of searching, sorting, keeping and accessing hospital information
(files) into electronic medical record in order to solve the problem associate with manual
method. The existing system has been studied and hence a computer based software was
provided to replace this manual method. These computer based systems generate the
patient report as the patient register in and out of the hospital. It also generate the
information regarding the doctor, nurse allot to the patient. This paper generally looks for a
more accurate, reliable and efficient method of computer to facilitate hospital record’s
keeping in General Hospitals to ensure efficient outcome that will lessen time consuming.
The study proposed that the design of hospital management record will be a solution to the
problem being experienced by the current manual method of keeping patient medical
record.

Dr. Ariyaratne, 2010: “A private hospital management system”. Postgraduate Institute of

Medicine, University of Colombo, Sri Lanka.

Entity Relationship (ER) Diagram models are commonly used for conceptual data modeling
during database design. Developing quality ER data models is a difficult task for both
learners and junior modelers. The main reason for this difficulty is that the ER modeling task
is cognitively complex. This research proposes a computer-based learning system designed
to not only reduce cog, visualization of details. The proposed interactive learning system is
based on a framework which provides systematic guidance and knowledge support during
ER modeling. The framework is based on the use of graphical organizers and animation
techniques to simplify problem domain complexity and support visualization during ER
modeling respectively.

5.0 Proposed Methodology

This project is related to a hospital management system. It maintains records of all the operationsthat
occur at any of the medical center in public institutions.it maintains two level of users, administrator.
2
Levelandthe user level.In the ER diagram, we can view the entities- Patient, Doctor,
Receptionist, Department, Medicine, Test, OT(Operation Theater), Room, Nurse, Ward boy,
Driver, Ambulance, Carriers, Accountant and Bill. Among these entities, relationships exist
which connect all the entities in the diagram. For example, Patient, Doctor and Receptionist
are connected via the relationship Appointment. In other words, a receptionist will set up a
doctor’s appointment for a patient. Similarly, Doctor, Patient and Medicine are connected
via the relationship Prescription. Here, a doctor may prescribe one or more medicine to a
patient. In a similar way, other entities are connected via relationships in a meaningful way.
Cardinality ratios [1] for the entities connected to a relationship are : - (NEXT PAGE)

Normalization rules:

1 NF: A relation is in first normal form if and only if the domain of each attribute contains
only atomic (indivisible) values, and the value of each attribute contains only a single value
from that domain

2 NF: A database is in second normal form if it satisfies the following conditions:

 It is in first normal form

 All non-key attributes are fully functional dependent on the primary key

3NF: A database is in third normal form if it satisfies the following conditions:

3
  It is in second normal form
 There is no transitive functional dependency

6.0 Resources Required

Sr.
Name of Resource/ Material Specifications Quantity Remark
No.

To collect
1 Internet 2mbps -
information

RAM8GB, Octa
2 Computer(PC) Core processor, 1 To type the data
SSD 160GB

To draw the ER
3 Drawing Sheet A4 1
diagram

7.0 Action Plan

Planned Name of
Sr. Planned
Details of activity Finish Responsible Team
No. start date
date Members

1 Project Proposal Aniket Sutar

2 Data Collection & Analysis Harshit Gorad

3 Preparation of Prototype/ Model Rohit Karande

4 Preparation of Report Samad Pirjade

5 Presentation & Submission Siddhik Shaikh

4
 Annexure –II
PART B – Micro-Project Proposal

Title of Micro-Project: --- Design E-R diagram of Hospital Management System and
Normalize upto 3NF.

1.0 Rationale
ER models are mostly developed for designing relational database in terms of concept
visualization and in terms of physical database design; there are still other situations
when ER diagrams can help. Depending on the scale of change, it can be risky to alter a
database structure directly in a DBMS. To avoid ruining the data in a production
database, it is important to plan out the changes carefully. ERD is a tool that helps. By
drawing ER diagrams to visualize database design ideas, have a chance to identify the
mistakes and design flaws, and to make correction before executing the changes in
database.
Database normalization is the process of organizing the attributes and tables of a
relational database to minimize data redundancy. Benefits of normalization are Greater
overall database organization. Reduction of redundant data, Data consistency within the
database, A much more flexible database design, A better handle on database security.
2.0 Course Outcomes Addressed
a) Design normalized database on given database.

3.0 Literature Review

1. Malik A. M., Khan R. H., 2009. Understanding the Implementation of an electronic
hospital information system in a developing country, 3rd Australasian Workshop on
HIKM, Wellington, New Zealand
Hospital Information System (HIS) is a comprehensive, integrated information system
designed to manage the administrative, financial and clinical aspects of a hospital. This study
is to describe those aspects of the implementation of hospital information system in three
tertiary hospitals in Klang Valley; Serdang Hospital, Selayang Hospital and University
Kebangsaan Malaysia Medical Centre (UKMMC). A qualitative study was conducted to
obtain views on information system development and implementation in the hospitals
mentioned above. In-depth interviews with personnel representing both the system providers
and the end-users were done guided by a questionnaire. The results of the interviews were
categorized into few themes namely the system development, human resource, scope of
implementation, support system, user-friendly, training, hardware and security. There were
differences in hospital information system development and implementation in the three
hospitals. Each system has its own strengths and weaknesses that make it unique. In
developing HIS, it’s important to ensure the system can work effectively and efficiently.
Quality human resource, good support system, user-friendly and adequate training of the end-
user will determine the success of implementation of HIS. Upgrading of hardware and
software as needed is the basis to keep up with the pace of technology advancement and
increasing number of patients. It is hoped that HIS will be implemented in all other hospitals
with effective integration and networking

2. Asabe.S.A., Oye, N. D., Monday Goji,” HOSPITAL PATIENT DATABASE

MANAGEMENT SYSTEM”, COMPUSOFT An International journal of Advance
Computer Technology.

5
Health care in India as in many other countries is confronted with growing demand for
medical treatment and services. The medical records must appropriately have all of the
patients’ medical history. Physicians must maintain flawless records, because this document
serves a number of purposes. This study on hospital management system is design to
transform the manual way of searching, sorting, keeping and accessing hospital information
(files) into electronic medical record in order to solve the problem associate with manual
method. The existing system has been studied and hence computer based software was
provided to replace this manual method. These computer based systems generate the patient
report as the patient register in and out of the hospital. It also generate the information
regarding the doctor, nurse allot to the patient. This paper generally looks for a more accurate,
reliable and efficient method of computer to facilitate hospital record’s keeping in General
Hospitals to ensure efficient outcome that will lessen time consuming. The study proposed
that the design of hospital management record will be a solution to the problem being
experienced by the current manual method of keeping patient medical record.
3. Dr. Ariyaratne, 2010: “A private hospital management system”. Postgraduate Institute of
Medicine, University of Colombo, Sri Lanka
Entity Relationship (ER) Diagram models are commonly used for conceptual data modeling
during database design. Developing quality ER data models is a difficult task for both learners
and junior modelers. The main reason for this difficulty is that the ER modeling task is
cognitively complex. This research proposes a computer-based learning system designed to
not only reduce cog, visualization of details.. The proposed interactive learning system is
based on a framework which provides systematic guidance and knowledge support during ER
modeling. The framework is based on the use of graphical organizers and animation
techniques to simplify problem domain complexity and support visualization during ER
modeling respectively.

4.0 Actual Methodology Followed

Following steps are followed for drawing an ER diagram

STEP 1: Identifying the entities

1. DOCTORS
2. HOSPITALS

3. PATIENT

4. MEDICINES

5. ROLES
6. PERMISSION
7. USER
8. LOGIN

An entity is known as column, an attribute is a property or characteristic of the entity

that holds it. An ERD entity is a definable thing or concept within a system

STEP2: Identifying the relationships:-

o Hospital has a set of patients.

Therefore the relation is 1:N.
o Hospital has a set of doctors.
6
 Therefore the relation is 1:.N.
o Doctor is associated with each patient.
Therefore the relations is n:1.
o Each patient has record of various test and examination conducted.
Therefore the relation is 1:N.

Cardinality:

Cardinality defines the possible number of occurrence in one entity which are
associated to the number of occurrences in another. The three common cardinal
relationships are one-to-one, one-to-many, and many-to-many.

 STEP 3 : Identify other relevant attributes

o DOCTOR-Doc_id, Doc_add, Doc_name, Doc_mobile, Doc_email, Doc_pass

o HOSPITAL-Hos_id, Hos_place, Hos_doc_id, Hos_desc, Hos_type

o `PATIENT-Pat_id, Pat_mobile, Pat_email, Pat_address

o MEDICIN-Medi-id, Medi_type, medi_desc

o ROLE-Role_id, Role_name, Role_desc

o USER-User_id, User_name, User_mobile, User_email, User_add

o LOGIN-Login_id, Login_role_id, Login username, Login password

Attributes:

Entities which are represented by a set of attributes. Attributes are descriptive properties
possessed by each member of an entity set.

o STEP 4:Identify the primary Key attribute

1. Doctors_id

2. Hospital_id

3. Patient_id

4. Med_id

5. Role_id

6. User_id

7. Login_id

7
Primary key:

A primary key is a special kind of entity attribute that uniquely defines a record in a
database table.

Generalization:

Generalization is the process of extracting common properties. From a set of entities and
create a generalized entity from it.

Specialization:
In specialization, an entity is divided into sub-entities based on their characteristics.
This is represented by a triangle shaped ISA relation.

After drawing ER diagram normalize this ER diagram up-to 3NF.

o Database Normalization is a technique of organizing the data in the database.

Normalization is a systematic approach of decomposing tables to eliminate data
redundancy (repetition) and undesirable characteristics Normalization is used for
mainly two purposes. Eliminating redundant (useless) data and Ensuring data
dependencies make sense i.e. data is logically stored.

Normalization rules are divided into the following normal forms:

o First Normal Form

o Second Normal Form
o Third Normal Form

For a table to be in the First Normal Form, it should follow the following 4 rules:

o It should only have single (atomic) valued attributes/columns.

o Values stored in a column should be of the same domain
o All the columns in a table should have unique names.
o And the order in which data is stored, does not matter.

For a table to be in the Second Normal Form, It should follow the following steps:-

o It should be in the First Normal form.

o And, it should not have Partial Dependency.

A table is said to be in the Third Normal Form, It should follow the following steps:-

o It is in the Second Normal form.

o And, it doesn't have Transitive Dependency.

8
5.0 Actual Resources Used

Sr. Name of Resource/

Specifications Quantity Remark
No. Material

To collect
1 Internet 2mbps
information

RAM2GB,Dual
2 Computer(PC) Core processor, 1 To type the data
Hare disc 160GB

To draw the ER
3 Drawing Sheet A4 1
diagram

6.0 Outputs of the Micro Project

1. E-R Model of Library Management System

9
2. Normalization
1. DOCTORS

Doc_id Primary key

Doc_add

Doc_name

Doc_mobile

Doc_email

Doc_pass

Pat_id Foreign key Pat_id references medicines

Hos_id Foreign key Hos_id references Hospital

2. HOSPITALS

Hos_id Primary key

Hos _place

Hos_doc_id

Hos_desc

Hos_type

Doc_id Foreign key Doc_id references doctor

Medi_id Foreign key Medi_id references medicines

User_id Foreign key User_id references user

3. PATIENT

Pat_id Primary key

Pat_name

Pat_mobile

Pati_email

Pat_address

Hos_id Foreign key Hos_id references Hospital

Doc_id Foreign key Doc_id references Doctor

User_id Foreign key User_id references User

10
4. MEDICINES

Medi_id Primary key

Medi_type

Medi_desc

Hos_id Foreign key Hos_id references Hospital

5. ROLES

Role_id Primary key

Role_name

Role_desc

User_id Foreign key User_id references User

Login_id Foreign key Login_id references Login

6. USER

User_id Primary key

User_name

User_mobile

User_email

User_address

Pat_id Foreign key Pat_id references medicines

Dos_id Foreign key Doc_id references doctor

Hos_id Foreign key Hos_id references Hospital

Login_id Foreign key Login_id references Login

Role_id Foreign key Role_id references Role

11
8. LOGIN

Login_id Primary key

Login_role_id

Login_username

Login_password

Role_id Foreign key Role_id references Role

User_id Foreign key User_id references User

7.0 Skill Developed / learning out of this Micro Project

1. To maintain the record of indoor and outdoor patients.
2. Management of Hospital
3. Learned how to draw the ER Diagram.
4. Learned how to normalize ER diagram up to 3NF.
5. Learned about how to use attributes in ER diagram during the project.

8.0 Applications of this Micro Project

o Hospital Management System not only provides an opportunity to the hospital
to enhance their patient care, but also can increase the profitability of the
organization. Hospital administrators would be able to significantly improve
the operational control and thus streamline operations. This would improve the
response time to the demands of patient care because it automates the process
of collecting, collating and retrieving patient information.
o
Database creation and patching - ERD tool like Visual Paradigm supports
database generation tool that can automate the database creation and patching
process by means of ER diagrams.
o ERD (Entity-Relationship Diagram) is the conceptual model. It represents
relationship between entities. ERD is converted into Relation model (tables)
using concepts of normalization (rules to prepare tables to store data). Any
application which requires data to be stored into database (tables) could be
considered as application of ERD and Normalization. For ex., Hospital
Management system.

9.0 Area of Future Improvement

o The features of the system depend on the generator. We can generate the whole
application for the ER diagram or only some components for this application.
o Normalization can be incremented from 4NF to5NF.
o In future ER diagram can be used for management of resources like blood bank
system, hospital management system, etc.

12
 Annexure – III

Teacher Evaluation Sheet

Name of Student: ________________________________________ Enrollment No.: _____________

Name of Programme: _____________________________________Semester: __________________
Course Title :_____________________________________________Code: _____________________

Title of the Micro-Project: Design E-R diagram of Hospital Management System and Normalize
upto 3NF.

Course Outcomes Achieved

__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________

Evaluation as per Suggested Rubric for Assessment of Micro Project

 (Please tick in appropriate cell for each characteristic)

Sr. Characteristic Poor Average Good Excellent

No to be assessed ( Marks 1-3 ) ( Marks 4 - 5 ) ( Marks 6 - 8 ) ( Marks 9- 10 )

Relate to very Related to some Take care of at- Take care of

few Los Los least one CO more than one
Relevance to
1 CO
the course

Not more than At-least 5 At –least 7 About 10

two sources relevant sources, relevant sources, relevant sources,
Literature (primary and at least 2 latest most latest most latest
Survey / secondary),
2
information very old
collection reference

Completion of Completed less Completed 50 to Completed 60 to Completed more

the Target as than 50% 60% 80% than 80 %
3
per project
proposal
Sample Size Sufficient and Sufficient and Enough data
small, data appropriate appropriate collected by
neither sample, enough sample, enough sufficient and
organized nor data generated data generated appropriate
presented well but not organized which is sample size.
and not organized and Proper inferences
Analysis of Data presented well. presented well drawn by
4 and No or poor but poor organizing and
representation inferences drawn inferences drawn presenting data
through tables,
charts and
graphs.

5 Quality of Incomplete Just Well Well

13
Sr. Characteristic Poor Average Good Excellent
No to be assessed ( Marks 1-3 ) ( Marks 4 - 5 ) ( Marks 6 - 8 ) ( Marks 9- 10 )

Prototype/ fabrication/asse assembled/fabric assembled/fabric assembled/fabric

Model mbly. ated and parts ated with proper ated with proper
are not functioning parts. functioning parts.
functioning well. In proper shape, In proper shape,
Not in proper within tolerance within tolerance
shape, dimensions and dimensions and
dimensions good good
beyond tolerance finish/appearanc finish/appearanc
limit. e. But no e. Creativity in
Appearance/finis creativity in design and use of
h is shabby. design and use of material
material

Very short, Nearly sufficient Detailed, correct Very detailed,

poor quality and correct and clear correct, clear
sketches, details about description of description of
Details about methods, methods, methods,
methods, material, materials, materials,
material, precautions and precautions and precautions and
Report precaution and conclusion, but Conclusions. conclusions.
6 conclusions clarity is not Sufficient Graphic Enough tables,
Preparation
omitted, some there in Description. charts and
details are presentation. But sketches
wrong not enough
graphic
description.

Major Includes major Includes major Well organized,

information is information but information and includes major
not included, not well well organized information ,well
7 Presentation
information is organized and but not presented
not well not presented presented well
organized . well

Any other
(depending
upon nature of
8
project: please
write indicators
by pen)

Could not reply Replied to Replied properly Replied most of

to considerable considerable to considerable the questions
number of number of number of properly
Defense question. questions but not question.
9 very properly

14
 Micro-Project Evaluation Sheet

Process Assessment Product Assessment

Total
Part A - Project Part B - Project individual
Project Methodology Marks
Proposal Report/Working Model Presentation/Viva
(2 marks) 10
(2 marks) (2 marks) (4 marks)

Note:
Every course teacher is expected to assign marks for group evolution for each group of students in
first 3 columns as per rubrics & individual evaluation in 4TH column for each group of students as per
rubrics based on viva.

Comments/Suggestions about team work/leadership/inter-personal communication (if

any)
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
__________________________

Any Other Comment:

_____________________________________________________________________
_____________________________________________________________________
____________________

Name and designation of the Faculty Member

- Mr. V. D. Thoke.
Lecturer.

Dated Signature

__________________________________________

*****

15