[College Logo]

Zion and Technology Business

College

DEPARTMENT OF Computer Science/INFORMATION Technology

Project Title: - --------------------------------------------------

A PROJECT SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR

THE AWARD OF BACHELORS OF SCIENCE (B.Sc.) IN INFORMATION SYSTEM

Group Members
No Name ID No Signature

1.
2.

Advisor Mr. ----------------- (MSc/Phd)

Submitted to: CS/ Department

Submission date: May 27, 2021

Hawassa, Ethiopia
Acknowledgement
Apart from the efforts of all the team members, the section of this project report topic depends
largely on the encouragement and guidance of our teachers. We take this opportunity to express our
gratitude to the teachers who have been instrumental in the approval of this project topic. We would
like to show our greatest appreciation to assistant Prof.. Abdela.Kand other staff members. We
cannot think them enough for their tremendous support and help. They motivated and encouraged
use very time while selecting the proper project topic. Without their encouragement and guidance,
we would not have been able to select the proper topic. The contribution and support received from
all the team members including Yewalashet, Bereket, Misgana, Biruk, Mihret & Nata is vital. The
team spirit shown by all has made a project report work successful.

1|Page
Table of Contents

2|Page
List of Tables

3|Page
List of figures

4|Page
ACRONYMS

5|Page
Abstract
The purpose of the project entitled as “HOSPITAL MANAGEMENT SYSTEM” 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 main
function of the system is register and store patient details and doctor details and retrieves
these details as and when required, and also to manipulate these details meaningfully
System input contains patient details, diagnosis details, while system output is to get
these details on to the screen. The Hospital Management System can be entered using a
username and password. It is accessible either by an administrator or receptionist. Only
they can add data into the database. The data can be retrieved easily. The data are well
protected for personal use and makes the data processing very fast.

6|Page
CHAPTER ONE

1. INTRODUCTION
1.1. Background of the Study
Healthcare especially in the developed world is characterized by rapidly increasing use
of information technology in patient care, increasing documentation, coding and
billing, and management. Rise of health information technology worldwide is increasing
the efficiency of health service delivery, reducing medical errors, improving quality of
care and providing better information for patients and physicians (Pollak and Lorch,
2007:4). The overall goal of the information management function is to obtain,
manage, and use information to improve health care and medical services,

7|Page
 performance, governance and management and support processes. The importance
of healthcare to individuals and governments and its growing costs to the economy have
contributed to the emergence of healthcare as an important area of research for scholars
in business and other disciplines. Information systems (IS) have much to offer in
managing healthcare costs and in improving the quality of care (Kolodner et al. 2008:
394).In additional, Piontek et al., (2010: 618) asserts that healthcare influences the
quality of human lives and function in the society. Healthcare mistakes have serious
consequences that can affect ability to carry out social and productive endeavors. Recent
reports highlight the gravity of adverse events in hospitals and the dangers such events
pose to individuals and the public. Healthcare information systems have changed the
healthcare industry drastically over the last decade as well as the last few years
(Abraham & Jungles). The forces of competition and advancements in healthcare
technology are pushing hospitals to follow the trend. Paperless healthcare systems have
become inevitable and any healthcare institute that doesn’t follow this trend will fall
behind the rest of the industry.
Health information system is a must and the faster this is adopted the more successful
the health care facility will be.(Swanson et al. 2010: 9). Delone and Mclean being one of
the most cited models in the fields of information systems seeks to provide
a comprehensive understanding of information systems success by identifying,
describing, and explaining the relationships between six success variables categories:
systems quality, information quality, user, user satisfaction, individual impact, and
organizational impact. Delone & Mclean (2003) model provides a comprehensive
frame work for measuring the performance of the information system and enhances the
understanding of information systems success. World Health Organization (WHO,
2008) cautions that, the goal of a health information system is often narrowly defined as
the production of good-quality data. The ultimate goal is to produce relevant
information that health system stakeholders can use for making transparent
and evidence-based decisions for health system interventions. Health information
management system performance should therefore be measured not only on the
quality of data produced, but on evidence of the continued use of data to
improve health system performance, respond to emergent threats, and improve

8|Page
 health (WHO, Improving health information systems in terms of data availability,
quality and use often requires interventions that address a wide range of possible
‘determinants of performance. Health information systems recognizes that although
new developments in technology, including the use of the internet and other modes of
communication offer great potential in the flow of information amongst the providers
and recipients regarding the provision and management of healthcare services, the
Ethiopian health sector remains far behind in taking advantage of such developments to
improve reporting (HIS, 2008). Despite vast amounts of resources and time invested in
the development and implementation of health information systems, health data
is barely used by health workers for service delivery planning and decision-
making. Performance is grossly under reported with developments to improve
information management lagging behind other sectors improvement activities;
the whole culture of information generation and use remain under-developed;
and mechanisms for validating and assuring reliability are not optimally functional.
1.2. Statement of the Problem
This chapter provides a comprehensive definition of the problem, people's perception of
the problem, and then provides a conceptual strategy for problem solving, ways to solve
it, the importance of problem solving, and then it passes to theoretical program
design for problem solving and technology. The study used to solve this problem.
A theoretical study of the problem and how to solve it
Problems with conventional system:
1. 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.
2. Lack of immediate information storage: - The information generated by
various transactions takes time and efforts to be stored at right place.
3. Lack of prompt updating: - Various changes to information like patient
details or immunization details of child are difficult to make as paper work is involved.
4. Error prone manual calculation: - Manual calculations are error prone and take a
lot of time this may result in incorrect information. For example: calculation of patient’s
bill based on various treatments.

9|Page
 5. Preparation of accurate and prompt reports: - This becomes a difficult task as
information is difficult to collect from various registers.
1.3. Objectives of the Project
The objective of this project is to develop hospital management software based on
Microsoft window application with structured Query language (T-SQL and SQL Server
as a database) as the back-end database hospital from file based system to a computer
database system. This software will help the company to be more efficient in
handling the daily activities and registration of their patients. The purpose of this
project is to give a complete requirement documentation, design, and implementation of
the software. It also explains the user interface, hardware and software and different
models that could be used to develop software such as this. Hospital are the
essential part of our lives, providing best medical facilities to people suffering from
various ailments, which may be due to change in climatic conditions,
increased work-load, emotional trauma stress etc. It is necessary for the hospitals to
keep track of its day-to-day activities & records of its patients, doctors, nurses, ward
boys and other staff personals that keep the hospital running smoothly & successfully.
But keeping track of all the activities and their records on paper is very cumbersome and
error prone. It also is very inefficient and a time-consuming process
Observing the continuous increase in population and number of people visiting the
hospital. Recording and maintaining all these records is highly unreliable, inefficient and
error-prone. It is also not economically & technically feasible to maintain these records
on paper. Thus keeping the working of the manual system as the basis of our project.
We have developed an automated version of the manual system.
. The main aim of our project is to provide a paper-less hospital up to 90%. It also aims
at providing low-cost reliable automation of the existing systems. The system also
provides excellent security of data at every level of user-system interaction and also
provides robust &reliable storage and backup facilities

1.3.1. General Objective (aim)

To develop a Hospital Management System that could address the issues that occur
in each manual system.

10 | P a g e
1.3.2. Specific objectives
1. Provide the standard coverage of records that can transacts.
2. Manage physical and medical check-ups services.
3. Deliver quick and reliable service on real- time basis.

1.4. Scope of the Study

As a result of resource limitations in both time and money, this study is based on patient
management, secure access of users and hierarchy of information and integration of all
users in to the health care delivery process.
1.5. Limitation of the Study
A lot of setbacks were encountered in course of this project. There were constraints in
many areas like:
i) FINANCE: The high cost of materials of the project and the everyday constraints
is increase in transportation taxi during data collection affected the research
work.
ii) DATA COLLECTION: The research work had a problem in collecting data from
a staff. However, we still remain indebted to the staff who generously
contributed immensely making this project successful.
iii) MATERIAL: Material constraints play a major role in that limiting some
research that would have contributed immensely.
1.6. Significance of the project
The study is important to the hospital patients since they could have medical information
without experiencing delays and incorrect information. If they wanted to access their
medical history, they would not be going through a difficult process. The hospital
especially the pharmacy and billing department would not go through a lot of paper
reports when it comes to payments and accounting records. The use of paper would still
be there but it could be reduced so that excessive paper loads would not be a problem.
The study was also significant to the staffs since they would be able to register, update,
delete, and search information within the system. It was beneficial to the hospital
since it could improve their management through connecting all their existing

11 | P a g e
 computers in one system. In general, the study was important to the hospital and
patients for it could serve as an applicable tool to maintain the productivity and quality
of service in the hospital. Hospital is a leading among the public hospital. Health
system functioning depends on production and use of quality health data and information
at all levels of the health system. This study serves as a starting point for the
assessment of HMS based on the situation in public to identify the strengths and
weakness of the system in improving health system functioning. The study forms a
basis for further research on evidence based management of health services in general
and specifically lead to generation of new ideas for better and more efficient
management of health facilities in Hawassa and the country at large. The study will look
at the use of hospital information system in a private and a public hospital. Findings
and recommendations of the study would contribute towards the ongoing efforts of
ministry of health to develop better health management operations system that would
benefit facilities and healthcare workers identify their weakness and thus propose better
ways that could help improve their efficiency through improved information use. The
findings of the study will be used by all health care workers and health care managers as
and will not rely on haphazard personal experiences or subjective personal judgments
or of friends/relative other than base their decisions and actions on concrete evidence
and thus help re-invent themselves as problem solvers.

1.7. Methodology
A methodology is defined as a collection of procedures, techniques, tools, and
documentation aids which will help developers in their efforts (both product and process
related activities) to implement a new system. For successful implementation, a well-
organized and systematic approach is crucial. Therefore, several methodologies were
developed to encourage the systematic approach to planning, analysis, design, testing
and implementation. Methodologies offer various tools and techniques to assist in
analysis, design and testing in terms of detailed design of software, data flowcharts and
database design.
Why Methodology?

12 | P a g e
 1. To complete a project within time and budget with the expected scope and quality we
need methodologies which provide for a framework.
2. Most methodologies have a general planning, developing and managing stages in
common. They suggest the development team the ways of thinking, learning and
arriving at a regular feasible solution.
1.7.1. Data Collection Methodology
a) Semi-structured interviews - Semi-structured interviews are conducted with a fairly
open framework which allow for focused, conversational, two-way communication. They
will be used both to give and receive information. In the process of developing the
system, the development team will interview the data entrants at Nahol hospital in order
to identify the processes, obtain specific quantitative and qualitative information from the
interviewees, obtain general information relevant to data entry, and to Gain a range of
insights on the process of the system. This tool will be used as a data collection
methodology of choice because it is; less intrusive to those being interviewed as the
semi-structured interview encourages two-way communication.
b) Direct Observation Direct Observation is a method in which a researcher observes and
records behavior / events / activities / tasks / duties while something is happening. This
will be used in correspondence to interviewing in order to gain a more live view of the
Hospital’s current management system. Direct observation will be used as a research
methodology of choice in designing the management system for Nahol Hospital because;
Observations give additional, more accurate information on behavior of people than
interviews or questionnaires.
c) Using available information this is a data collection method that involves the process
of examining and evaluating already
d) Online: It is our second source of information. We have also been watching tutorials
online about how other Hospital management systems work in other countries.
1.7.2. System Analysis and Design Methodology (only for software
development)

Object Oriented Approach

13 | P a g e
The methodology we will be using is object-oriented approach, the focus is on capturing the
structure and behavior of information systems into small modules that combines both data and
process. The main aim of Object Oriented Design (OOD) is to improve the quality and
productivity of system analysis and design by making it more usable.

In analysis phase, OO models are used to fill the gap between problem and solution. It performs
well in situation where systems are undergoing continuous design, adaption, and maintenance. It
identifies the objects in problem domain, classifying them in terms of data and behavior.

1.7.3. Development Tool and Technologies (working Environment)

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
 En closed in angle (like <html>). HTML tags most commonly come in pairs
like <h1> and </h1>, although 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

14 | P a g e
 written in languages such as JavaScript which affect the behavior of HTML web
pages.
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 .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 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.
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 plat forms. The data in

15 | P a g e
 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.
 Uses multi-layered server design with independent modules. 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.
 Support for up to 64 indexes per table (32 before MySQL 4.1.2). Each index may
consist of 1to 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.
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

16 | P a g e
 LOCALIZATION:
The server can provide error messages to clients in many languages.
All data is saved in the chosen character set.
CLIENTS AND TOOL:
MySQL includes several client and utility programs. These include both
command-line programs such as MYSQL dump and MYSQL admin, 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
MYSQL check client. MySQL also includes
my isamchk , a very fast command-line utility for performing these operations on

MyISAM tables.
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

17 | P a g e
 code can be inserted in to 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
Example
x = document. Get Element by Id ("demo"); //Find the HTML element with
id="demo "x. inner HTML = "Hello JavaScript"; //Change the content of the HTML
element document. Get Element by Id () is one of the most commonly used HTML
DOM methods.
OTHER USES OF JAVASCRIPT:
 Delete HTML elements
 Create new HTML elements
 Copy HTML elements
 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

18 | P a g e
 documentgetElementById("demo").innerHTML="Hello
Dolly";document.getElementById("myDIV").innerHTML="How are you?";
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
PHP costs nothing, it is free to download and use
WHAT IS PHP FILE?
PHP files can contain text, HTML, CSS, JavaScript, and PHP code
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, and 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 XML.
WHY PHP?
PHP runs on various platforms (Windows, Linux, Unix, Mac OS X, etc.)
PHP is compatible with almost all servers used today (Apache, IIS, etc.)
PHP supports a wide range of databases
PHP is free. Download it from the official PHP resource: www.php.net

19 | P a g e
1.7.4. System Implementation (only for software development).

Implementation is the process of having system personal check out and provides
new equipment’s into use, train the user 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. To problem
encountered are covering files, training user, 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. So large computer system many take as long as a year to
convert. Implementation of a modified application to replace the existing one using
the same computer. This type of conversing is relatively easy to handle, usually
there are no major change in the file. Our project is yet to be implemented.
Implementation Environment
The implementation view of software requirement presents the real world
manifestation of processing functions and information structures. This computerized
system is specified in a manner that dictates accommodation of certain
implementation details. The implementation environment of the developed system
facilitates multiple users to use this system simultaneously. The user interfaces are
designed keeping in mind that the users of this system are familiar to using GUI-
based systems. Thus, we restricted ourselves to developing a GUI-based system so
that it becomes easier for the end user to get acquainted to the developed system.

1.7.5. Testing and Deployment Methodology

Software testing is the final phase of the development of a software system, where
the program is executed step by step to evaluate its performance and detect errors.
We perform different testing procedures to check the functionality of our proposed
System. The following are some of the testing procedures.
 Unit testing: Unit testing is an action used to validate that separate units of source
code remains working properly. While implementing the code our project team
conducted the following types of unit test:

20 | P a g e
  Statement testing: Every statement in our project code is executed at least once to
look its correct functionality.
 Branch testing: Every decision point in the code is executed at least once to look
its correct functionality.
 Loop testing: Every loop in the code is executed at least once to look its correct
functionality.
 Integration Testing - Integration testing identifies problems that occur when units
are combined. After unit testing, our system is also tested whether every unit is
integrated to every other unit. The main aim of integration testing is to verify the
functional, performance, and reliability between the modules that are integrated. For
example in case of login if the user enters invalid user name or password process is
rejected this shows the integration among classes is properly working. Therefore we
implement a testing conducted on an integrated system to evaluate the HCMS
performance with its specified requirements.
 System Testing: -The system is functionally tested based on the use case model
developed during the analysis phase because they describe the exact behavior of
how the users work with the application. The entire system is tested and approved,
since it addresses all the user requirements such as accepts the data, process the
data, stores the data, notify data entry errors and retrieve stored data. By doing so
the system is working in line with the user ‟s requirements.

1.7.6. Security Methodology

Security and Access Permissions: - The system provides or contains user name and password for
each user based on their privilege. This performs the following activity: -

 Authenticated user with predefined access right will only enter to the information related
to database.
 Every user should use strong passwords especially admin.
 User must enter valid user name and password to login to system. Without this, access to
the system is denied.
 System allows only registered users to access hospital management system

21 | P a g e
1.7.7. Backup and Recovery Methodology
Backup and Recovery: - the team use removable flash disks, or CDs for backup and
recovery.
1.8. System Requirement (Only for System Development)

1.8.1. Software Requirement

Software Requirements

Operating System Database User Interface

design

Windows XP, Windows 7 Windows 8, Microsoft SQL Server Visual studio 2013,
Windows10 Management studio ,SQL Client NET Framework 4.5

Table (1.1): Software Requirement

1.8.2. Hardware Requirement

Hardware Requirement

Processor RAM Disk space

1.6 GHz or faster 1GB of RAM (1.5 GB if running 5400 RPM hard drive and
processor on a virtual machine) 5 GB of available hard disk
space

Table (1.2): Hardware Requirement

1.9. Feasibility Study
Feasibility study is carried out in order to find out if a certain project would be
successful given the environment and some characteristics done and also to suggest
possible alternative solutions. These characteristics are technical, operational and
economical.

22 | P a g e
1.9.1. Technical Feasibility
This is concerned with specifying equipment and software that will successfully
satisfy the user requirement; the technical needs of the system may vary
considerably, but might include: The facility to produce outputs in a given time:
1. Response time under conditions.
2. Ability to process a certain volume of transaction at a particular seep.
3. Facility to communicate data to distant location.

1.9.2. Operational Feasibility

It is mainly related to human organization and political aspects. The points to
be considered are:
1. What changes will be brought with the system?
2. What organizational structures are distributed?
3. What new skills will be required? Do the existing staff members have these
skills? If not, can then the trained due course of time.

1.9.3. Economic Feasibility

Economic analysis is the most frequently used technique for evaluating the
effectiveness of a proposed system. More frequently known as cost/benefit system
and compare them with costs. If benefits outweigh costs, a decision is taken to
design and implement the system.
1.10. Cost Estimation and Schedule Breakdown

1.10.1. Cost Estimation

Even though it is difficult to provide an accurate cost estimate, the following is a
rough estimate of the costs associated with the project excluding knowledge, skill
time and energy of the member student

Item Quantity Unit price Total

Hardware Flash 1 300 300

23 | P a g e
 Cd 3 25 75
A4 paper 1 275 275
Notebook 1 50 50
Pen 6 10 70
Software Apache server 1 20 20
MYSQL 1 20 20
Notepad 1 20 20
Xamp/Xampp 1 30 60

Other cost Any cost we - - 500

may spend
through project
time line
Contingency 5% 70
Total 1460

1.10.2. Schedule Breakdown

Each part of tasks of the project is delivered by collaborating with each of the group
members. Each group members have equal responsibility to complete the project
successfully. Our project contains list of activities, number of days used to
accomplish a task with its start and end date, deliverables of each phase

The table below describes time schedule of or project.

Number Activity November December January February

1 Title selection 

2 Writing 
Proposal

3 Requirement 
gathering

24 | P a g e
 4 Analysis phase  

5 Implementatio 
n phase

6 Testing 

CHAPTER TWO

2. DESCRIPTIONS OF EXSTING SYSTEM

2.1.1. Introduction of the Existing System
Hospitals currently use a manual system for the management and maintenance of
critical information. The current system requires numerous paper forms, with data
stores spread throughout the hospital management infrastructure. Often information is
incomplete or does not follow management standards. Forms are often ost in
transit between departments requiring a comprehensive auditing process to ensure
that no vital information is lost. Multiple copies of the same information exist in the
hospital and may lead to inconsistencies in data in various data stores.
2.1.2. Proposed System Description
Hospital Management System is designed for any hospital to replace their existing
manual paper based system. The new system is to control the information of patients.
Room availability, staff and operating room schedules and patient invoices. These
services are to be provided in an efficient, cost effective manner, with the goal of
reducing the time and resources currently required for such tasks .

2.1.3. Strength of Existing System

2.1.4. Weakness of Existing System

25 | P a g e
CHAPTER THREE

3. SYSTEM FEATURES
3.1.Introduction
To make a Hospital management system software, you should clearly understand what
processes you want to establish, what functions the system will support, and clearly
define its users. All the determined requirements for the system are fixed in SRS
(Software Requirements Specification) to achieve a common vision on the product with
your vendor and lay down the optimal set of functions. Accurate estimation is also
formed on an SRS basis. It can be drawn for you by a specialized company or a vendor
that provides the software product on a
3.2.Functional requirements
Functional requirements are the description of the facility or feature required. Functional
requirements deal with what the system should do or provide for users. They include
description of the required functions, outlines of associated reports or online queries, and
details of data to be held in the system.
The following are the functional requirements of the proposed system.
Patient registration. The registration consists of adding patients to the system and
assigning unique IDs to them, which each patient will use while in the hospital.
Checkout. All data is archived after patients’ discharge and saved for reuse.
Treatment. Allows a doctor to keep all the necessary documentation for patients’
treatment. This includes maintaining a treatment plan, managing analysis and
prescriptions, storing data, and monitoring their medical history.
Data report generation. Report generation consists of creating and storing patient
information in the form of a report, which includes the name, phone number, bed
number, name of the attending physician, etc. In addition, the generation of reports on the
presence/absence of free beds also applies to this requirement.
Billing system. Hospital billing software provides safe and reliable work with finances in
the organization. It automatically generates detailed budget data and reports on in-patient,
laboratory, and pharmacy services.
Search. The search capability allows you to quickly find the right doctors, patients,
certain information about the services and work of hospitals. Using the search, patients

26 | P a g e
 can find out their test results, the cost of services, and the physicians’ working hours,
while doctors can read the data about their patients.

 Inventory Management. Inventory management saves an organization’s time and

money by reducing staff working hours on manual work with the inventory. It also
helps control the quantity and quality of available hospital resources, which allows
you to plan orders for medical supplies. Thanks to the automatic search and the
folder-based structure, the hospital staff can find the missing item in seconds.
 Data reports and statistics. The system includes the availability of mandatory
patient information and the ability to edit and update the data at any time.

3.3. Non-Functional requirements

Non-functional requirements define the efficient operation of HMS and must specify the
certain criteria the system must comply with. Let’s take them one by one:

 Security consists of:
o Patient identification and know your customer (KYC) mechanisms;
o Logon ID and encrypted password;
o Data security of incoming information must be guaranteed;
o Roles & Permissions requirements, which are based on the idea that each
user should see and do only what is allowed by the permission system, and
all others should be blocked.
 Performance includes:
o Response time — the system response must be fast, within one second of
the request;
o Capacity — support no less than 200 concurrent users, depending on the
size of the organization, and is unlimited for registration;
o Law compliance — the system should be adapted to the legal framework of
the country in which it is used.
 For maintainability, it is worth highlighting two points:
o Errors — the system records all errors that have occurred;
o Back-up — the availability of automatic and on-demand backups;
o Disaster recovery — allows you to quickly restore the code infrastructure on
a new server in case of loss or theft of a working device.
 Reliability lies in continuous accessibility of the system 24/7;
 Responsive design — the site should work well on all devices and browsers, so
you don’t have to create applications for other platforms.

3.4. System Analysis Models

27 | P a g e
 3.4.1. Introduction
3.4.2. Use Case Diagram
3.4.3. Sequence Diagram
3.4.4 Activity Diagram
3.4.5 Analysis Level Class diagram
3.4.6 User Interface Design
3.4.7 User Interface Prototyping

CHAPTER FOUR

4. SYSTEM DESIGN
4.1. Introduction
4.2. Purpose of the System Design Document (SDD)
Purpose of the System design document The purpose of the system design document of
Hospital Management System is to find out how the system is to be constructed and to get
the information needed, to control the actual implementation of the system. To specify it
 To provide a description for how the new Hospital management system will be
constructed.
 To find out the hardware/software stages on which the system will operate.
 To determine the architecture of the system to be developed.
 To determine the persistent data storage.

4.3. Design Goal

 The design goals represent the desired qualities the system should have and provide a
consistent set of criteria that would be taken into consideration when making design
decisions. The following are mentioned as the design goals.
 Usability: The system we will develop should provide user friendly and self-explanatory
graphical user interface that eases the interaction of the user with the system. In addition,
the system should be flexible, efficient, and reliable.
 Portability: the system should be able to run on any mobile that is web based.

28 | P a g e
  Performance: the main performance measure for a project is time, so the system should
give fast responses for user requests.
 Maintenance: The system should be easily extensible to add new functionalities. It
should also be easily modifiable to make changes to the features and functionalities.
 Availability: The system should be available for twenty-four hours per week (24/7) so
that users can have access to it anytime.
 Reliability: The system should maintain and perform its functionalities under any
condition.
 Dependability: The system should provide security in such a way that unauthorized users
can not have access to the system‟s resource.

4.4. Architectural Design

4.4.1. Logical View of the Architecture
4.4.2. Process View
4.4.3. Deployment View
4.5.
4.5. Database Design
4.4.1. ER Diagram
4.4.2. Relational Mapping & Database Normalization

CHAPTER FIVE

5. CONCLUSION AND RECOMMENDATION

5.1. Conclusion
5.2. Recommendation

References

Appendix

29 | P a g e