Title Hospital Management System: A Project Work Submitted To The Department of Physical Science Rongo University

-1-
TITLE
HOSPITAL MANAGEMENT SYSTEM
A Project work submitted to the
DEPARTMENT OF PHYSICAL SCIENCE

RONGO UNIVERSITY
Submitted by
ABDIFATAH ABDI HAJI (Admission No: CSC/023/2016)

BSA- COMPUTER SCIENCE 3rd year
Rongo University.
Guided by
LECTURER: NICKSON AMUMO
Declaration.
This research project which is my original work has not been presented for a bachelor of science in any
other university .No part of this project may be reproduced may be reproduced without the prior
permission of the author.
Project Report Hospital Management System

-2-
Declaration by supervisor
This project has been submitted for examination with my approval as University Supervisor.
Name of Supervisor. Date.
…………………………… ………………………….
Sign
ACKNOWLEDGEMENT.
The satisfaction that accompanies that the successful completion of any task would be incomplete without
the mention of people whose ceaseless cooperation made it possible, whose constant guidance and
encouragement crown all efforts with success.
I am grateful to our project guide Mr. Nickson Amumo for the guidance, inspiration and constructive
suggestions that helpful us in the preparation of this project.
I also thank my colleagues who have helped in successful completion of the project.
ABSTRACT
My project Hospital Management System includes registration of patients, storing their details
into the system, registration of receptionist, storing their details into the system and registration of doctors,
storing their details into the system. My software has the facility to give a unique id for every patient,
receptionist, doctor and stores the details of every patient and the staff automatically. It includes a search
facility to know the current status of each room. User can search availability of a doctor and the details of a
patient using the id.

-3-
The Hospital Management System can be entered using a username and password. It is accessible either
by an administrator, receptionist or doctor. Only the staff can add data into the database. The data can be
retrieved easily. The interface is very user-friendly. The data are well protected for personal use and
makes the data processing very fast.

-4-
Contents
TITLE................................................................................................................................................ 1
Declaration. ................................................................................................................................... 1
Declaration by supervisor ............................................................................................................. 2
ACKNOWLEDGEMENT. ........................................................................................................... 2
ABSTRACT .................................................................................................................................. 2
CHAPTER. 1 .................................................................................................................................... 7
INTRODUCTION ........................................................................................................................ 7
1.1 BACKGROUND ............................................................................................................ 7
1.2 PROBLEM STATEMENT............................................................................................. 7
1.3 PROBLEM SOLUTION. ............................................................................................... 7
1.4 PROJECT OBJECTIVES ................................................................................................... 8
1.5 LIMITATION OF THE CURRENT SYSTEM .................................................................. 8
1.6 BENEFITS OF THE PROPOSED SYSTEM ..................................................................... 9
1.7 LIMITATION OF THE PROPOSED SYSTEM ................................................................ 9
1.8 SCOPE OF THE PROJECT ............................................................................................. 9
CHAPTER 2 ................................................................................................................................... 10
LITERATURE REVIEW ........................................................................................................... 10
CHAPTER 3. .................................................................................................................................. 10
3.1 DATA COLLECTION ......................................................................................................... 10
3.1.1TOOLS AND TECHNIQUES ........................................................................................ 10
3.2DATA ANALYSIS. ............................................................................................................... 11
3.3 REQUIREMENTS ANALYSIS ........................................................................................... 12
3.3.1SOFTWARE REQUIREMENTS ................................................................................... 12
3.3.2HARDWARE REQUIREMENTS .................................................................................. 13
CHAPTER 4. .................................................................................................................................. 13
Design and methodology ............................................................................................................ 13
4.1 INRODUCTION ............................................................................................................... 13

-5-
4.2 DATABASE DESIGN ...................................................................................................... 14

4.3 DATA FLOW DIAGRAM ............................................................................................... 16
CHAPTER 5. .................................................................................................................................. 18
5.1 SCHEDULE .......................................................................................................................... 18
5.2 WORK BREAKDOWN STRUCTURE. .............................................................................. 18
5.3 The Gantt chart...................................................................................................................... 20
CHAPTER 6 ................................................................................................................................... 21
6.1 INTRODUCTION ................................................................................................................ 21
6.2 TESTING STRATEGY ........................................................................................................ 21
6.2.1 Unit testing ..................................................................................................................... 21
6.2.2 Integration testing .......................................................................................................... 21
6.2.3 Acceptance testing ......................................................................................................... 21
6.3 TEST PLAN .......................................................................................................................... 22
6.3.1 Unit testing ................................................................................................................ 22
6.3.2 Integration testing ..................................................................................................... 22
6.3.3 Acceptance testing .................................................................................................... 22
CHAPTER 7. .................................................................................................................................. 23
SYSTEMS’S SAMPLE SCREEN SHOTS ................................................................................ 23
HOME PAGE/ INDEX PAGE ................................................................................................... 23
ADMIN LOGIN PAGE ............................................................................................................. 24
RECEPTIONIST HOME PAGE ................................................................................................ 24
UPDATE PATIENT INFO PAGE: ............................................................................................ 25
DOCTOR HOME PAGE ............................................................................................................ 25
ALL APPOINTMENTS PAGE .................................................................................................. 26
SAMPLE SOURCE CODE OF THE SYSTEM......................................................................... 27
Code for login. ........................................................................................................................ 27
Code for registration. .............................................................................................................. 29
Code for entering patient information. .................................................................................... 30
Project budget. ............................................................................................................................ 31
CHAPTER 8 ................................................................................................................................... 32

-6-
RECOMMENDATION .............................................................................................................. 32
CONCLUSION. .......................................................................................................................... 32
CHAPTER 9 ................................................................................................................................... 33
BIBLIOGRAPHY ....................................................................................................................... 33
CHAPTER 10 ................................................................................................................................. 34
WEBILIOGRAPHY ................................................................................................................... 34

-7-
CHAPTER. 1
INTRODUCTION
1.1 BACKGROUND
The university has had a high increase in the number of students and staff in the recent past. The
maintenance of records of these students and staff is manual. The file for each patient is kept and is
retrieved upon the subsequent visit.
Normally the patients who are the students and the staff present identification cards at the reception which
are checked to verify whether they have their records or files there. If not, a new file is created containing
the staff identification details and in which future consultation details will be recorded.
If the file is already there, the patient is asked to go to the consultation room where he or she is diagnosed
and the details recorded in the patient’s file. The patient is either referred to the laboratory or treatment
room for tests and medication respectively depending on the situation.
1.2 PROBLEM STATEMENT.
The maintenance of records of these students and staff is manual. The file for each patient is kept and is
retrieved upon the subsequent visit.
Normally the patients who are the students and the staff present identification cards at the reception which
are checked to verify whether they have their records or files there. If not, a new file is created containing
the staff identification details and in which future consultation details will be recorded.
If the file is already there, the patient is asked to go to the consultation room where he or she is diagnosed
and the details recorded in the patient’s file. The patient is either referred to the laboratory or treatment
room for tests and medication respectively depending on the situation.
Due to the increasing number of students and staff as the university expands to a fully-fledged university,
several problems have arisen. They include-
Lack of immediate retrievals: -The information is very difficult to retrieve and to find particular
information like- E.g. - To find out about the patient’s history, the user has to go through various registers.
This result in inconvenience and wastage of time.
Lack of immediate information storage: - The information generated by various transactions takes time and
efforts to be stored at right place.
Lack of prompt updating: - Various changes to information like patient Details are difficult to make as
paper work is involved.
Error prone manual stock taking: - Manual stock taking are error prone and take a lot of time this may
result in incorrect information. For example, about the medicine in stock.
Preparation of accurate and prompt reports: - This becomes a difficult Task as information is difficult to
collect from various registers.
1.3 PROBLEM SOLUTION.
1. Improved Manual System:-

-8-
One of the alternative solutions is the improvement of the manual system. Anything, which can be done by
using automated methods, can be done manually. But the question arises how to perform thing manually in
a sound manner. Following are some suggestions, which can be useful in the manual system.
A more sophisticate register maintenance for various Patient Information, Doctor’s diary, medicine stock
availed for can be maintained at central place. Adequate staff may be maintained so that updation is made
at the very moment at the same time. Proper person for proper work should be made responsible so that a
better efficiency could be achieved. This needs a lot of work force.
2. Batch System:-
Another alternative solution can be used of computer based batch system for maintaining the information
regarding purchase details, customers and employees. A batch system refers to a system in which data is
processed in a periodical basis. The batch system is able to achieve most of the goals and sub goals. But a
batch system data is processed in sequential basis. Therefore batch system is not suggested.
3. Online System:-
This system provides online storage/updation and retrieval facility. This system promises very less or no
paper work and also provides help to Doctor and operational staff. In this system everything is stored
electronically so very less amount of paper work is required and information can be retrieved very easily
without searching here and there into registers. This system is been discussed here.
1.4 PROJECT OBJECTIVES

The following were the project objectives:
To identify the current technology that is used to develop the registry system.
To design and develop a database to contain details of the patients and staff within the hospital
management system
Implement a system that will perform the above-mentioned tasks in the hospital system.
1.5 LIMITATION OF THE CURRENT SYSTEM.

1. Lack of immediate retrievals: -The information is very difficult to retrieve and to find particular
information like- E.g. - To find out about the patient’s history, the user has to go through various
registers. This result in inconvenience and wastage of time.
2. Lack of immediate information storage: - The information generated by various transactions
takes time and efforts to be stored at right place.
3. Lack of prompt updating: - Various changes to information like patient Details are difficult to
make as paper work is involved.
4. Error prone manual stock taking: - Manual stock taking are error prone and take a lot of time this
may result in incorrect information. For example, about the medicine in stock.
5. Preparation of accurate and prompt reports: - This becomes a difficult task, as information is
difficult to collect from various registers. The information collected in the reports is often
inaccurate due to human error.
6. Deteriorations of records:-The files and folders in which the information is stored deteriorate
with time i.e. there is wear and tear of the files and folders.

-9-
1.6 BENEFITS OF THE PROPOSED SYSTEM

 Planned approach towards working: - The working in the organization will be well planned and
organized. The data will be stored properly in data stores, which will help in retrieval of
Information as well as its storage.
 Accuracy: - The level of accuracy in the proposed system will be higher. All operation would be
done correctly and it ensures that whatever information is coming from the center is accurate.
 Reliability: - The reliability of the proposed system will be high due to the above stated Reasons.
The reason for the increased reliability of the system is that now there would be proper storage and
access to information.
 No Redundancy: - In the proposed system utmost care would be that no information is repeated
anywhere, in storage or otherwise. This would assure economic use of storage space and
consistency in the data stored.
 Immediate retrieval of information: - The main objective of proposed system is to provide for a
quick and efficient retrieval of information. Any type of information would be available whenever
the user requires.
 Immediate storage of information: - In manual system, there are many Problems to store the
largest amount of information.
 Easy to Operate: - The system should be easy to operate and should be such that it can be
developed within a short period and fit in the limited budget of the user.
1.7 LIMITATION OF THE PROPOSED SYSTEM
1. Computers have to be bought and installed which could be costly.
2. A network will be needed to connect the computers within the facility.
3. Implementation of the automated system will require buying of computers that will act as a
platform upon which the system well run.
4. Implementation of the system calls for employment a person has knowledge about computers.
1.8 SCOPE OF THE PROJECT
The software can be used in any hospital that has medical/health center within the organization for
maintaining patients’ tests and treatment details by customizing some of the features. That suits that
particular organization.

- 10 -
CHAPTER 2.
LITERATURE REVIEW.
There are many systems developed that have been developed related to this hospital management system
but however, these systems are too complex for a local level 5 hospital like the one of Rongo. Most of the
level 5 hospitals encompass many procedures irrelevant to Provincial Hospital management system.
System provides the benefits of streamlining of operations, enhanced administration and control, improved
response, cost control and improved profitability. The program can look after Inpatients, OPD patients,
records, database treatments, status illness, and billings. A systematic approach to the way documents are
managed, can transform your Hospital resources to its highest utility and advantage. System has Admin,
Doctor, Nurse, Administration, Pharmacist and Patient modules. Payroll and attendance record of
employees can be maintained. Messages can be sending within this application. Patient can send online
request for appointment. Medicines updated inventory record can be maintained. Blood donor's record can
be maintained and they can be called as needed.
The other system is the outspan hospital management system which
CHAPTER 3.
SYSTEM ANALYSIS
3.1 DATA COLLECTION
Data collection involved finding facts of the activities being carried in hospital management system aiming
at gathering information on its operation and procedures like registration process, treatment details,
recording process, diagnosis processes and so on.
3.1.1TOOLS AND TECHNIQUES

Sources of data used were:
1) PRIMARY SOURCES

- 11 -
In order to get facts hospital management system works, an official introductory letter from the department
introduced me to the interviewees. This enabled them to give out information without hesitating. The
interviewees included doctors, nurses, receptionists and patients.
INTERVIEWS.
The introductory letter from the department accorded me direct communication to the interviewees. This
enabled them to respond without hesitation.
OBSERVATION.
This is not a new field but rather a new approach to analyzing computer system.one of its main goals is not
to superimpose the interviewer’s or analyst’s viewpoints on the system but to use the viewpoint of the
people within the system. An ethic view of the system is the outside view or what the analyst sees. This is
basically information gathering by observation.
This involved examining of activities going on from registration of patients, consultation details, treatment
section and the laboratory section. This gave a picture on what happens on the ground and who does the
work.
QUESTIONNAIRES.
Analysis of the data collected was basically to identify the following:
Information to be included in the system.
Scope of the system in terms of data and information.
3.2DATA ANALYSIS.
Analysis of the collected data was basically performed to identify the following.
Information that was to be included in the system.
Scope of the system in terms of data and information.
Information category.
Research findings
The table below summarizes the feedback from questionnaires .this tool helped in the collection of data
from the receptionists the nurses and doctors. A sample of the questionnaire is shown in the appendix.
Table 1
Question No of Reponses Facts gained
Are you computer literate? 4 Yes
1 No
Is there a computer system that supports 6 No

record keeping?

- 12 -
Do you think a computer system is 6 Yes

necessary in the management of records?
What reports are produced by the manual 4 N /A

system? 2 No response
How many patients seek medical services 3 100

there in a day? 2 Over 100
1 Less than 100.
How many staff students seek medical 4 100

services there in a day? 1 Over 100
1 Less than 100
Do you want to continue working with 6 No

current system?
Which departments have been 6 None

computerized?
Summary of the findings

From the feedback from the questionnaire, it was evident that university medical center has not been
computerized as a whole .this may be due to the fact that ICT in the hospital is still growing. From the
sample, most people are computer literate though training may be necessary for a few. All areas
/departments of the hospital management system need to be computerized. All of the respondents seemed
not to be sure if reports are generated. The response was N/A” or blank response.
Observation and interview techniques helped in knowing the process followed form registration of new
patients in the files, consultation details and also how doctor details are dealt with.
3.3 REQUIREMENTS ANALYSIS
3.3.1SOFTWARE REQUIREMENTS
Operating System : Windows 2010/XP
Front end : SQL Xampp 6.0
Back end : MS Access

- 13 -
3.3.2HARDWARE REQUIREMENTS
Processor :X86 Compatible processor with 1.7

GHz Clock speed
RAM : 512 MB or more
Hard disk : 20 GB or more
Monitor : VGA/SVGA
Keyboard : 104 Keys
Mouse : 2 buttons/ 3 buttons
CHAPTER 4.
Design and methodology
4.1 INRODUCTION
The water fall model
The Software Development Methodology (SDM) to be used in this project is the Software Development
Life cycle (SDLC). Where there is a structured set of activities required to develop a software system
required to develop a software system
Specification;
Design; 3) Validation;
4) Evolution.
This is based on the waterfall model with rapid prototyping which is a sequential design process often used
in software development process. The development is seen as a flowing downwards steadily. In the Model,
one phase has to be finalized before the process can progress to the next phase.

- 14 -
Merits of water fall model

Dividing the development of a system into phases makes the development process more manageable and it
gives the opportunity for control of the application development process.
The methodology helps to ensure that the specifications are complete and they are communicated to
systems development staff.
The following phase cannot start until the previous has finished. This helps to identify problems with
requirement during design and also problems in coding are also uncovered.
Demerits of waterfall model

One problem with the waterfall model is that it does not provide feedback that is commitments must be
made at early stage in the process and it is difficult to respond to changing customer requirements
4.2 DATABASE DESIGN
PATIENT
NAME TYPE CONSTRAINTS
Patient_id Int(25) Primary key

Full name Varchar(50) Not null
DOB Int(20) Not null
Weight Int((25) Not null
Phone No Varchar(50) Not null
Address Varchar(70) Not null

- 15 -
RECEPTIONISTS

Email Varchar(50) Primary key
Password Varchar(50) Not null
Full name Varchar(100) Not null
DOCTORS

email Varchar(50) Primary key
password Varchar(100) Not null
full name Varchar(100) Not null
specialty Varchar(50) Not null
ADMIN

email Varchar(30) Primary key
password Varchar(100) Not null

- 16 -
4.3 DATA FLOW DIAGRAM
Level 1 DFD Administrator
Administrator
Hospital Hospital Database

Login Details Management
System
Login
Level 2 DFD Administrator
Controls Overall Data Advanced Add/Edit/Delete Data

Hospital
Administrator Management User
System

- 17 -
Level 1 DFD User
User
Hospital Hospital Database

Login Details Management
System
Login
Users include
 Receptionists
 Doctors

- 18 -
CHAPTER 5.
5.1 SCHEDULE
Hospital Management
System
Problem Feasibility Proposal Design

Identification Coding Documentation Presentation
Study Writing and And And
Reporting Analysis Testing
5.2 WORK BREAKDOWN STRUCTURE.
Activity Task name Immediate Duration Start Finish

Predecessor. In weeks
A Problem identification - 3 Week 1 Week 3
B Feasibility study A. 2 week 4 Week 6

C Proposal writing A,B. 1 Week 4 Week 7
D Design and analysis C. 1 Week 7 Week 8
E Coding and testing D. 3 Week 8 Week 10
F Documentation D,E. 1 Week 11 Week 13
G Presentation and F 1 Week 8 Week 13

Implementation

- 19 -
Activities
Problem identification.
Feasibility study.
Proposal writing D. Interface design.
Coding and testing
Documentation.
Presentation.
Activity. Immediate Duration (weeks).

Predecessor.
A. Problem - 3
Identification.
B. Feasibility study. A. 2
C. Proposal writing. A,B. 1
D. Interface design. C. 1
E. Coding and testing D. 3
F. Documentation. D,E. 1
G. Presentation. F 1

- 20 -
5.3 The Gantt chart.
NOV NOV10 NOV 29 DEC13 DEC 19 DEC 23 JAN 26

- 21 -
CHAPTER 6
SYSTEM TESTING
6.1 INTRODUCTION
System testing involves testing the system to validate that it meets that it meets user specifications and
objectives.
System test objectives are
To analyze the test results.
Test the system against user’s requirements.
The components to be tested are

To test the system to validate it only accepts valid data.
Check whether the system is giving the required output.
6.2 TESTING STRATEGY
This involves testing the system using different types of system tests that were performed on the system.
This is aimed at uncovering errors and measuring the system capability. The following system tests
6.2.1 Unit testing
This is the test in the development process and ensures that each unique path of the project performs
accurately to the documented specifications and contains clearly defined inputs and expected results.
Each module was tested to ascertain that it fully performs as expected.
6.2.2 Integration testing.
This involves testing integration of modules. This was done to ensure that modules interactions with each
other were working and that integration of the modules making up the system was working.
6.2.3 Acceptance testing
This involves testing the system with the intent of confirming readiness of the product and customer
acceptance.

- 22 -
6.3 TEST PLAN
6.3.1 Unit testing.

Test Test area Expected results
Module testing Adding new record System should be able to add

new records to the database
Delete records The system should be able to

delete unwanted records
Update records The system should update

records and save changes made.
Search records The system should be able to

retrieve relevant records required
by the user.
6.3.2 Integration testing

Test Test area Expected Results
Integration test user authentication valid users should log into the
system
Relationships among modules The established relationships

should work as expected.
6.3.3 Acceptance testing

Testing the system with the intent of confirming readiness of the product and customer acceptance.
Test Test area Expected results
Acceptance testing Interaction of users with the The user should be able to
system use the system with ease
6.3.4 Usability testing

This is making sure at the objects are usable even after they have been completely tested. This test
determines whether the users will be compatible with system.

- 23 -
CHAPTER 7.
SYSTEMS’S SAMPLE SCREEN SHOTS
Login window
Different users have different login information stored in the database. They can login to the system
through this interface, or change their passwords for security reasons. This form is loaded when user starts
the program.
HOME PAGE/ INDEX PAGE

- 24 -
ADMIN LOGIN PAGE
RECEPTIONIST HOME PAGE

- 25 -
UPDATE PATIENT INFO PAGE:
DOCTOR HOME PAGE

- 26 -
ALL APPOINTMENTS PAGE

- 27 -
SAMPLE SOURCE CODE OF THE SYSTEM.
Code for login.

<?php
function login($email_id_unsafe, $password_unsafe, $table = 'users')
{
global $connection;
$email_id = secure($email_id_unsafe);
$password = secure($password_unsafe);
$sql = "SELECT COUNT(*) FROM $table WHERE email = '$email_id' AND password =
'$password';";
$result = $connection->query($sql);
$num_rows = (int) $result->fetch_array()['0'];
if ($num_rows > 1) {
//send email to sysadmin that my site has been hacked
return 0;
} elseif ($num_rows == 0) {
echo status('no-match');
return 0;
} else {
echo "<div class='alert alert-success'> <strong>Well done!</strong> Logged In</div>";
$_SESSION['username'] = $email_id;
if ($table == 'admin') {
$_SESSION['user-type'] = 'admin';
}
if ($table == 'users' || $table == 'doctors' || $table == 'clerks') {

$sql = "SELECT fullname FROM $table WHERE email = '$email_id' AND password =
'$password';";
$result = $connection->query($sql);
$fullname = $result->fetch_array()['fullname'];
$_SESSION['fullname'] = $fullname;

- 28 -
if ($table == 'users') {
$_SESSION['user-type'] = 'normal';
} elseif ($table == 'clerks') {
$_SESSION['user-type'] = 'clerk';
} else {
$_SESSION['user-type'] = 'doctor';
}
}
return 1;
}
}
?>

- 29 -
Code for registration.

<?php
function register($email_id_unsafe, $password_unsafe, $full_name_unsafe, $speciality_unsafe = 'doctor',
$table = 'users')
{
global $connection,$error_flag;
$email = secure($email_id_unsafe);
$password = secure($password_unsafe);
$speciality = secure($speciality_unsafe);
$fullname = ucfirst(secure($full_name_unsafe));
$sql;
switch ($table) {
case 'users':
$sql = "INSERT INTO $table VALUES ('$email', '$password', '$fullname');";
break;
case 'doctors':
$sql = "INSERT INTO $table VALUES ('$email', '$password', '$fullname','$speciality');";
break;
case 'clerks':
$sql = "INSERT INTO $table VALUES ('$email', '$password', '$fullname');";
break;
default:
// code...
break;
}
if ($connection->query($sql) === true) {

echo status('record-success');
if ($table == 'users' && $error_flag == 0) {
return login($email, $password);
}
} else {
echo status('record-fail');
}
}
?>

- 30 -
Code for entering patient information.

<?php
function enter_patient_info($full_name_unsafe, $age_unsafe, $weight_unsafe, $phone_no_unsafe,
$address_unsafe)
{
global $connection, $error_flag,$result;
$full_name = ucfirst(secure($full_name_unsafe));
$age = secure($age_unsafe);
$weight = secure($weight_unsafe);
$phone_no = secure($phone_no_unsafe);
$address = secure($address_unsafe);
$sql = "INSERT INTO `patient_info` VALUES (NULL, '$full_name', $age,$weight,

'$phone_no','$address');";
if ($connection->query($sql) === true) {

echo status('record-success');
return $connection->insert_id;
} else {
echo status('record-fail');
return 0;
}
}
?>

- 31 -
Project budget.
ITEM COST
Equipment
Computer 40000
1500
Flash disk
50
CD
subtotal 41550
Software
Windows 2010/XP/2007 12000
SQL XAMPP/WAMP
subtotal 12000
Photocopy& printing 2500
total 56050

- 32 -
CHAPTER 8
RECOMMENDATION AND CONCLUSIONS
RECOMMENDATION
I recommend that the development be continued together with like-minded persons who live to see the
dream I had and build effective hospital systems that can be used to cut costs of manual labor and enable
efficiency of service provision.
I also recommend that an improvement be made on this system to enable the generation of bills for the
staff members instead those bills being generated in the finance office which consumes time and can
result in drastic effects when the patient is totally sick.
I therefore recommend the inclusion of a purely designated laboratory as a research lab where students can
have the opportunity to implement their ideas and innovations of different forms of systems.
CONCLUSION.
The major achievement of this project is the ability to register new patients and staffs i.e. doctors and
receptionists and store their data in the database. The most important thing that must be appreciated by all
is that, the system is an eye opener to a lot more investigation and detailed research for implementation
and improvement purposes in order to add to the general knowledge base.
The system is for computerizing the working in a hospital. The software takes care of all the requirements
of an average hospital and is capable to provide easy and effective storage of information related to
patients that come up to the hospital.

- 33 -
CHAPTER 9
BIBLIOGRAPHY
http://unpan1.un.org/intradoc/groups/public/documents/UNPAN/UNPAN023 588.PDF(10-03-2008)
http://www.mcdonline.gov.in/mcd/birthfaq.jsp(10-02-2008)
http://www.ers-can.com (12-04-2008)
http://www.unicef.org/bangladesh/birthregistrationsystem.pdf(12-04-2008)
http://www.freepatentsonline.com/4233661.html(20-03-2010)
http://www.scribd.com/doc/24070840/Hospital-Management-System-
Synopsis-and-Project-Report
http://www.scribd.com/doc/13569522/09ProjectHospital-Management-
System (15-05-2011)

- 34 -
CHAPTER 10
WEBILIOGRAPHY
1. http://www.vbdotnetheaven.com/
2. http://www.connectionstrings.com/

Title Hospital Management System: A Project Work Submitted To The Department of Physical Science Rongo University

Uploaded by

Copyright:

Title Hospital Management System: A Project Work Submitted To The Department of Physical Science Rongo University

Uploaded by

Document Information

Original Title

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Title Hospital Management System: A Project Work Submitted To The Department of Physical Science Rongo University

Uploaded by

Copyright:

-1-

HOSPITAL MANAGEMENT SYSTEM

A Project work submitted to the

DEPARTMENT OF PHYSICAL SCIENCE

ABDIFATAH ABDI HAJI (Admission No: CSC/023/2016)

LECTURER: NICKSON AMUMO

Project Report Hospital Management System

Project Report Hospital Management System

Project Report Hospital Management System

Project Report Hospital Management System

4.2 DATABASE DESIGN ...................................................................................................... 14

Project Report Hospital Management System

Project Report Hospital Management System

Project Report Hospital Management System

1.4 PROJECT OBJECTIVES

1.5 LIMITATION OF THE CURRENT SYSTEM.

Project Report Hospital Management System

1.6 BENEFITS OF THE PROPOSED SYSTEM

Project Report Hospital Management System

3.1.1TOOLS AND TECHNIQUES

Project Report Hospital Management System

Are you computer literate? 4 Yes

Is there a computer system that supports 6 No

Project Report Hospital Management System

Do you think a computer system is 6 Yes

What reports are produced by the manual 4 N /A

How many patients seek medical services 3 100

How many staff students seek medical 4 100

Do you want to continue working with 6 No

Which departments have been 6 None

Summary of the findings

Front end : SQL Xampp 6.0

Back end : MS Access

Project Report Hospital Management System

Processor :X86 Compatible processor with 1.7

RAM : 512 MB or more

Hard disk : 20 GB or more

Keyboard : 104 Keys

Mouse : 2 buttons/ 3 buttons

Design and methodology

Project Report Hospital Management System

Merits of water fall model

Demerits of waterfall model

4.2 DATABASE DESIGN

NAME TYPE CONSTRAINTS

Patient_id Int(25) Primary key

Project Report Hospital Management System

NAME TYPE CONSTRAINTS

NAME TYPE CONSTRAINTS

NAME TYPE CONSTRAINTS

Project Report Hospital Management System

4.3 DATA FLOW DIAGRAM

Level 1 DFD Administrator

Hospital Hospital Database

Level 2 DFD Administrator

Controls Overall Data Advanced Add/Edit/Delete Data

Project Report Hospital Management System

Level 1 DFD User

Hospital Hospital Database

Project Report Hospital Management System

Problem Feasibility Proposal Design

5.2 WORK BREAKDOWN STRUCTURE.

Activity Task name Immediate Duration Start Finish