ARBA MINCH UNIVERSITY

ARBAMINCH INSTITUTE OF TECHNOLOGY (AMIT)

“Preparation of Dataset, and Report Generation For Arba Minch Hospital”

Name ID

1. EndalkachewYalew .….…….Ramit/1660/06
2. NakachewAcham……….……Ramit/1503/05
3. EfrataAlemu…………..….…. Ramit/1649/06
4. RehmetBeshir …………..……Ramit/1806/06
5. TsegentLema……………..…..Ramit/1873/06
6. Demoze Haile………………… Ramit/1365/05

Advisor Name: - Alazar Baharu

Submitted to Department of Computer Science and IT, AMIT, Arba Minch University, in
Partial fulfillment for the requirement of the Degree of Bachelor Science in (Information
Technology)

Arba Minch, Ethiopia

Jun, 2017
 Arba Minch University
Arba Minch Institute of Technology (AMIT)
Approval Sheet
--------------------------------------------------------------------------------------------------

This is to certify that the senior project titled “Preparation of Dataset, and Report

Generation for Arba Minch Hospital “Submitted by

1. Endalkachew Yalew .….…….RAMIT/1660/06

2. EfrataAlemu…………..….…. RAMIT /1649/06
3. RehmetBeshir …………..…… RAMIT /1806/06
4. TsegentLema……………..….. RAMIT /1873/06
5. Demoze Haile………………… RAMIT /1365/05
6. NakachewAcham……….…… RAMIT /1503/05

To the department of Computer Science and Information Technology, Arba Minch for the partial
fulfillment of the requirement of the Degree of Bachelor Science in Information Technology, is a
bona fide record of the project done by them under my supervision. The contents of this
document in full, or in parts, have not been submitted to any other institute or university for the
award of any degree or diploma.

Mr. Alazar
(Guide)
Date: 6 Jun, 2017
Arba Minch

Final Year Project CSIT 2009 E C(AMU). Page I

Acknowledgement
First of all we would like to thank GOD keeping us healthy. Lots of problems have overcome
with the assistance of GOD. Without his will nothing could be done. We have taken efforts in
this project. And also thanks our Advisor Mr Alazar Baharu for all his support with this
project. Mr.Alazar. B always has time for our questions and his comments on our thesis have
been valuable. In addition to this we wish to thank our friends for supporting us in many ways.
Last but not least, we are deeply grateful to our family supported in many ways. Lastly, our
thanks’ and appreciation also go to AMIT, Department of Computer Science and Information
Technology in developing the project and people who have willingly helped us out with their
talents.

Final Year Project CSIT 2009 E C(AMU). Page II

Abstract
Now a day’s recording data and generating report plays vital and immeasurable role in health
care related researches. In order to record a qualified data and deliver reports to facilitate works
in health center institutes should have integrate computerized system. In line with this fact Arba
Minch Hospital also has no integrated and computerized system to collect data and generate
report since it has started giving service for the community. Relatively looking from previous
years the current paper based data collection and report generation process implemented by
AMH is delivering a good service for the society even though it’s not satisfactory. To solves this
problem there is a need to develop information management system which will help the Hospital
to collect data, prepare dataset and generate report. In order to develop the system we followed
the object oriented system design approach. In addition to this the collection of data in offline
mode will be handled by ODK collect and the synchronization will be handled by ODK
aggregate tool. This proposal focuses on requirements analysis, design and implementation of
dataset preparation and report generating system for AMH.

Final Year Project CSIT 2009 E C(AMU). Page III

Keyword
Acronym Definition

AMH Arba Minch Hospital

EC Ethiopian Calendar

ODK Open Data kit

OOSAD Object Oriented System Analysis and Design

HTML Hyper Text Markup Language

CSS Cascading Style Sheet

XLS Filename Extension (Microsoft Excel spreadsheet file)

UML Uniform Modeling Language

MS Micro-Soft

PHP Personal Home Page

Final Year Project CSIT 2009 E C(AMU). Page IV

Table of Contents
CHAPTER ONE ............................................................................................................................. 1
INTRODUCTION .......................................................................................................................... 1
1. Introduction ................................................................................................................................. 1
1.1. Background of Organization ................................................................................................ 1
1.2 .Background of the Project ................................................................................................... 2
2. Team Composition ...................................................................................................................... 3
3. Task and Schedule ...................................................................................................................... 4
4. Problem Statement ...................................................................................................................... 5
5. Detailed Objectives of the project............................................................................................... 5
5.1. General objectives ................................................................................................................ 5
5.2. Specific objective ................................................................................................................. 5
6 .Scope of the Project .................................................................................................................... 6
6.1. In scope ................................................................................................................................ 6
6.2. Out scope ............................................................................................................................. 6
7. Significance of the Project .......................................................................................................... 6
8. Target Beneficiaries of the System ............................................................................................. 6
9. Methodology ............................................................................................................................... 7
9.1. Data collection methodology ............................................................................................... 7
9.1 .1 Primary Data collection Methodology used ................................................................. 7
9.1.2. Secondary Data collection ............................................................................................ 7
9.2. Selection of application development strategy .................................................................... 7
9.3. Selection of application development tools ......................................................................... 8
9.4. System Implementation and Testing Methodology ............................................................. 8
10. System Requirement ................................................................................................................. 9
10.1. Software specification ........................................................................................................ 9
10.2. Hardware specification ...................................................................................................... 9
11. Feasibility Analysis ................................................................................................................... 9
11.1. Operational feasibility........................................................................................................ 9
11.2. Technical feasibility ........................................................................................................... 9
11.3. Economic feasibility ........................................................................................................ 10
11.4. Political feasibility ........................................................................................................... 10
11.5. Schedule feasibility .......................................................................................................... 10
CHAPTER TWO .......................................................................................................................... 11

Final Year Project CSIT 2009 E C(AMU). Page V

DESCRIPTION OF THE EXISTING SYSTEM ......................................................................... 11
2.1. Introduction to the Existing System ................................................................................... 11
2.2. Players of the Existing System .............................................................................................. 11
2.3. Major Functions/Activities in the Existing System ........................................................... 12
2.4. Business Rule ..................................................................................................................... 12
2.5. Bottleneck of the Existing System ..................................................................................... 13
2.5.1. Performance ................................................................................................................ 13
2.5.2. Security and Controls .................................................................................................. 13
2.5.3. Efficiency .................................................................................................................... 13
2.6. Practices to be preserved .................................................................................................... 13
2.7. Proposed Solution for Existing System ............................................................................. 13
2.8. Requirements of the Proposed System .............................................................................. 14
2.8.1. Functional Requirements ............................................................................................ 14
2.8.2. Non Functional Requirements .................................................................................... 15
CHAPTER THREE ...................................................................................................................... 16
SYSTEM ANALYSIS .................................................................................................................. 16
3.1. Introduction ........................................................................................................................ 16
3.2. System Requirement Specifications (SRS) ........................................................................ 16
3.2.1. Actor Identification ..................................................................................................... 16
3.3. Use Case Diagram.............................................................................................................. 16
3.4. Use Case Documentation ................................................................................................... 18
3.4.1. Use Case Documentation for Login ............................................................................ 18
3.4.2. Use Case Documentation for Collect Data ................................................................. 19
3.4.3. Use Case Documentation for Manage User Account ................................................. 20
3.4.4. Use Case Documentation for Fill Diagnosis Information........................................... 21
3.4.5. Use Case Documentation for Generate Report ........................................................... 22
3.4.6. Use Case Documentation for Follow Request Status ................................................. 23
3.4.7. Use Case Documentation for View Report ................................................................. 24
3.5. Sequence Diagrams ............................................................................................................ 25
3.5.1. Sequence Diagram for Login ...................................................................................... 25
3.5.2. Sequence Diagram for Data Collection ...................................................................... 26
3.5.3. Sequence Diagram for View Data .............................................................................. 27
3.5.4. Sequence Diagram for Submit Data ........................................................................... 28
3.5.5. Sequence Diagram for Manage User Account............................................................ 29

Final Year Project CSIT 2009 E C(AMU). Page VI

 3.5.6. Sequence Diagram for Generate Report ..................................................................... 30
3.5.7. Sequence Diagram for Follow Request Status............................................................ 31
3.6. Activity Diagram ............................................................................................................... 32
3.6.1. Activity Diagram for Login ........................................................................................ 32
3.6.2. Activity Diagram for Collect Data .............................................................................. 33
3.6.3. Activity Diagram for Manage User Account .............................................................. 34
3.6.4. Activity Diagram for Generate Report ....................................................................... 35
3.6.5. Activity Diagram for Approve Request ...................................................................... 36
3.6.6. Activity Diagram for View Report ............................................................................. 37
3.7. Class Diagram .................................................................................................................... 38
3.8. User Interface Prototype .................................................................................................... 39
CHAPTER FOUR ......................................................................................................................... 40
SYSTEM DESIGN ....................................................................................................................... 40
4.1. Introduction ........................................................................................................................ 40
4.2. Class Type Architecture ..................................................................................................... 40
4.3. Class Modeling .................................................................................................................. 42
4.3. State Chart Modeling ......................................................................................................... 43
4.3.1. State Chart for login: ................................................................................................... 43
4.3.2. State Chart diagram for Collect Data: ......................................................................... 44
4.3.3. State Chart diagram for manage user Account: .......................................................... 45
4.3.4. State chart diagram for Generate Report: ................................................................... 46
4.3.5. State Chart diagram for View Report: ........................................................................ 47
4.4. Collaboration Modeling ..................................................................................................... 48
4.4.1. Collaboration diagram for Login: ............................................................................... 48
4.4.2. Collaboration diagram for Collect Data:..................................................................... 49
4.4.3. Collaboration diagram for Fill Diagnosis information: .............................................. 50
4.4.4. Collaboration diagram for Approve user account:...................................................... 50
4.4.5. Collaboration diagram for Generate Report: .............................................................. 51
4.5. Component Modeling ........................................................................................................ 51
4.5.1. Component Diagram: .................................................................................................. 52
4.6. Deployment Modeling ....................................................................................................... 53
4.6.1. Deployment Diagram: ................................................................................................. 53
4.7 Persistence modeling .......................................................................................................... 54
4.8. User Interface design sample ............................................................................................. 55

Final Year Project CSIT 2009 E C(AMU). Page VII

 User interface for Home page ............................................................................................... 55
CHAPTER FIVE .......................................................................................................................... 58
IMPLEMENTATION AND TESTING ....................................................................................... 58
5.1 Introduction ......................................................................................................................... 58
5.2. Final Testing of the system ................................................................................................ 58
5.3. Training .............................................................................................................................. 59
5.4. Installation Process ............................................................................................................ 59
5.5. Hardware and software acquisitions .................................................................................. 59
CHAPTER SIX ............................................................................................................................. 60
CONCLUSION AND RECOMMENDATION ............................................................................ 60
Conclusion ................................................................................................................................ 60
Recommendations ..................................................................................................................... 61
Reference .................................................................................................................................. 62
Appendix ................................................................................................................................... 63

Final Year Project CSIT 2009 E C(AMU). Page VIII

List of Table
Table 1: Team composition ............................................................................................................ 3
Table 2: Gentt chart ........................................................................................................................ 4
Table 3: Use case documentation for login................................................................................... 18
Table 4: Use case documentation for collect data ........................................................................ 19
Table 5: Use case documentation for manage user count ............................................................. 20
Table 6: Use case documentation for fill diagnosis information .................................................. 21
Table 7: Use case documentation for generate report ................................................................... 22
Table 8: Use case documentation for follow request status .......................................................... 23
Table 9: Use case documentation for view report ........................................................................ 24
Table 10: Class type architecture description ............................................................................... 41

Final Year Project CSIT 2009 E C(AMU). Page IX

List of Figure
Figure 1: use case diagram ............................................................................................................ 17
Figure 2: Sequence diagram for login ........................................................................................... 25
Figure 3: Sequence diagram for data collect................................................................................. 26
Figure 4: Sequence diagram for view data ................................................................................... 27
Figure 5: Sequence diagram for submit data ................................................................................ 28
Figure 6: Sequence diagram for manage user account ................................................................. 29
Figure 7: Sequence diagram for generate report ........................................................................... 30
Figure 8: Sequence diagram for permission ................................................................................. 31
Figure 9: Activity diagram for login ............................................................................................. 32
Figure 10: Activity for collect data ............................................................................................... 33
Figure 11: Activity diagram for manage user account.................................................................. 34
Figure 12: Activity diagram for generate report ........................................................................... 35
Figure 13: Activity diagram for approve report ............................................................................ 36
Figure 14: Activity diagram for view report ................................................................................. 37
Figure 15: Class diagram .............................................................................................................. 38
Figure 16: User interface prototype .............................................................................................. 39
Figure 17: Class type architecture diagram .................................................................................. 40
Figure 18: Class modeling ............................................................................................................ 42
Figure 19: State chart diagram for login ....................................................................................... 43
Figure 20: State chart diagram for collect data ............................................................................. 44
Figure 21: State chart diagram for manage user account .............................................................. 45
Figure 22: State chart diagram for generate report ....................................................................... 46
Figure 23: State chart diagram for view report ............................................................................. 47
Figure 24: Collaboretion diagram for login .................................................................................. 48
Figure 25: Collaboration diagram for collect data ........................................................................ 49
Figure 26: Collaboration diagram for fill diagnosis information.................................................. 50
Figure 27: Collaboration diagram for approve user account ........................................................ 50
Figure 28: Collaboration diagram for generate report .................................................................. 51
Figure 29: Component diagram .................................................................................................... 52
Figure 30: Deployment diagram ................................................................................................... 53

Final Year Project CSIT 2009 E C(AMU). Page X

Figure 31: Persistence modeling diagram ..................................................................................... 54
Figure 32:Home page .................................................................................................................... 55
Figure 33:Login ............................................................................................................................ 56
Figure 34:Researcher page ............................................................................................................ 57

Final Year Project CSIT 2009 E C(AMU). Page XI

 CHAPTER ONE
INTRODUCTION
1. Introduction
Now days it is important to avoid paper based data collection by using computerized system.
This computerized system decrease the load of employees by providing simple mechanism to
record data, save, prepare dataset and generate reports for researchers about patients’ health
status information.
Preparation of dataset and Report Generation process give’s important service for the
organization when hospital employees want to get data from dataset. Through the project by
“Collecting, Synchronization, Preparing Dataset and Report Generation management
system for Arba Minch Hospital” is easy. This project is used to simplify tasks for Hospital
physicians, Lab technicians and card officers by minimizing very complicated and tedious tasks
that will be done manually, by using a computerized system.
When the numbers of Patients are increasing recording and storing data manually and giving
information service for researchers and generating reports will be very difficult task. So in order
to solve this problem we apply object oriented system analysis and develop strategy to automate
this business process.

1.1. Background of Organization

Arba Minch Hospital is found in South Nation and Nationalities of people region particularly in
GamoGofa zone, established in 1961 EC. It is basically acting like a referral hospital for a large
area around it. According to the data collected by interviewing the hospital manager, this hospital
serves approximately about 2,007,473 people and actually sees over 150,000 patients per year.

Even though they serve so many patients, they only have 9 specialists and also have only one
ambulance. They have 3 other surgeon and 2 gynecologists, and the last remaining surgeon is
planning to leave soon. Though they have 5 operating rooms, there is only one especial machine.

The hospital was originally built to house 50 beds but has now expanded to 350 beds. Yet, they
only have one working autoclave, one laundry machine, one section machine and one oxygen
concentrator. Generally AM hospital has 576 man powers working currently.

Final Year Project CSIT 2009 E C(AMU). Page 1

1.2 .Background of the Project
The current system of Arba Minch Hospital data collection, dataset preparation and reporting
done using paper based system, however the users, researchers and the Employees numbers is
increasing rapidly. It is very difficult to serve them by using current system. The Patients must
bring card from card section to register and the card section attaché the file with the card and
give to the doctor then the Doctor asks the Patient what he/she feel and record the symptom on
the form and forward the symptom to the laboratory section or others. The laboratory section test
for symptom by taking samples from the patient and they will send their finding to the doctor
and finally the Doctor will subscribe the medicine and after recording his subscriptions on the
patients record he/she will send the record to the card room, then the data will be stored over
there. If a researcher needs report or data for his/her research they will be requested to take the
paper based data and prepare their own dataset according to their need.
In this proposed Project we want to solve this problem by developing a robust and simple data
set preparer and reporting information management system.

Final Year Project CSIT 2009 E C(AMU). Page 2

 2. Team Composition
Table 1: Team composition

Project title Preparation of Dataset and Report Generation

Student Name Id Number Email Responsibility
Endalkachew RAMIT/1660/06 [email protected] Manager & Programmer
Yalew
NakachewAcham RAMIT/1503/06 [email protected] Programmer& Designer
EfrataAlem RAMIT/1649]/06 [email protected] System Analyst & Data
collector
RehmatBeshir RAMIT/1806/06 [email protected] Designer & System
Analyst
TsegenetLema RAMIT/1941/06 [email protected] Data collector &Time
Keeper
Demoze Haile RAMIT/1365/05 [email protected] Data collector &Time
Keeper
Date December 2016

Advisor Alazar Baharu

Final Year Project CSIT 2009 E C(AMU). Page 3

3. Task and Schedule
The proposed system will be completed in time by the help of our advisor, internal motivation,
availability of budget and development tool. The time schedule of the proposed project
development has been given in the following Gantt chart as follow
Gantt chart
Table 2: Gentt chart

Project Schedule

S.No Phases 1st 2nd 3rd 4th 5th 6th

Quarter Quarter Quarter Quarter Quarter Quarter
1stDec- 20thDec- 20thJan- 19thMar- 20thMay- Jun15
12thDec 17thJan 18thMar 19thMay 1stJun
1 Project proposal
2 Collect the data
about existing
design
3 Analyze the
existing design
4 Design the new
System
5 Implement the
design and
testing
6 Project Closure

Final Year Project CSIT 2009 E C(AMU). Page 4

4. Problem Statement
The existing Dataset and Reporting system is functioning using paper based system. This paper
based system lead to problems like, do not give clear information for researchers because of
illegible hand right and some abbreviate words, need manpower for arranging the data and
organization of data, resources consuming like paper and printer, search-ability and getting data
takes long time when researchers and doctors want data about the patients, the data may be lose
completely when emergency happen. Due to the above facts researches done in this topic are too
little because of the above stated problems. In addition to this the institution reporting process
will take a long time to generate fact based report to external information requestors.

5. Detailed Objectives of the project

5.1. General objectives

The main objective of this project is to develop an information system to automate data
collection, data set preparation and reporting process of AMH.

5.2. Specific objective

In order to achieve the general objective, the following specific objectives are needed.
 Understand the paper based process.
 Review the current system to identify the problems and flaws.
 Identify functional and nonfunctional requirements.
 Propose possible solutions to solve the discovered problems.
 Model the new system using object oriented methodologies.
 Preparing dataset and enabling the system for generating reports.
 Designing form to record data related to health status of patients.
 Study about the implementation of ODK collect, ODK aggregate and XLS form
generator.
 Finally implement and test the new system.

Final Year Project CSIT 2009 E C(AMU). Page 5

6 .Scope of the Project

6.1. In scope
The scope of this project is going to be developing a system that can help AMH to collect, to
prepare dataset and reporting system.
6.2. Out scope
This system will not automate each transaction and business processes available at AMH rather
than the business process explained in the in scope.
7. Significance of the Project
The significances of this project are:-

 To reduce data redundancy.

 To extract data easily.
 Researchers can get clear and more organized reports when they need for some
information.
 To avoid the problems of delaying times especially for researchers.
 To provide immediate response to the users.
 To reduce wastage of the man powers, resource and time
 It is more secure.
8. Target Beneficiaries of the System
There are different bodies that will be benefited from this system. The main beneficiaries of this
system include:
 Arba Minch Hospital.
 Researcher

Final Year Project CSIT 2009 E C(AMU). Page 6

9. Methodology
In order to develop the proposed system we are going to use different data collection,
requirement analysis, System design and Implementation and testing methods. These
methods are described as follows.

9.1. Data collection methodology

9.1 .1 Primary Data collection Methodology used

To collect primary data that can help us to identify facts about the existing system we will use
interviews and participatory observation.

 Interviews: This is one of the methods that will be used to collection data about the
AMH existing system. We will conduct the formal interview by preparing questions
about the existing system and we will interview doctors, Laboratory technicians.
 Participatory Observation: This is another type primary data collection methodology
used to collect observatory data. We will observe the system as observers as well as a
user to understand the existing system.
9.1.2. Secondary Data collection
To collect secondary data to support the primary collected data we will use document analysis.
 Documentary analysis:-We use document analysis to gathered information from
different types of document available and used in the current system. We will collect
different usefully documents first and we will analyze it to find some useful information
that can help us to develop proposed system.

9.2. Selection of application development strategy

 OOSAD: Object-oriented analysis and design (OOSAD) is a popular technical
approach for analyzing and designing a system by applying the object oriented paradigm
and visual modeling functional and non functional requirements throughout the
development of the system to foster better stakeholder communication and data or
information quality [1].

Final Year Project CSIT 2009 E C(AMU). Page 7

9.3. Selection of application development tools
 Server application:
o Xampp
 Programming language:
o Server side script
 Java script
 PHP
o Client server scripts
 HTML
 CSS
 Code Editor used:
o Dream waver
 Offline data collection and synchronization tolls used:
o ODK collect and application
o ODK aggregate
 Form generation tool:
o XLS form generator
 Word processor:
o MS word
 UML diagram Design tool:
o Edraw Max
o Visio

9.4. System Implementation and Testing Methodology

 Parallel system implementation methodology:-We use parallel system implementation
methodology for both the old and new systems operate side-by-side for a period of time.
Both are maintained and kept up-to-date so that in the event of the failure of the new
system, the organization can fall back on the old one [2].
 Unit testing: -The goal of unit testing to segregate each part of the program and test that
the individual parts are working correctly [3].

Final Year Project CSIT 2009 E C(AMU). Page 8

10. System Requirement

10.1. Software specification

The OS used to host the application and the browsers that will be compatible with the application
we are going to develop are listed as follows:
 OS used:
o Windows 7
o Android
o Linux
 Browser software used:
o Internet Explorer
o Google Chrome
o Opera
o Baidu Browser

10.2. Hardware specification

The minimum hardware specifications used to run the system after development is:
 512 MB Minimum RAM
 5 GB Minimum hard drive

11. Feasibility Analysis

11.1. Operational feasibility

Our project creates a good environment for users. The firs assumption here is now a day's
everyone is capable of using computer and smart phones. Since our system will use computers
and smart phones with little bit of training given the system will be fully functional. In addition
to this the systems operations will be built to make them operationally easy and simple.

11.2. Technical feasibility

The proposed system can be implementing by using simple and clear technology and the staff
will be trained to get enough experience on the system. In the other hand we have also the
technical capacity, toll and skill to develop the application. So we can say the proposed system is
technically feasible.

Final Year Project CSIT 2009 E C(AMU). Page 9

11.3. Economic feasibility
Economic feasibility identifies the financial benefit and cost associated with the proposed
project. The cost needed for this project looks like big at initial time, however in future we can
see it will pay back and we can save a lot out of it. Due to this reasons we can say the proposed
system is economically feasible.

11.4. Political feasibility

The system is free from any legal and contractual risks.

11.5. Schedule feasibility

This proposed project will be developed in seven months. This fact has been brought in to
ground after we have analyzed to identify problem of the existing system. In addition to this we
are going to use different tools and technologies that can help us develop our application within
the planned data and time. We can say that with the help of above stated facts our project is
schedule feasible and will be completed at the stated data and time.

Final Year Project CSIT 2009 E C(AMU). Page 10

 CHAPTER TWO
DESCRIPTION OF THE EXISTING SYSTEM

2.1. Introduction to the Existing System

This chapter describes about the existing system for collecting patient data and generates report
for researchers are paper based. In addition to this the current system is not well secure. The
system is venerable for many natural and human disasters in different way. Because of this the
organization may lose its data. When they collect data about the patient still they use paper based
method. This method is exposing the data to security problem. It also needs long process to give
service for users. The information that is collected in different period must arrange in catalogue
form and stored in card section. This types of data collection and arrangement needs skilled
manpower (HIT) and resource (paper, printer…).When we see about the process of generating
report for researchers it takes long process starting from requesting permission up to getting
generated report. Researcher must be fulfilling some rules of the organization and procedures to
get approval permission from manager. Generally based on the above bottleneck of the system
we initiate to do computer based Preparation of Dataset and Report Generation Management
System.
2.2. Players of the Existing System
The actors in the current system are:-
 Doctor: - who check the Patient what he/she feel and record the symptom on the form
and forward the symptom to the laboratory section.
 Pharmacy:-someone who Prepares medications by reviewing and interpreting physician
orders and Controls medications by monitoring drug therapies.
 Laboratory Technicians: -Laboratory Technicians are technician who performs the
practical hands-on work in laboratories based on the doctor information.
 (Health IT)HIT:-Professionals whose responsibility is enter data that collect from
Doctors or any other means and they extract these data when the researcher needs
information for research purpose.
 Nurse: -who treat the Patient what he/she feel and record the symptom and forward to
the laboratory section. Most of time Nurses can work like Doctor.
 Researcher: - Someone who collect data about the patient for research purpose.

Final Year Project CSIT 2009 E C(AMU). Page 11

  Patient: -are users who get service from this hospital.
 Manager:-someone who manage all activity in the organization. Such as giving
permission for researchers, managing users and employees.

2.3. Major Functions/Activities in the Existing System

The following section will summarize the function of existing system with their input, process
and output.
Manage Data
 Input: - valid data.
 Process: - collect and organize data.
 Output: - Generate report for researchers and others.
Record patient information
 Input: - Patient detail information.
 Process:-Ask patient about their information.
 Output: - Store information in card section.

2.4. Business Rule

The business rule of the existing system is deepened on manual based activity for giving service
and collecting data for patients. Patients and researchers get service after long process. Patients
before getting the treatment they must bring card from card section to register and the card
section attaché the file with the card and give to the doctor then the Doctor asks the Patient what
he/she feel and record the information on the form and forward the symptom to the laboratory
section. The laboratory section test for symptom by taking samples from the patient based on the
doctor’s written symptom and they will send their finding to the doctor and then the Doctor will
write the description for patient. Finally the doctor collects the data and send to the card room. In
the card section HIT receive the collected data and put in the catalogue form.HIT can control all
activity of data entry and extra. Those stored data uses for research purpose. If a researchers need
report or data from the hospital they must have valid ethical clearance and propose the request to
the manager. The manager receive the request and checking the clearance whether the clearance
valid or not. If the clearance is legal the manager gives the permission and direct to HIT.HIT also
checks the permission and give the report to the researcher.

Final Year Project CSIT 2009 E C(AMU). Page 12

2.5. Bottleneck of the Existing System

2.5.1. Performance
The performance of existing system is less, because the response time is not fast. That means the
response time have direct relation with performance.

2.5.2. Security and Controls

Since all the data about the patients associated within the process are recorded and stored
manually, faces many security problems. The information or data may be stealing by clerk or
other, destroying by fire. So the security that the process provides is not good. The system
shouldn’t provide sufficient protection for accessing and manipulation of the data’s associated
with the system. Therefore, it is not easily protected and control.

2.5.3. Efficiency
The efficiency of the current system is insufficient, because of response time.

2.6. Practices to be preserved

The existing system provides information about the patients by generating report which collected
before by using manual system. This is good practice that we want to preserve on the new
system. However, the main goal of the project is preparing dataset and generating report with
computer expert system and a future technology by reducing the problems of the current system.
The new system will provide good services for hospital stack holders especially for physicians,
nurses, researcher, laboratory technicians etc.

2.7. Proposed Solution for Existing System

 The solution of the problems is solving by developing simple and fast system by
shorten the process when giving service for users. Means the response time is short.
 The system is access by anywhere using computer and android phone that integrated
with mainly focuses offline.
 The new system will avoid the problems of delaying times especially for researchers.

 The Doctors and other nurses and laboratory technician collect data offline, save and
submit into dataset.

Final Year Project CSIT 2009 E C(AMU). Page 13

  The wastage of the man powers, resource and time will be avoided.
 Generating clear and more organized reports for Doctors about the previous history of
patients if she/he got service before and researchers.
 Developed system security must be hard.
2.8. Requirements of the Proposed System

2.8.1. Functional Requirements

The functionally of our proposed system requires process, Input related, Storage related
requirements, Output related and other specific functionality that define what a system is
supposed to accomplish.
Process requirements
 The system enables the respected body to collect data or detail information about each
patient and stores that information permanently in the dataset.
 The HIT or Manager enters patient’s Id number in the search field and generates report
from dataset.
 When the patient didn’t register the system generate new registration form.
Input related requirements
 Detail information about each user should be entered in the dataset by the doctors.
 When the new patient gets service, their personal information should be entered to the
dataset.
Output related requirement
 The system shall provide immediate response to the users.
 The system shall store patient information in the dataset.
Storage related requirements
The system shall store all the data related with all the tasks performed into a dataset.

Final Year Project CSIT 2009 E C(AMU). Page 14

2.8.2. Non Functional Requirements
Non-Functionality of proposed system requires performance, User Interface, Security and access
permissions, and other specific functionality that define what a system is supposed to accomplish
many tasks.
Performance
 Our proposed system shall provide every time to accesses for the users.
 The proposed system runs on many operating systems.
 After the user login and request what he/she wants the response time is fast.
User Interface
 Users easily navigate and access our system by using user interface designed.
 The system must be compatible with many operating system environment and user
friendly
Security and Access Permission
 Our system is secured; means unauthorized body cannot access the system and system
resources.
 The system shall permit the doctors to edit patient’s information.
Usability
Preparation of Dataset and Generating Report Management System provide service with smart
phones and mouse and keyboard navigation.
Availability
Preparation of Dataset and Generating Report Management System is available every time for
the application of the users.
Supportability
The Preparation of Dataset and Generating Report Management System application should be
supportable in the current equipment such as computers, monitors and smart mobile phone.

Final Year Project CSIT 2009 E C(AMU). Page 15

 CHAPTER THREE
SYSTEM ANALYSIS

3.1. Introduction
The project development in a team used an object oriented system development methodology. In
this development methodology we analyze the proposed system by applying the object oriented
paradigm and visual modeling functional and non functional requirements throughout the
development of the system to foster better stakeholder communication and data or information
quality. Because the Object oriented system development approach gives easier and natural way
to break down problems into simple, small and manageable components so that it reduces the
vague appearance of the big problem. Moreover, it is predominately used and popular method in
present software development trend.
The major activities described in this chapter are Constructing a use case model ,Documenting
the use case course of events, constructing sequence and activity diagram analysis level class
diagram and user proto type about the proposed system.
3.2. System Requirement Specifications (SRS)

3.2.1. Actor Identification

HIT: - A special user of the system who can manage the system setup access right for other
users. And also can update the patient’s information from the dataset.
Doctor: - Someone who can access the system and collect data about the patients like doctor.
Laboratory Technicians:-the professional who check the diagnosis experimentally.
Researchers: - Someone who can access system and generate the report for his/her research to
get information.
Manager:-She/he visit the dataset and evaluate the collected data and manage all users.

3.3. Use Case Diagram

A use case diagram is simplest representation of a user's interaction with the system and
depicting the specifications of a use case. A use case diagram can portray the different types of
users of a system and the various ways that they interact with the system.

Final Year Project CSIT 2009 E C(AMU). Page 16

 Figure 1: use case diagram

Final Year Project CSIT 2009 E C(AMU). Page 17

3.4. Use Case Documentation

3.4.1. Use Case Documentation for Login

Table 3: Use case documentation for login

Use case name Login

Use case number UC1
Actors Doctor, Laboratory Technician, HIT and Manager
Description The authentication for authorized users in the system and deliver them the
right to visit their specified privileged page.
Pre-condition The users must have user name and password.
Basic course of Actors action systems response
action Step1: Doctor, Laboratory Step 2: System display login page.
Technician, HIT and Step 4: System checks the validity of
Manager. Initiate to login. username and password and also checks for
Step 3: User enter user authentication and authorization.
name and password. Step5:If the user is authenticated &
authorized on the system then user privilege
to access only system privileged pages for
that user.

Alternate courses of Step 4: If the user’s entry (user name and Password) is not validated and
action verified the system displays “invalid username or password” message and
return to step 2.
Post condition User able to access the required information i.e.user is now logged into
the system.

Final Year Project CSIT 2009 E C(AMU). Page 18

3.4.2. Use Case Documentation for Collect Data
Table 4: Use case documentation for collect data

Use case name Collect data

Use case number UC2
Actors Doctor, and Lab-Technician
Description Collect patient information during treatment.

Pre-condition They must be login in to the user interface before recording data.
Basic course of Actors action systems response
action
Step1: The user’s login into the Step 2: The system displays the
system by entering correct user form what we fill from service page
name and password. by clicking collect data button.
Step 3: Doctor or nurse record
patient data.
Step 4: Then save recorded data.

Alternate courses of When the recorded data is not valid they can update or delete.
action
Post condition Submit all saved data to the data set.

Final Year Project CSIT 2009 E C(AMU). Page 19

3.4.3. Use Case Documentation for Manage User Account
Table 5: Use case documentation for manage user count

Use case name Manage User Account

Use case number UC3
Actors HIT
Description Manage all user account.

Pre-condition They must be login in to the system.

Basic course of Actors action systems response
action Step1: HIT login into the admin Step 2: The system displays admin
page by entering correct user name page.
and password.
Step 3:HIT can create, delete
And update, user accounts.

Alternate courses of When the created or deleted account is invalid HIT can update.
action
Post condition Can create, delete and update user accounts.

Final Year Project CSIT 2009 E C(AMU). Page 20

 3.4.4. Use Case Documentation for Fill Diagnosis Information
Table 6: Use case documentation for fill diagnosis information

Use case name Fill Diagnosis Information

Use case number UC4
Actor Laboratory Technician
Description It describes the process of check the diagnosis and record the patient
information.
Pre-condition Laboratory Technician must be login before recording information.
Basic course of Actors action Systems response
action
Step1: The user’s login into the Step 2: The system displays the form what
system by entering correct user we fill from service page by clicking
name and password. collect data button.
Step3: Laboratory Technician
record patient data.
Step 4: Save recorded data.
.

Alternate courses When the recorded data is not valid they can update or delete.
of action
Post condition Submit all saved data to the data set.

Final Year Project CSIT 2009 E C(AMU). Page 21

 3.4.5. Use Case Documentation for Generate Report
Table 7: Use case documentation for generate report

Use case name Generate report

Use case number UC5
Actor HIT
Description Generates a report of all activities undertaken in a specified period.
Pre-condition HIT should have an accountant has to be remembering user name and password
to login the system.
Basic course of Actors action Systems response
action
Step1: HIT initiate to login Step 2: System display login page.
Step3: HIT enters user name and Step4: System checks the validity of user
password and click login button name and password and also checks for
Step6:-Generate report. authentication and authorization.
-Invalid user name or password system
display error message
Step5: System display reports generate
page.
Alternate courses Step 4: invalid user name or password return to step2.
of action
Post condition HIT generated report

Final Year Project CSIT 2009 E C(AMU). Page 22

 3.4.6. Use Case Documentation for Follow Request Status
Table 8: Use case documentation for follow request status

Use case name

Follow Request Status
Use case number UC6
Actor
Researcher
Description It describes the process following request status to get permission and access the
report.
Pre-condition The researcher must have legal ethical clearance.
Basic course of Actors action Systems response
action
Step1: Researcher visits the hospital site and send Step3: The system
request. displays the researcher
Step2: The Manager login and view request. information.
Step4: Manager calls the researcher by phone. Step9: System generates the
Step5: Researcher come and having ethical report from dataset.
clearance.
Step6: The manager views the clearance and
approves it.
Step7: Manager directs the researcher to HIT.
Step 8: HIT view the approved permission and
initiate to generate report and enter the correct
information and click generate button.
Alternate courses If the researcher gives the invalid clearance the manager rejects it.
of action
Post condition The Manager approve the request of researcher and give permission .HIT
generate the report and give to the researcher.

Final Year Project CSIT 2009 E C(AMU). Page 23

 3.4.7. Use Case Documentation for View Report
Table 9: Use case documentation for view report

Use case name View Report

Use case number UC7

Actor HIT and Manager

Description It describes the process of viewing patient information for different purpose.

Pre-condition HIT and Manager should have an account and has to be remembering user name
and password to login the system.

Basic course of Actors action Systems response

action
Step1:Iinitiate to login Step 2: System display login page.

Step3: Enters user name and Step4: System checks the validity of user
password and click login button. name and password and also checks for

Step6: HIT and Manager view authentication and authorization.

patient information. Invalid user name or password system
display error message

Step5: System display patient report.

Alternate courses Step 4: invalid user name or password return to step2.

of action

Post condition View patient in information in the system.

Final Year Project CSIT 2009 E C(AMU). Page 24

3.5. Sequence Diagrams
Sequence diagram of our system illustrate the object that participate in the use case and the
message that passes between them over time for one use case

3.5.1. Sequence Diagram for Login

Figure 2: Sequence diagram for login

Final Year Project CSIT 2009 E C(AMU). Page 25

3.5.2. Sequence Diagram for Data Collection

Figure 3: Sequence diagram for data collect

Final Year Project CSIT 2009 E C(AMU). Page 26

3.5.3. Sequence Diagram for View Data

Figure 4: Sequence diagram for view data

Final Year Project CSIT 2009 E C(AMU). Page 27

3.5.4. Sequence Diagram for Submit Data

Figure 5: Sequence diagram for submit data

Final Year Project CSIT 2009 E C(AMU). Page 28

3.5.5. Sequence Diagram for Manage User Account

Figure 6: Sequence diagram for manage user account

Final Year Project CSIT 2009 E C(AMU). Page 29

3.5.6. Sequence Diagram for Generate Report

Figure 7: Sequence diagram for generate report

Final Year Project CSIT 2009 E C(AMU). Page 30

3.5.7. Sequence Diagram for Follow Request Status

Figure 8: Sequence diagram for permission

Final Year Project CSIT 2009 E C(AMU). Page 31

3.6. Activity Diagram
Activity diagram is basically a flow chart to represent the flow from one activity to another
activity. The activity can be described as an operation of the system. So the control flow is drawn
from one operation to another.

3.6.1. Activity Diagram for Login

Figure 9: Activity diagram for login

Final Year Project CSIT 2009 E C(AMU). Page 32

3.6.2. Activity Diagram for Collect Data

Figure 10: Activity for collect data

Final Year Project CSIT 2009 E C(AMU). Page 33

3.6.3. Activity Diagram for Manage User Account

Figure 11: Activity diagram for manage user account

Final Year Project CSIT 2009 E C(AMU). Page 34

3.6.4. Activity Diagram for Generate Report

Figure 12: Activity diagram for generate report

Final Year Project CSIT 2009 E C(AMU). Page 35

3.6.5. Activity Diagram for Approve Request

Figure 13: Activity diagram for approve report

Final Year Project CSIT 2009 E C(AMU). Page 36

3.6.6. Activity Diagram for View Report

Figure 14: Activity diagram for view report

Final Year Project CSIT 2009 E C(AMU). Page 37

3.7. Class Diagram

Figure 15: Class diagram

Final Year Project CSIT 2009 E C(AMU). Page 38

3.8. User Interface Prototype

Figure 16: User interface prototype

Final Year Project CSIT 2009 E C(AMU). Page 39

 CHAPTER FOUR
SYSTEM DESIGN

4.1. Introduction
In this chapter we will transform the analysis model to 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. The result of system design is a model that
includes a clear description of each of these strategies, subsystem decomposition, and a UML
deployment diagram representing the hardware/software mapping of the system. The hardware
our system uses are:-Android phones Tablets, computers and server. The software’s used are
ODK collect ODK aggregate; XLSForm generator and java run time environment (JRE) and
Apache tomcat.

4.2. Class Type Architecture

The class type architecture describes how the data set Preparation and reporting system works
and interacts with the user by dividing work into different layers. A layered approach is used to
design the system. These layers are interface layer, process layer, domain layer, persistent layer
And system layer..

Figure 17: Class type architecture diagram

Final Year Project CSIT 2009 E C(AMU). Page 40

 Class Type Architecture Description

Table 10: Class type architecture description

 User interface layer The user interface layer represents the front end of the Web Client
and Mobile interface and contains the actual GUI elements that users
view and click.
 Process layer This Layer implements business logic that involves
collaborating with several domain classes or even other
process classes.
 Domain layer This layer is used to transfer data from application layer or
presentation layer to data layer. This layer is also used when
a class variables are declared corresponding to the fields of
the database which can be required for the application and
make the properties. So that, the team can gets or sets the
data using these properties into the variables.
 Persistence layer This layer encapsulates the capability to store, retrieve, and
delete objects/data permanently without revealing details of
the underlying storage technology. This layer is also a class
to get or set data to the database queries back and forth.
 System layer This Layer provides operating-system-specific functionality for our
applications, isolating our software from the operating system (OS)
by wrapping OS-specific features, increasing the portability of our
application

Final Year Project CSIT 2009 E C(AMU). Page 41

4.3. Class Modeling
Class diagram are the basis of object oriented analysis and design. A class diagram shows the
classes of the system, their interrelationships (including, inheritance, aggregation and
association) and the operations and attributes of the classes. Class diagrams are used for wide
variety of purposes, including both conceptual/domain modeling and detailed design modeling.

Figure 18: Class modeling

Final Year Project CSIT 2009 E C(AMU). Page 42

4.3. State Chart Modeling
The state chart diagram has been used to show the change of an object through time. Based upon
events that occur, the state diagram shows how the object changes from start to end. The state of
different objects in our system has been illustrated in the following diagrams

4.3.1. State Chart for login:

Figure 19: State chart diagram for login

Final Year Project CSIT 2009 E C(AMU). Page 43

4.3.2. State Chart diagram for Collect Data:

Figure 20: State chart diagram for collect data

Final Year Project CSIT 2009 E C(AMU). Page 44

4.3.3. State Chart diagram for manage user Account:

Figure 21: State chart diagram for manage user account

Final Year Project CSIT 2009 E C(AMU). Page 45

4.3.4. State chart diagram for Generate Report:

Figure 22: State chart diagram for generate report

Final Year Project CSIT 2009 E C(AMU). Page 46

4.3.5. State Chart diagram for View Report:

Figure 23: State chart diagram for view report

Final Year Project CSIT 2009 E C(AMU). Page 47

4.4. Collaboration Modeling

A collaboration diagram resembles a flowchart that portrays the roles, functionality and behavior
of individual objects as well as the overall operation of the system in real time. To show the
collaboration of different objects in our system collaboration modeling diagram has been used.

4.4.1. Collaboration diagram for Login:

Figure 24: Collaboration diagram for login

Final Year Project CSIT 2009 E C(AMU). Page 48

4.4.2. Collaboration diagram for Collect Data:

Figure 25: Collaboration diagram for collect data

Final Year Project CSIT 2009 E C(AMU). Page 49

4.4.3. Collaboration diagram for Fill Diagnosis information:

Figure 26: Collaboration diagram for fill diagnosis information

4.4.4. Collaboration diagram for Approve user account:

Figure 27: Collaboration diagram for approve user account

Final Year Project CSIT 2009 E C(AMU). Page 50

4.4.5. Collaboration diagram for Generate Report:

Figure 28: Collaboration diagram for generate report

4.5. Component Modeling

The component model illustrates the software components that will be used to build our system.
We use component diagram to model the physical implementation of the system and high level
software components and their interfaces. We use the following software components for our
project:-
 XLSForms:is a tool to simplify the creation of data collection forms. Forms can be
designed with Excel by keeping the rules and regulations then the xlsx file will be
converted into .xml file by using xlsform application.
 ODK-Collect: is an droid application installed on android smart devises which helps us
to download xlsform form the server, render them, allow to enter data, help us to save
filled data and synchronize the completed form data with the server .
 ODK-Aggregate: provide functionality to upload, manage, collect and synchronize
forms

Final Year Project CSIT 2009 E C(AMU). Page 51

4.5.1. Component Diagram:

Figure 29: Component diagram

Final Year Project CSIT 2009 E C(AMU). Page 52

4.6. Deployment Modeling
UML deployment diagram show how software components are physically deployed on
processors. We have used Deployment modeling to show the our system deployment Process at
the time of system deployment.

4.6.1. Deployment Diagram:

Figure 30: Deployment diagram

Final Year Project CSIT 2009 E C(AMU). Page 53

 4.7 Persistence modeling
Persistence modeling is used to communicate the design of the database, usually the data
base to both the users and the developers. It is also used to describe the persistence data
aspect of the system. The following diagram indicates the persistence diagram of the system.

Figure 31: Persistence modeling diagram

Final Year Project CSIT 2009 E C(AMU). Page 54

4.8. User Interface design sample
User interface for Home page

Figure 32: Home page

Final Year Project CSIT 2009 E C(AMU). Page 55

User interface for Login

Figure 33: Login

Final Year Project CSIT 2009 E C(AMU). Page 56

User interface for Researcher

Figure 34: Researcher page

Final Year Project CSIT 2009 E C(AMU). Page 57

 CHAPTER FIVE
IMPLEMENTATION AND TESTING
5.1 Introduction

In this phase what the group members have done is turning the physical design specification into
working computer code and also application, and then the code is tested until most of the errors
have been detected and corrected. User sites are prepared for new system and user must come
totally on the new system rather than the existing one to get there work done. There are some
managerial activities in this, coding, testing, and installation.
5.2. Final Testing of the system
Blackboxtesting: -To test our system, the tester may use black box testing, if he/she has not
enough time to check internal modules or codes. By looking only input /output or user interface,
the tester can test our systems functionalities without looking the internal code. We used this
testing technique for the following reasons:-

 This testing type is more effective on larger units of code

 Tester needs no knowledge of implementation, including specific programming
languages
 Tester and programmer are independent of each other
 Tests are done from a user's point of view

White box testing: -

In this type of testing, skilled man in different programming languages tries to test the logic of
our system. If the person who tests the system is not skilled, it is difficult to understand our
systems functionality. If any failures occur while testing the system in all of the above testing
methods, the team will take immediate correction where this fault occurred before jumping to
next work. So, that it will meet the goal.

Final Year Project CSIT 2009 E C(AMU). Page 58

5.3. Training
During the deployment of the system, the project group members will give short time training for
the system administrators and other employees explaining how the system works and in what
way they can manage the system developed.

5.4. Installation Process

Once the system has been published, the user can start and access his/her authorized page with
proper authentication and authorization processes.
5.5. Hardware and software acquisitions
For the project implementation; the following Software and hardware tools are used.
5.5.1 Hardware Tools:-
 Server: for connection to the client computer(to host the system)
 Computers
 Network connection
 Printer: For printing Documentation
5.5.2 Software Tools
For the System implementation the following software’s are used.
 Notepad++
 Mysql database server
 Xampp
 Android sdk tools
 Eclipse bundle

Final Year Project CSIT 2009 E C(AMU). Page 59

 CHAPTER SIX
CONCLUSION AND RECOMMENDATION

Conclusion
Until now we have been doing the documentation of preparations of data set and report
generation and mainly the implementation of this system. In the documentation we have seen the
introductory sections about the overall system we have also done the detail analysis and the
design of the system that we developed and implemented in the final year project. We summarize
the progress with respect to the main objectives of the project. We conclude that the following
perceptional views as we have done the project throughout this year.
PDRG system supports to manage patient information and generate report for Arba Minch
hospital. Moreover the system can also be used for Researchers can get clear and more
organized reports, generate report and perform management activity. The new system will
changes the current manual system of AMH preparation of dataset to computerized manner. It is
more flexible and secure when it compared within the current system. Our project solves the
current problem of Arba hospital.

Final Year Project CSIT 2009 E C(AMU). Page 60

Recommendations
According to scope of our project the team develops PDRG system .Because of the time constraint we
cannot do beyond to our scopes, but in the future the team believes that this system can be fully
operational by having enough time and full information. Next, the team would recommend that further
work should be done on the system in order to make the system fully functional like official website.

Final Year Project CSIT 2009 E C(AMU). Page 61

Reference

 Some previous done documents

[1] https://en.wikipedia.org/wiki/Object-oriented_analysis_and_design
[2] https://www.dlsweb.rmit.edu.au/toolbox/busadmin/topics/topic13/t13_02.htm
[3] https://en.wikipedia.org/wiki/Unit_testing#Techniques
[4] https://www.tutorialspoint.com/uml/uml_activity_diagram.htm
[5] https://en.wikipedia.org/wiki/Sequence_diagram
[6] https://en.wikipedia.org/wiki/Class_diagram

Final Year Project CSIT 2009 E C(AMU). Page 62

Appendix
Coding

<?php
session_start();
include("config/config.php");
?>
<?php
if (isset($_POST['login'])
//session start();
$username =$_POST['username'];
$password=$_POST['password'];
$_SESSION['username']=$username;
//$ecode = base64_encode ($password);

Final Year Project CSIT 2009 E C(AMU). Page 63

$query = "SELECT * FROM account1 WHERE username='$username' AND
password='$password' "; $result = mysql_query($query)or die(mysql_error());
$num_row = mysql_num_rows($result);
$row=mysql_fetch_array($result);
$row_id=$row['username'];
$user_type =$row["account_type"];
$row=mysql_fetch_array($result);
if ($num_row> 0 ) {
if ($user type=="HIT"){
header ('location: HIT/HIT.php');
$_SESSION ['id'] =$row_id;
}
else if($user type=="Manager"){
header ('location:Manager.php ');
$_SESSION['id']=$row_id; }
else if($user_type=="Doctor"){
header('location:Doctor.php');
$_SESSION['id']=$row_id;
}
else if($user type=="Lab-Technician"){
header('location:lab_techn.php');
$_SESSION ['id']=$row_id
}
}
else {
//header('location:access_denied.php');
echo header("Location: login.php?action=error");

Final Year Project CSIT 2009 E C(AMU). Page 64

}}
?>
<script language="JavaScript">
function check ()
{
if(document.getElementById("username").value =="")
{
alert('Please Enter user name !!');
document.getElementById("username").focus();
return false;
}
if(document.getElementById("password").value =="")
{
alert('Please Enter password !!');
document.getElementById("password").focus();
return false;
}
if(document.getElementById("account_type").value == "Please Choose"){
alert ('please choose your account type');
document.getElementById ("account type").focus();
return false;
}
if(isUcase(document.getElementById("username").value) == false ||
isUcase(document.getElementById("password").value) == false)
{
alert("Username and Password not match!!");
document.getElementById("username").value = "";

Final Year Project CSIT 2009 E C(AMU). Page 65

document.getElementById("password").value = "";
document.getElementById("username").focus();
return false;
}
}
</script>
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Researcher form sample code
<script type='text/javascript'>
functionformValidator(){
varfname = document.getElementById('fname');
varlname = document.getElementById('lname');
var sex = document.getElementById('sex');
var address = document.getElementById('address');
var email = document.getElementById('email');
varphon No = document.getElementById('phonNo');
var Legal Clereance = document.getElementById('fil');
var status id = document.getElementById('status');
// validating patient first name for non empty !!
if(document.getElementById("fname").value=="")
{
alert("Enter first name !!");
document.getElementById("fname").focus();
return false;
}
if(document.getElementById("lname").value == "")
{
alert("Enter father name");
document.getElementById("lname").focus();
return false;
}
// validating account type for non empty !!
if(document.getElementById("sex").value=="")
{
alert("please select sex!!");
document.getElementById("sex").focus();
return false;
}

if(document.getElementById("address").value == ""){
alert("Enter address please !!");
document.getElementById('address').focus();

Final Year Project CSIT 2009 E C(AMU). Page 66

return false;
}

if(document.getElementById("email").value == ""){
alert("please enter email adress");
document.getElementById("email").focus();
return false;
}
if(document.getElementById("phonNo").value == ""){
alert("please enter phon number");
document.getElementById("phonNo").focus();
return false;
}
if(document.getElementById("fil").value == ""){
alert("please enter legal clereance");
document.getElementById("fil").focus();
return false;
}
if(document.getElementById("status").value == ""){
alert("please enter status id");
document.getElementById("status").focus();
return false;
}
}
</script>
<?php
if(isset($_POST['send']))
{
$fname=$_POST['fname'];
$lname=$_POST['lname'];
$sex=$_POST['sex'];
$address=$_POST['address'];
$email=$_POST['email'];
$phonNo=$_POST['phonNo'];
$status=$_POST['status'];
$file=$_POST['fil'];
$query="INSERT INTO researcher(fname,lname,sex,address,email,phonNo,status_id)
VALUES('{$fname}','{$lname}','{$sex}','{$address}','{$email}','{$phonNo}','{$status}') ;";
$result_set=mysql_query($query);
if(!$result_set){
die("query is failed".mysql_error());
}
else{
echo "Uploading";
echo "After seting path for: ".$_FILES['fil']['name'];
$path=$_FILES['fil']['name'];

Final Year Project CSIT 2009 E C(AMU). Page 67

copy($_FILES['fil']['tmp_name'],"C:/xampp/htdocs/PDRG1/PDRG/documents/".$_FILES['fil']['
name']);
echo "start uploading";
$query="update researcher set legal_clearance='$path' where status_id='$status'";
$con=mysqli_connect('localhost','root','','pdrg');
$result=mysqli_query($con,$query);
if($result===true)
echo "<script>alert('send successfully' )</script>";
else echo "<h1>File upload failed</h1>";
echo "'send successfully'";
}
}
?>

Final Year Project CSIT 2009 E C(AMU). Page 68