UNIVERSITY OF BURAO

FACULTYOF INFORMATION,
COMMUNICATION AND TECHNOLOGY

Hospital Management system Project

A PROJECT PROPOSAL SUBMITTED TO THE DEPARTMENT
OF INFORMATION COMMUNICATION AND TECHNOLOGY
IN PARTIAL FULFILMENT OF BACHELOR DEGREE
SCIENCE.

By:
Abdirisak Ahmed Mohamed
Roll No: 3425

BICT-------: ICT INDIVIDUAL PROJECT

i
Burao University –Somaliland
www.Uob-edu.net
facultyofict@uob-edu.net
Printed By:
--------------------------------------------------
Burao-Somaliland

ii
DECLARATION AND APPROVAL

Declaration
I hereby declare that this project is my original individual work, done
in partial fulfillment of the requirement for Qualification for
graduation with the degree of Bachelor of information
communication and technology at University Of Burao, Faculty of
Information Communication Technology.
Burao-Somaliland.
Student Name: …………………….… signature: ……………

iii
Approval
I hereby declare that this project was undertaken with my
approval and under my supervision

Supervisor Name: Mr. Eng. Osman Haji Hassan Dheeg. Signature …………..

iv
Dedication
This thesis is dedication to my beloved family firstly my father Ahmed Mohamed
Elmi and my mother Maryam Salad Jama you have been loved and supported me
throughout all my endeavors. Secondly my brother Abdirahman Ahmed
Mohamed. You were always a source of inspiration and encouragement during this
journey of education.
Also my previous dean Mr. Aidarous Hassan Deex
Finally my dear teachers played remarkable position to complete well for my
education.

v
ACKNOWLEDGEMENT
I express my gratitude to Mr. Mohamed Abdi Elmi for his help, guidance throughout
the work for this project without him I would not have been able to complete this
project to such success.
I would also like to thank my Supervisor Eng. Osman Haji Hassan Dheeg who
helped me to accomplish this project.
I would also like to thank my classmates who helped me directly or indirectly in
accomplishing this work.

Finally I would also like to thank other faculty members who provided me with
moral support during the course of this project.

vi
ABSTRACT
Hospital management system is a distributed web Application developed to maintain
the details of hospital in any hospital.

Hospital management system is a computerized system designed and programmed

to deal with day to day operations taking place. The program can look after
inpatients, outpatients, records, database treatments, status illness, billings in the
pharmacy and labs all assets in the Hospital. It also maintains hospital information
such as ward id, doctors in charge and department administering. The purpose of the
project is to computerize the Front Office Management of Hospital to develop
software which is user friendly, simple, fast, and cost – effective. It deals with the
collection of patient’s information, diagnosis details, etc. Traditionally, it was done
manually. The project outlines all the process followed to come up with the software
that is from analysis to testing the system.
It maintains all the information about the patient details, also the details about the
hospital employees and payroll system which enable to generate the payslip. The
application is actually a suite of web applications developed using asp.net.
It is simple to understand and can be used by anyone who is not even well known
with simple hospital management system. It is user friendly and just asks the user to
follow step by step operations by giving him few options. It is fast and can perform
many operations of a hospital.
This software package has been developed using the powerful coding tools of asp.net
and C# at Front End and Microsoft Sql Server at Back End. The software is very
user friendly. The package contains different modules like Patient details and blood
bank system. This version of the software has multi-user approach. For further
enhancement or development of the package, user’s feedback will be considered.

vii
Table of Contents

Declaration and Approval ........................................................................................................................ iii

Approval .................................................................................................................................................... iv
Dedication .................................................................................................................................................. v
Acknowledgment ........................................................................................................................................ vi
Abstract...................................................................................................................................................... vii
Chapter One: (HMS) ................................................................................................................................. 1
1.0 Introduction ............................................................................................................................. 1

1.1 Background ............................................................................................................................. 2

1.2 General Objectives .................................................................................................................. 3
1.2.1 Specific Objectives .................................................................................................. 3
1.3 Statement of the problem ....................................................................................................... 4
1.4 Scope of the restriction ........................................................................................................... 4
1.5 Project Phases/Stage ............................................................................................................... 4
1.5.0 Requirement Definition stage ................................................................................ 5
1.5.1 Prototyping .............................................................................................................. 5
1.5.2 Designing Stage ....................................................................................................... 6
1.5.3 Development stage .................................................................................................. 6
1.5.4 Integration and testing stage .................................................................................. 6
1.5.5 Training and maintenance stage ............................................................................ 6
1.6 Tools and methodologies ........................................................................................................ 7
1.7 Schedule ................................................................................................................................... 7
1.8 Requirement structure ........................................................................................................... 8
1.8.1 Functional requirements ........................................................................................ 8
1.8.2 Non-functional requirements ................................................................................. 8

2.0 Chapter Two: Literature Review ....................................................................................................... 9

2.1 IMPORTANCE OF LITEARATURE REVIEW ................................................................ 9

2.2 PURPOSE OF LITERATURE REVIEW ............................................................................ 9

2.3 LITERATURE REVIEWS ON TOPICS RELATED TO THE PROJECT ................... 10

2.4 CONCLUSION ..................................................................................................................... 10

viii
3.0 Chapter three: Data modeling .......................................................................................................... 11

3.1 Introduction ........................................................................................................................... 11

3.2 Data schema / Data information .......................................................................................... 11

3.3 Data dictionary ...................................................................................................................... 12

3.4 Problems with the Manual System ...................................................................................... 15

3.5 Benefits of computerized system/new .................................................................................. 16

3.7 Sharing of Data ..................................................................................................................... 16

3.8 Data Integrity ........................................................................................................................ 16

3.9 Data Security ......................................................................................................................... 16

3.10 Privacy ................................................................................................................................. 17

3.11 Backup and Recovery ......................................................................................................... 17

3.12 Data Consistency ................................................................................................................. 17

4.0 Chapter four: Data modeling ............................................................................................................ 18

4.1 Problem Statement ................................................................................................................ 19

4.2 System Interface/ Design ...................................................................................................... 20

5.0 Chapter Five: Implementation and Testing .................................................................................... 39

5.1 Conclusion ............................................................................................................................. 40

5.2 Reference ............................................................................................................................... 41

ix
 Chapter One: Introduction to HMS.
1.0 Introduction
Hospital Management System is crucial technology components that enable a single
outlet or enterprise to better serve its hospital with beverage transactions and controls
Telecommunication hospital. Hospital Management System has been proposed to
be implemented to replace the manual system to automatic system. The main aim
of this project is computerization of all processes which happens in the Hospitals. It
is a database system for creating a selective retrieved of information for subsequent
analysis, manipulation and application.
Hospital Management System helps the hospital manager to manage the hospital
more effectively and efficiently by computerizing orders, billing and patient details
control. This management system is designed for Burao General Hospital.
The system processes transaction and stores the resulting data. Reports will be
generated from these data which help the manager to make appropriate business
decisions for the hospital.

1
1.1 Background
Hospital Management system (HMS) is a computer or web based system that
facilitates managing the functioning of the hospital or any medical setup. The
system or software will help in making the functioning paperless. It integrates
all the information regarding patients, doctors, staff and Blood bank details
etc. Into one Software.

2
 1.2 General Objectives
HMS was introduced to solve the complications from managing all the paper
works of every patient associated with the various departments of
hospitalization with confidentiality.
HMS provides the ability to manage all the paperwork in one place, reducing
the work of staff in arranging and analyzing the paperwork of the patient.
HMS does many works like:
 Maintaining the medical records of the patient
 Maintaining the contact details of the patient
 Tracking the bill payment
 Time saving technology
 Improved efficiency by avoiding human errors.

1.2.1 Specific Objectives

A hospital management system is a software designed to manage all the areas of a
hospital such as medical, financial, administrative and the corresponding processing
of services the objectives of hospital are the following.
 Design a system for better patient care.
 Reduce hospital operating costs.
 Provide MIS (Management Information System) report on demand to
management for better decision making.
 Better co-ordination among the different departments.
 Patient management (scheduling, registration and long-term care)

3
1.3 Statement of the problem
The problem that currently facing the hospital is that the system they were using was
manually and stored in book and computer excel spreadsheet which is hard to capture
A huge data and can Coues delay for their work, data redundancy and less of
integrity at hospital happen.
Lack of immediate retrievals: - The information is very difficult to retrieve and to
find particular information like- E.g. - To find out about the patient’s history, the
user has to go through various registers. This results in inconvenience and wastage
of time. Error manual calculation: - Manual calculations are error prone and take a
lot of time this may result in incorrect information.
Preparation of accurate and prompt reports: - This becomes a difficult task as
information is difficult to collect from various registers.
1.4 Scope of Restriction
This program will be a perfect way to manage the hospital system. This application
contains login form, patient registration, patient details, doctor registration, blood
bank system,. Hospital Management application allow patients to edit their
information like patient name, contact number, address, disease from which he is
suffering from etc.
It can be used in any Hospital, Clinic, Dispensary or Pathology labs for maintaining
patient details and their test results.

1.5 Project Phases/Stages

In developing the Hospital Management System, the developer
Prefers to use one of the generally accepted Hospital Software’s development
techniques. This technique has got 6 stages or phases roughly known:
 Requirement collection
 Analysis
 Designing
 Coding
 Testing
 Training and Implementing.
There will be a formal quality assurance review process for each stage.

4
1.5.0 Requirement Definition stage
The requirement definition stage develops user needs and user requirements. These
requirements define the major functions of the intended application, define
operational data areas and reference data areas, and define the initial data entities.
Major functions include critical processes to be managed, as well as mission critical
inputs, outputs and reports, a user class hierarchy is developed and as hospital cited
with these major functions, data areas, and data entities.
These requirements are fully described in the primary deliverables for this stage.
The Requirements Document: The requirements document contains complete
descriptions of each requirement, including diagrams and references to external
documents as necessary.

1.5.1 Prototyping
I use prototyping method to develop this project because, Prototyping is an attractive
idea for complicated and large systems for which there is no manual process or
existing system to help determining the requirements. In such situations letting the
client "plan" with the prototype provides invaluable and intangible inputs which
helps in determining the requirements for the system. It is Hospital an effective
method to demonstrate the feasibility of a certain approach. This might be needed
for novel systems where it is not clear those constraints can be met or that algorithms
can be developed to implement the requirements.
The process model of the prototyping approach is shown in the figure below:

5
1.5.2 Designing Stage
There are many factors that must be considered when designing the system
Software because the user must be able to interact with the system in a way that the
system will understand whatever the input given by the user.

The designing stage is about explanation of alternative system and justification for
Chosen alternative functional, detailed specifications of all system elements (data,
Processes, inputs and outputs); Technical, detailed specifications of all system
elements.

1.5.3 Development stage

This stage converts design into complete information system include acquiring and
Installing of system's informant, creating and testing database, preparing test case
Procedures, testing files, coding compiling, refining program.
1.5.4 Integration and testing stage
During the integration and test stage, the system arte facts, help system, and test data
are migrated from the development environment to a separate test environment. At
this point, all test cases are run to verify the correctness and completeness of the
Hospital Management system.
Successful execution of the test suite confirms a robust and complete migration
Capability.
During this stage, reference data is finalized for production use and production users
are identified and linked to their appropriate roles, the outputs of the integration and
Test stage include an integrated set of the System and a help system.

1.5.6 Training and maintenance stage

This stage describes task to operate and maintain the system. The application users
will be trained by the development team as how to use the product.

6
1.6 Tools and methodologies
According to the requirements of the Hospital, these development tools and
methodologies are selected:-
MYSQL, Selected for Database development and processing DBMS.
Visual Studio: - as the IDE (Integrated Development Environment) for the user
interface design and Hospital management system integration.
ASP.NET and C#: - Hospital management system Development methodology is
purely object oriented.
Methodologies for Requirements collection include interview, prototyping and
Investigation.

1.7 Work Scheduling and Breakdowns

No Start Date Task Name End Date
1.0 01-01-2021 Requirement Gathering 15-02-2021

2.0 17-02-2021 Requirement analysis 20-02-2021

3.0 22-02-2021 Project Designing 28-02-2021

4.0 01-03-2021 Project Development 30-03-2021

5.0 01-04-2021 Project Integration and Testing 10-04-2021

6.0 11-04-2021 Project Development 12-04-2021

7.0 13-04-2021 Training 15-04-2021

7
1.8 Requirement structure
Requirement structure can be divided into two types: -

1.8.1 Functional requirements

Functional requirements is what the system should be exactly do, this fulfills all
Hospital needs from the system.

1.8.2 Non-functional requirements:

Non-functional requirements Is the general behavior of the system both will be
gathering different data collection methodologies.

1.8.3 Functional requirements of Hospital Management system

This system should meet the functional requirements and perform functionality
effectively and efficiently.
System stores the information of Hospital in detail, Patient and the Doctor and staff
Information.
The Patients, doctors and staff will provide their name, place of birth, date of birth,
gender, occupation and other details.
The system should keep track the staff billing system. Finally, the System will print
reports.
1.7.4 Non-functional requirements of Hospital Management system
A user-friendly interface with proper menus.
Data transfer should be accurate and within a Hospital can able amount of time
keeping in mind the network traffic.
The system should be fully secured. The system should accepts only users have
access permission (Rolls, User Names, and Passwords).

8
2.0 Chapter Two: Literature Review
This chapter summarizes the evaluation of the literature relevant to the Hospital
Management System. It examines theories, concepts, approaches, methods and
Techniques relevant to the project. Similar existing technologies relating to the
Development the HMS are discussed.

2.1 IMPORTANCE OF LITERATURE REVIEW

A literature review may consist of simple summary of key source, but in the social
science, a Literature review has an organizational pattern and combines both
summary and synthesis, often within specific theoretical categories. A summary is a
recap of the important information of the source but a synthesis is a re-organization,
or a reshuffling of that information, in a way that informs how you are planning to
investigate a research problem. The analytical features of a literature review might:
 Give a new understanding of old material or association with old
understandings
 Trace the intellectual progression of the field including major debates
 Depending on the situation, evaluate the sources and advice the reader on the
most pertinent or relevant research
 Usually in the conclusion of a literature review, identifies where gaps exist
in how a problem has be researched to date.
2.2 Purpose of the literature review
 The purpose of a literature review is to gain an understanding of the existing
research and debates relevant to a particular topic or area of study, and to
present that knowledge in the form of a written report.
 Conducting a literature review helps you build your knowledge in your field.
 You’ll get a better understanding of how research findings are presented and
discussed in your particular discipline.
 To identify gaps in knowledge and unresolved problems that your research
can address.
 To develop your theoretical framework and methodology.
 To provide an overview of the key findings and debates on the topic.

9
2.3 LITERATURE REVIEWS ON TOPICS RELATED TO THE PROJECT
A HMS refers to the systems and processes at the intersection between HOSPITAL
MANAGEMENT SYSTEM (HMS) and information technology.
a) “A hospital resource and patient management system based on real-time
data capture and intelligent decision making” Author(s): Musa, A. Lancashire
Bus. Sch.,
Univ. of Central Lancashire, Preston, UK Yusuf, Y, Meckel.M. Systems and
Informatics (ICSAI), 2012 International Conference.
One of the major challenges existing hospital management Systems face is around
operational efficiency and wait times between different processes, departments and
persons. This Paper highlights such limitations of existing systems and
Proposes a RFID (Radio Frequency ID) and wireless sensor Based, location and
information management framework that facilitates real time tracking of hospital
assets, personnel and patients as they move through pre-set procedures as part of
daily activities of the hospitals. The system covers the visual simulation and
providing ability to analyses the ongoing operations so they can be corrected to
Achieve increased process efficiency and service levels.

b) “Study on information system of health care services Management in hospital”

Author(s): Damping Hu, Antai Sch. of Manage. Shanghai Jiaotong Univ., China
Weiguo Xu ; Huizhang Shen ; Mengyu Li. Services
Systems and Services Management, 2005. Proceedings of ICSSSM '05. 2005
International Conference
This paper reviews the HIS (Hospital Management Systems) Which are widely used
in many hospitals in China mainly to provide easier and faster way for daily medical
tasks /activities with a GUI And provides for overcoming some of the limitations of
HMS , eg. HMS aims at improving quality of health care services but do not have
way of evaluating /measuring those. So this paper proposes HMS (Hospital
Management System) which aims at improving quality of services, identifying cost
reduction areas, analyses and evaluating the health care service. The ability to
evaluate the services facilitates hospital achieve higher Customer satisfaction scores
and get a competitive edge against those hospitals which scoreless or use HMS and
do not have ways of promoting the quality of their services.

2.4 CONCLUSION
This program has characteristics that makes it different from all the programs studied
in the previous paragraphs, it combines HMS and patient details in one program. It
records daily operation, patient complaints and what every employee has done each
day.

10
 3.0 Chapter Three: Data modeling
3.1 Introduction
A data model is a way of describing how data is organized and accessed. Data
models are represented graphically in a diagram with accompanying text typically
in the form of a data dictionary.
A data model is produced for a particular subject matter (domain) and a Specific
purpose and is based on a formal specification. Data models define data elements
and relationships among data elements.
3.2 Data schema / Data information
Table Name Columns
Create users Userid, Username, Password, confirm_pass, user_type,
secret_question, secret_answer.
Login Username, password.
Patient Registration patient_id, birth_date, first_name, last_name, age, contact, gender,
blood_group, marital_status, occupation, department.
Patient Details patient_id, first_name, last_name, ward_no, room_no,pain_type,
gender, blood_group, laboratory, treatment, other_details.

Staff Management staff_id, first_name, last_name, birth_date, contact, email,

address, age, gender, staff_title.

Billing staff_id, first_name, last_name, salary, date, month, title,

payment_type

Blood Bank Id, first_name, last_name, birthdate, age, contact, gender,

blood_type

Birth registration Birth_id, first_name, last_name, mother_name, contact, birthdate,

gender, blood_type

11
3.3 Data dictionary
Table structure for table User Creation.
Field Type Constraint
userid Int(20) Primary Key
Username Varchar(30) Not Null
password Varchar(20) Not Null
confirm_pass Varchar(20) Not Null
user_type Varchar(20) Not Null
secret_question Varchar(50) Not Null
secret_answer Varchar(50) Not Null

Table Structure of Login

Field Type Constraint
Username Varchar(30) Not Null
Password Varchar(30) Not Null

Table Structure of Patient Registration

Field Type Constraint
patient_id Int(10) Primary key
birth_date Date Not Null
first_name Varchar(30) Not Null
last_name Varchar(30) Not Null
age Number(10) Not Null
contact Number(10) Not Null
gender Varchar(10) Not Null
blood_group Varchar(10) Not Null
marital_status Varchar(10) Not Null
occupation Varchar(50) Not Null
description Varchar(50) Not Null

12
Table Structure of Patient Details
Field Type Constraint
patient_id Int(10) Not Null
first_name Varchar(30) Not Null
last_name Varchar(30) Not Null
ward_no Varchar(20) Not Null
room_no Varchar(20) Not Null
pain Varchar(30) Not Null
gender Varchar(30) Not Null
blood_group Varchar(30) Not Null
laboratory Varchar(50) Not Null
treatment Varchar(50) Not Null
other_details. Varchar(50) Not Null

Table Structure of Staff Management

Field Type Constraint
staff_id Int(10) Primary Key
first_name Varchar(30) Not Null
last_name Varchar(30) Not Null
birth_date Date Not Null
contact Number Not Null
email Varchar(30) Not Null
age Number Not Null
gender Varchar(30) Not Null
staff_title Varchar(50) Not Null

Table Structure of Billing

Field Type Constraint
staff_id Int(10) Not Null
first_name Varchar(30) Not Null
last_name Varchar(30) Not Null
salary Number Not Null
date Date Not Null
month Varchar(30) Not Null
title Number Not Null
payment_type Varchar(30) Not Null

13
Table Structure of Blood-bank
Field Type Constraint
Id Int(10) Not Null
first_name Varchar(30) Not Null
last_name Varchar(30) Not Null
Birthdate Date Not Null
age Number Not Null
contact Number Not Null
gender Varchar(30) Not Null
blood_type Varchar(20) Not Null

Table Structure of Birth Registration

Field Type Constraint
Birth_id Int(10) Not Null
first_name Varchar(30) Not Null
last_name Varchar(30) Not Null
mother_name Varchar(20) Not Null
contact Varchar(20) Not Null
birthdate Varchar(30) Not Null
gender Varchar(30) Not Null
blood_group Varchar(30) Not Null

14
3.4 Problems with the Manual System
Training problems: the problems associated with training and advising people to
be disciplined enough to maintain the maintenance system, i.e. to write the data into
the system Report acquisition problems - the effort associated with finding
meaningful data and statistics in the system. Registers and logs with good design are
difficult. Summarizing data and writing reports take lot of time.
Data duplication: the same data gets repeated over and over since the workers find
it hard to keep track of the documents, information and transactions
Lack of security: since data is stored in filing cabinets it is freely available to
anyone. If information falls into the wrong hands it can be used against the company
and customers and can blackmail them.
Common errors: when entering data customers might have accidentally switched
details and data since it is hand written.
Inconsistency of data: there will be an unavailability for future use, since data might
get misplaced during manual filing.so data won’t be preserved properly for future
use.
Repetition of work: if there are any changes to be made, the data will have to be
entered again.at times the worker would forget to make the changes or forget that
they had already altered it and might redo it again, its again time consuming.
Too much paper work: since everything and every details is written down manually
in paper there will be too much paper work!
Space consuming: since the data and paper is stored in filing cabinets it consumes
too much place, as the amount of work done on paper increases the filing cabinets
too increases.
Slow retrieval of data: the information of customers and details are stored in
different parts of the site and so takes a long time to retrieve the data.it takes a long
time to find the information about a relevant person.in case of a Delivery, the
delivery will be held back.

15
3.5 Benefits of computerized system/new system
A Database Management System (DBMS) is defined as the software system that
allows users to define, create, maintain and control access to the database. DBMS
makes it possible for end users to create, read, update and delete data in database. It
is a layer between programs and data.
Compared to the File Based Data Management System, Database Management
System has many advantages. Some of these advantages are given below:
3.6 Reducing Data Redundancy
The file based data management systems contained multiple files that were stored in
Many different locations in a system or even across multiple systems. Because of
this, there were sometimes multiple copies of the same file which lead to data
redundancy.
This is prevented in a database as there is a single database and any change in it is
Reflected immediately. Because of this, there is no chance of encountering duplicate
data.
3.7 Sharing of Data
In a database, the users of the database can share the data among themselves. There
are various levels of authorization to access the data, and consequently the data can
only be shared based on the correct authorization protocols being followed.
Many remote users can also access the database simultaneously and share the data
Between themselves.
3.8 Data Integrity
Data integrity means that the data is accurate and consistent in the database. Data
Integrity is very important as there are multiple databases in a DBMS. All of these
Databases contain data that is visible to multiple users. So it is necessary to ensure
that the data is correct and consistent in all the databases and for all the users.
3.9 Data Security
Data Security is vital concept in a database. Only authorized users should be allowed
to access the database and their identity should be authenticated using a username
and Password. Unauthorized users should not be allowed to access the database
under any circumstances as it violates the integrity constraints.

16
3.10 Privacy
The privacy rule in a database means only the authorized users can access a database
According to its privacy constraints. There are levels of database access and a user
can only view the data he is allowed to. For example - In social networking sites,
access constraints are different for different accounts a user may want to access.

3.11 Backup and Recovery

Database Management System automatically takes care of backup and recovery. The
users don't need to backup data periodically because this is taken care of by the
DBMS. Moreover, it also restores the database after a crash or system failure to its
previous condition.

3.12 Data Consistency

Data consistency is ensured in a database because there is no data redundancy. All
data appears consistently across the database and the data is same for all the users
viewing the database. Moreover, any changes made to the database are immediately
reflected to all the users and there is no data inconsistency.

17
 Chapter Four: System Development
 The developed system encompasses various activities associated with
managing
employee information
The main functionalities available in this system are:
Maintaining employee profiles
Leave management
Blood bank management
Task management
Billing system
Maintaining outpatient details
 Providing Birth Certificate
All users are presented with the same login interface. User must login the system by
means of valid username/password combination. After access is granted to the
system, the admin can add a new user to the system by entering the basic information
which are the full names and email address. During the process of user registration,
the all users are issued with a unique username and password combination. Seeing
that the system holds private employee information, the admin has the ability to
monitor all activity logs into the system by date and time. The newly added user logs
into the system with a default password which can later be changed to a more secure
password. All employees can edit basic information such as newly acquired
technical skills and emergency contacts. The SAD has the ability to view all users
under his/her department, assign a task and trainings. Upon logging in to the system,
the HR manager gets notifications on the leave applications submitted and has the
ability to approve or reject leave requests as they are submitted.

The HR carries out all employee tasks which include the ability to view and edit
basic details, view pending tasks, projects and trainings. The HR also has to the
ability to generate employee reports in PDF format.

18
4.1 Problem Statement
Manual handling of hospital information poses a number of challenges. The use of
paper work in handling some of these processes could lead to human error, papers
may end up in the wrong hands and not forgetting the fact that this is time
consuming. A number of current systems lack employee self-service meaning
employees are not able to access and manage their personal information directly
without having to go through their HR departments or their managers have all the
employee information stored at the headquarters of the company making it difficult
to access the employee information from remote places when needed at short notice.
The aforementioned problems can be tackled by designing and implementing a web
based Hospital management system. This system will maintain patient information
in a database by fully privacy and authority access. The project is aimed at setting
up hospital information system about background and the work experience in order
to help monitor the performance and achievements of the employee through a
password protected system.

19
4.2 System Interface & Design

Login Form

Figure 3 Login form

protected void Button1_Click(object sender, EventArgs e)

{
if (txtusername.Text == "" || txtpassword.Text == "")
{
message.Text = "Empty Fields not allowed";
}

else
{
Connection obj = new Connection();
obj.conection();
obj.sql = "Select * From Users Where Username='" +
txtusername.Text + "' and password='" + txtpassword.Text + "'and
user_type='" + txttype.Text + "' ";
obj.cmd = new SqlCommand(obj.sql, obj.con);
obj.dr = obj.cmd.ExecuteReader();
string type=txttype.Text;

if ((obj.dr.Read()) == true)

20
 {
type = obj.dr[4].ToString();
if (txttype.Text == "Admin")
this.Dispose();
Response.Redirect("Homepage.aspx");
}
else if (txttype.Text == "User")
Response.Redirect("user_mainform.aspx");
else
message.Text = "Username And Password Is Incorrect";
{

message.Text = "Username And Password Is Incorrect";

txtusername.Text = "";
txtpassword.Text = "";
txtusername.Focus();

}
protected void Button2_Click(object sender, EventArgs e)
{
Response.Redirect("forget.aspx");
}
}

21
User main form

Figure 4 User Main form

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
<link rel="stylesheet" href="style.css">
<style type="text/css"> </style>

</head>
<body>
<table align="center" class="auto-style20">
<tr>
<td class="auto-
style27">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
nbsp;&nbsp;&nbsp;&nbsp
<asp:Image ID="Image1" runat="server" Height="57px"
ImageUrl="~/Imgs/1200px-Emblem_of_Somaliland.svg.png" Width="96px"
style="text-align: center" />
</td>
<td class="auto-style28">

22
 <strong><span class="auto-style23">HOSPITAL MANAGEMENT
SYSTEM</span></strong></td>
<td><strong><span class="auto-style19"><asp:Image
ID="Image2" runat="server" Height="55px" ImageUrl="~/Imgs/1200px-
Emblem_of_Somaliland.svg.png" Width="108px" />
</span></strong></td>
</tr>
</table>
<p class="auto-style16">
<strong><span class="auto-style17">Somaliland Ministry Of
Health Development</span></strong></p>

<div class="sideBar">

<nav>

<ul>
<li><a href="#">Patient Registration</a></li>
<li><a href="#">Patient Details<a/></li>
<li><a href="#">OPD<a></li>
<li> <a href="#">Staff Management</a></li>
<li> <a href="#">Billing Management</a></li>
<li> <a href="#">Blood-bank Management</a></li>
<li> <a href="#">Birth Registration</a></li>
<li> <a href="#">Birth Certificate</a></li>
<li> <a href="#">Create User</a></li>
<li class="dropdown"> <a href="#">Show Records
<span>&rsaquo;</span></a>
<ul>
<li> <a href="#">Birth Certificate</a></li>
<li> <a href="#">Birth Certificate</a></li>
</ul>
</li>
<li> <a href="#">About</a></li>
<li> <a href="#">Contact</a></li>
<li> <a href="#">Logout</a></li>
</ul>
</nav>

<div class="image">
&nbsp;<img alt="" class="auto-style26"
src="../Imgs/vvvvvv.jpg" /></div>

</div>
<table class="auto-style4" border="1">

<tr>

23
 <td class="auto-style6"><span class="auto-style5">
<strong>© All Rights Are Reserved s Are Reserved
</strong></span>&nbsp;<asp:HyperLink ID="HyperLink12" runat="server"
CssClass="auto-style5" Font-Bold="True" NavigateUrl="~/homepage.aspx">
© Hospital Management System</asp:HyperLink>
</td>

</tr>
</table>

</body>
</html>

24
Patient Registration Form

Figure 5 Patient Registration

if (txtid0.Text == "" || txtbirthdate.Text == "" ||
txtfirst_name.Text == "" || txtlast_name.Text == "" || txtage.Text ==
"" || txtcontact.Text == "" || txtgender.Text == "" || txtblood.Text
== "" || txtmarital.Text == "" || txtoccupation.Text == "" ||
txtdepartment.Text == "")
{
message.Text = "Empty Fields not allowed";
return;

}
Connection v = new Connection();
v.conection();
v.sql = "Select * From patient where first_name= '" +
txtfirst_name.Text + "'";
v.cmd = new SqlCommand(v.sql, v.con);
v.dr = v.cmd.ExecuteReader();
if (v.dr.Read() == true)
{

25
 message.Text = "This user account exists or used his name
before try to create another one!";
return;
}
//XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
if (txtfirst_name.Text == txtlast_name.Text)
{
message.Text = "The First Name And Last Name are Same";

return;
}
else
{

Connection obj = new Connection();

obj.conection();
obj.sql = "insert into patient values('" + txtid0.Text +
"' , '" + txtbirthdate.Text + "' ,'" + txtfirst_name.Text + "' ,'" +
txtlast_name.Text + "','" + txtage.Text + "','" + txtcontact.Text +
"', '" + txtgender.SelectedItem + "', '" + txtblood.SelectedItem +
"','" + txtmarital.SelectedItem + "','" + txtoccupation.Text + "' ,'"
+ txtdepartment.Text + "' )";
obj.cmd = new SqlCommand(obj.sql, obj.con);
obj.dr = obj.cmd.ExecuteReader();
message.Text = "New User Sucessfully Registred";

}
protected void Button2_Click(object sender, EventArgs e)
{
Auto();
message.Text = "";

txtfirst_name.Text = "";
txtlast_name.Text = "";
txtcontact.Text = "";
txtage.Text = "";
txtoccupation.Text = "";
txtdepartment.Text = "";
}
}

26
Patient Details Form

Figure 6 patient details

if (txtid.Text == "" || txtfirst_name.Text == "" || txtlast_name.Text
== "" || txtward_no.Text == "" || room_no.Text == "" || txtpain.Text
== "" || txtgender.Text == "" || txtblood.Text == "" ||
txtlaboratory.Text == "" || txttreatment.Text == "" || txtdetails.Text
== "")
{
message.Text = "Empty Fields not allowed";
return;

}
Connection v = new Connection();
v.conection();
v.sql = "Select * From patient_details where first_name = '" +
txtfirst_name.Text +"' and last_name= '" + txtlast_name.Text + "'";
v.cmd = new SqlCommand(v.sql, v.con);
v.dr = v.cmd.ExecuteReader();
if (v.dr.Read() == true)
{

27
 message.Text = "This user account exists or used his name
before try to create another one!";
return;
}
//XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
if (txtfirst_name.Text == txtlast_name.Text)
{
message.Text = "The First Name And Last Name are Same";

return;
}
else
{

Connection obj = new Connection();

obj.conection();
obj.sql = "insert into patient_details values('" +
txtid.Text + "' ,'" + txtfirst_name.Text + "' ,'" + txtlast_name.Text
+ "','" + txtward_no.Text + "','" + room_no.Text + "','" +
txtpain.Text + "', '" + txtgender.SelectedItem + "', '" +
txtblood.SelectedItem + "','" + txtlaboratory.Text + "','" +
txttreatment.Text + "' ,'" + txtdetails.Text + "' )";
obj.cmd = new SqlCommand(obj.sql, obj.con);
obj.dr = obj.cmd.ExecuteReader();
message.Text = "New User Sucessfully Registred";

28
Blood bank Management Form

Figure 7 Blood bank management

if (txtid.Text == "" || txtfirst_name.Text == "" || txtlast_name.Text
== "" || txtbirthdate.Text == "" || txtage.Text == "" ||
txtcontact.Text == "" || txtgender.Text == "" || txtblood.Text == "" )
{
message.Text = "Empty Fields not allowed";
return;

}
Connection v = new Connection();
v.conection();
v.sql = "Select * From bloodbank where first_name= '" +
txtfirst_name.Text + "' and last_name ='" + txtlast_name.Text + "' ";
v.cmd = new SqlCommand(v.sql, v.con);
v.dr = v.cmd.ExecuteReader();
if (v.dr.Read() == true)
{
message.Text = "This user account exists or used his name
before try to create another one!";
return;
}
//XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

29
 if (txtfirst_name.Text == txtlast_name.Text)
{
message.Text = "The First Name And Last Name are Same";

return;
}
else
{

Connection obj = new Connection();

obj.conection();
obj.sql = "insert into bloodbank values('" + txtid.Text +
"' ,'" + txtfirst_name.Text + "' ,'" + txtlast_name.Text + "','" +
txtbirthdate.Text + "' ,'" + txtage.Text + "','" + txtcontact.Text +
"', '" + txtgender.SelectedItem + "','" + txtblood.SelectedItem +
"')";
obj.cmd = new SqlCommand(obj.sql, obj.con);
obj.dr = obj.cmd.ExecuteReader();
message.Text = "New Blood Bank Were Sucessfully
Registred";

30
Staff Registration Form

Figure 8 Staff registration

if (txtid.Text == "" || txtbirthdate.Text == "" || txtfirst_name.Text
== "" || txtlast_name.Text == "" || txtage.Text == "" ||
txtcontact.Text == "" || txtgender.Text == "" || txtstaff_title.Text
== "")
{
message.Text = "Empty Fields not allowed";
return;

}
Connection v = new Connection();
v.conection();
v.sql = "Select * From staff where first_name= '" +
txtfirst_name.Text + "'";
v.cmd = new SqlCommand(v.sql, v.con);
v.dr = v.cmd.ExecuteReader();
if (v.dr.Read() == true)
{

31
 message.Text = "This user account exists or used his name
before try to create another one!";
return;
}
//XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
if (txtfirst_name.Text == txtlast_name.Text)
{
message.Text = "The First Name And Last Name are Same";

return;
}
else
{

Connection obj = new Connection();

obj.conection();
obj.sql = "insert into staff values('" + txtid.Text + "'
,'" + txtfirst_name.Text + "' ,'" + txtlast_name.Text + "','" +
txtbirthdate.Text + "' ,'" + txtcontact.Text + "','" + txtemail.Text +
"','" + txtaddress.Text + "','" + txtage.Text + "', '" +
txtgender.SelectedItem + "', '" + txtstaff_title.SelectedItem + "')";
obj.cmd = new SqlCommand(obj.sql, obj.con);
obj.dr = obj.cmd.ExecuteReader();
message.Text = "New User Sucessfully Registred";

32
Staff Billing Form

Figure 9 Staff Billing form

if (txtid.Text == "" || txtfirst_name.Text == "" || txtlast_name.Text
== "" || salary.Text == "" || date.Text == "" || txtmonth.Text == ""
|| txttitle.Text == "" || txtpayment.Text == "" )
{
message.Text = "Empty Fields not allowed";
return;

}
Connection v = new Connection();
v.conection();
v.sql = "Select * From billing where first_name= '" +
txtfirst_name.Text + "' and last_name ='" + txtlast_name.Text + "' ";
v.cmd = new SqlCommand(v.sql, v.con);
v.dr = v.cmd.ExecuteReader();
if (v.dr.Read() == true)
{
message.Text = "This user account exists or used his name
before try to create another one!";
return;
}

33
 //XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
if (txtfirst_name.Text == txtlast_name.Text)
{
message.Text = "The First Name And Last Name are Same";

return;
}
else
{

Connection obj = new Connection();

obj.conection();
obj.sql = "insert into billing values('" + txtid.Text + "'
,'" + txtfirst_name.Text + "' ,'" + txtlast_name.Text + "','" +
salary.Text + "' ,'" + date.Text + "','" + txtmonth.SelectedItem + "',
'" + txttitle.SelectedItem + "','" + txtpayment.SelectedItem + "')";
obj.cmd = new SqlCommand(obj.sql, obj.con);
obj.dr = obj.cmd.ExecuteReader();
message.Text = "New Monthly Billing Were Sucessfully
Registred";

34
Birth registration Form

Figure 10 Birth registration

if (txtid.Text == "" || txtfirst_name.Text == "" || txtlast_name.Text
== "" || txtmother.Text == "" || txtcontact.Text == "" ||
birthdate.Text == "" || txtgender.Text == "" || txtblood.Text == "" ||
txtdetails.Text == "")
{
message.Text = "Empty Fields not allowed";
return;

}
Connection v = new Connection();
v.conection();
v.sql = "Select * From birth_register where first_name = '" +
txtfirst_name.Text + "' and last_name= '" + txtlast_name.Text + "'";
v.cmd = new SqlCommand(v.sql, v.con);
v.dr = v.cmd.ExecuteReader();
if (v.dr.Read() == true)
{
message.Text = "This user account exists or used his name
before try to create another one!";
return;
}
//XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
if (txtfirst_name.Text == txtlast_name.Text)
{

35
 message.Text = "The First Name And Last Name are Same";

return;
}
else
{

Connection obj = new Connection();

obj.conection();
obj.sql = "insert into birth_register values('" +
txtid.Text + "' ,'" + txtfirst_name.Text + "' ,'" + txtlast_name.Text
+ "','" + txtmother.Text + "','" + txtcontact.Text + "','" +
birthdate.Text + "', '" + txtgender.SelectedItem + "', '" +
txtblood.SelectedItem + "','" + txtdetails.Text + "' )";
obj.cmd = new SqlCommand(obj.sql, obj.con);
obj.dr = obj.cmd.ExecuteReader();
message.Text = "New Birth Record were Sucessfully
Registred";

36
User registration Form

Figure 11 Create Users

if (txtId.Text == "" || txtuser.Text == "" || txtpassword.Text == ""
|| txtconfirm_pass.Text == "" || txtusertype.Text == ""||
Secret_question.Text == "" || Secret_answer.Text=="")
{
message.Text = "Empty Fields not allowed";
return;

}
Connection v = new Connection();
v.conection();
v.sql = "Select * From Users where Username= '" + txtuser.Text
+ "'";
v.cmd = new SqlCommand(v.sql, v.con);
v.dr = v.cmd.ExecuteReader();
if (v.dr.Read() == true)
{
message.Text = "This user account exists or used his name
before try to create another one!";
return;
}
//XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
if (txtpassword.Text != txtconfirm_pass.Text)
{
message.Text = "Mismatch of Password Confirmation";

37
 return;
}
else
{

Connection obj = new Connection();

obj.conection();
obj.sql = "insert into Users values('" + txtId.Text + "' ,
'" + txtuser.Text + "' ,'" + txtpassword.Text + "' ,'" +
txtconfirm_pass.Text + "', '" + txtusertype.SelectedItem + "', '" +
Secret_question.SelectedItem + "','" + Secret_answer.Text + "' )";
obj.cmd = new SqlCommand(obj.sql, obj.con);
obj.dr = obj.cmd.ExecuteReader();
message.Text = "New User Sucessfully Registred";

38
 Chapter Five: IMPLEMENTATION & TESTING
This chapter will explore the different aspects concerned with the implementation of
the developed system. This project was concerned with the development and
implementation.
The Hospital management system we began with analysis of the current and
proposed systems, the design of the system to be developed, and in this chapter we
shall deal with implementation of the developed system.
Testing is very important and critical to the success of any project that aims at
delivering working software.
There are many types of testing that a system may be subjected to, however only
the ones in the testing objectives will be carried out for this system.
The goals in testing this system include validating the quality, usability, reliability
and performance of the application.
Hospital Management System is a distributed web application, developed to
maintain the details of employees working in any hospital.
It maintains the information about the patient, doctors, and other departments of the
hospital, also the details about the payroll system which enable to generate the
payslip.
The web application is actually a suite of web applications developed using
Asp.net with c#.
It is simple to understand and can be used by anyone who is not even familiar with
Simple hospital system. It is user friendly and just asks the user to follow step by
step operations by giving him few options. It is fast and can perform many operations
of a hospital.
This web package has been developed using the powerful coding tools of Asp.net
with c# at Front End and Microsoft Sql Server at Back End. The website is very
user friendly.
The package contains different modules like patient details.
Hospital Management system is a web application that enables users to create and
store Hospital Records. The web application also provides facilities of a payroll
system which enables user to generate Pay slips too.
This web application is helpful to department of the organization which maintains
data of hospital related to an organization.
Asp.net is a platform independent language. Its created applications can be used on
a standalone machine as well as on distributed network.
Thus ASP project was chosen as background to design this application.
39
5.1 CONCLUSION
Since this project has been designed exclusively as a project, certain complexities
that do faced by any real life manual problem like total no. of patient, address
redundancy etc. are considered in this project. But enhancement to the project can
easily be made without changing the current design and programming structure.

40
5.2 Reference
www.academia.edu/6880602/09_Project_Hospital_management_system
www.researchgate.net/publication/343149774_Hospital_Management_System
Hospital Management System.pdf
www.academia.edu/36406675/Hospital_Management_System_Project_report
School Of coding / Hospital Management system.pdf
https://www.amazon.com/Design-Development-Hospital-Management-
System/dp/3847330519

41