Professional Documents
Culture Documents
By
Neeme Mwengesyali Grace
15/BIS/MC/R/008
Option: Business Information System
Supervisor:
Mr. Lowu Francis
Department of Computing and Technology
School Of Business
Bugema University
March, 2018
APPROVAL
This Project Report has been submitted with the approval of my supervisor.
Bugema University
2
DECLARATION
I NEEME MWENGESYALI GRACE do hereby declare that this Project Report is mine and has
not been or submitted for any other diploma award to any other University before.
School of Business
Bugema University
3
ACKNOWLEDGEMENT
I thank all those who assisted me for the success of this research project above all I thank the
Almighty God for His love, mercy and sustenance that He had accorded me and my family for
the unnumbered blessings he granted to me. I also thank my supervisor Mr. Lowu Francis for
4
ABSTRACT
This research was carried out at St. Francis Hospital found in Nsambya, Kampala. It
concentrated on web-based system using various information systems, tools and techniques. The
research also involved analyzing the need of the appointment system for the St. Francis Hospital
for issuing required data and then producing a user-friendly system for Doctors. Then it will
ready to be uploaded on the user’s machine.
5
Table of Contents
APPROVAL..................................................................................................................................................2
DECLARATION...........................................................................................................................................3
ACKNOWLEDGEMENT.............................................................................................................................4
ABSTRACT...................................................................................................................................................5
CHAPTER 1..................................................................................................................................................8
1.0 Introduction..........................................................................................................................................8
1.2 The Problem Statement........................................................................................................................9
1.3 Aim....................................................................................................................................................10
1.4 Objectives..........................................................................................................................................10
1.5 Scope..................................................................................................................................................10
1.6 Justification........................................................................................................................................11
CHAPTER 2................................................................................................................................................12
LITERATURE REVIEW............................................................................................................................12
2.0 Introduction....................................................................................................................................12
2.2 Benefits of Utilizing the system.....................................................................................................12
2.3.0 Research Methods Used..............................................................................................................13
2.4 Development techniques and standards used to design the system...............................................14
2.5 Maintenances.................................................................................................................................14
2.5 Justification....................................................................................................................................15
2.6 Conclusion.....................................................................................................................................15
CHAPTER 3................................................................................................................................................16
METHODOLOGY......................................................................................................................................16
3.0 Introduction....................................................................................................................................16
3.1.0 Requirements Gathering.............................................................................................................16
3.2.0 Tools that were used to Design the system.................................................................................17
3.3.0 Tools that were used in implementing the system......................................................................18
3.4 Conclusion.....................................................................................................................................19
CHAPTER 4................................................................................................................................................20
SYSTEM DESIGN......................................................................................................................................20
4.0 Introduction....................................................................................................................................20
4.1.0 Conceptual Design......................................................................................................................20
4.2.0 User Interface structure and Behavior design.............................................................................21
4.3.0 System Design:...........................................................................................................................23
6
4.4 Review of the System Design........................................................................................................24
CHAPTER 5................................................................................................................................................25
IMPLEMENTATION..................................................................................................................................25
5.0 Introduction........................................................................................................................................25
5.1 visual basic.........................................................................................................................................25
5.2 Text Editor.........................................................................................................................................25
5.3 .0 system pages Appearance..............................................................................................................26
CHAPTER 6................................................................................................................................................33
6.0 Discussion..........................................................................................................................................33
6.1 Recommendation...............................................................................................................................33
6.2 Limitations.........................................................................................................................................34
6.4 Conclusion.........................................................................................................................................35
APPENDIX..................................................................................................................................................36
REFERENCES............................................................................................................................................37
7
CHAPTER 1
1.0 INTRODUCTION
Generally, Automation plays an important role in the world economy and in daily experience.
Engineers strive to combine automated devices with mathematical and organizational tools to
create complex systems for a rapidly expanding range of applications. The Patient Information
Management System (PIMS) is an automated system that is used to manage patient information
and its administration. It is meant to provide the Administration and Staff, with information in
(Malhotra, p. 2009). Hospital is an organization that mobilizes the skills and efforts of a widely
defined hospital as an integral part of social and medical organization that provides
the complete curative and preventive health care and treatment to people. Hospitals are the
focal points of education for the health professionals and clinical research necessary for
advancement of medicine. Thus, the hospital is one of the most complexes of all administrative
organizations. The main purpose of the hospital is to provide adequate care and treatment to the
people. (Mansi, p. 2010)Various operational works that are done in a hospital include: recording
information about the Patients, generating bill, recording information related to diagnosis
information about various diseases and medicines available to cure them etc. All these
works are done in most hospitals on papers. The need for proper management of the
health sector leads to the creation of an electronic means of keeping records, administering
8
discharge, querying of data, prescription helper and also good accountability. Information
(Anna, p. 2003). Hospital management system (HMS) system has been widely implemented in
many hospitals over the world to allow the proper management of medical records for different
types of cancer patients. In Malaysia only, a small number of hospitals have implemented a HMS
system, due to the high installation and implementation cost and the lack of trained technician for
maintenance. Medical information is needed in any health organization to avoid medical errors
and inappropriate decisions. Hospital based management systems have been developed to
(Adusei, p. 2010) developed an intelligent CDM system for a computer aided breast cancer
detection and diagnosis using mammography, where the CDM system efficiently retrieves and
analyzes the mammogram images. The aim of CDM systems is to provide a fast and secure
platform to health care organizations, to improve the speed of simultaneous access and retrieval
The adoption and use of technology in South African (SA) hospitals is not new. Some SA
researchers have undertaken research on this topic with an aim towards improving existing
health technologies at hospitals. A recent review of the literature highlights some of these
researches
Smit and de la Harpe’s (2008) study sought to investigate if electronic Information system has
any benefit over paper-based systems. It noted that the medical industry was slow to adopt
technology as compared to industries like finance and engineering. The authors proposed a
9
computer based system owing to the vast benefits over paper Based systems. Computer benefits
according to what will include central data maintenance, non-existing duplicate information,
electronic records that could be employed to improve continuity of care in the SA healthcare
setting by developing a technological model that employs several of these electronic record
systems. The research concluded that paper-based methods of recordkeeping are inadequate in
(sooklal, p. 2012) Critically evaluated the current state of a hospital’s health record system;
established a global best practice in record storage and management; as well as determine the
desirability of introducing more technological record storage mechanisms and quantified the
system with the benefits of reducing space, infrastructure dedicated to medical record storage,
Health appointments (2017), Problem statement statistics from the ministry of health report on
the state of regional referral hospitals in Uganda indicates that more than 80% of the hospitals
still use the book register system for example a file is opened for each patient that is admitted to
the medical personnel justification. A survey conducted around Kampala shows that some
hospitals such as kadic, mengo and nakasero hospitals have tried to adopt the computerized
systems. However, these system record patient’s arrivals and are used for billing purposes.
Furthermore, these systems are only accessible by the administration and cannot be accessed
10
The records for cancer patients in Nsambya hospital have over time been run down due to
misplacing or keeping their records together with others different from cancer, this led to poor
record keeping since it’s a paper-based system. The fact that the current system used is manual
poses many disadvantages like; great possibility of losing patients previous records and files due
to misplacement, disasters occurrences like fire outbreaks; It wastes a lot of time for example in
regards to capturing, analyzing and verifying details about the cancer patients, scheduling and
making of their appointments. St. Francis Nsambya hospital should be in position to efficiently
store and keep track of the records for their Cancer patients.
Therefore, this project is set to produce a web-based hospital management system that will
enable St. Francis Nsambya hospital to keep track of their cancer patients’ records.
11
1.1 PROBLEM STATEMENT
There are a lot of patients seeking diagnosis and medical treatment on breast cancer and other
cancer ailments in hospitals every day. Most hospitals are using manual management system for
cancer patients and they keep their records together with others different from cancer, which is
not reliable, efficient and time consuming when it comes to retrieve data stored a long time ago.
The current system uses paper-based system of keeping patient’s records. First, the patient
registration is done on a paper, this paper report which composes the description of patient’s
condition and type of screening test is sent to the radiology department in the hospital. After the
test, the images and results, which are on a paper will be transmitted to the physician, who will
then decide on future action. All the paper work is stored in the documentation room. Now, this
is a challenge in terms of Storage Space, Backup and also data retrieval, this is because papers
become too much. Therefore, there is a need to design a hospital management system for cancer
patient to replace their existing manual, paper work-based system.
1.2 AIM
The aim of the study is to develop the web-based management system for cancer patient which is
going to help hospital in registration process and being in touch with their doctors at any time.
1.3 OBJECTIVES
1) To collect a requirement and analyze them for help in the design of a web-based management
4) To test and validate the web-based management system for cancer patient
1.4 SCOPE
The project will establish electronic Health Management system for St. Francis Hospital in
12
This work will be limited within offices of Hospital and on computers only, helping in solving
previously mentioned problems above in the problem statement. The advanced Hospital
Management System for cancer patients includes registration of patients, storing their details into
the system and also computerized billing in the pharmacy, and labs. The database will make
retrieval of data efficient and accurate. The system will generate reports whenever required.
1.5 JUSTIFICATION
Apparently, the role of web-based system is basic and essential within each hospital that wants to
keep a really good control and record concerning its personnel data, functionality and
performance on all levels in its structure. Therefore, this project will be useful to the Hospital in
such a way that, it will be easier and faster to retrieve records of patients at any given time, not
only that but also, Scheduling and making appointments, the system simplifies this job by
showing availability of hospital resources. It will also reduce on the need for storage space for
the records and the time it takes to retrieve the records. Therefore, this project is set to produce a
web-based hospital management system for cancer patients that will enable St. Francis Nsambya
13
CHAPTER 2
2.0 LITERATURE REVIEW
An appointment is an arrangement to do something or meet someone at a particular time and
place. Patient flow management requires addressing three aspects of a patient unit: arrival of
patients, service process, and queuing process. Working on the patient’s arrival includes
controlling its patient panel size, balancing patient volumes across available sessions, and
achieving desirable patient arrival pattern within a session. The goal here is to improve
alignment between the unit’s service capacity and demand. Another approach is to improve the
unit’s service process. The use of a web-based information system helps manage patient ‘s
appointment data effectively. There are other Systems that allow access to assist administrators,
first responders and the public. The National Library of Medicine (NLM) has developed several
systems for Health Systems, ranging from hazardous material detection to a lost person finder.
These systems can be beneficial to public administrators during a crisis in coordinating with
patient’s records, appointment scheduling and recovery efforts. According to Simon, Goldberg
and Adini (2012), where paper based systems were initially used by the general public to store
data, it is now being adopted by governments and non-governmental organizations as a tool for
health system management. Simon, et al (2014). Also assert, “An organized and systematic
recording and storage of data is crucial to mitigating loss of information and damage to
infrastructure.”
In Addition to that, there are a variety of information systems that can be implemented (Kendall
& Kendall, 2011). They include:
1. Transaction Processing Systems (TPS). These are information systems that are designed
to perform daily routine business transactions. A user inputs data into the system and it is
transformed into output based on the data.
2. Office Automation Systems and Knowledge Work Systems. Office Automation Systems
support workers by helping them analyze or manipulate information but not create them.
Knowledge Work Systems, on the other hand, help workers such as scientist, engineers,
and doctors create new knowledge.
14
3. Management Information System (MIS). An MIS includes a TPS but it outputs
information that is useful for decision making. It uses a common database to access
information. An MIS requires good interaction between hardware, software and people to
be effective.
4. Decision Support Systems (DSS). It is similar to a MIS but it supports decision making in
all its phases. The final decision, however, is still left to the decision maker.
5. Expert Systems. An expert system captures knowledge of a human expert and uses that
knowledge to solve problems in an organization. Unlike DSS, it takes the best solution to
a problem.
6. Executive Support Systems. These are systems that produce summarized reports that will
help top executive and managers make strategic decisions.
15
improve the internal security. The use of firewalls and encryption can help protect patient data
from such threats.
CHAPTER 3
3.0 METHODOLOGY
This is a description of methods chosen to achieve the objectives of the proposed system. It will
go on to describe the techniques of data collection that will be employed in the research study of
the proposed systems. The system development life cycle (SDLC), the researcher has chosen to
use is Agile model. In this model, the system follows a series of events;
The importance of this stage is to find out what the users want or need from the proposed
information systems in order to gain clear understanding of the current system and the problems
3.2 Analysis
This is where we will carry out a feasibility study on all the activities performed by the
administrators and the current system and identify the challenges they face so that we can help
solve them. The purpose of the Analysis Phase is to formulate and formalize the system's
requirements. This is accomplished by establishing what the system is to do, according to the
requirements and expectations of the system's end users. The modeling of these requirements is
then performed in the form of business, data, event, and process models to demonstrate the
understanding of the requirements. This enables the developers and customers to move forward
under the same set of expectations with respect to scope and requirements. The process map
16
3.7 Design
Project design is an early phase of the project where a project's key features, structure, criteria for
success, and major deliverables are all planned out. The Information system will be designed to
prove whether it will conform to the user requirement and whether it will fulfill its requirement
objectives. We will use the DFD diagrams to design how the system will be developed with its
layout.
Researchers’ examine concerned on the software development techniques and standards. It has
got different phases that are more important to a designer of the software. These include:
I. Planning phase: This phase was to obtain the system definition which helped to be
implemented, if accepted, in the subsequent analysis and design phase. The basic
activities were:
II. Analysis phase: This phase the analyst read books and went through records, collected
forms for later analysis or interviews people. As information was collected, the analyst
documented the important aspects so it can be referred to later on. For this purpose,
he/she used forms charts or tables.
III. Design phase: This phase particularly deals with design the system/software showing the
physical layout the system after planning was done.
IV. System implementation: It consist the tasks which were necessary to bring a developed
system into operational use and turn it over to the users. It involves programmers, users
and it’s planning and timing a function of the system analyst.
V. Maintenances: When the system began its operation, a formal evaluation procedure is
put into effect to monitor the results of the operation. The system evaluation phase
continued for the life of the system materially aiding in the discovery of a system
weaknesses and trend in the long-range planning for the subsequent systems.
3.2.0 Tools that were used to Design the System
This comprises of tools and methods especially diagrams used to analyze design and implement
the system. The Microsoft Visio Studio software and Data flow diagrams.
The Gantt chart shows the sequence of activities that the researchers used to follow right from
the beginning of the project to its completion. The Gantt char shows system development
schedule. This research methodology shows how data was gathered, the tools and techniques
used when collecting this data and tools used to design and implement the system also the Gantt
chart shows the sequence of activities that the researcher followed right from the beginning of
the project to its completion. Below is a Gantt chart showing system development schedule
18
3.2.2 Data flow diagram
It was used for showing the data flow from the source to the destination and showing the
processes that were taken by the designer to show the system how it will be flowing its data from
the source to its destinations. This showed how system operates.
3.3.1 Notepad
This was used to create system in terms of forms of the system. This stage particularly deals with
design the system showing the physical layout the system after planning was done. Microsoft
Visual Basic is a programming software that is used in the design of user interfaces and forms.
There are lots of Microsoft Visual Basic versions allowing one to work very fast and effective.
Many people have used Microsoft Visual Basic in creating website, smart phone applications and
system software because it is easier to use and to debug.
3.4 Summary
This chapter presents the techniques and tools that the researcher used to design and implement
the system. It also presents the order of activities right from the start of the project to
maintenance. Therefore, this chapter presents the basis upon which the next chapter will begin.
The chapter also gives out the starting point of the coming chapter which will be established by
the development methodologies that were selected for the project design and implementation.
19
CHAPTER 4
SYSTEM DESIGN
4.0 Introduction
This comprises of tools and methods especially diagrams used to analyze design and implement
the system. The design used Data flow diagrams (DFD). This chapter represents the way the
system is and its layout. First by starting with the Conceptual Design.
The analysis of existing was covered by several researches including questions that were about
how the current system functionalities ,advantages and disadvantages of the current system and
finally the founded solution to the weakness of current system were also implemented. During
that scrutiny several questions that were intended to examine how the functional qualities of the
existing system were appraised, this where I was emphasized on the exploitation of user full
data for assisting to make a really contribution and improvement of different statements that
were testified with the results provided with the following questions:
4.2.1. A system
A collection of components that work together to realize some objectives
Forms, some of the component of the system are input, processing and output.
20
4.2.2. Analysis
The term analysis covers several meaning according for each and every domain, in management
analysis has the meaning of looking on financial situation in order to make an specific decision
while in information system the analysis can defined as process of developing ideas in order to
construct or to renew system according to a user requirements.
4.2.3. A design
A design is a structured model that can be a result of analyzed system or other object output.
The use case diagram shows how the users interact with the System;
Doctors will:–
i. Enter Patients
ii. Create Appointments
iii. View Patients Records
iv. Edit Records
v. Print Reports
21
vi. Delete Appointment
Nurse will be –
i. Add Patients
ii. Create Appointments
iii. Print Reports
iv. View Patients Reports
Explanations:
Activity Diagram indicates how the users interacts with the system
In the case above, they process begins with the user selecting the type of activity or a form to
be used, either a nurse or a doctor, on doctors account, there is an authentication feature were
the user enters the password and username, if it fails, then the system returns an error.
If the users successfully sign in, the system enables him/her to do different activities
including; Printing the Report, View the Appointment, delete appointment, add an
appointment and also print reports then the process ends.
On the other side of the system, the nurse login as a nurse, this module enables the nurse to
do different activities including; Adding an appointment, print appointment, add patients and
view patients reports then the process ends.
22
4.1.3 Database
Figure 4.1.4
Figure 4.1.4 Shows the database and the relationships within the tables.
One nurse can create appointments and also One nurse can register many Patients.
One patients can have many appointments with doctors
One Doctor can have many appointments and also one doctor can have many patients to attend to
One Disease can have many patients
23
4.2.0 User Interface structure and Behavior design
This window is a welcoming window that contains the Login to the User window and
administrator window. The administrator window is linked to other windows where he/she can
view the reports, view entered data or members registered, print the reports. The User window is
linked to a window were he/she can enter new members, if a member is entered already new,
they just enter the tithe brought like stipulated above. An example of a how a Login window
looks like is shown below;
USER INTERFACE
Verification Registration
process process
Appointment Patients
Registration Report
Report
Printing
24
4.3.1 User Interface
The user interface provides a graphical friendly interface layout for the user to interact with
system. It consists of all the links to the other windows of the system
25
CHAPTER 5
IMPLEMENTATION
5.0 Introduction
Technology that was used in this system and applied during system designing is mentioned
below;
This was used to create forms of the system that are used to interact between the user and the
system. It is a software that has a programming language that was used in the design of user
interfaces, forms, reports of the entire of the system. Many people have used Visual Basic in
creating desktop software or systems because it is easier to create a computer based system with
this programming and it’s graphical with user friendliness.
The above mentioned software made things easier in terms of coming up with a database to use
for the system to store the data in the system.
5.3.1 Home
26
This form is the welcoming page that contains the links that navigates to all the system. This
form links all the navigation from the Doctors form and the nurse’s. Other forms like reports for
both registering patients, appointment arrangement form are linked to this form. As shown on the
diagram below.
This form shows the user or gives the user the options of where to put data. An example is when
a patient comes for the first time, the user clicks on the patients to register him/her in the system.
27
If the patient is the has been already registered, the user (Nurse) clicks on the Appointment so as
to schedule the appointment.
This form is used to register the new patients who have come to schedule appointments for
the first time. As shown below, the user (Nurse) enters the first name of the patients, gender
28
and a number is assigned to him/her that uniquely identifies him/her, the address, room
number, contacts and Diagnosis. When the registration is done, the systems takes the user to
the appointment form where the appointment is schedules.
29
From the diagram above, this form is for the appointment scheduling, like shown above, when
the patient is successfully registered, you come to this stage. Here the user uses the number
assigned to enter all the details of the patient like shown below. Instead of putting the particulars
in the system again, the user uses the number and he enters the assigns or schedules the
appointment. In this form, the user captures data like the appointment date and time, room
number, the doctor assigned to you and also the status of the appointment, if the appointment is
pending, the system shows the red cross, if the status is of the appointment is done then the green
tick will display.
30
CHAPTER 6
6.2 Discussion
The research carried out at St. FrancisHospital located in Goma, Congo concentrated on having a
computerized tithing system. The research is involved analyzing the already system and then
The research also aimed at finding out different tools and techniques used to design electronic
Appointment process and how they can be used to design such a system.
6.3 Recommendations
Ever since, St. FrancisHospital has found it easy to tabulate the statistical reports, manage their
appointments and also to store the data without a lot of paper work being done. Therefore, I
6.3 Conclusions
The entire research project enabled the researcher to come up with a Hospital Appointment
system that facilitates the easy handling appointments and tabulation of reports, together with
improved data storage via the electronic database, hereby improving on the efficiency of
Appointment processes.
31
6.5 Future work
The different dimensions in which further research can be carried out to construct on this
include;
Mobile version of the system were each user will be able to make appointments via
32
REFERENCES
Kendall, K., & Kendall, J. (2011). Systems analysis and design (8th ed.). New Jersey:
Prentice Hall.
Lee LM, Teutsch SM, Thacker SB, St. Louis ME. Principles & Practice of Public Health
Surveillance. 2009 New York, NY: 2009
Simon, Goldberg and Adini (2012)
http://www.sciencedirect.com/science/article/pii/S0268401215000638
https://www.thebureauinvestigates.com/2013/07/13/revealed-police-forces-are-taking-up-to-30-
longer-to-react-to-999-calls/
33
“Analysis of the Short Message Service (SMS) and Cell Broadcast Service (CBS) for
Report ETSI TR 102 444 V1.1.1. European Telecomm. Standards Inst., 2006.
34