UNIVERSITY OF GONDAR

FACULITY OF INFORMATICS

DEPARTMENT OF COMPUTER SCIENCE

IBEX PRIMARY

HOSPITAL MANAGEMENT SYSTEM

By

Group member ID Number

1) Eshete Dagne ………………………………………GUR/3785/08

2) Ezezew Dagen …………………………………… GUR/07483/09
3) Kidist Fentahun …………………………………. GUR/3853/08
4) Kinfemichael Dembelo……………………………..GUR/3855/08
5) Mahilet Maru………………………………………GUR/3870/08

UNDER THE GUIDANCE OF

Mr. Kedir Yasin

04/14/2011
 CERTIFICATE

I certify that this BSC industrial project entitled online ibex primary hospital management
system written by:

Name of Group Member Signature

Ezezew Dagen –––––––––––

Eshete Dagne –––––––––––

Kidist Fentahun –––––––––––

kinfeMichael Dembelo –––––––––––

Mahilet Maru –––––––––––

This is approved by me for submission. I certify further that, to the best of my knowledge, the
report represents work carried out by the students.

________________________________________________
Date Name and Signature of Supervisor
 Ibex Primary Hospital Management System 2011

DECLARATION
This is to declare that the project work which is done under the supervision of Kedr Yasin and
having the title Ibex hospital management system is the full contribution of:

1. Ezezew Dagne _____________

2. Eshete Dagne _____________
3. Kidist Fentahun _____________
4. KinfeMichae Dembelo _____________
5. Mahilet Maru _____________

No part of the project work has been reproduced illegally (copy and paste) which can be
considered as Plagiarism. All referenced parts have been used to argue the idea and cited
properly. We will be responsible and liable for any consequence if violation of this declaration
occurs.

Date: 14/06/2019

Computer science Page ii

 Ibex Primary Hospital Management System 2011

ACKNOWLAGEMENT
We would like to thank the director of IBEX PRIMARY HOSPITAL for giving us relevant
information about the hospital and giving idea about what our system should provide in order to
make things easier for the hospital worker’s and to give good service for the customer.

Last but not least we thank our advisor Mr. Kedr Yasin for giving us such a wonderful
opportunity to expand our knowledge for our own branch and giving us guidelines to present a a
better industrial project. It helped us a lot to realize of what we study for.

Computer science Page iii

 Ibex Primary Hospital Management System 2011

ABSTRACT
The hospital is one of the most important Institutes in the world. The hospital must be
computerized to efficiently manage the data and patients.

Web based Ibex primary hospital management system is a system that minimize problems that
are caused by manual system that the primary hospital is using at this time. In this project we
intended to change the current manual system in to web based system that is interactive, easily
accessible because this system can be accessed by internet, helpful for the users in order to get
medical recommendations from their doctor at any time, to minimize overcrowding of
customers, to make support provider’s work easier. Generally it provides fast, efficient,
flexible, reliable and secure services for better satisfaction of customers and improvement of
motivation of the employee..

We used the object oriented software development methodology to conduct this project, the
programming language is PHP and HTML and the data repository is SQL. During the analysis
and design process of project our team used iterative software model. In order to collect
information about the hospital and it decide what the system should solve we use observation
and interview. We hope the proposed system will bring a great change on the way currently
IBEX primary hospital Management System is working.

Computer science Page iv

 Ibex Primary Hospital Management System 2011

Table of Contents
CERTIFICATE .......................................................................................................................... i
DECLARATION ...................................................................................................................... ii
ACKNOWLAGEMENT .......................................................................................................... iii
ABSTRACT ............................................................................................................................ iv
LIST OF FIGURE.................................................................................................................. viii
LIST OFTABLE ...................................................................................................................... ix
ACRONYM .............................................................................................................................. x
CHAPTER ONE ....................................................................................................................... 1
1.1. Introduction ................................................................................................................ 1
1.2. Background ................................................................................................................ 1
1.3. Statement of the problem ............................................................................................ 2
1.4. Objectives ................................................................................................................... 2
1.4.1. General objective ................................................................................................. 2
1.4.2. Specific objective................................................................................................. 3
1.5. Scope of project .......................................................................................................... 3
1.6. Limitation of project ................................................................................................... 3
1.7. Significance of project ................................................................................................ 3
1.9.1 Beneficiary of project ............................................................................................... 4
1.8. System development methodology .............................................................................. 4
1.8.1. Data collection (fact-finding) method................................................................... 5
1.9. System development tool ............................................................................................ 5
1.9.1. Software tools ...................................................................................................... 5
1.9.2. Hardware tools..................................................................................................... 6
1.10. Gantt chart............................................................................................................... 7
Chapter two .............................................................................................................................. 8
2.1 Introduction ..................................................................................................................... 8
2.2 Current system ................................................................................................................ 8
2.2.1 Major function of existing system description ........................................................... 8
2.2.2 Problem of current system ........................................................................................ 8
2.3 Requirement Gathering.................................................................................................... 9
2.3.1. Observation: ............................................................................................................ 9
2.3.2.Interview: ................................................................................................................. 9

Computer science Page v

 Ibex Primary Hospital Management System 2011
2.3.3. Results found ......................................................................................................... 10
2.4 Business rule ................................................................................................................. 10
2.5. Proposed system ........................................................................................................... 10
2.6. Requirement analysis of the new system ....................................................................... 11
2.6.1. Functional requirements......................................................................................... 11
2.6.2. Non functional requirements ...................................................................................... 13
2.7. System model ............................................................................................................... 16
2.7.1.Scenario.................................................................................................................. 16
2.7.2 Use case model ....................................................................................................... 19
2.7.2.1. Use case description............................................................................................ 21
2.7.2 Activity activity diagram ........................................................................................ 37
2.7.3. Object model ......................................................................................................... 44
2.7.3.1 Data dictionary .................................................................................................... 44
2.7.3 Class diagram .................................................................................................... 48
2.7.4 Dynamic modelling ................................................................................................ 50
2.7.4.1 Sequence diagram ................................................................................................ 50
2.7.5 User interface ......................................................................................................... 56
CHAPTER THREE ................................................................................................................ 57
3.1 INTRODUCTION ......................................................................................................... 57
3.2 Design goals and objectives ........................................................................................... 57
3.3. Current software architecture ........................................................................................ 58
3.4. Proposed System Architecture ...................................................................................... 58
3.4.1 Overview ................................................................................................................ 58
3.4.2 Subsystem decomposition ....................................................................................... 59
3.4.3 Hardware/software mapping ................................................................................... 61
3.4.4 Persistent data management .................................................................................... 62
3.4.5. Access control and security ....................................................................................... 63
3.4.6 Subsystem services ................................................................................................. 63
3.5Detailed class diagram .................................................................................................... 64
3.6Package diagram ............................................................................................................ 66
Chapter Four ........................................................................................................................... 67
Implementation ....................................................................................................................... 67
4.1. Mapping Model to code ............................................................................................ 67

Computer science Page vi

 Ibex Primary Hospital Management System 2011
4.2 Source code for major classes packages or interfaces ............................................... 70
4.3 Screen images .......................................................................................................... 87
Chapter Five ........................................................................................................................... 89
CONCLUSION....................................................................................................................... 89
Reference ................................................................................................................................ 94

Computer science Page vii

 Ibex Primary Hospital Management System 2011

LIST OF FIGURE
Figure 1: Use case diagram fir ibex primary hospital system ................................................... 20
Figure 2: Activity diagram for login ........................................................................................ 38
Figure 3: class diagram for the proposed system...................................................................... 49
Figure 4: Sequence diagram for set appointment ..................................................................... 50
Figure 5: Sequence diagram for view lab order ....................................................................... 51
Figure 6: Sequence diagram for search drug ............................................................................ 52
Figure 7: Sequence diagram for send comment ....................................................................... 52
Figure 8: Sequence diagram for login ...................................................................................... 53
Figure 9: Sequence diagram for send lab result ....................................................................... 54
Figure 10: Sequence diagram for generate report.................................................................... 55
Figure 11: Sequence diagram for admit patient. ....................................................................... 55
Figure 12 : Interface of home page .......................................................................................... 56
Figure 13: Interface for doctors’ page...................................................................................... 56
Figure 14: System architecture for proposed system. ............................................................... 59
Figure 15: Component diagram ............................................................................................... 60
Figure 16: Deployment diagram .............................................................................................. 61
Figure 17: Component diagram subsystem service .................................................................. 64
Figure 18: Detailed class diagram ........................................................................................... 65

Computer science Page viii

 Ibex Primary Hospital Management System 2011

LIST OFTABLE
Table 1: Use case description for login .................................................................................... 21
Table 2:Use case description for manage patient account ........................................................ 22
Table 3: Use case description for change password ................................................................. 22
Table 4: Use case description for write feedback ..................................................................... 23
Table 5: Use case description for view feedback ..................................................................... 24
Table 6: Use case description for manage employee's account ................................................. 24
Table 7: Use case description for generate report .................................................................... 25
Table 8: Use case description for search medicine ................................................................... 26
Table 9: Use case description for manage notification ............................................................. 27
Table 10: Use case description for renew account ................................................................... 27
Table 11: Use case description for update patient history ........................................................ 28
Table 12: Use case description for manage bed ....................................................................... 29
Table 13: Use case description for view appointment .............................................................. 29
Table 14: Use case description for accept patient .................................................................... 30
Table 15: Use case description for send result ......................................................................... 31
Table 16: Use case description for approve payment ............................................................... 31
Table 17: Use case description for view own history ............................................................... 32
Table 18: Use case description for send order.......................................................................... 33
Table 19: Use case description for admit patient...................................................................... 33
Table 20: Use case description for assign doctor ..................................................................... 34
Table 21: Use case description for view lab result ................................................................... 34
Table 22: Use case description for update store ....................................................................... 35
Table 23: Use case description for view patient history ........................................................... 35
Table 24: Use case description for view notification................................................................ 36
Table 25: Use case description for request to renew own account ............................................ 36
Table 26: Use case description for view order ......................................................................... 36
Table 27: Use case description for logout ................................................................................ 37

Computer science Page ix

 Ibex Primary Hospital Management System 2011

ACRONYM
CPU: - Central Processing Unit

CSS: - Cascading Style Sheet

IPHMS:- Ibex Primary Hospital Management System

MY_SQL:- Microsoft structural query language.

OPD:-Out Patient Department

PHP: - Hypertext Preprocessor

PID:- patient Instantaneous Description

RAM: - Ranadom Access Memory

UI:- User Interface

UML: - Unified Modeling Language

URL: -Uniform Resource locator

Computer science Page x

 Ibex Primary Hospital Management System 2011

CHAPTER ONE

1.1. Introduction
Hospitals 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 and records of its patients, doctors, nurses, ward boys and other staff personals that
keep the hospital running smoothly and successfully.[15]

The main cause of most of Ethiopia's health problems is the relative isolation of large segments
of the population from the modern sector and majority of the population resides in the rural area
where there is no or limited health services. Additionally, widespread illiteracy prevents the
dissemination of information on modern health practices. A shortage of trained personnel and
insufficient funding also hampers the equitable distribution of health services in the country.

Web Based Hospital Management System for IBEX primary Hospital is a software product
suite designed to improve the quality and management of IBEX hospital in the areas of patient
diagnostic process. This project enables the hospital to improve effectiveness and quality of
work.

This project deals about managing IBEX primary hospital’s system by improving the manual
system in to web based application. The project mainly focuses on registering new patient in to
the system by creating account for them that need user name, password, and e-mail to login to
the system, in order to see their medication procedure and their appointment, to get notification
about the hospital and other health advises form the doctor and the hospital etc….

In addition to this the project works for the hospital to have its own notification board to post
new services, new information about the hospital,and to advertise the hospital.

1.2. Background
Ibex primary hospital is found in the Amhara regional state, Gondar city in Kebele 18. it was
established by 6 stakeholders based on the standard by minister of health within the range of 60
to 70 employees in 2003 E.C. The standard of the hospital at the beginning was as general
hospitalbut after few years the minister of health decided to decrease its status in one level and
declare it to be primary hospital, it was established to provide work space for hefty doctors and
to give qualitative service for users.

Computer science Page 1

 Ibex Primary Hospital Management System 2011
In general at this time the hospital is running with 60 to 70 employees including two doctors,
two health officers, nurses and other part-timer specialists in dental, dermatology, psychology,
and surgical departments. The hospital has total number of 5 OPD and 10 beds to give
satisfaction for the users.

1.3. Statement of the problem

Ibex primary hospital works almost all its activities manually so this system has created many
problems like:

 Manual file handling or data storing ; the hospital is currently using paper to do all of its
work related with patient and Employee.
 It needs high effort and cost to maintain records: it is so hard for the clerks to register
new patients and to assign doctor, it is not easy for the doctor to do all the medication
manually and write prescription.
 Risk on Security and controlling: the patient’s privacy is not secured because the
workers that are working in the hospital can get it easily.
 It consumes a lot of time in file processing and generating reports: it takes a lot of time
to generate report because the manager should see all the patient history to get the
needed information.
 It is very difficult to find particular information from the chart.
 Waste of money : because of the costs that the hospital pay to print prescriptions and
other forms with its logo and by the patients side if the patient forget his chart number he
have to get a new chart so this makes it extravagancy.
 There is loss of patient chart (data) because of two things; the first one is when the
patient is forgetting his/her card number. The second one is that if the clerks misplace
order of chart they cannot search and find the chart store, in both case.

1.4. Objectives
In this section we explain our general and specific objective.

1.4.1. General objective

The general objective of this project is developing online web based system for Ibex primary
hospital.

Computer science Page 2

 Ibex Primary Hospital Management System 2011

1.4.2. Specific objective

In order to achieve the general objective:

 Study the existing system major functionsand problem.

 Find out the functional and non functional requirements.
 Design database based up on analyzed data.
 Design user interface.

1.5. Scope of project

The system boundary including functions like:

 Manage patient’s information.

 To use e-prescription of drug and laboratory.
 Design notification board for the hospital.
 Manage pharmacy store.
 It does not include blind users.

1.6. Limitation of project

It is a disclaiming factor of the project. It is the functionality that is not being covered by the
system due to shortage of manpower, time.

 Do to unreliable internet connection to use the system.

 Our system does not include online payment.

1.7. Significance of project

Beneficiary of this system are employees of the hospital mainly employees that has direct
contact with the customers and the customers them self are the main users and beneficiaries of
this system.

 Patient can also see the results online.

 Eachtaskis performed easily.
 The system gives fast service to the customer.
 The system minimizes employee overload of work.
 The data are secured.
 To write report easily.

Computer science Page 3

 Ibex Primary Hospital Management System 2011
 Results of tests, prescription and investigate on advice will be automatically updated in
the database.
 Enable patients send feedback to the hospital.
 Prevent the data from damage.
 Information accessing will be easy.

1.9.1 Beneficiary of project

When this project is finalized and implemented, the beneficiaries of this system are:

Doctor: doctors in our system they can get the prescriptions easily and use them merrily not
only this the doctors can also contact with their patient using this system.

Nurse: they are the main beneficiaries of the system because it the current system they have
load on ordering which patient should they serve first. The other thing that became easy for
them is the bed management.

Customer: the main purpose of this system is to make the customers happy and make things
easy for them by giving them opportunity to see their history online and to receive
recommendations from their doctor and the pharmacist.

Lab technician: in the existing system it is hard for lab technicians to read the hand writing of
doctors and to send lab result to the doctor but by using our system we solve this two problems

Clerk: clerks the system make the work of clerks by changing the manual based registration
form digital and also the main problem of their work is totally solved because by using this
system they can search the needed charts easily by using patient id or phone number of the
patient.

Pharmacist: like lab technicians it is hard for pharmacists to read the hand writing of doctors so
we provide e prescription to solve this and the other benefit of our system is the pharmacist can
know which medicine is available in the store and also can see their expired date and discard
them from the list.

1.8. System development methodology

Methodology is a guideline for solving problems with specific components such as tasks,
methods, techniques and tools component.

Computer science Page 4

 Ibex Primary Hospital Management System 2011
We used object oriented development methodology to conduct this project.

The model that we will use in our system development life cycle is the Iterative model.
Because of

 Parallel development can be planned.

 Testing during smaller iteration is easy.
 Risk analysis is better
 Better suited for large and mission-critical projects.

1.8.1. Data collection (fact-finding) method

Our team used different methods to gather data about Ibex Hospital. Gathering data is most
important of projects to know the requirement of Organization and to understand how they are
working at this time.

We use the following methods:

 Interview:

Since, interview allows the team to explore about the problem domain in detail; we have chosen
it as our primary data collection methodology.

First group members interviewed the Director of Ibex Primary hospital about all background of
hospitals, how the existing system works, what is the sequence of action to give the required
service to customers and generally about the all functionality of current system.

 Observation:

We observed the work flow of IBEX primary hospital and how they are managing it. We had
followed direct observational technique to understand the problem of the existing system. Even
though interview is very important to gather information, direct observation is simpler.
Appendix [A]

1.9. System development tool

To develop the proposed system, we use different hardware and software tools for different
purpose.

1.9.1. Software tools

E-draw max: used to draw UML-diagrams by the use of object oriented approach.

Computer science Page 5

 Ibex Primary Hospital Management System 2011
Sql: it is used to run or browse at a server side and also it is used for database design.

MS-Word: to write and edit our documentation.

Notepad++: it used to write source code of the proposed system.

HTML: It is used to create interactive forms..

JS: JavaScript is the scripting language of the Web. JavaScript use to define the content of
web pages like, css to specify the layout and JavaScript behavior of web pages.

CSS: Is designed primarily to enable the separation of document content from document
presentation, including elements such as the layout, colors, and fonts.

PHP: Is used to generate dynamic page content.

Any web browser: used to run or browse at a client side.

Photoshop: used for editing images.

1.9.2. Hardware tools

We use the following hardware’s are for this project.

Computer:used to deploy and implement the system.

Mobile Phone:we used mobile phone to record sound when we interview peoples and to use its
camera.

Printer: used to print files

Flash: used for backup

Computer science Page 6

 Ibex Primary Hospital Management System 2011
1.10. Gantt chart

Axis Title

13-Nov 2-Jan 21-Feb 12-Apr 1-Jun

Proposal

Start date
Requirment Analysis
End date
Axis Title

System Designe

Code and Implementation

Testing

Computer science Page 7

 Ibex Primary Hospital Management System 2011

Chapter two

2.1 Introduction
In this chapter we analyzed the current system and identify the problem of the existing
system in order to make out all the functional and non functional requirement of the new
system to be developed and to produce model of the new system using use case model,
activity diagram, state diagram, class, and sequence diagram.

2.2 Current system

In this section we briefly reviewed the current manual system used by IBEX primary
hospital.

2.2.1 Major function of existing system description

Currently the Organization is doing every task manually. The organization use paper to
register patient’s information, the laboratory results of patients, given medication to
patients. This type of data handling causes loss of data and the current system requires
numerous paper forms and the current system does not handle all the information as
single database because the system is not integrated. The main problem of the
organization is to give a service to a patient the chart of patient is send from one OPD to
another by nurse. This type of task is time consuming and it causes twisted order of charts
because of this the patient may not get the medication on time. There is no a modern
system that searches file or patient information, the patients does not communicate easily
with doctor and does not get advice from doctor without coming to hospital and the
patient may forget the appointment date.

2.2.2 Problem of current system

Since it is manual based the existing system and customers have faced many problems.
Among those problems the problem of data management is the core one because data is
not easily accessible, not well organized, not secured from damage and it is stored
redundantly in the form of multiple copies of files. Since it is manual based the system is
not efficient, do not give better quality service to the customers so the customer is not
satisfied with the service.

There is loss of patient chart (data) because of two things; the first one is when the
patients are forgetting their card number. The second one is that if the clerks misplace

Computer science Page 8

 Ibex Primary Hospital Management System 2011
order of chart in store they cannot search and find the chart so the patients loss their
medical information and should get new chart and this is extravagancy.

In general:-

 Security and Controls: it is difficult to control and secure these manual records,
since it does not have any authentication and authorization system.
 Searching/ accessing: The registrar wants to search a specifying document or file
he/she must retrace a lot of documents file that set in the registrar office this take a
lot of time. In the current system there is no easy way to get a customer file so to
access or to search the customer information is very difficult.
 Updating:since in the current system the registrar use manual to record the
customer information. If the registrar makes a mistake he /she need to remove the
written information or need to change the file. So to update or to delete the record
information is difficult to workers.
 Economic:In the existing system of ibex primary hospital many operation are
done on the paper and use a lot of man power. This cause high consumption of
resources like papers, man power, time, pen etc. Therefore the existing system
cost is in terms of the above factors very high.
 Data storage problem: it is hard to access the needed data easily even if we
access it is difficult to change edit.

2.3 Requirement Gathering

This section describes the methods that we used to gather data and what data we gather by
using the methodologies.

2.3.1. Observation:
We observed how the existing system is working and we saw forms that the current
system is using to register patients, to give appointment for patient, to write laboratory
and pharmacy prescription, and form that is used to generate report. Appendix A

2.3.2.Interview:
First group members interviewed the Director of Ibex Primary hospital about all
background of hospitals, how the existing system is working, what is the sequence of
action to give the required service to customers and generally about the all functionality
of current system, and about the History of the hospital.

Computer science Page 9

 Ibex Primary Hospital Management System 2011
2.3.3. Results found
Team members have seen the existing system. We used two requirement gathering
models to identify the problems of existing system which are interview, observation
finally Team member discussion with them.

We give conclusion about: -

 How the existing system is performing tasks?

 Background information about the hospital work performance.
 Drawback of the existing system.
.

Assuming what user needs and expects and we try to implement as the stallholders' need
and expectation.

2.4 Business rule

Business rule are principles, requirements and polices that must be fulfilled and obligated
in order the system to function properly and effectively. IBEX has its own businesses rule
to inform the residents how it facilitates the service and the type of services which are
functional used by whom.

The existing system has many business rules or principles some of them are:

BR1:The users have to pay money again if his chart gives service above 15 days.

BR2: Users can access their own history.

BR3: new patients must be registered by clerk.

BR4. Patents PID must be unique.

BR5: The clerk should have to secure the patient personal file.

2.5. Proposed system

The new system deals with automating the system that IBEX hospital is using. It is
efficient in facilitating different tasks in the hospital, like register patient and give unique
card number, registering new employees in the system and giving them authority as they
deserve, to delete and update patient and employees account, handling all document, to

Computer science Page 10

 Ibex Primary Hospital Management System 2011
automate the user, secure patients secret and his account and to minimize work load on
allocating bed.

As a whole the system

 Gives accelerated service for all users.

 Can search required information.
 Control data of customer as needed
 Can save time for the users.
 Hold data base in organized manner.
 Is easy to search, retrieve and update.
 Has security, because the user can only enter into the system by login.

In addition, the system uses session control method for more secured working
environment. That means, any person who knows the URL (uniform resource locator) of
a specific form cannot get it directly without login. The system identifies the unauthorized
user by the incorrect entered user name and password. Any unauthorized person can't
enter in to the system. Admin system can manage all data base of the hospital. System
identifies registered person and unregistered person.

2.6. Requirement analysis of the new system

2.6.1. Functional requirements

Functional requirements define the functions that are provided by the system[1]. The
system that the team develops has different functions or features which are actions of the
system to satisfy the system needed and be acceptable by the user. The functional
requirements that will provided by the new system include:

For admin:

 Managing Employee Accounts: The system allows the administrator to manage

employees account in case of updating, deleting, and creating new account.
 Generate Report: The system allows administrator to view patient history and
generate report from it.
 View feedback: The administrator can view feedback of users about the services
the hospital is giving.
 Manage own account: in order to update and view own account.

Computer science Page 11

 Ibex Primary Hospital Management System 2011
 Manage Department: a division of a large organization, dealing with a specific
area of activity.

Clerk:

 Manage patients account: Clerk can create patients account and update patient’s
profile.
 Assign doctor: Assigning a doctor or specialist to the patient.
 View appointment.
 Renew users account.
 Manage own account

For customer:

 View notification: View new information about healthy life style tips and
information about IBEX hospital.
 Request to renew own account: after 15 days the PID will be deactivated so the
patient have pay again in order to get the hospitals service..
 Give Comment: - The system shall allow users to send feedback to the hospital.
 Manage own account.
 View appointment.
 View own history

Doctor:

 Accept patient: Accept newly recorded patient.

 Update patient history.
 Upload the medication of patient online.
 Send order: To write e-prescription for pharmacists and laboratories.
 To write recommendation for the patient.
 Make appointment: To make appointment with his patient.
 Admit patient.
 Manage own account.
 Search medicine

Computer science Page 12

 Ibex Primary Hospital Management System 2011
Lab technician:

 View approved order: This system benefits to lab technician to view orders.
 Send lab result: to upload lab results to the doctor.
 Manage own account.

Pharmacist:

 View approved order: To view order from the doctor.

 Manage drug.
 Write notes: Write notes for patients.
 Manage own account.

Casher:

 View order: See the orders from the doctor.

 Approve payment: make sure the patients pay before getting the service.
 Manage own account.

Nurse:

 Manage bed: view and update bed status and save it.
 Update patient history.
 Manage own account.

2.6.2. Non functional requirements

Non functional requirement is essentially specifies how the system should behave and
that is the constraint upon the system[2]. These are

Availability: - data must be available at anytime from anywhere where there is an

internet connection.

Accuracy: - there must be error handling. Operation can be done correctly and it ensures
that the information is coming from the database is accurate.

Reliability: - system to be developed should perform consistently specific operations

without failure.

Computer science Page 13

 Ibex Primary Hospital Management System 2011
Usability: - user is able to learn, operate, feed inputs and interpret output through the
interaction with the system.

Security: - allow login to only authorized users. For security issue, only authenticated
user can visit the system. Any unauthorized user cannot access the data.

Confidentiality: - system protects sensitive information.

Efficiency: - system developed handles capacity, throughput, and response time

Error handling: - handles an error done by any user of the system and display error
message.

User friendly Interface: Users can easily input and retrieve their profile.

2.6.2.1. User interface and human factors

The knowledge required from the user to access the system is: - computer usage and
website interface access. The interface of the proposed system is very easy for users.

2.6.2.2. Documentation
This proposed system contains the written document that describes the project and the
detailfunction of the proposed system and the existing system. Proposal, analysis and
design of theproject, sample code of the implementation include the document of the
project.

2.6.2.3. Hardware requirements

The hospital should have desk top computers having typical storage capacity and
processing speed.

2.6.2.4. Security issue

Each hospital workers have their own privilege to access the data. Only the authorized
usercan insert, update and delete data of the customer and also any necessarily activity
done by authorized user, that means to do the above activity the system require a
username and password to login. Generally the new system in terms of security has
highsecurity so the hacker cannot get information easily.

Computer science Page 14

 Ibex Primary Hospital Management System 2011
2.6.2.5. Performance characteristics
The system is accessible by specified actors in the hospital. It should be given more
emphasis for the speed to access it. The proposed system support a number of user at a
time and to access any information or any data does not need much time the user can get a
response with a short of time.

So the performance of the organization became more efficient and effective in terms of
time, cost and quality.

 Efficiency: - The proposed system can give response for micro even Pico second,
so this has fast response time.
 Effectiveness: - Compared to the existing or manual system the proposed system
is effective to perform tasks.
 Time consuming: - The proposed system uses less time to perform over all tasks
as compared to the manual system.
 Resource consuming: - The proposed system performs tasks within a minimum
resource. Like it reduces paper consumption, reduce man power by reducing
labor work.

2.6.2.6. Error handling

The proposed system handles some errors easily and effectively and solves those errors
by giving information or by helping.

 User error: -User may not insert may insert string but the intended is number and
vice versa, string and inserting duplicate items. The system displays message in
order to solve the problem and also give information about how to use the system.
 Logging error: -The proposed system can handle errors that come at the time of
login. the user wants to login the system by incorrect user name or password the
system can identify weather the user is authorizing or not by the input password
and user name and if the input is incorrect the system handle the error and display
message to user.

2.6.2.7. Quality issue

Information in database should be accurate and updated. Since the data store in the
computerized way any information does no became fade and loss at any time and store
for a long time. The system to be developed is web based and used different latest

Computer science Page 15

 Ibex Primary Hospital Management System 2011
software when it will develop; the system gives fast and efficient service to all users. Use
suitable software and hardware to develop system will able to achieve adaptability,
availability, flexibility, and reliability of the system.

2.6.2.8. The system modifications

The system should be easily modifiable. If there is change on the process of hospital
information management system and wants to add new feature with new technology on
the proposed system any trained person can be modified based on change criteria and can
use new technology.

2.6.2.9. Resource issues

Server:

The minimum hardware requirement for MySQL is-

 CPU: 32 bit or 64 bit

 Cores: AMD Dual-core processor C70
 RAM: 2GB (or higher is recommended)

Client:

 Web browser
 Graphics and interface tools to load display
 Internet connection

2.7. System model

2.7.1.Scenario
Doctor log in

Doctor enters username and password. The system checks weather the entered username
and Password is valid. If it’s valid doctor logs in to the system. The system displays all
available doctor operations that the doctor can perform.

Patient log in

Patient enters username and password. The system checks weather the entered username
and Password is valid. If it’s valid Patient logs in to the system. The system displays all
available Patient operations that the Patient can perform.

Computer science Page 16

 Ibex Primary Hospital Management System 2011
Lab Technician log in

Lab Technician enters username and password. The system checks weather the entered
username and Password is valid. If it’s valid Lab Technician logs in to the system. The
system displays all available Lab Technician Operations that the Lab Technician can
perform.

Nurse log in

Nurse enters username and password. The system checks weather the entered username
and Password is valid. If it’s valid nurse logs in to the system. The system displays all
available nurse Operations that the nurse can perform.

Casher

Casher enters username and password. The system checks weather the entered username
and Password is valid. If it’s valid casher logs in to the system. The system displays all
available casher Operations that the casher can perform.

Clerk

Clerk enters username and password. The system checks weather the entered username
and Password is valid. If it’s valid clerk logs in to the system. The system displays all
available clerk Operations that the clerk can perform.

Pharmacist log-in

Pharmacist enters username and password. The system checks weather the entered
username and Password is valid. If it’s valid Pharmacist logs in to the system. The system
displays all available Pharmacist operations that the Pharmacist can perform.

Generate report

Admin log in to the system with username and password and select main generate report.
System display generate report menu. Admin select view report. The system displays
report.

Accept patient

Doctor log in to the system with username and password and select accept patient menu.

Computer science Page 17

 Ibex Primary Hospital Management System 2011
View appointment

Patient log in to the system with username and password and select view appointment
menu. The system displays to use view appointment form. Patient fill the required
information and if patient appointment fill the system displays the message set
appointment is valid else invalid.

View lab result

Doctor log in to the system with username and password and select view lab result menu.
System display list of patient lab result.

View approved lab Order

Lab technician log in to the system with username and password and select view
approved lab order menu. System display list of approved lab order.

Manage drug

Pharmacist log in to the system with username and password. System display Pharmacist
home page. Pharmacist select the manage drug menu and search or view by drug id. If
drug is present system display drug information.

Manage bed

Doctor log in to the system with username and password and select bed men. System
display list of type of bed.

View feed back

Admin log in to the system with username and password and select view feedback menu.
System display feedback of the system.

Assign doctor

Clerk log in to the system with username and password and select view assign menu.
System display list of the list and assigned doctor.

Choice doctor

Computer science Page 18

 Ibex Primary Hospital Management System 2011
Patient log in to the system with username and password and select the choice menu.
System display list of doctor and their information.

View notification

Patient log in to the system with username and password and select the view notification
menu. System displays the notification information of patient.

Send lab order

Lab Technician enters username and password. The system checks weather the entered
username and Password is valid. If it’s valid Lab Technician logs in to the system. The
system displays all available send lab order that the Lab Technician send by appropriate
order can perform.

View recommendation

Patient enters username and password. The system checks weather the entered username
and Password is valid. If it’s valid logs in to the system. The system displays all available
recommendation Operations that the patient can perform.

Approve payment

Casher enters username and password. The system checks weather the entered username
and Password is valid. If it’s valid casher logs in to the system. The system displays all
the approve payment available casher Operations that the casher can perform.

2.7.2 Use case model

A use case is a description of how users perform tasks on the system[6,7,10]. A use case
includes two main parts:

 the steps a user will take to accomplish a particular task on your system
 the system should respond to a user's actions

A use case begins with a user's goal and ends when that goal is fulfilled. The use case
diagram below shows the user’s tasks perform on the IBEX primary hospital.

Computer science Page 19

 Ibex Primary Hospital Management System 2011

Figure 1: Use case diagram fir ibex

bex primary hospital system

Computer science Page 20

 Ibex Primary Hospital Management System 2011
2.7.2.1. Use case description
Table 1: Use case description for login

Use case name Login

Actors Admin, Patient, Nurse, Doctor, lab technician, pharmacist, Clerk, Casher

Description How actors uses this form to log into the system.

Pre-condition The actors should be registered first or need to have an account with valid
username and password to login.

Basic flow of User action System response

event
1. Open login page. 2. Display the login page with
login form.
3. Enter the authorized username
and password in the login form. 5. Check the authorized username
and password.
4. Click on login button
6. If the username and password
7. End use case. is correct login in the system.

Alternate A1 If the entered user name and password is not valid

course of action
1.1 it displays “please enter valid user name and password” go to basic flow

1.2 The system informs the user to re-enter username and password up to 3
trials.

B2 If the user forgot the user name and password display reset user name
and password page.

Post condition The users logged in to the main page.

Computer science Page 21

 Ibex Primary Hospital Management System 2011

Table 2:Use case description for manage patient account

Use case name Manage patient’s account

Actor Clerk

Description How to create users account and update user’s profile.

pre-condition The Clerk must login to the home page of the system.

Basic course of action User action System response

1. Open the create 2.Display the available
account page or the page or form.
update profile page.
5. Check the filled
3. Fill the appropriate information on the form.
information in the
form. 6. If the filled information
is correct the system saves
4. Click on create or it on the system database.
update button.
7. Display the
8. End use case. acknowledgement
message.
Alternative courses of action A1. Invalid information entry

1.1. If the clerk enter incorrect name and other

information error message displays

1.2. Go to step 3 and fill again

post condition Create account successfully or update profile

successfully.

Table 3: Use case description for change password

Use case name Change password

Computer science Page 22

 Ibex Primary Hospital Management System 2011
Actor Patient

Description Changing existing password.

Precondition Actor must have existing password and user name.

Basic course of action User action System action

1. Actor clicks on “change 2. System will display

password” button. create account form.
3. System displays a form
4. The actor fills the form
to be file.
and click done button.
5. The System checks if it
7.end of use case.
is valid or not.
6.system display
Successful message when
it is valid.
Alternative course of action A1: system displays an error message when information
is not correct.

1.1: system will give a chance to re-enter the incorrect

part at step 4.

Post condition The actor gets the new password and can login by new
password.

Table 4: Use case description for write feedback

Use case name write feedback

Actors Patient

Description: To enable the patient to comment the hospital.

Precondition: The customer must be having a suggestion about the system.

Basic courses of action User action System response

1. Open the comment page. 2. Display Comment page.

3. Enter name and email 6. Display the acknowledgement

address. message.

Computer science Page 23

 Ibex Primary Hospital Management System 2011

4. Enter comment. 7. If the name, email address and

comment correctly filled the system
5. Click on send button. send the comment to the officer.

9. End use case.

Post condition Suggestion will be commented.

Table 5: Use case description for view feedback

Use case name View comment

Actor Admin

Description This use case allows Admin to view comments.

Pre-condition Admin must login into home page.

Basic course of action User action System response

1. Login in the 3. Display the
system. comments page.

2. Open comments
page.

4. End use case.

Post-condition View comment successfully.

Table 6: Use case description for manage employee's account

Use case name Manage employee’s account

Actor Admin

Description How to create users account and update user’s profile.

pre-condition The Admin must login to the home page of the system.

Basic course of action User action System response

Computer science Page 24

 Ibex Primary Hospital Management System 2011
1. select the needed 2.Display the available
page weather create, page or form.
update, or delete page.
5. Check the filled
3. Fill the appropriate information on the form.
information in the
form. 6. If the filled information
is correct the system saves
4. Click on done it on the system database.
button.
7. Display the
8 acknowledgement
.. End use case. message.
Alternative courses of action A1. Invalid information entry

1.1. If the admin enter incorrect name and other

information error message displays

1.2. Go to step 3 and fill again

post condition Create account successfully or update profile

successfully.

Table 7: Use case description for generate report

Use case Name: Generate report

Actor: Admin

Description: Admin prepare a report about the overall work of the hospital

Precondition: Admin must be log in to the system

Main course of action: System action User action

1) System display menu 2)Admin clicks on Generate report

3) System displays interface for 4)Admin fill report

generate report.
5) Admin clicks on save button.
6) Systems validate the user input

Computer science Page 25

 Ibex Primary Hospital Management System 2011
and unfilled input.

7) Use case Exit.

Post condition Generate report successfully

Alternative flow of A4.If the fill form is invalid system display the form again
event

Table 8: Use case description for search medicine

Use case name Search medicine

Actor Pharmacist

Description: The Pharmacist searches the drug in store.

Precondition The Pharmacist must login in the system.

Basic course of action User action System response

1. Login in the system. 3. Display the search

medicine with the
2. Open search page. search form.

4. Enter the name of medicineon 6. The system searches

the search form. the drug from store
table on the database.
5. Click on search button
7the system will show
8. End use case. the pharmacist if the
medicine is available
or not.
Alternative course of action A1. If the medicine is not available it will recommend the
pharmacist to get one.

Computer science Page 26

 Ibex Primary Hospital Management System 2011
Table 9: Use case description for manage notification

Use case name Manage notification

Actor Admin

Description Administrator can post, update, and delete information in the home
page.

Pre-condition The system admin must login the home page of the
Administrator

Basic course of action User action System action

1.Admin opens administrator page. 4. The system

displays the page
2. The admin select manage notification
that contains the
button.
needed form.
3. The system admin can select create,
delete, or update button. 6. the system
5. Admin selects the file to be uploaded or verifies its validity.
can write a post by himself, select the
7. System display
notification that he want to delete, select the
successful message
notification to update and then click the
if it is valid.
button done.

8. Use case ends.

Alternative course of action A5. If the filled form is not valid.

5.1System display error message.

5.2. Go step 5 and do it again.

Post condition The notification is managed successfully.

Table 10: Use case description for renew account

Use case name Renew account

Actor Clerk

Description This use case allows the clerk to renew patients

account if it is deactivated.

Pre-condition Clerk should login to the system.

Computer science Page 27

 Ibex Primary Hospital Management System 2011
Basic course of action User action System action

1. Clerk login to the 3. System display

system. renew account page

2. Clerk clicks on 5. System displays

renew patient account information of patient.
button.
7. System displays
4. Clerk insert card acknowledgment
no of user. message.

6. Clerk renew patient

account.

8. Use case ends.

Alternative course of action A1.if card number inserted is not found, system
displays error message and back to the flow step
4.

Post condition Renew patient account.

Table 11: Use case description for update patient history

Use case name Update patient history

Actor Doctor, Nurse

Description To update stored patient history.

Pre-condition The actor should login to the system.

Basic course of action User action System action

1. Actor login to the system. 2. The System display the

3. the Doctor selects update available page

link 4. The System displays the

5.The Doctor update the available page.

information’s 7. The system updates the patient

6.The Doctor select submit history.

button

Computer science Page 28

 Ibex Primary Hospital Management System 2011
8. Use case ends.

Alternative course of action A. If the system verifies unauthorized entry.

A1. The system display Error message to notify unauthorized
entry.

Table 12: Use case description for manage bed

Use case name Manage bed

Actor Nurse

Description Nurse manage the bed on different condition.

Pre-condition The Nurse must login to the system.

Basic Course of Action User action System action

1. The Nurse has to 2. The System display the

login to the system. available page.
3 the Nurse selects 4. The System display bed
manage bed link. status.
5. nurse add 6. system show successful
changes and save message
7. Use case ends.

Alternative course of action A. If the system verifies unauthorized entry.

A1. The system display Error message to notify
unauthorized entry.

Post condition Be is managed successfully.

Table 13: Use case description for view appointment

Use case name: View appointment

Actor Clerk, Patient
Description The actors view the appointment that is created by
from the Doctor.
Pre-condition The Doctor set the appointment
Basic Course of Action User action System action

Computer science Page 29

 Ibex Primary Hospital Management System 2011
1. The Actors has to 2. The System display the
login to the system. available page
3. the Actors selects 4. The System asks patients
view appointment card number
5. actor intercard 6. system display
number appointment
7. end of use case
Alternate Course of Action A. If the system verifies unauthorized entry.
A1. The system display Error message to notify
unauthorized entry.
A2. The use case resumes from step 5 of basic
course of action.

Post condition The actors view the appointment.

Table 14: Use case description for accept patient

Use case name: Accept patient

Actors Doctor
Description To Accept new patient for treatment
Pre-condition Patient must admitted to doctor
Basic Course of Action User action System action

1. Doctor has to login to the 2.The System

system. display the
3. Doctor click accept available page
patient link 4. system display
5. doctor select patient and patients waiting
view symptoms list
7. doctor chose accept or 6. system give
decline button choice for doctor
8. use case end.
Alternate Course of Action A. If the system verifies unauthorized entry.
A1. The system display Error message to notify
unauthorized entry.
Post condition Patient treated by doctor.

Computer science Page 30

 Ibex Primary Hospital Management System 2011

Table 15: Use case description for send result

Use case name: send result

Actors Laboratory technician
Description The Lab technician Send laboratory result
investigation
Pre-condition The doctor sends order to the Lab technician.
Basic Course of Action User action System action

1.Lab.tecnician 3. The system display

login to the system result entry form
2. Lab technician
open laboratory
result page.
4. Lab technician
fill form and submit
5. end of use case
Alternate Course of Action A. If the system verifies unauthorized entry.
A1. The system display Error message to
notify unauthorized entry.
A2. The use case resumes from step 4 of
basic course of action.
Post condition The Lab. technician sends laboratory result

Table 16: Use case description for approve payment

Use case name: Approve payment

Actor Casher
Description Casher to approve the customer pay
Pre-condition Patient have to be registered first
Basic Course of Action User action System action

1: the Casher has to 3: system ask patient

login to the system. card number
2: casher select 5: system display
approve form

Computer science Page 31

 Ibex Primary Hospital Management System 2011
paymentlink 7: system send the
4: casher submit doctors order to the
card number pharmacist or
6: casher make the allocate doctor to the
customer pay and patient.
submit 8: system display
9. use case end successful message
Alternate Course of Action A. If the system verifies unauthorized entry.
A1. The system display Error message to
notify unauthorized entry.
A2. The use case resumes from step 5 of
basic course of action.
B1. If the patient does not pay the system
will reject him so that he cannot get the
service
Post condition Approving payment

Table 17: Use case description for view own history

Use case name: View own history

Actor Patient
Description To view patient medical history
Pre-condition The Patient must login to the system
Basic Course of Action System action User action

1: Patient has to 2: The System display

enter the system by the available page
using name and 4: The System
password. displays history
3: The Patient
selects view history
5: Use case ends
Alternate Course of Action A. If the system verifies unauthorized
A1. The system display Error message to
notify unauthorized entry.

Computer science Page 32

 Ibex Primary Hospital Management System 2011

Post condition The Patient view their patient history

Table 18: Use case description for send order

Use case name: Send order

Actor Doctor
Description In order to send order for pharmacist, and
clerk
Pre-condition The Doctor must login to the system
Basic Course of Action System action User action

1: the doctor must log in 2: The System

1. Doctor log in to the system with user name to the system display the
and password and select order lab link. 3: the doctor should select available page
2. System display order lab page. the needed prescription
3. Doctor fill all required filed and click send 4: select medicine or
button. laboratory examination
4. If valid all required filed, system display the 5: select whom to send
message “order lab is successfully to send lab and send
technician”. 6: Use case ends

Alternate Course of Action A. If valid all required field the system to

display error message and go back to step 3.
Post condition doctor has successfully to order lab

Table 19: Use case description for admit patient

Use case name Admit patient

Description The Nurse assigns bed to patient.
Actor Nurse
Pre-condition The patients disease is hard must take a bed.
Basic cores of action: User action System response
1. The Clerk and 2. The system will
open the admit display the available
patient page. beds.

Computer science Page 33

 Ibex Primary Hospital Management System 2011
3. Clerk selects and 4. the system update
assigns the bed to the number of bed. .
the patient.
5. use case end
Alternative course of action A. If the bed is not available the system
displays “ there is no fee bed”.
Post condition The nurse assign the bed to the patient
successfully.

Table 20: Use case description for assign doctor

Use case name Assign Doctor

Actor Clerk
Description Clerk assign doctor to the patient .
Pre-condition Client registers to the system.
Basic course of action User action System response
1Clerk open register 4. The system confirms for
page . the selection.
2. Clerk observes to the
available doctors and
their specializations
3. Clerk selects the
doctor.
5.end use case
Post condition Clerk selects or chooses the doctors and assign to client.

Table 21: Use case description for view lab result

Use case name View Lab Result

Actor Doctor
Description The doctor views the client’s status or result of
client that added from the lab. Technician
ordered from the doctor.
Pre-condition The lab. Technician sends result to the doctor
Basic course of action User action System response

Computer science Page 34

 Ibex Primary Hospital Management System 2011
1.doctor open view 4. The system
result page. receives clients ID
2. doctor enter clients and name.
registration number. 5. system display
3. doctor view the disease type or
added result investigated test
6. end use case
Post condition The doctor views the investigated result.

Table 22: Use case description for update store

Use case name Update store

Description Pharmacist can add and subtract number of drug in store.
Actor pharmacist
Pre-condition The drug list must store in the database
Basic Course of Action User action System action

1. Pharmacist clicks the link 2. The system will display the

update store. available drug list.
3. Pharmacist updates list and 5. The system saves the update.
amount of drug in store. 6. Show successful message.
4. Click the button save.
7. End use case.
Post condition Pharmacist updates the status of pharmacy.

Table 23: Use case description for view patient history

Use case name View patient history

Description In order to generate report the admin views patient history.
Actor Admin
Pre-condition The actor should login to the system.
Basic Course of Action User action System action

1. Patient clicks the link view. 2. The system will display the
3. End use case. available patient history list.

Post condition Admin views patient history

Computer science Page 35

 Ibex Primary Hospital Management System 2011
Table 24: Use case description for view notification

Use case name View notification

Description Patients view notifications that are posted on the notification
board.
Actor Patient
Pre-condition The patient must login to the system
Basic Course of Action User action System action

1. Patient clicks the link view 2. The system will display the
notification. available notification.
7. End use case.
Post condition Patient knows the status of the hospital and get healthy life style
tips from the hospital.

Table 25: Use case description for request to renew own account

Use case name Request to renew own account

Description When patients account is deactivated and if he want to get a
service his account must be activated.
Actor Patient
Pre-condition The patient should login to the system
Basic Course of Action User action System action

1.Patient clicks the link 2. The system will display the

request to renew. available form.
3. Patient fills the form and 4. The system checks the
then Patient clicks done validity of the form.
button. 5. The system sends the request
7. End use case. to the clerk.
6. Show successful message.
Alternative course of action A1. If the form is not valid
1.1 the system leads the user to step 3
Post condition The system show successful message.

Table 26: Use case description for view order

Use case name View order

Computer science Page 36

 Ibex Primary Hospital Management System 2011
Description The actors view the order of the doctor.
Actor Casher, Pharmacist, Lab technician
Pre-condition The actors should login to the system
Basic Course of Action User action System action

1. actor clicks the link view 2. The system will display the
order. available order.
3. End use case.
Post condition The system show successful message.

Table 27: Use case description for logout

Use case name Logout

Participating actors:

Pre- Condition: Actors should be logged in.

Description To Exit from services.

Flow of action Admin, Doctor, Nurse, Clerk, Casher, Lab

technician, Pharmacist clicks on logout button.

2.7.2 Activity activity diagram

An activity diagram describes the flow of control in a system. So it consists of activities
and links. The flow can be sequential, concurrent or branched. Activity diagrams are used
to visualize the flow of controls in a system[3,4,5]. This is prepared to have an idea of
how the system will work when executed. Activity diagram is basically a flow chart to
represent the flow form one activity to another activity. The activity can be described as
an operation of the system. So the purposes can be described as.

 Draw the activity flow of a system.

 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.

Computer science Page 37

 Ibex Primary Hospital Management System 2011

Figure 2: Activity diagram for login

Figure 3: Activity diagram for change password

Computer science Page 38

 Ibex Primary Hospital Management System 2011

Figure 4:ctivity diagram for write feedback

Figure6: Activity diagram for manage bed

Computer science Page 39

 Ibex Primary Hospital Management System 2011

Computer science Page 40

 Ibex Primary Hospital Management System 2011

Figure 7: Activity diagram for generate report

Computer science Page 41

 Ibex Primary Hospital Management System 2011

Figure8: Activity diagram for search for medicine

Computer science Page 42

 Ibex Primary Hospital Management System 2011

Figure9: Activity diagram for manage notification

Figure10: Activity diagram for renew account

Computer science Page 43

 Ibex Primary Hospital Management System 2011

Figure11: Activity diagram for approve payment

2.7.3. Object model

2.7.3.1 Data dictionary

Class Attribute Data type Description
Patient F-name String Patients are the customers of
M-name String the system and all the other
L-name String entities of the system are
Sex Char directly or indirectly give
Age Integer service for them.
Phone-No Varchar
PID Varchar
Region String
Town String
Kebele Varchar
H. No Varchar
Date Date

Computer science Page 44

 Ibex Primary Hospital Management System 2011
Password Varchar
Doctor F-name String Doctors are the one that give
M-name String the medication for the
L-name String patients and this doctors can
Sex Char be part-timer specialists or
Age Integer general doctors.
Email Varchar
SSN Varchar
Department String
Level String
Role String
Password Varchar
Clerk F-name String Clerks era the one that have
M-name String the authority to register new
L-name String patients.
Sex Char
Age Integer
Email Varchar
SSN Varchar
Role String
Password Varchar
Admin F-name String Admin is the person that
M-name String manages the hole system.
L-name String
Sex Char
Age Integer
Email Varchar
SSN Varchar
Role String
Casher F-name String In this system cashers
M-name String approve weather the
L-name String customer pays money or not.
Sex Char
Age Integer
Email Varchar

Computer science Page 45

 Ibex Primary Hospital Management System 2011
SSN Varchar
Role String
Nurse M-name String Nurses are the one that
L-name String assists the doctor.
Sex Char
Age Int
Email Varchar
SSN Varchar
Role String
Pharmacist F-name String Pharmacists are the one that
M-name String give medicine for the patient
L-name String based on the prescription that
Sex Char the doctor writes.
Age Integer
Email Varchar
SSN Varchar
Role String
Lab technician F-name String Lab technician is the one that
M-name String works all the lab examination
L-name String ordered by the doctor.
Sex Char
Age Integer
Email Varchar
SSN Varchar
Password Varchar
Bed Bed no Integer Id of bed.
Room no Integer Id of the Room
Room Type Varchar General or Private Room
Bed status String Give information weather it
is free or not
Patient history Patient id Varchar This information includes the
Date Date history of patient along with
Symptom Varchar the patient id, name and also
Patient name String symptom.
History number Integer

Computer science Page 46

 Ibex Primary Hospital Management System 2011
Disease name Varchar
Medication Varchar
Doctors name String

Account Acc-type Varchar Used to assign any account

Username String type
Password Varchar
Email Varchar
Department De_name Varchar This use to managed the
DID Varchar department of hospital.
Spac_name String
EID Varchar
PID Varchar
Appointment app_no Int
app_reason String This information used to
PID Varchar give and view appointment
app_time Time to patient
Date Date
Doc_name String
Lab result PID Varchar This information used to
P_name String display lab result of patient
Lab_result Varchar
technicianName String
LID Varchar
Drug Drug_id Varchar This information used to
D_name String update ,view the drug.
Registerd-Date Date
Expired-Date Date
Availability String
Lab order PID Varchar This used to arrange the lab
P_name String order.
Prescription Varchar
Date Date
Doc_name String
LID Varchar

Computer science Page 47

 Ibex Primary Hospital Management System 2011
Medicine order PID Varchar This used to write and view
p-name String the medicine order.
Prescription Varchar
Date Date
doc_name String
Feedback Name String This information used to
Email Varchar display the feedback of
hospital system.

2.7.3 Class diagram

UML class diagrams show the classes of the system, their inter-relationships, and the
operations and attributes of the classes.

Computer science Page 48

 Ibex Primary Hospital Management System 2011

Figure 3:: class diagram for the proposed system

Computer science Page 49

 Ibex Primary Hospital Management System 2011
2.7.4 Dynamic modelling
We have identified a number of entity, boundary and control objects, along the way we
have also identified some of their attributes and associations, we represent this objects in
a sequence diagrams, depicting the interaction that occur during the use case to identify
additional associations and attributes.

2.7.4.1 Sequence diagram

Sequence diagrams describe interactions among classes in terms of an exchange of
messages over time. They're also called event diagrams. A sequence diagram is a good
way to visualize and validate various runtime scenarios.[8] These can help to predict how
a system will behave and to discover responsibilities a class may need to have in the
process of modeling a new system.

UML sequence diagrams model the flow of logic within our system in a visual manner,
enabling us both to document and validate our logic and are commonly used for both
analysis and design purposes.

Figure 4: Sequence diagram for set appointment

Computer science Page 50

 Ibex Primary Hospital Management System 2011

Figure 5: Sequence diagram for view lab order

Computer science Page 51

 Ibex Primary Hospital Management System 2011

Figure 6: Sequence diagram for search drug

Figure 7: Sequence diagram for send comment

Computer science Page 52

 Ibex Primary Hospital Management System 2011

Figure 8: Sequence diagram for login

Computer science Page 53

 Ibex Primary Hospital Management System 2011

Figure 9: Sequence diagram for send lab result

Computer science Page 54

 Ibex Primary Hospital Management System 2011

Figure 10: Sequence diagram for generate report

Figure 11: Sequence diagram for admit patient.

Computer science Page 55

 Ibex Primary Hospital Management System 2011
2.7.5 User interface
The user interface, in the industrial design field of human–machine interaction, is the
space where interactions between humans and machines occur[9].

Figure 12 : Interface of home page

Figure 13: Interface for doctors’ page

Computer science Page 56

 Ibex Primary Hospital Management System 2011

CHAPTER THREE

3.1 INTRODUCTION
System design is the transformation of the analysis model into a system design model. Up
to now team member were in the problem domain. System design is the first part to get
into the solution domain in a software development. This chapter contains the description
and design diagram of proposed software architecture, overview of the design system,
decomposition of subsystem, diagram of component, deployment diagram, persistent data
management such as database design, access control and security and the detail of class
diagram.

3.2 Design goals and objectives

The objectives of design are to model the system with high quality. The design goals are
derived from non-functional requirements that means non-functional requirement is the
description of the feature characteristics and attribute of the system as well as any
constraints that may limit the boundary of the proposed solution. Design goals describe
the qualities of the system that the developers should consider.

 Easy to implement:The design of the system is easy to change it in to

implementation or code for the project group. It is also easy to design and
implement the database of the system.
 Flexibility: The team may have to change the way in which certain things work.
The design accommodates these changes with minimum effort.
 Extensibility: The system design is be able to accommodate new functionality
easily when it is needed. Ideally when the institutional operations become
enhanced, the team must be able to add new stuff by adding code and not by
modifying existing code, because modifying existing code may break stuff that
was already working.
 Reliability: The system consists of all the major functionalities.
 Fault Tolerance: The system is fault tolerant to loss of connectivity with the
routing service or other faults.
 Usability: The system is easy and user friendly. It doesn`t require a high level of
expertise in computers. Any user can access it simply using user guide

Computer science Page 57

 Ibex Primary Hospital Management System 2011
 Response time: The system responds as quickly as possible for authorized or
unauthorized access requests.
 Memory space: The system considers the memory space in which run.
 Security: The system security is taken in to consideration to make institutional
information and financial cases secure and confidential.
 End User Criteria: - The system have simple and understandable graphical user
Interface such as forms and buttons, which have descriptive names. It gives
reliable response for each user request at least before the session expires. All the
interfaces, forms and buttons are written or designed in a simple language or
common language so that the user can access it without any difficult.

3.3. Current software architecture

When a patient enters the hospital the following sequence of operation is carried out. First
and foremost, the patient is registered in the card/registration room, and then the patient
goes to the nurse’s room for examination (vital signs), the runner then carries the patient
folder to the doctor’s for diagnosis. After the diagnosis, the patient is then sent to the
laboratory for test or the patient is sent to the pharmacy for collection of drugs; the
pharmacy section checks the patients prescribed drugs and cost them before the folder is
sent to the bill office for billing. After diagnosis the patient can also be referred to another
clinic or to see a consultant in the same hospital.

3.4. Proposed System Architecture

3.4.1 Overview
The purpose of designing is to show the direction as to how application is developed and
to obtain clear and enough information needed to derive the actual implementation of the
application. The work is based on the services provided in the internet to customer. Once
the services is available based on the customer request the services will be delivered with
each specific privilege to access, to receive, to visit site. The architecture used for the
system is a 3 level client/server architecture where a client can use internet browsers to
access the online IBEX primary hospital management system within the local area
network of the agency or anywhere using the internet. It stores these data in a relational
database management system. The middle level (web/application server) implements the
business logic, controller logic and presentation logic to control the interaction between
the application’s clients and data. The controller logic processes client requests such as
Computer science Page 58
 Ibex Primary Hospital Management System 2011
requests reservation and show services provided the printing enterprise ssystem services
from the database. Business rules enforced by the business logic dictate how clients can
and cannot access application data and how applications process data.

Figure 14: System

ystem architecture for proposed system.

When
en a request is made on a web page through the browser, PHP that is residing on the
web server processes the request. It connects to the database to retrieve the requested
information and sends its response back to the browser which displays the output on
another web page. The advantage of this architecture is that the database is more secured
as it is only accessible by the application logic that resides on the web server.

3.4.2 Subsystem decomposition

ecomposition
To reduce the complexity of the solution domain, we de
decompose
compose a system into simpler
parts, called subsystems, which are made of a number of solution domain class. In the
case of complex subsystems, we recursively apply this principle and decompose a sub
sub-
system
ystem into simpler subsystems. ddecomposition results large
rge systems in to a set of loosely
dependent parts
arts which make up the system. sub-system
sub ystem decomposition is the way that
helps us to distinguish the part of the operations that takes place under the organization.

The following are the sub systems that are derived from the functionality of the system of
ibex hospital management:--[13]

Computer science Page 59

 Ibex Primary Hospital Management System 2011

Interface IPHMS client

Application Logic
IPHMS server

Drug management Pharmacy

management

Patient management
Employee
management

Account
Laboratory management Notification
management management

Feedback Bed management

management

Appointment Report management

management

Storage IPHMS storage

Figure 15: Component diagram

Computer science Page 60
 Ibex Primary Hospital Management System 2011
3.4.3 Hardware/software mapping
When the project team say hardware/software mapping for the system, it describes how
subsystems are assigned to hardware and off-the-shelf components. It also lists the issues
introduced by multiple nodes and software reuse. In this system design mainly there are
three hardware components. The client side, server side and database when the team
applies the system, necessary software will be loaded to each side hardware components.
Network should be installed between each side. Then each subsystem software will be
assigned and configured to the mapped hardware. Then the local area network will be
connected to the internet and the system will be functional.[11, 12]

Account Management

Employee management

Patient management

Pharmacy management
«HTML» «SQL»
IPNMS Client IPNMS Storage
Laboratory
management

Drug management

Notification
management

Feedback management

Appointment
management

Report management

Bed management

Figure 16: Deployment diagram

Computer science Page 61

 Ibex Primary Hospital Management System 2011
3.4.4 Persistent data management
Persistent data management describes the persistent data stored by the system and the
data management infrastructure required for it. This section typically includes the
description of data schemes, the selection of database, and the description of the
encapsulation of the database. Here As the system includes huge data received from users
and implemented in large organization such as universities, colleges, and
nongovernmental organization, it needs persistence data storage. So that our software
system uses a database called SQL server to manage and store data persistently.

keys index and integrity rules. A DB schema specifies details based on the capabilities,
terminologies, and constraints the chosen DBMS.[14]

Computer science Page 62

 Ibex Primary Hospital Management System 2011
3.4.5. Access control and security
The access control for system is implemented through capability list. This representation
comes up to be compact and efficient for the system.

Actor Privilege
Admin Control system()
Manage account()
View information()
Patient View appointment()
View own history()
Send comment()
Doctor Set appointment()
Manage own account()
Generate report()
Send lab order()
Nurse Admit patient()
Give medication()
Manage blood bank()
Manage ward()
Manage own account()
Generate report()
Lab Technician View lab order()
Report lab result()
Manage own account()
Generate report()
Chaser Register cash ()
Manage own account ()
Generate report ()
Pharmacist Manage drugs()
View medication order()
Generate report()
Manage own account()
Clerk Register patient ()
View appointment ()
Generate report ()
Manage own account ()

3.4.6 Subsystem services

In this section we describe the service provided by each sub system. In this case, we will
define the subsystem decomposition by identifying the services provided by each
subsystem. Generally this section describes the service provided by each subsystem.

Computer science Page 63

 Ibex Primary Hospital Management System 2011

Figure 17: Component diagram subsystem service

3.5Detailed class diagram

Class diagram with visibility and signature specified for each attributes and operations. In
this class diagram we define which attributes and operations are private to that class,
which attributes and operations can be accessed by the class decedents (protected), and
which attributes and operations are publicly accessible by the class user (public). We also
define the return type of each operations as well as the number and type of parameters of
each operations.

Computer science Page 64

 Ibex Primary Hospital Management System 2011

Figure 18: Detailed

etailed class diagram

Computer science Page 65

 Ibex Primary Hospital Management System 2011
3.6Package diagram
There are sub systems listed above and the dependency between them is described.

Interface

IPNMS Client

Application logic

server

IPNMS Client

Application Logic

Notification management
Laboratory management Drug management

Bed management Feedback management

Account Management

Employee management Pharmacy management Appointment management

Patient management Report management

Storage

IPNMS Client

Computer science Page 66

 Ibex Primary Hospital Management System 2011

Chapter Four

Implementation

4.1. Mapping Model to code

4.1.1 Bidirectional one to one association

The customers can view their medication history or information. In this case the customer
object has one to one association with the medhistory class. More over the medhistory
class can display and use customer history. In this case the medhistory class needs to
access its corresponding customer object. So we decided this association as a
bidirectional association.

Public class Customer { public class Medhistory() {

Private Medhistory History;
private Customer Patient;
Public customer () {
public Medhistory (Customer Patient) {
History = new Medhistory (this);
} this.Patient = Patient;

Public Medhistory getMdhis() { }

Return History;
Public Customer getCustt() {
}
Return Patient;
}

4.1.2 Bidirectional One-to-many associations

The doctor class can handle lots of customer information in this case the doctor object has
one-to-many association with the customer class. Moreover the customer class displays
the name of the doctor that is treating him/her, so a customer object need to access his/her
corresponding doctor object .in this case we decide this association as a bidirectional
association.

Computer science Page 67

 Ibex Primary Hospital Management System 2011

public class Doctor {

public class CustomerInfo () {
private CustomerInfo Custinfo;
private Doctor Doc;
public Doctor() {
public CustomerInfo (Doctor Doc) {
Custinfo = new CustomerInfo (this);
this.Doc = Doc;
}
}
Public CustomerInfo getCustinfo() {
Public Customer getPatientt() {
Return Doc;
}

4.1.3 Unidirectional one-to-many association

The administrator class can post many notification classes in this case notification object
has one-to-many association with administrator object, so we decide this association as a
unidirectional association.

public class Administrator { public class Notification () {

private Notification Post; private Administrator Admin;
public Administrator() { public Notification (Administrator Admin)
{
Post = new Notification (this);
this.Admin = Admin;
}
}
Public Notification getPost() {
Public Administrator getAdminn() {
Return Admin;
}

Computer science Page 68

 Ibex Primary Hospital Management System 2011
4.1.4 Bidirectional many-to-many association
The all posted information can be viewed by several users. In this case the User object
has many-to-many association with Notification class. Moreover the notification class can
display and use user type information. In this case a notification object needs to access its
corresponding category. So we decide this association as a bidirectional association.

public class User { public class Notification () {

private Notification Notice; private User Use;
public User() { public Notification (User Use) {
Notice = new Notification (this); this.Use = Use;
} }
Public Notification getInfoget() { Public User getUsese() {
Return Notice; Return Use;
} }
}

Figure 4.1 : Mapping the class model to a storage schema.

1 1
Customer Medhistory

uid username type

Symptom History_no uid

1 *
Doctor CustomerInfo

doid uname type

symptom doid Uid Date Time Dieses_name

Computer science Page 69

 Ibex Primary Hospital Management System 2011

* *

User Notification

Noti_title Containt uid

Uid Type

1 *
Administrator Notification

Noti_title Containt uid

Uid Type

4.2 Source code for major classes packages or interfaces

// sample code for login page

<?php

session_start();

include("connection.php");

?>

<!DOCTYPE html>

Computer science Page 70

 Ibex Primary Hospital Management System 2011
<html>

<head>

<title>IHMS</title>

<link href="style.css" rel="stylesheet" type="text/css"/>

<script src="css/ac_activex.js" type="text/javascript"></script>

<link href="css/template_css.css" rel="stylesheet" type="text/css" />

</head>

<body>

<div id="wrapper">

<div id="header">

<table width="100%" height="auto">

<tr><td width="20%"style=" >

<div id="ja-leftcol"><div class="moduletable">

<h3><font style size=5>Login Form</font></h3>

<form method="post" action="" id="form1">

<table>

<tr><td><strong>E-mail:</strong></td></tr>

<tr><td><input type="email" name="email" placeholder="E-mail"

required/><span id="idno" class="error" ></span></td></tr>

<tr><td><strong> Password:</strong></td>

<tr><td><input type="password" name="pass" placeholder="******"

required/><span id="password" class="error" ></span></td></tr>

<tr><td><strong>Remember?</strong>

Computer science Page 71

 Ibex Primary Hospital Management System 2011
<input type="checkbox" name="remember" value="yes"
class="submit"align="left"/></td></tr>

<tr><td><button name="login">Login</button></td></tr>

</table>

<p><a href="patient/patientaccount.php" target="iframe1">

Create an account</a></p></div>

<?php

$_SESSION['curd']= date('Y-m-d');

include("connection.php");

if(isset($_POST['login'])){

$email=$_POST["email"];

$pass=$_POST["pass"];

$get_user = "select* from account where email='".$email."' and

password='".$pass."' and status='active'";

$result=$con->query($get_user);

if($result->num_rows>0){

while($row=$result->fetch_assoc()){

$_SESSION['photo']=$row["user_image"];

$_SESSION['roll']=$row["roll"];

$_SESSION['logemail']=$row["email"];

$_SESSION['loguname']=$row["uname"];

$_SESSION['uide']=$row["uid"];

$_SESSION['Date']=$row["Date"];

Computer science Page 72

 Ibex Primary Hospital Management System 2011
}

$disD=strtotime($_SESSION['Date']);

$curd=strtotime( $_SESSION['curd']);

$diff=$curd-$disD;

$_SESSION['netday']=floor($diff/(60*60*24));

if($_SESSION['netday']>15)

$qry = "update account set status='deactive' where email='".$email."' and

password='".$pass."'";

if($con->query($qry)===true)

if($_SESSION['roll']=="Clerk"){

echo"<script>window.open('clerk/clerkhome.php','_self')</script>";

elseif($_SESSION['roll']=="Casher"){

echo"<script>window.open('casher/casherhome.php','_self')</script>";

elseif($_SESSION['roll']=="Doctor"){

echo"<script>window.open('doctor/doctorhome.php','_self')</script>";

Computer science Page 73

 Ibex Primary Hospital Management System 2011
}

elseif($_SESSION['roll']=="Nurse"){

echo
"<script>window.open('nurse/nursehome.php','_self')</script>";

elseif($_SESSION['roll']=="Admin"){

echo
"<script>window.open('admin/adminhome.php','_self')</script>";

elseif($_SESSION['roll']=="Lab_technitial"){

echo
"<script>window.open('lab/labtechnicialhome.php','_self')</script>";

elseif($_SESSION['roll']=="Patient"){

echo
"<script>window.open('patient/patienthome.php','_self')</script>";

elseif($_SESSION['roll']=="Pharmacist"){

echo "<script>window.open('pharmacist/pharmacisthome.php','_self')</script>";

elseif($result->num_rows==0)

Computer science Page 74

 Ibex Primary Hospital Management System 2011
{
$user = "select* from doctor where email='".$email."' and password='".$pass."' and
dstatus='active'";

$result=$con->query($user);

if($result->num_rows>0)

while($row=$result->fetch_assoc()){

$_SESSION['department']=$row["department"];

$_SESSION['logemail']=$row["email"];

$_SESSION['loguname']=$row["uname"];

$_SESSION['password']=$row["password"];

echo "<script>window.open('doctor1/doctorhome1.php','_self')</script>";

elseif($result->num_rows==0)

echo "<script>alert('Password or E-mail is not correct!')</script>".mysqli_error($con);

}}}?>

<div id="footer">

<?php

include('footer.php');

?>

</div> </div>

Computer science Page 75

 Ibex Primary Hospital Management System 2011
</body>

</html>

//admin view all users

<?php

session_start();

require("../connection.php");

include("functions/functions.php");

$_SESSION['count']=0;

if(!isset($_SESSION['email'])){

header("location:../logink.php");

?>

<!DOCTYPE html>

<html>

<head>

<title>IHMS</title>

<link href="../css/style.css" rel="stylesheet" type="text/css"/>

</head><body>

<div id="wrapper">

<?php

include('header.php');

?>

<table width="100%" height="auto">

Computer science Page 76
 Ibex Primary Hospital Management System 2011
<tr><td width="10%"style="background-color:#00688B" >

<?php

include('navigation.php');

?>

</td>

<td width="60%">

<span id="form"><table width="50%"><tr><td>

<div id="content_timeline">

<form action="home.php?id=<?php echo $user_id;?>" method="post"

id="f">

<h2>All Registered Users on this

Site:</h2><br/>

<?php

$get_members = "select * from account";

$run_members =
mysqli_query($con,$get_members);

while($row = mysqli_fetch_array($run_members)){

$user_id = $row['uid'];

$user_name = $row['uname'];

$user_image = $row['user_image'];

echo " <a href = 'user_profile.php?uid=$user_id'>

Computer science Page 77

 Ibex Primary Hospital Management System 2011
<img src = '../image/user_image/$user_image' width='50' height='50'
title='$user_name'/></a>";}

?>

</div>

</tr></table>

</span>

</td><td width="25%">

<?php

include('../calander.php');?>

</td></tr>

<tr><td colspan="3">

<div id="footer">

<?php

include('footer.php');

?><

</div> </td></tr></table></div>

<!--end of main wrapper-->

</body>

</html>

//casher approve payment

<?php

session_start();

require("../connection.php");

Computer science Page 78

 Ibex Primary Hospital Management System 2011
include("functions/functions.php");

$qry='select* from medicineorder where status=" "';

$result=$con->query($qry);

$order=mysqli_num_rows($result);

$qry="select* from patienthistory where status='sendtocasher'";

$result=$con->query($qry);

$pr=mysqli_num_rows($result);

if(!isset($_SESSION['email'])){

header("location:../logink.php");

?>

<!DOCTYPE html>

<html>

<head>

<title>IHMS</title>

<link href="../css/style.css" rel="stylesheet" type="text/css"/>

</head>

<body>

<div id="wrapper">

<?php

include('header.php');

?>

<table width="100%" height="auto">

Computer science Page 79
 Ibex Primary Hospital Management System 2011
<tr><td width="10%"style="background-color:#00688B" >

<?php

include('navigation.php');

?>

</td>

<td width="60%">

<?php

require("../connection.php");

$qry="select* from patienthistory where status='sendtocasher'";

$result=$con->query($qry);

?>

<table class="data-table" style="margin-left: 5px;margin-right: 15px;margin-top: 5px; "

border="1" cellspacing="0"cellpadding="2" >

<tr bgcolor='#69a3d6'>

<th>Patient card-number</th>

<th>patient name</th>

<th>selected doctorid</th>

<th>selected doctor-name</th>

<th>Date</th>

<th>Status</th>

<th>Option</th>

</tr>

Computer science Page 80

 Ibex Primary Hospital Management System 2011
<?php

if($result->num_rows>0){

while($row=$result->fetch_assoc()){

$_SESSION['pid']=$row["pid"];

$_SESSION['cardno']=$row["cardno"];

$_SESSION['pname']=$row["pname"];

$_SESSION['docid']=$row["docid"];

$_SESSION['docname']=$row["docname"];

$_SESSION['date']=$row["Date"];

$_SESSION['status']=$row["status"];

echo"<tr>";

echo"<td>". $row["cardno"]."</td>";

echo"<td>". $row["pname"]."</td>";

echo"<td>". $row["docid"]."</td>";

echo"<td>". $row["docname"]."</td>";

echo"<td>". $row["Date"]."</td>";

echo"<td>". $row["status"]."</td>";

echo "<td><a href=\"cardpayment.php?pid=$row[pid]\">Card-

payment</a></td>";

echo"</tr>";

}else

echo"no result is found";

Computer science Page 81

 Ibex Primary Hospital Management System 2011
echo"".mysqli_error($con);

?></table>

</td><td width="25%">

<?php

include('../calander.php');

?>

</td></tr>

<tr><td colspan="3">

<div id="footer">

<?php

include('footer.php');

?>

</div> </td></tr></table></div>

<!--end of main wrapper-->

</body>

</html>

// clerk renew account

<!DOCTYPE html>

<html>
Computer science Page 82
 Ibex Primary Hospital Management System 2011
<head>

<title>IHMS</title>

<link href="style.css" rel="stylesheet" type="text/css"/>

</head>

<body>

<div id="wrapper">

<div id="header">

<table style="height:95px" style="width:100%">

<tr><td height="90px" style="width:75%"><img src="image/hedae.jpg"

width="135.0%" height="130px" style="pading:0px">

</td><td></td><td style="align:right;width:25%">

</td></tr> </table>

</div>

<table width="100%" height="auto">

<tr><td></td> <td width="400px"><div id="ContentLeft" style="margine:10px"><ul>

<li>

<button class="collapsible"><i class="icon-reorder" ></i> Account create</button>

<div>

<a href="patientaccount.php"><i class=" icon-building" ></i>As patient</a>

<br></div></li>

<li><button class="collapsible"> <i class="icon-reorder" ></i> Request</button><div>

<a href="accountrenew.php"><i class=" icon-building" ></i> Account-Renew </a> <br>

Computer science Page 83

 Ibex Primary Hospital Management System 2011
</div></li></ul></div></td>

<td width="60%">

<span id="form"><table width="50%"><tr><td>

<h2 style="color:Black;text-decoration:none">Send Account renew Request</h2></td>

</tr></table>

<form name="f1" method="post" action="#" style="background-color:#f3f3f3">

<fieldset><center><h2 style="background-color:#00688B"> Request</h2></center>

<center>

<table>

<tr><td width="100px">User-Type:</td><td><select type="text" name="u_type"

required>

<option >enter user type...</option>

<option>Patient</option></select>

</td>

</tr>

<tr><td width="50">User-Name:</td><td><input type="text" name="un"

placeholder="enter user name..." required></td>

</tr>

<tr><td width="50">PassWord:</td><td><input type="password" name="pw"

placeholder="enter user name..." required></td>

</tr>

<tr><td width="50">Date:</td><td><input type="Date" name="date" placeholder="enter

date..." required></td>

</tr>

Computer science Page 84

 Ibex Primary Hospital Management System 2011
</table></center><br>

<script>

var coll = document.getElementsByClassName("collapsible");

var i;

for (i = 0; i < coll.length; i++) {

coll[i].addEventListener("click", function() {

this.classList.toggle("active");

var content = this.nextElementSibling;

if (content.style.display === "block") {

content.style.display = "none";

} else {

content.style.display = "block";

});

</script>

<?php

require("connection.php");

if($con)

if(isset($_POST['submit']))

$u_type=$_POST["u_type"];
Computer science Page 85
 Ibex Primary Hospital Management System 2011
$un=$_POST["un"];

$pw=$_POST["pw"];

$_SESSION['date']=$_POST["date"];

$query="update account set

status='Requested',Date='".$_SESSION['date']."' where uname='".$un."'

and password='".$pw."' and roll='Patient' and status='deactive'";

if($con->query($query)===true)

echo"<font color='green'>succesfully requested!!</font>";

else echo mysqli_error($con)."<font color='red'>request is not sended!</font>";

else

die("Connection Failed:");

?>

<center> <table><tr><td
width="100px"></td><td>

<input type="submit" name="submit"

value="Login"></td><td></td><td></td><td><input type="reset" name="reset"
value="Cancel"></td></tr></table></center></fieldset>

</form>

</span></td>

<td width="25%">

Computer science Page 86

 Ibex Primary Hospital Management System 2011
</td></tr>

<tr><td colspan="4">

<div id="footer" align="center">

<?php

include('footer.php');

?>

</div> </td></tr></table></div>

</body>

</html>

4.3 Screen images

Figure 4.2 : Administrator home

Computer science Page 87

 Ibex Primary Hospital Management System 2011

Figure 4.3: Administrators post

Computer science Page 88

 Ibex Primary Hospital Management System 2011

Chapter Five

CONCLUSION
This system development project includes two phases; the first phase deals with the
analysis and requirement phase of the life cycle and the second phase deals with the
Design phase. At the end of the first phase, we reviewed our plan in order to understand
how much we succeed our goal. Team member start this work by identifying the
significance of automated system for IBEX primary hospital and the overall method
wehad used for the development process are:

 Defining the system development methodology and identifying process. This

involved defining the system development methodology, identifying resource,
cost requirements, setting the deliverable and scheduled for the project.

The business area analysis helps the team to truly understand the major functional areas
and processes of the system. Through this we evaluated the weakness and strength of the
existing system.

After that, team member performed requirements analysis to discover user and system
requirements. This phase consisted of the functional as well as non-functional
requirements of the system development.

Then we undertake the major phase in system development process object oriented
analysis. Here, we tried to model the new system we proposed using UML
diagrams: Use case, sequence, activity and class diagrams Also, we designed the new
system user interface prototype by using different software.
5.2 RECOMMENDATION
According to scope of our project the team develops the online web based application for
IBEX primary Hospital, in the future the team member recommended the following
things to be added:

1. We develop this web site for only IBEX primary hospital if there exist a case that
needs to be referred for Gondar referral hospital the system of the two hospitals
must be connected with each other and to connect them first there have to be a
developed system for Gondar referral hospital.

Computer science Page 89

 Ibex Primary Hospital Management System 2011
2. This system uses user name, password and roles as main security mechanism we
recommended for the next to develop identification of digital signature of all
authorized
users.
3. This system is not helpful for visually impaired peoples so for the future we
recommend system like this to be helpful for all peoples.
4. This web site is using English language only we recommend it to be translated
with different national and regional languages.

Appendix[A]

Computer science Page 90

 Ibex Primary Hospital Management System 2011

Computer science Page 91

 Ibex Primary Hospital Management System 2011

Computer science Page 92

 Ibex Primary Hospital Management System 2011

Computer science Page 93

 Ibex Primary Hospital Management System 2011

Reference

[1]. Lan Somerville, “software engineering”, eighth edition, Addition-

Wesley, 2006.

Computer science Page 94

 Ibex Primary Hospital Management System 2011

[2]. Lan Somerville, “software engineering”, eighth edition, Wesley, 2006.

[3].Scott W. Ambler. (2003).Agile development for use case diagram with UML
(3rdEdition)[Online].http://www.agilemodeling.com/artifacts/useCaseDiagram.htm.availa
ble (January, 01, 2011).
[4]. I.Booch, “Object-Oriented Analysis and Design with Applications “, Third Edition,
USA, Addition-Wesley, April 2007.
[5]. Scott W. Ambler. (2003).Agile activity diagram Development with UML (3rdEdition)
[Online].http://agilemodeling.com/artifacts/activityDiagram.htm available (January, 10,
2011)

[6].Scott W. Ambler. (2003).Agile development for use activity diagram with

UMLhttps://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-
activity-diagram/. available (January, 15, 2003).

[7].Scott W. Ambler. (2003).Agile development for use class diagram with UML.
http://www.agilemodeling.com/style/classDiagram.htm. Available (January, 10, 2011)

[8]. https://www.smartdraw.com/sequence-diagram/

[9].https://www.tutorialspoint.com/software_engineering/software_user_interface_design.htm
[10] Object-oriented SoftwareDevelopment, Conclusion third edition by Elefelious
Getachew, on November,2011.

[11] Deployment-diagrams-overview. [Online]. Available: http://www.umldiagrams.

org/deployment-diagrams-overview.html [Accessed 6 November 2018].

[12] Deployment diagram. [Online]. Available:

https://en.wikipedia.org/wiki/Deployment_diagram [Accessed 12 November 2018.

[13]Component Diagram. [Online]. Available:

https://creately.com/diagram/example/gqz0nrua1/Component+Diagram [Accessed 12

November 2018.

[14] Persistent data management. [Online]. Available: https://en.wikipedia.org/wiki/

Persistent data+ management [Accessed 4 October 2018].

Computer science Page 95

 Ibex Primary Hospital Management System 2011

Glossary
Class Diagram: Is a type of static structure diagram that describe the
structure of a system by showing system classes, their
attribute, operation and the relationship among the class.

Component Diagram Is UML diagram depicts how components are wired

together to form larger components and or software
system.
Functional requirement Is a requirement that specifies what the system should do
or what the system should perform
Hardware Is computer equipment including all the components use
to make the computer
Non-functional are requirements which specify criteria that can be used to
requirement judge the operation of a system, rather than specific
behaviors
Software Computer programs, instructions that make hardware
work

Scenario Is an instance of use case explaining concerned major set

of actions
Sequence Diagram Is a king of interaction diagram that show how process
operate with one another and in what order
Software design Is the transformation of an analysis model into a system
design model During system design, developers define
the design goals of the project and decompose the system
into smaller subsystems that can be realized by individual
teams
System Any collection of component element that work together
to collect task
Use case diagram Graphical Representation of mark full of step wise
activity and action with support for choice, iteration and
concurrency

Computer science Page 96

 Ibex Primary Hospital Management System 2011
User interface The combination of menus, screen design, keyboard
command, command language and help, which creates the
way a user interact with computers.
User Any user of the system including database administrator,
librarian, member, system administrator
Design Goal Describes the quality of the system that should be
optimized
Software Architecture Provides a high level view of the system by decomposing
it into smaller and manageable pieces and study the
relationship among this pieces
Hardware/Software Is activity of selecting Hardware and software
mapping configuration for the system
Persistent Data Data that exists from session to session. Persistent data
are stored in a database on disk or tape.
Are data that will be tracked and stored in the system
permanently
Access Control The management of admission to system and network
resources. It grants authenticated users access to specific
resources based on company policies and the permission
level assigned to the user or user group. Access control
often includes authentication, which proves the identity of
the user or client machine attempting to log in.
Control Flow Describes how the system sequences operations and
whether the system is event driven or procedure driven.
Boundary Condition Specifies how the system is initialized and shutdown.

Computer science Page 97