UNIVERSAL COLLEGE OF TECHNOLOGY

MENELIK II REFERAL HOSPITAL WEB BASED ONLINE

HOSPITAL MANAGEMENT SYSTEM
Submitted
In partial fulfillment of the requirements for bachelor degree
In
Computer science
Advisor: Mr. Ermiyas Weldeyohannes (MSc.)
By

Name ID Number
1. Abraham Adane UCT/0005/09
2. Anteneh Danale UCT/0015/09
3. Ashenafi Kirose UCT/0010/09
4. Dagim Kibebe UCT/0020/09
5. Yeharertsehay G/mikale UCT/0030/09

July, 2021
 Declaration
We do here by declare that this project has never been presented or published in this
campus or in any institutions of learning. Therefore, it is our own work. We do this
projectunder the supervision of Mr. Ermiyas Woldeyohanes.

Name Signature Date

Abrham Adane -------------------------- ---------------------

Anteneh Danale -------------------------- ---------------------

Ashenafi Kirose --------------------------- ---------------------

Dagim Kibebe --------------------------- ---------------------

Yeharertsehay G/mikale --------------------------- ---------------------

 Certificate
This is to certify that I have read this project and that in my opinion it is fully available, in scope and
quality, as a project for the degree of Bachelor of Science. This work has not been submitted elsewhere for
award of any other degree.
Name of advisor signature

Mr. Ermiyas Woldeyohanes (Msc.)

 Acknowledgment
In preparing this project, we were in contact with many people, Above all, we would like to

thank the Almighty God for his guidance, provision and mercies throughout our life, and for

helping us to accomplishment for this final project. We would also like to express our deepest

gratitude to our advisor: Mr. Ermiyas Woldeyohanes (Msc). We have learnt a lot from the

fruitful discussions that we had, and have benefited a lot from his experience. We are giving

specifically grateful for his extraordinary willingness to assist our whenever we needed help.

Finally, we are also very thankful to all lecturers of department of computer science for their

guidance, advices and motivation. Without their continued support and interest, this project

would not have been the same as presented here. Thank you very much.
List of Acronyms and Abbreviations

HCL Hardware compatibility list

HMS Hospital Management System

HTML Hypertext Markup Language

ICU Intensive Care Unit

sysML systems modeling language

UML unified modeling language

XML Extensible Markup Language

RDD Resilient Distributed Datasets

SVG Scalable Vector Graphics

XUL XML User Interface Language

I
List of Figures

Figure 1-1 Structure of the Organization ........................................................................................ 3

Figure 2-1 Use case diagrams for hospital management system .................................................. 10
Figure 2-2 sequence diagram for log in ........................................................................................ 17
Figure 2-3 sequence diagram for register patient.......................................................................... 18
Figure 2-4 sequence diagram for send lab report .......................................................................... 19
Figure 2-5 Sequence diagram for generate report ......................................................................... 20
Figure 2-6 Sequence diagram for view report .............................................................................. 21
Figure 2-7 Sequence diagram for assign patient ........................................................................... 22
Figure 2-8 Sequence diagram description for login ...................................................................... 23

II
List of Tables

Table 1-1 Progress I ........................................................................................................................ 6

Table 1-2 Progress II ....................................................................................................................... 6
Table 1-3 Materials and financial requirements ............................................................................. 7
Table 2-1 Use case description for login ...................................................................................... 11
Table 2-2 Use case description for register patient ....................................................................... 12
Table 2-3 Use case description for examine patient ..................................................................... 13
Table 2-4 Use case description for generate report....................................................................... 14
Table 2-5 Use case description for send lab report ....................................................................... 15
Table 2-6 Use case description for view report ............................................................................ 16

III
Table of Contents

Declaration ...................................................................................................................................... 2
Certificate ........................................................................................................................................ 3
Acknowledgment ............................................................................................................................. I
CHAPTER ONE ............................................................................................................................. 1
1 Introduction ............................................................................................................................. 1
1.1 Background of the Hospital Management System ....................................................................... 2
1.2 Menelik II Hospital ........................................................................................................................ 2
1.3 Statement of the Problem ............................................................................................................ 4
1.4 Objective of the Project ................................................................................................................ 5
1.4.1 General Objective ................................................................................................................. 5
1.4.2 Specific Objective .................................................................................................................. 5
1.5 Scope of the Project ...................................................................................................................... 5
1.6 Work plan and Financial Requirement.......................................................................................... 6
2 SYSTEM MODELING ........................................................................................................... 8
2.1 Use case model ............................................................................................................................. 8
2.1.1 Actor specification ................................................................................................................ 9
2.1.2 Use case diagram ................................................................................................................ 10
2.1.3 Use case description ........................................................................................................... 11
2.2 Sequence diagram ....................................................................................................................... 17
CHAPTER THREE ...................................................................................................................... 24
3 System design ........................................................................................................................ 24
3.1 INTRODUCTION TO UML ............................................................................................................. 24
3.1.1 UML Design ......................................................................................................................... 24
3.2 Requirement Analysis and Specifications ................................................................................... 25
3.2.1 Introduction ........................................................................................................................ 25
3.2.2 Hardware Requirement ...................................................................................................... 26
3.2.3 Software Requirements ...................................................................................................... 26
3.3 The Proposed system .................................................................................................................. 27

IV
 3.3.1 Functional Requirement ..................................................................................................... 27
3.3.2 Non Functional Requirement .............................................................................................. 27
3.4 Software Specification ................................................................................................................ 27
3.4.1 HTML ................................................................................................................................... 27
3.4.2 Cascading Style Sheets (CSS): .............................................................................................. 28
3.4.3 MySQL ................................................................................................................................. 29
3.4.4 Security ............................................................................................................................... 29
3.4.5 CONNECTIVITY .................................................................................................................... 30
3.4.6 LOCALIZATION ..................................................................................................................... 30
3.4.7 CLIENTS AND TOOLS:........................................................................................................... 30
3.5 JAVASCRIPT PROPERTIES:............................................................................................................ 32

V
 Chapter One

1 Introduction

Menelik II Referral Hospital is a prestigious hospital situated in the heart of Addis Ababa with a
very large patient capacity. This number is increasing at a rapid pace with each passing day. The
Management of the hospital is concerned with the increasing effort in keeping the records of the
patients and recording their activities. The hospital also keeps the information of its employees.
With an eye on the future, the Senior Management of Menelik II Hospital’ has decided to shift to
a computerized hospital Management and Information System, which may keep the records of its
patients, employees, and medical tests. Besides, it may be able to efficiently handle the Patient
Evaluation track and Patient feedbacks.[1]

Its rich Medical Store serves to the purpose of the medicines of the patients who visit this
hospital. The medical store currently is facing problems in maintaining its inventory and keeping
its relations up-to-date with its suppliers. The Medical Store issues medicines to the patients and
also receives the unused medicines in good condition from the patients to minimize wastage.
With increasing number of patients this record keeping has become a burden and is no longer
sustainable with the current manual system. It, therefore, badly needs an improved and efficient
computerized system for maintaining its Inventory, Issue, and purchase activities.

The hospital treats both indoor patients and the outdoor patients. It has to maintain full
information of the indoor patients as well as outdoor patients for the purpose of historical use.
Doctors who serve to the hospital are the regular employees of the hospital; however,
sometimes-external doctors are used to handle complicated cases. So the hospital needs to
maintain its Doctors’ records separately along with the records of its other employees. All these
operations are getting unmanageable day by day because of the stiff rise in data.

With an eye on the future, the Senior Management of Menelik II Hospital has decided to invest
into a computerized Hospital Management & Information System which may keep the records of
its patients, employees, medical store, doctors etc. and may also be able to handle its complete
Accounting.

1
 Hospital is an institution for treatment, care & cure of the sick & wounded, for the study of
disease and training of physicians, nurses & health care personnel.

Human Body is a very complex and sophisticated structure and comprises of millions of
functions. All these complicated functions have been understood by man him, part-by-part their
research and experiments. As science and technology progressed, medicine became an integral
part of the research. Gradually, medical science became an entirely new branch of science. As of
today, the Health Sector comprises of Medical institutions i.e. Hospitals, HOSPITALs etc.
research and development institutions and medical colleges. Thus the Health sector aims at
providing the best medical facilities to the common man.[2]

Hospital also treats inpatient and outpatient and also gives medical advice for different patient.

1.1 Background of the Hospital Management System

Presently all the hospital functionalities are done manually. These means when the patient come
then, registered by the hospital to treat by the physician , it must first be registered by the
secretary at the card room .That is if the patient want to consult meat a doctor he/she can visit till
his /her chance called. This is making the person very difficult mean he/she may be very sick
unless he/she could to meet or consult the doctor our patient tickets cads are distributed directly.
The lab room technician also gets instruction order from the doctor by manually then the lab
technician follow condition through by taking. The pharmacist also gets the order from the
doctor (gotten from lab report) to register the drug to patient. Generally the whole system activity
and management system is controlled by the manager of the hospital; therefore it needs to be
change from manually to computer system.
1.2 Menelik II Hospital
It was the first Ethiopian hospital in Addis Ababa which was established in 1910 by the order of
Emperor Menelik II & in the compound of this hospital there is a statue of the emperor himself.
At present it is serving as a government hospital. It's located around kebena. Menelik Hospital is
one of the best institutions for treatment, care & cure of the sick & wounded and also used for
the study of disease and training of physicians, nurses & health care personnel.

2
According to the definition of hospital; the Menelik hospital is also responsible to take care of
the people's health condition by the corporation (team work) of the physicians, nurses & health
care personnel and also the hospital service include surgery, midwifery, Psychologist and other
services. Hospitals also treat inpatient and outpatient and also give medical advice for different
patient.[3]
Our project is based on the above concept i.e. automation of Administration and Management of
Hospital. The project has been developed keeping in-view the following aspects:-

(i) Working environment of the Hospital.

(ii) The thought-process and attitude of Ethiopia people.

(iii) The literacy rate of Ethiopia.

(iv) The Existing system, being used in the majority of Hospitals.

(v) The availability of Infra-structural facilities likes finance, skilled personals, and working

environment.

Figure 1-1 Structure of the Organization[4]

3
1.3 Statement of the Problem

Existing systems provide the basic functionalities needed to be handled in a hospital

management environment. In the existing system all the patient details, doctor availability details
and regarding the tests done to the patients prescribed by the doctor is maintained manually by
the receptionist. It is very important to maintain efficient software to handle information of
Hospital. This application provides a way to record this information and to access these in a
simple way. Today all the hospital functionalities are done so we decided to work on this project.
The manual handling of the record is time consuming and highly prone to error. The purpose of
this project is to automate or make online, the process of day-to-day activities like Room
activities, Admission of New Patient, Discharge of Patient, Assign a Doctor, and finally compute
the bill etc. We have tried our best to make the complicated process Hospital Management
System for menelik ii hospital as simple as possible using Structured & Modular technique &
Menu oriented interface. We have tried to design the software in such a way that user may not
have any difficulty in using this package & further expansion is possible without much effort.
Even though we cannot claim that this work to be entirely exhaustive, the main purpose of my
exercise is perform each Hospital’s activity in computerized way rather than manually which is
time consuming.

Some of the statement of the problem includes

 Lack of security of data
 Time consuming
 Manually work
 Consuming of cost
 Needs many staff members
 Difficult to manage the system
 Difficult to access large data and organize
 Difficult to update patient data

4
 1.4 Objective of the Project

1.4.1 General Objective

The general objective of this project is to develop web based online hospital management system for menelik ii
referral hospital management system.

1.4.2 Specific Objective

 To Computerize all details regarding patient details by implementing RDD

 Scheduling the appointment of patient with doctors to make it convenient for
both
 To design the Data Base
 To develop prototype test and implement
 Documentation

1.5 Scope of the Project

 It can be used in any hospital, clinic & pathology labs for maintaining patient details &
their test results.
 Maintaining patient details information (patient registration).
 Providing & maintaining all kinds of tests for a patient ( Laboratory
system)
 Get the medical report online
 Easily take appointment from specialist and also contact with specialist in
emergency case.
 Create, delete and update patient records within few clicks

5
1.6 Work plan and Financial Requirement
Tables 1 and 2 shows the work plan activities to be accomplished within the scheduled time.
Table 3 shows the materials and financial requirement to complete this study.

S. Activities Phase I, 2021

No. April May June
1 2 3 4 1 2 3 4 1 2 3 4 1
1 Project
proposal,
approval
2 Literature
survey
3 Presentation
progress I

Table 1-1 Progress I

S.No. Activities Phase-II, 2021

June July August
Weeks Weeks Weeks
1 2 3 4 1 2 3 4 1 2 3 4 4
1 Data collection,
analysis and
documentation
2 writing, editing
3 Submission and
final
presentation

Table 1-2 Progress II

6
S.N Item Quant Unit Unit Price Sub-Total
o. ity (ETB) Price
(ETB)

1 Books, journals and related --- --- 2000 2000

documents

2 Transportation cost --- --- 3500 3500

3 Daily allowance --- --- 7500 7500

4 Paper 01 2000 2000

pack

5 Printing and photocopy --- --- 3000 3000

6 Typing and binding --- --- 3000 3000

7 16 GB flash disk 01 500 500

8 External hard disk 1TB 3500 3500

Total 25,000

Table 1-3 Materials and financial requirements

7
 Chapter Two
2 SYSTEM MODELING
System modeling studies the use of models to conceptualize and construct in business and
information technology development and deals the modeling techniques to analyses the hospital
management system. For modeling the system object oriented analysis methodology is used,
which includes use case modeling, sequence diagram and class diagrams. Generally, it helps to
understand the functionality of the hospital management system and to view how the system
actors: manager, doctor, patient, record keeper, financial manager, lab technician, pharmacist are
communicating with the system and their activity.
2.1 Use case model
A use case describes particular functionality that a system is supposed to perform or shows by
modeling. Each use case describes a possible scenario of how the external entity interacts with
the system. That means it interacts the overall of the system to external users (manager, doctor,
patient, record keeper, financial manager, lab technician, pharmacist). In modeling use case each
use case describes the interaction between the actors, use cases with in the system boundary.[5]
 Use case: describes the sequence of action that provides a measurable value to an actor
and draw as horizontal ellipse and contains use case name inside the ellipse.

 Actor: are users of a system that plays a role to one or more use cases.

8
  Relationship: relationships are simply indicates by arrow connecting actors and the use
cases.

Direct Association

2.1.1 Actor specification

This specifies and describes who are the actors participate in hospital management system. An
actor is a role that somebody or something external to the system plays with regard to a use case.
Those actors are listed and described below:-
 Manager: People who manage the hospital and employee have privilege of to control the
system. Activities of manager log in, generate and view report.
 Doctor: a person who examines and treat patient. Activities of doctor log in, generate
report, give prescription, and refer.
 Patient: a person who requires a medical care. Activity of patient gives payment and
access service.
 Lab technician: a person who examine sample taken from patient. Activities of lab
technician is send lab report to doctor.
 Nurse: a person who care for patient. Activities of nurse log in and generate report.
 Record keeper: a person who register patient and assign patient to doctor. Activities of
record keeper log in, register patient, assign patient.
 Pharmacist: a person who gives drug for patient based on their prescription. Activities of
pharmacist log in give drug and take payment from patient.

9
2.1.2 Use case diagram
Use case diagram shows the interaction between the actors (manager, doctor, pharmacist, nurse,
lab technician, patient, record keeper) and the use cases which is found in our proposed hospital
management system.

Figure 2-1 Use case diagrams for hospital management system

10
2.1.3 Use case description
Use case description includes descriptions of the use case, preconditions, post conditions, basic
flow of event and whatever which is important in modeling the user goal.

Use case ID UC-1

Use case name Login
Actor Manager, doctor, record keeper, pharmacist,
nurse and lab technician.
Description This use case describes how an actor logs into
the system.
Pre-condition The actor must have an account to login to the
system.
Basic course of action 1. The record keeper, doctor, pharmacist, lab
technician, nurse, manager wants to login
the system.
2. the system displays login form
3. the record keeper, doctor, pharmacist, lab
technician, nurse and manager inter user
name & password
4. the system validates the entered
information
5. the system displays main windows
6. the use case ends

Alternative course of action A. 4.1 If the entered user name or

password not valid.
A. 2. 2 Back to step 3.
Post-condition The system display main windows after user name
& pass word enter correctly.

Table 2-1 Use case description for login

11
Use case ID UC-2

Use case name Register patient

Actor Record keeper

Description the record keeper who register the patient

Pre-condition the record keeper use the entered information for register the patient
Past condition-the record keeper register patient based on entered
information
Includes Get service
Basic course of action Old New
1. The patient come again 1. Register patient and give ID
2. Record keeper Ask his/her 2. Assign patient to doctor
ID and enter ID number
3. Retrieve his/her data
4. Assign patient to doctor
Alternative course of action A. 2.1. If the entered ID is not valid.
A. 2.2. Back to step 2.
Post-condition The patient details registered to the system.

Table 2-2 Use case description for register patient

12
Use case ID UC-3
Use case name Examine patient
Actor Doctor
Description examines and treat patient
Pre-condition Patient must give information about his/her
filling
Includes Give prescription
Basic course of action 1. First the doctor ask the patient
2. If the patient in critical condition
3. Based on the patient information
the doctor take sample from patient
and send to lab technician
4. The lab technician examine patient
sample and send result to doctor
5. The doctor give prescription to
patient

Alternative course of action A .2.1. If the patient not in critical condition

A .2.2. Back to step 5.
Post-condition treat

Table 2-3 Use case description for examine patient

13
Use case ID UC-4
Use case name Generate report
Actor Nurse, doctor &Lab technician

Description Doctor, lab technician &nurse generate report.

Pre-condition The system displays a form to generate report

Basic course of action 1. The pharmacist, nurse, doctor, lab
technician wants to generate report.
2. The system displays a form to
generate report
3. All actors in the HMS enter user name
& pass word.
4. The system validates the entered
information.
5. The system displays main windows
6. The use case ends

Alternative course of action 4.if the entered password or user name is

invalid
A.4.The system display error messages and

Post-condition All actors generate report.

Table 2-4 Use case description for generate report

14
Use case ID UC-5
Use case name Send lab report
Actor lab technician
Description send lab report is process of sending lab report
to the doctor
Pre-condition The lab technician to send the lab
reports first he/she gets an order from
the doctor.

Basic course of action 1. The lab technician wants to send lab

report.
2. The system displays a form to send
lab report
3. The lab technician fills the user
name &password
4. The system validates the entered
information
5. The system displays main
windows for lab technician to send lab
report

Alternative course of action A4.1.if the lab technician cannot correctly

enter the user name & password
A4.2. The system displays error message
A4.3.The lab technician reenter user name &
password

Post-condition Lab technician send lab report to doctor

Table 2-5 Use case description for send lab report

15
Use case ID UC-6
Use case name view report
Actor Manager
Description Manager view report from the generated
reports
Pre-condition The displays a form to view report
Basic course of action 1. The manager wants to view report.
2. The system displays a form to view report
by a manager.
3. The manager enter user name & pass word
4. The system checks the entered in
formations.
5. The enter entered in formation is valid
6. The system displays main windows.
7. The use case ends

Alternative course of action A5.if the manager not correctly enters the user
name & password.
A5.The system displays a message error
A5.The manager refill again the user name or
pass ward to View Report.

Post-condition The manager view report

Table 2-6 Use case description for view report

16
2.2 Sequence diagram
The sequence diagram modeling is used to show the interaction between the object and actors in
sequence way. Sequence diagram shows the message that pass between them over time for one
use case.

log in<<controller>> log in form<<UL>> database account

: user

<<destroy>>
1 : click() <<destroy>>
2 : initiat()

3 : display form

4 : fill user name and passward

5 : click log in buten

6 : transfer information

7 : chick validation
<<destroy>>
8 : valid()

9 : dissplaye main page

10 : invalid

11 : erorr please enter coractly

Figure 2-2 sequence diagram for log in

17
 database registration information
registration buten <<controler>> registration form<<UL>>

: recour d keeper

<<destroy>>
1 : click() <<destroy>>
2 : initiet()

3 : display log in form

4 : fill user name and passward

5 : click log in buten

6 : transsfer information
<<destroy>>
7 : che ck validation
8 : valid()

9 : displaye information
10 : save registration()

11 : not valid()

12 : erorr entry please enter again

Figure 2-3 sequence diagram for register patient

18
 buten <<controler>> form<<UL>> database<<account>>

: labe technitan
<<destroy>>
1 : click() <<destroy>>
2 : iniat()

2 : display form
4 : enter labe report

<<destroy>>
5 : click
6 : send report()

Figure 2-4 sequence diagram for send lab report

19
 form<<UL>> database
generat report<<controller>>
: doctor,lab technitian,nurse

<<destroy>>
1 : click() <<destroy>>
2 : initiat()

3 : display form

4 : enter information

5 : click <<destroy>>
6 : send information an d stor()

Figure 2-5 Sequence diagram for generate report

20
 view<< controller>> view forem<<UL>>
database

: manger

<<destroy>>
1 : click() <<destroy>>
2 : initiat()

3 : display hompage
4 : fill user name and passward

5 : click

6 : transfer information

7 : chic k validation

8 : valid()

9 : display stord inf ormation

10 : invalid()

11 : erorr messag please enter corac tly

Figure 2-6 Sequence diagram for view report

21
 database
information form<<UL>>
information <<controler>>

: record keeper

<<destroy>>
1 : click() <<destroy>>
2 : initiat()

3 : display form
4 : enter patient id number

5 : click
6 : transfer information

7 : chick validation
<<destroy>>
8 : valid()

9 : retrive patien t file and assign

10 : invalid please enter again

Figure 2-7 Sequence diagram for assign patient

22
 record keeper acount doctor

+name: varchar +user name: varchar +name: varchar

+age: int +pasward: varchar 1 +der_id: varchar
1
+sex: varchar +sex: varchar
1 +log in() +age: int
+id: varchar 1 +log out()
+address: varchar 1 +examin()
1 +give perscription()
+rigister()
+generat report() 1 +generat report()
+1

patient

+name: varchar 1
+age: int
+sex: varchar *
+address: varchar labe technitian manager
1
+registerd() +name: varchar +name: varchar
+give payment() +sex: varchar +sex: varchar
+get service() +age: int 1 1 +age: int
+address: varchar +office number: int
* +id: varchar 1 +id: varchar
+sample() +log in()
+labe report() +view report()

+1

1 nurs

+name: varchar *
+sex: varchar
+age: int
+id: varchar
+address: varchr

+examin()
+generat report()

Figure 2-8 Sequence diagram description for login

23
 Chapter Three
3 System design
This chapter contains the design goal, system decomposition, deployment diagram,and
persistence data management.
3.1 INTRODUCTION TO UML:

3.1.1 UML Design

The Unified Modeling Language (UML) is a standard language for specifying, visualizing,
constructing, and documenting the software system and its components. It is a graphical
language, which provides a vocabulary and set of semantics and rules. The UML focuses on
the conceptual and physical representation of the system. It captures the decisions and
understandings about systems that must be constructed. It is used to understand, design,
configure, maintain, and control information about the systems.[6]
The UML is a language for:

Visualizing

Specifying

Constructing

Documenting

24
  Visualizing

Through UML we see or visualize an existing system and ultimately we visualize how
the system is going to be after implementation. Unless we think, we cannot implement.
UML helps to visualize, how the components of the system communicate and interact
with each other.

 Specifying

Specifying means building, models that are precise, unambiguous and complete UML
addresses the specification of all the important analysis design, implementation decisions
that must be made in developing and deploying a software system.

 Constructing

UML models can be directly connected to a variety of programming language through

mapping a model from UML to a programming language like JAVA or C++ or VB.
Forward Engineering and Reverse Engineering is possible through UML.

 Documenting

The Deliverables of a project apart from coding are some Artifacts, which are critical in
controlling, measuring and communicating about a system during its developing
requirements, architecture, desire, source code, project plans, tests, prototypes releasers,
etc...

3.2 Requirement Analysis and Specifications

3.2.1 Introduction
To be used efficiently, all computer software needs certain hardware components or the other
software resources to be present on a computer. These pre-requisites are known as
(computer) system requirements and are often used as a guideline as opposed to an absolute
rule. Most software defines two sets of system requirements: minimum and recommended.
With increasing demand for higher processing power and resources in newer versions of
software, system requirements tend to increase over time. Industry analysts suggest that this

25
 trend plays a bigger part in driving upgrades to existing computer systems than technological
advancements.

3.2.2 Hardware Requirement

The most common set of requirements defined by any operating system or software application
is the physical computer resources, also known as hardware. A hardware requirements list is
often accompanied by a hardware compatibility list (HCL), especially in case of operating
systems. An HCL lists tested, compatibility and sometimes incompatible hardware devices for a
particular operating system or application. The following sub-sections discuss the various aspects
of hardware requirements.
Hardware Requirements for Present Project:

PROCESSOR : Intel Core, i3

RAM : 4GB

HARD DISK : 500GB

3.2.3 Software Requirements

Software Requirements deal with defining software resource requirements and pre-requisites that
need to be installed on a computer to provide optimal functioning of an application. These
requirements or pre-requisites are generally not included in the software installation package and
need to be installed separately before the software is installed.

Software Requirements for Present Project:

OPERATING SYSTEM : Windows 7/ 8/10
FRONT END : Html, css, java script.
SERVER SIDE SCRIPT : Php
DATABASE : MySQL

26
3.3 The Proposed system
Our system changes the manual activity in to web- based system. The new introduced system
3.3.1 Functional Requirement
An existing system compromises different players to carry out its job. The major actors in the
existing system are:

Patient: a person who is get service from the Menelik ii referral hospital.

Record keeper: a person who is responsible for record information of the patient.

Doctor: a person who is give treatment for patient.

Pharmacist: a person who arrange drug and gives for the patient, who is responsible for register
drug, check drug type, updating drug.

Lab technician: a person who send patient’s lab result back to the doctor.

Manager: the person, who controls the hospital work division or all parts of the hospital system,
who is responsible for managing and coordinating the system.

3.3.2 Non Functional Requirement

Some of Nonfunctional requirements are listed below:

 Our system is protected with password to secure patient data

 The system is very fast in terms of time and space and has capable of storing data.

 The system must have its own attribute that makes reliable and flexible.

 Hospital management system is simple, easy to understand and user friendly

3.4 Software Specification

3.4.1 HTML:
HTML or Hypertext Markup Language is the standard markup language used to create web
pages.

HTML is written in the form of HTML elements consisting of tags enclosed in angle
brackets (like <html>). HTML tags most commonly come in pairs like <h1> and </h1>, although

27
 some tags represent empty elements and so are unpaired, for example <img>. The first tag in a
pair is the start tag, and the second tag is the end tag (they are also called opening
tags and closing tags). Though not always necessary, it is best practice to append a slash to tags
which are not paired with a closing tag.

The purpose of a web browser is to read HTML documents and compose them into visible or
audible web pages. The browser does not display the HTML tags, but uses the tags to interpret
the content of the page. HTML describes the structure of a website semantically along with cues
for presentation, making it a markup language rather than a programming language.

HTML elements form the building blocks of all websites. HTML allows images and objects to
be embedded and can be used to create interactive forms. It provides a means to create structured
documents by denoting structural semantics for text such as headings, paragraphs, lists, links,
quotes and other items. It can embed scripts written in languages such as JavaScript which affect
the behavior of HTML web pages.

3.4.2 Cascading Style Sheets (CSS):

It is a style sheet language used for describing the look and formatting of a document written in a
markup language. While most often used to style web pages and interfaces written
in HTML and XHTML, the language can be applied to any kind of XML document,
including plain XML, SVG and XUL. CSS is a cornerstone specification of the web and almost
all web pages use CSS style sheets to describe their presentation.

CSS is designed primarily to enable the separation of document content from document
presentation, including elements such as the layout, colors, and fonts.[1] This separation can
improve content accessibility, provide more flexibility and control in the specification of
presentation characteristics, enable multiple pages to share formatting, and reduce complexity
and repetition in the structural content. [7]

CSS can also allow the same markup page to be presented in different styles for different
rendering methods, such as on-screen, in print, by voice (when read out by a speech-based
browser or screen reader) and on Braille-based, tactile devices. It can also be used to allow the
web page to display differently depending on the screen size or device on which it is being

28
 viewed. While the author of a document typically links that document to a CSS file, readers can
use a different style sheet, perhaps one on their own computer, to override the one the author has
specified. However if the author or the reader did not link the document to a specific style sheet
the default style of the browser will be applied.

3.4.3 MySQL:

MySQL is developed, distributed, and supported by Oracle Corporation. MySQL is a

database system used on the web it runs on a server. MySQL is ideal for both small and large
applications. It is very fast, reliable, and easy to use. It supports standard SQL. MySQL can be
compiled on a number of platforms. The data in MySQL is stored in tables. A table is a collection of
related data, and it consists of columns and rows. Databases are useful when storing information
categorically.

Features of MySQL:

Internals and portability:

 Written in C and C++.

 Tested with a broad range of different compilers.

 Works on many different platforms.

 Tested with Purify (a commercial memory leakage detector) as well as with Val grind, a GPL
tool.

3.4.4 Security:
 A privilege and password system that is very flexible and secure, and that enables host-based
verification.

 Password security by encryption of all password traffic when you connect to a server.

Scalability and Limits:

 Support for large databases. We use MySQL Server with databases that contain 50 million

records. We also know of users who use MySQL Server with 200,000 tables and about
5,000,000,000 rows.

29
 Support for up to 64 indexes per table (32 before MySQL 4.1.2). Each index may consist of 1
to 16 columns or parts of columns. The maximum index width is 767 bytes for InnoDB tables,
or 1000 for MyISAM; before MySQL 4.1.2, the limit is 500 bytes. An index may use a prefix of
a column for CHAR, VARCHAR, BLOB, or TEXT column types.

3.4.5 CONNECTIVITY:
Clients can connect to MySQL Server using several protocols:

 Clients can connect using TCP/IP sockets on any platform.

 On Windows systems in the NT family (NT, 2000, XP, 2003, or Vista), clients can
connect using named pipes if the server is started with the --enable-named-
pipe option. In MySQL 4.1 and higher, Windows servers also support shared-memory
connections if started with the --shared-memory option. Clients can connect through
shared memory by using the --protocol=memory option.

 On UNIX systems, clients can connect using UNIX domain socket files

3.4.6 LOCALIZATION:
 The server can provide error messages to clients in many languages.
 All data is saved in the chosen character set.

3.4.7 CLIENTS AND TOOLS:

 MySQL includes several client and utility programs. These include both command-
line programs such as mysqldump and mysqladmin, and graphical programs such
as MySQL Workbench.
 MySQL Server has built-in support for SQL statements to check, optimize, and
repair tables. These statements are available from the command line through
the mysqlcheck client. MySQL also includes myisamchk, a very fast command-line
utility for performing these operations on MyISAM tables.

30
  MySQL programs can be invoked with the --help or -? option to obtain online
assistance.

 WHY TO USE MySQL:

• Leading open source RDBMS

• Ease of use – No frills
• Fast
• Robust
• Security
• Multiple OS support
• Free
• Technical support
• Support large database– up to 50 million rows, file size limit up to 8 Million TB

 JAVASCRIPT:

JavaScript is the scripting language of the Web. All modern HTML pages are using JavaScript.
A scripting language is a lightweight programming language. JavaScript code can be inserted
into any HTML page, and it can be executed by all types of web browsers. JavaScript is easy to
learn.

 WHY TO USE JAVASCRIPT:

JavaScript is one of the 3 languages all web developers must learn:

1. HTML to define the content of web pages

2. CSS to specify the layout of web pages
3. JavaScript to specify the behavior of web pages

OTHER USES OF JAVASCRIPT:

 Delete HTML elements

 Create new HTML elements
 Copy HTML elements

31
  In HTML, JavaScript is a sequence of statements that can be executed by the web
browser.

 JAVASCRIPT STATEMENTS:

 JavaScript statements are "commands" to the browser.

 The purpose of the statements is to tell the browser what to do.
 This JavaScript statement tells the browser to write "Hello Dolly" inside an HTML
element with id="demo":

 Semicolon;

 Semicolon separates JavaScript statements.

 Normally you add a semicolon at the end of each executable statement.
 Using semicolons also makes it possible to write many statements on one line.

 JAVASCRIPT CODE:

 JavaScript code (or just JavaScript) is a sequence of JavaScript statements.

 Each statement is executed by the browser in the sequence they are written.
 This example will manipulate two HTML elements:

Example
 document.getElementById("demo").innerHTML="Hello Dolly";
document.getElementById("myDIV").innerHTML="How are you?";

3.5 JAVASCRIPT PROPERTIES:

 Properties are the values associated with a JavaScript object.

 A JavaScript object is a collection of unordered properties.
 Properties can usually be changed, added, and deleted, but some are read only.

 PHP:

WHAT IS PHP?

• PHP is an acronym for "PHP Hypertext Preprocessor"

• PHP is a widely-used, open source scripting language
• PHP scripts are executed on the server
WHAT IS PHP FILE?

• PHP files can contain text, HTML, CSS, JavaScript, and PHP code

32
 • PHP code are executed on the server, and the result is returned to the browser as plain
HTML
• PHP files have extension ".php"
WHAT CAN PHP DO?

• PHP can generate dynamic page content

• PHP can create, open, read, write, delete, and close files on the server
• PHP can collect form data
• PHP can send and receive cookies
• PHP can add, delete, modify data in your database
• PHP can restrict users to access some pages on your website
• PHP can encrypt data
With PHP you are not limited to output HTML. You can output images, PDF files, and even
flash movies. You can also output any text, such as XHTML and XM

33
 Chapter Four
4 Sample Screenshots

4.1 User Interface Design

4.1.1 The Login Form

This form is one way of the security features we imbedded in to our project. All the users can log on the system
only if they have user id and password.

There is only one login for all the users like Receptionist, doctor, Lab Technician and Pharmacists of Menelik II
Referral Hospital.

Figure 4-1 Login user interface

4.2 Menu Design

4.2.1 Main Menu

The main menu is also called as Central Administration Menu from which the users are directed to the required
task

Figure 4-2 Main Menu

34
 4.2.2 Reception Task Menu

The reception task menu provides us record patient information and assigned to doctor facility

Under Reception task different forms are grouped in their respective sub-menus.

Reception task sub-Menus

Figure 4-3 Reception Task Menu

4.2.3 Record Patient Menu

A real task to this package to provide the relevant records electronically about patient information details

Figure 4-4 Add new patient

35
 4.2.4 Assign Patient to Doctor Menu

This facility enables the patient to get the assigned Doctor for treatments.

Fig 3.16 Assign Patient to Doctor

4.2.5 The Report Menu

The Receptionist generates two reports. Namely Patient Record and Assigned to doctor

Figure 4-5 Report Menu

36
 4.2.6 The patient report

This report belongs to patient record. It generates report for patient information.

Figure 4-6 Patient Information

4.2.7 Assigned to doctors report

This report belongs to patient assigned to doctors. It generates report for which doctor patient assigned.

Figure 4-7 Assigned Patient to doctor

4.2.8 Doctor Main Menu

Figure 4-8 Doctor Main Menu

37
4.2.9 Patient History

Figure 4-9 Patient History

4.2.10 Hematology Menu

Figure 4-10 Hematology Menu

38
 4.2.11 Doctor Task

Under doctor task different forms are grouped in their respective sub-menus the doctor will assign the patient to
laboratory for different test and pharmacy for medication

Figure 4-11 Hematology Menu

39
 4.2.12 Lab Technician Main Menu

Figure 4-12 Lab Technician Main Menu

4.2.13 Laboratory Task

Under laboratory task different forms are grouped in their respective sub-menus.

Lab Hematology Lab Technician will select the patient id which has sent to him by the Doctor and click the go
button and will get the diagnoses list which has ordered by the Doctor.

Lab Technician will test as per the Doctor requested and send the result back to the Doctor. After this, the Doctor
is ready to prescribe the medicine.

40
 Figure 4-13 Hematology lab test

4.2.14 Report Lab Hematology

The doctor will get the lab result which is sent by the technician from lab report of hematology

Figure 4-14 Hematology lab result

41
 4.2.15 Drug Prescriptions

The doctors will prescribe the appropriate medicine and send to the pharmacist so that the patient will take the
medicine which is prescribed by the doctor.

Figure 4-15 Hematology lab test.

4.2.16 Issue Drug

The pharmacist will issue the drug as per doctor prescription to the patient.

Figure 4-16 Issue Drug

4.3 Implementation
4.3.1 System Testing
System Testing is an important stage in any system development lifecycle. Testing is a process of executing a
program with the intention of finding errors. The importance of software testing and its implications with respect
to software quality cannot be overemphasized. Software testing is a critical element of software quality assurance
and represents the ultimate review of specification, design and coding. A good test case is one that has a high
probability of finding an undiscovered error. To do this, there are many ways of testing the system’s reliability,
completeness and maintainability.

42
 4.3.2 Unit Testing

In the unit testing the analyst tests the program making up a system. The software units in a system are the
modules and routines that are assembled and integrated to perform a specific function. In a large system, many
modules on different levels are needed. Unit testing can be performed from the bottom up starting with the
smallest and lowest level modules and proceeding one at a time. For each module in a bottom-up testing, a short
program executes the module and provides the needed data.

4.3.3 Integration Testing

Integration testing is a systematic technique for constructing the program structure while conducting test to
uncover errors associate with interfacing. Objectives are used to take unit test modules and built program structure
that has been directed by design. The integration testing is performed for this Hospital Management System when
all the modules where to make it a complete system. After integration the project works successfully.

4.3.4 Validation Testing

Validation testing can be defined in many ways, but a simple definition is that can be reasonably expected by the
customer. After validation test has been conducted, one of two possible conditions exists. The functions or
performance characteristics confirm to specification and are accepted.

A deviation from specification is uncovered and deficiency list is created. Proposed system under consideration
has been tested by using validation testing and found to be working satisfactorily. For example, in this project
validation testing is performed against inpatient search module. This module is tested with the following valid and
invalid inputs for the field patient name.

4.3.5 White Box Testing

White box testing, sometimes called glass-box testing is a test case design method that uses the control structure
of the procedural design to derive test cases. Using white box testing methods, the software engineer can derive
test cases that guarantee that all independent paths with in a module have been exercised at least once.

Exercise internal data structure to assure their validity. For example in this project white box testing is performed
against inpatient module. Without entering text if we apply it displays the message “First add record then save it”
else it should be saved.

4.3.6 Black Box Testing

This method treats the coded module as a black box. the module runs with inputs that are likely to cause errors.
Then the output is checked to see if any error occurred. This method cannot be used to test all errors, because
some errors may depend on the code or algorithm used to implement the module.

43
 4.4 System Implementation
Implementation is the process of having system personal check out and provides new equipments into use, train
the users to install a new application and construct any files of data needed to use it. There are three types
of implementation.

Implementation of computer system to replace a manual system. The problems encountered are covering files,
training users, creating accurate files and verifying print outs for integrity.

Implementation of a new computer system to replace an existing one. This is usually difficult conversion. If not
properly planned, there can be many problems.

Implementation of a modified application to replace the existing one using the same computer. This type of
conversion is relatively easy to handle, usually there are no major changes in the file. Our project is yet to be
implemented.

4.5 Sample Coding’s

4.5.1 Login form

<?php

$host="localhost"; // Host name

$username="root"; // Mysql username

$password="vertrigo"; // Mysql password

$db_name="hmsdb"; // Database name

$tbl_name="login"; // Table name

// Connect to server and select databse.

mysql_connect("$host", "$username", "$password")or die("cannot connect");

mysql_select_db("$db_name")or die("cannot select DB");

44
// username and password sent from form

$myusername=$_POST['myusername'];

$mypassword=$_POST['mypassword'];

// To protect MySQL injection (more detail about MySQL injection)

$myusername = stripslashes($myusername);

$mypassword = stripslashes($mypassword);

$myusername = mysql_real_escape_string($myusername);

$mypassword = md5(mysql_real_escape_string($mypassword));

$sql="SELECT * FROM $tbl_name WHERE user_username='$myusername' and user_password='$mypassword'

and user_active='1'";

$result=mysql_query($sql);

// Mysql_num_row is counting table row

$count=mysql_num_rows($result);

// If result matched $myusername and $mypassword, table row must be 1 row

if($count==1){

45
// Register $myusername, $mypassword and redirect to file "login_success.php"

session_register("myusername");

session_register("mypassword");

while($results = mysql_fetch_array($result)){

$userType=$results['user_type'];

$userName=$results['user_username'];

$_SESSION['CurrentLogin']=$userName;

$_SESSION['userID']=$results['user_relid'];

if($userType=="D")

header("location:doctor/index.php");

else if ($userType=="R")

header("location:reception/index.php");

else if ($userType=="L")

header("location:lab/index.php");

else if ($userType=="P")

header("location:pharmacy/index.php");

else{

$msg="Invalid User";

header("location:index.php");
46
 }

else {

$msg="Invalid User";

header("location:index.php");

?>

4.5.2 Main Menu

<div class="rounded">

<nav id="mainav" class="clear">

<ul class="clear">

<li class="active"><a href="index.php">Home</a></li>

<li><a class="drop" href="#">Doctors Task</a>

<ul>

<li><a href="#">Lab</a>

<ul>

<li><a href="hematology.php">Hematology</a></li>

<li><a href="urin.php">Urin</a></li>

</ul>

47
 </li>

<li><a href="drug.php">Drug Perscription</a></li

</ul>

</li>

<li><a class="drop" href="#">Report</a>

<ul>

<li><a href="#">Lab</a>

<ul>

<li><a href="hemareport.php">Hematology</a></li>

<li><a href="patienthis.php">Patient History</a></li>

</ul>

</li>

<li><a href="drugreport.php"></a></li>

</ul>

</li>

</ul>

</nav>

</div>

48
 Chapter Five
5 Conclusion and Recommendation
5.1 Conclusion

This project is undertaken to develop an Online Hospital management system for the Menelik II Referral
Hospital. The system takes care of the requirements of hospital and is capable to provide easy and effective
storage of the information related to the patient who reaches the service. Our new automated online computerized
system can display patient’s information, generates the laboratory test results and available medicines in the
Pharmacy.

On other hand, it generates test reports; provide prescription details including various test, medicine
prescribed to the patient. The system also, provides the facility of backup as per schedule.

In Object Oriented analysis, the team tried to verify the systems requirements using use case modeling. To
model the logic of usage scenarios, sequence diagrams were drawn. Classes of the new system and their
relationship are identified and documented in conceptual modeling. Activity diagrams were drawn and user
interfaces are prototyped and validated by users.

5.2 Recommendation

Since data management of the hospital is a vital part of its operation and its survival in the modern world, it
must be well updated.

We recommend further work to create the system that generates the bill generation, Store, x-ray and bed
allocation systems.

We also recommend on linking by internet to assign the patient referral to other higher different hospitals to
fast response for the patient health care mechanism.

49
 References

1. The DeLone and McLean Model of Information Systems Success

2. http://www.w3schools.com/html/

3. http:// www.connectionstrings.com/

50