KIRINYAGA UNIVERSITY

SCHOOL OF PURE AND APPLIED SCIENCES

PATIENT MANAGEMENT SYSTEM

PRESENTED BY;

HAMISI ONESMUS KILUMO

CT101/G/6255/19

PROJECT SUPERVISOR

MR. EDWIN IRERI

DECLARATION

This project is my original work and has not been presented for a degree or any other award in
any other University.”

NAME: …………………………………………..

Signature.................................................... Date..............................................................

I confirm that the work reported in this proposal was carried out by the candidate under my
supervision.

SUPERVISOR’S NAME: …………………………………………………….

Signature........................................................... Date......................................................

i
DEDICATION

I dedicate this project to my dear father, who has been nicely my supporter until my research was

fully finished, and my beloved mother who, for months past, has encouraged me attentively with

her fullest and truest attention to accomplish my work with truthful self-confidence

ii
ACKNOWLEDGMENT

Above all, I would like to thank God for giving me the strength and the knowledge throughout my academic

journey, my parents for the financial, motivation, moral and spiritual support, my friends for lending a hand

towards this endeavor and my lecturers particularly Dr. Ereri for steering me towards making this course a

success.

iii
ABSTRACT

The Patient Management System is primarily concerned with the well-being and proper care of

patients in hospitals. The system is designed to input patient information and guide the patient

through the registration and payment processes, as well as to save patient information for future

use. The Patient Management System is a software product suite designed to improve the quality

and management of hospital management in the areas of clinical process analysis and activity-

based costing. The primary goals of this system are to collect patient information, capture a doctor's

prescription for a given patient, and finally allow the pharmacist to access and charge the doctor's

prescription for a given patient. The current systems do not provide a platform for patient feedback

where patients can provide feedback and rate the services provided. Another identified gap is that

current systems do not generate medical reports of a patient's medical history, which is critical in

patient treatment. All of this is incorporated into the proposed system, improving patient care. Agile

development is the system methodology used in this project for the design, planning,

implementation, and achievement of the objectives. Agile methodology ensures continuous

collaboration between customers and the development team, which is critical for this project.

iv
Table of contents

DECLARATION ..................................................................................................................................... i
DEDICATION ........................................................................................................................................ ii
ACKNOWLEDGMENT ....................................................................................................................... iii
ABSTRACT ........................................................................................................................................... iv
List of Figures ....................................................................................................................................... vii
List of Tables. ....................................................................................................................................... viii
CHAPTER ONE: INTRODUCTION ................................................................................................... 1
1.1: Introduction ......................................................................................................................................... 1

1.2 Background of the study .................................................................................................................. 1

1.3: Current/existing system .................................................................................................................. 1
1.4: Problem statement ........................................................................................................................... 2
1.5: Proposed Study ................................................................................................................................ 2
1.6: Purpose of the study ........................................................................................................................ 2
1.7: General Objectives .......................................................................................................................... 2
1.8: Specific Objectives ........................................................................................................................... 2
1.9: Justification of the study ................................................................................................................. 3
1.10: Scope ............................................................................................................................................... 3
1.11: Limitations of the study ................................................................................................................ 3
1.12: Significance of the study ............................................................................................................... 4
CHAPTER TWO: LITERATURE REVIEW. ..................................................................................... 5
2.1 Introduction ...................................................................................................................................... 5
2.2 Related literature reviews ................................................................................................................ 5
2.2.1. AfyaServe....................................................................................................................................... 5
2.2.2. Clinicore ........................................................................................................................................ 6
2.2.3. MocDoc .......................................................................................................................................... 7
2.2.4. eHospital ........................................................................................................................................ 8
2.2.5 Medicentre ...................................................................................................................................... 9
2.3 Gaps ................................................................................................................................................. 10
2.4 Conceptual Framework.................................................................................................................. 10

v
2.5 Chapter Conclusion ........................................................................................................................ 11
CHAPTER THREE: SYSTEM DEVELOPMENT METHODOLOGY ......................................... 12
3.1 Introduction .................................................................................................................................... 12
3.2 Development methodology ............................................................................................................. 12
3.3: Justification of the Methodology .................................................................................................. 13
3.4: Data Collection .............................................................................................................................. 16
3.5: Data Analysis ................................................................................................................................. 16
3.6 Chapter Conclusion ........................................................................................................................ 17
CHAPTER FOUR: SYSTEM DESIGN ............................................................................................. 18
4.0 Introduction .................................................................................................................................... 18
4.1 System requirements ...................................................................................................................... 18
4.1.0 Hardware requirements............................................................................................................. 18
4.1.1 Software requirements .............................................................................................................. 18
4.2 Functional requirements ................................................................................................................ 19
4.2.0 User ............................................................................................................................................ 19
4.2.1 Admin ......................................................................................................................................... 19
i. Efficiency requirement................................................................................................................ 20
ii. Reliability requirement ............................................................................................................... 20
v. Implementation requirement ..................................................................................................... 20
vi. Delivery requirement .................................................................................................................. 20
4.4 System analysis................................................................................................................................ 20
4.6 Database design............................................................................................................................... 21
4.6.0 Database Implementation ......................................................................................................... 21
4.6.1 Database design tables .............................................................................................................. 21
CHAPTER FIVE: SYSTEM TESTING AND IMPLEMENTATION ................................................ 23

5.0 Introduction .................................................................................................................................... 23

5.1 Construction .................................................................................................................................... 23
5.2 Unit testing ...................................................................................................................................... 26
5.3 Integration testing........................................................................................................................... 27
5.4 System testing .................................................................................................................................. 27
5.5 Acceptance testing .......................................................................................................................... 27
5.8 Conclusion ....................................................................................................................................... 28

vi
CHAPTER SIX: CONCLUSION AND RECOMMENDATION..................................................... 29
6.0 Introduction .................................................................................................................................... 29
6.1 Conclusions...................................................................................................................................... 29
6.2 Recommendation ............................................................................................................................ 29
6.3 Scope for future work..................................................................................................................... 29
References.............................................................................................................................................. 30
APPENDICES ....................................................................................................................................... 32
Appendix I: Budget............................................................................................................................... 32
Appendix II: Schedule .......................................................................................................................... 33

vii
List of Figures

Figure 2.1: Afyaserve....................................................................................................... 7

Figure 2.2: Clinicore. ..................................................................................................... ..8

Figure 2.3: MocDoc. ....................................................................................................... .9

Figure 2.4: eHospital. ...................................................................................................... 10

Figure 2.5: Medicentre .................................................................................................... 11

Figure 2.6: Conceptual Framework............................................................................…...12

Figure 3.1: Agile Software Development.......................................................................... 14

vii
List of Tables.

Table 1: Budget................................................................................................................. 19

Table 2: Schedule.............................................................................................................. 19

viii
CHAPTER ONE: INTRODUCTION

1.1: Introduction

This chapter relates to the background of the study, the problem statement and objectives of the

study, the study justification, and the limitations of the study.

1.2 Background of the study

The Patient Management System is a suite of software products designed to improve the quality

and control of hospital management in the areas of clinical process analysis and activity-based

costing. A patient management system allows people to develop their organization and improve

their effectiveness and quality of work. Efficient management of critical processes is critical to a

hospital's success. Healthcare is characterized by rapidly increasing usage, especially in developed

countries. Improving information technology, documentation and management in patient care. The

global rise of medical information technology will improve the efficiency of healthcare, reduce

medical errors, improve the quality of care, and improve patient and physician information. The

overall goal of the Information Management function is to acquire, manage, and use information

to improve healthcare and medical services, performance, governance, and management and

support processes. Information Systems “IS” There is much that can be done to control healthcare

costs and improve the quality of care.

1.3: Current/existing system

Most of the current system is manual and requires you to pay a registration fee and fill out a form

with your details. The form is then saved to a file. This leads to a lot of work because if a patient

or doctor wants to retrieve previous patient data, they have to go through all the files.

1
1.4: Problem statement

Patient overload in most hospitals and the rapidly spreading coronavirus were identified as

problems. The slow retrieval of previous data is also a problem. In order to know the patient's

medical history, the user has to search various files and records. This leads to inconvenience and

wasted time. Error-prone hand calculations have also been identified as a problem. Manual

calculations are error prone, time consuming and can lead to incorrect information. For example,

calculating patient bills based on different treatments

1.5: Proposed Study

The proposed system will provide a platform that can capture patient details and store them for

easy retrieval.

1.6: Purpose of the study

To create a patient management system that would enable hospitals to input patient data into a

computerized system is the goal of this study.

1.7: General Objectives

The project's primary goal is to create a patient management system

1.8: Specific Objectives

1. To create a system that records patient information..

2. To develop a module that will capture doctor’s prescription for a given patient
3. To develop a module that will allow the patient to rate services provided by doctors.

2
1.9: Justification of the study

The implementation of a patient management system gives us the capacity to streamline and

digitize all of the institutional procedures, improving customer service while lowering costs and

streamlining the search for medical records, bills, patients, and other relevant information.

1.10: Scope

After installing hospital software, daily functions such as patient registration, admission

management, and overall management of various departments can be performed more easily and

accurately.

The modules of the patient management system are simple to use and navigate. It has a unified

user interface with several modules. Officials can easily incorporate these modules into their

processes and make the best use of the patient management system. Overall, this improves hospital

administration infrastructure.

1.11: Limitations of the study

Some of the limitations of the system are shortage of professional healthcare faculty who have in-

depth knowledge of Patient Management System and other similar technologies and lack of

resources like computers that can be used in training and learning on making use of the Patient

Management System. In general, experience, and knowledge of using computer applications

3
1.12: Significance of the study

This study is important for hospitalized patients so they can obtain medical information without

experiencing delays or misinformation. If you want access to her medical history, you don't have

to go through a difficult process. Hospitals, especially pharmacies and billing departments, did not

go through many paper reports regarding payments and accounting records. Paper consumption is

still there, but can be reduced, so excessive paper load is not a problem. The survey was also

relevant for employees as they can register, update, delete and search information within the

system. Connecting all existing computers into one system has been beneficial to the hospital as it

allows for better management. In general, this study was important for hospitals and patients as it

could serve as a relevant tool to maintain productivity and service quality in hospitals.

4
CHAPTER TWO: LITERATURE REVIEW.
2.1 Introduction

This chapter explains the case study of the project. It includes forms of the former systems that are

related to this system.

2.2 Related literature reviews

2.2.1. AfyaServe
AfyaServe is a cutting-edge health information management system in Kenya that seeks to

optimize healthcare center operations by providing cutting-edge technology at competitive pricing.

Their dedicated Lab Information System (LIS) also facilitates clinical decision-making by

producing precise and timely health data. AfyaServe, a division of the RIANA Group, a well-

known provider of technology solutions in Kenya, makes use of the technological know-how of

our group companies to put the emphasis back on the human in your healthcare service. Patients,

who are the most important stakeholders, should always have a positive interaction with you. As

a result, they advocate for a patient-first philosophy, which aids in the management of patient flow

and the reduction of wait times. By incorporating a complete hospital information management

system, medical professionals can easily access patient information and relevant data. This allows

for a more rapid, straightforward, and fruitful connection between the patient and the practitioner.

AfyaServe's newest patient management solution automates repetitive tasks to boost employee

productivity. It is possible to track the number of people who are working at any given time,

evaluate their performance, and improve teamwork. A hospital information management system

enables staff to access and retrieve data quickly and accurately. The main stakeholders, the

patients, should always have a positive contact. This patient management software ensures data

privacy and security, which is critical in the sensitive healthcare industry. Using cutting-edge

5
patient management software ensures that critical data is only accessible to authorized personnel.

Furthermore, a robust and focused Lab Information System enables the medical team to respond

quickly and accurately, improving patient care quality and patient experience.

Figure 2.1: AfyaServe

2.2.2. Clinicore

Clinicore is a healthcare management system suited for clinics, hospitals and general health service

providers. It features modules that fully integrate with each other and enhance the movement and

flow of patients and information through the various service points using a dynamic in-built service

process flow system. Clinicore enabled hospitals to go paperless, increasing efficiency, and it is

easy to access reports at the click of a button.

6
Figure 2.2: Clinicore

2.2.3. MocDoc

MocDoc is a platform that revolutionizes the way you manage your Clinics and Hospitals. With

MocDoc, you get a fully integrated healthcare management suite delivered on a cloud-based

platform that provides a robust, secure, and always-on solution for your needs. MocDoc's vision

is to be a modern healthcare platform that allows caregivers and the general public to manage their

medical records and access them from any device, at any time.

7
Fig 2.3: MocDoc

2.2.4. eHospital

eHospital Systems is a comprehensive and integrated Hospital Management System designed to

manage all aspects of hospital operations such as medical, financial, and administrative. It includes

electronic health records, business intelligence and revenue cycle management. When a new

patient comes to the reception desk, a unique number is automatically allotted to him. Patient

demographics like Name, Age, Gender, Address etc. and the services desired are entered into the

software.

8
Fig 2.4: eHospital

2.2.5 Medicentre

This Hospital Management Software offers a solution to your hospital's workflow, clinical, and

financial issues. The software is divided into many integrated modules, each addressing a specific

activity and all working together to improve hospital management while providing excellent

customer service. Medicentre is locally developed with local conditions in mind to fit well to the

needs of local hospitals as well as other hospitals and medical centres in the region. Data entry is

simplified by use of auto-complete features integrated throughout the system. Where necessary,

search engines have also been included to facilitate the process of finding data and information.

Moreover, alerts have also been integrated in the system to remind and alert users on critical events

such as lab requests, examination requests, queue alerts, doctor’s requests, appointment reminders,

stock levels, payments among others.

9
Figure 2.5: Continuous Care

2.3 Gaps

The reviews of the above systems show that the main goal is to provide quality service to patients.

However, none of the above systems provide a platform for patient feedback where patients can

respond and rate the services provided. This is significant because it provides management with

firsthand information from patients and can even identify which doctor or nurse is not meeting the

hospital's standards based on the ratings given. The aforementioned systems also do not generate

medical reports of a patient's medical history, which is essential in patient treatment. All of this

will be incorporated into the proposed system, thereby improving patient care.

2.4 Conceptual Framework

The conceptual framework gives a brief overview of the interaction between the users and the

system itself.

10
.Patient Doctor
Registration

Lab

Billing/Paying Pharmacy

Figure 2.6

2.5 Chapter Conclusion

In this chapter, we discussed and reviewed the current systems. We discussed how they work, what

are some of the gaps the systems do not cover and what is being done about it. We also gave a

conceptual framework, which is just an overview of how users will interact with the system

11
CHAPTER THREE: SYSTEM DEVELOPMENT METHODOLOGY

3.1 Introduction

This chapter discusses the methods that will be used by the researcher to collect data on the project,

development and implementation of the project. It involves developing software development

work into distinct stages and coming up with manageable units for better planning and time

management.

3.2 Development methodology

Agile development is the methodology used in this project for the design, planning,

implementation, and achievement of the objectives. This methodology refers to a group of iterative

software development methodologies in which requirements and solutions evolve through team

collaboration. Throughout the process, agile methodology ensures collaboration between

customers and the development team. The user feedback is used to improve the system. This means

that agile development ensures that after deploying a prototype version, improvements can be

made in later versions based on user feedback. There are several agile software development

methodologies available, and we will use the Feature Driven Development methodology in this

project.

12
Figure 3.1: Agile Software Development

3.3: Justification of the Methodology

Agile methodology is essential because consumers provide feedback, so improvements are made

to ensure it meets user needs. Agile methodology also necessitates minimal planning, so any

changes can be made later in the development phase. The software's functionality is what

determines the research's success. Changes requested during any development phase are

implemented with little to no approval.

13
The phases of Agile Software Development include:

1. Planning: This will entail developing a set of plans to guide me through the project's

development, execution, and closure phases. Plans developed during this phase will aid in

the management of time, cost, quality, change, risk, and issues. This ensures that all

iterations are completed on time and that resources are used wisely. Requirement analysis

will aid in the identification of functional and nonfunctional requirements. It will entail

gathering information, analyzing it, documenting it, validating it, and managing it. In order

to complete the user task, the researcher will collect the user's requirements. In the system

specifications. The researcher will outline the minimum hardware specifications required

in terms of processor, RAM, and hard disk.

2. Design

This will assist in identifying key system features, structure, and how major deliverables

are planned. The Unified Modelling Language is one of the design tools to be used (UML).

This will aid in describing the system's boundary, structure, and behavior, as well as the

objects contained within it. A flowchart, the second tool, will provide a graphical

representation of all the logic sequences. A Data Flow Diagram (DFD) is the third tool,

and it graphically represents the flow of data in the system.

3.

This is the stage at which the system is actually coded. The researcher intends to use

Hypertext Markup Language (HTML), Cascading Style Sheet(CSS), JavaScript and

Hypertext Preprocessor (HTTP) to construct the system (PHP). HTML is supported by all

14
browsers worldwide and can easily interoperate with other programming languages such

as PHP.

4. Testing

This phase involves testing all developed modules and creating documentation. The

researcher will use functional and non-functional testing, unit testing and integration

testing to ensure that all units work efficiently.

5. This phase entails testing and documenting all developed modules. To ensure that all units

work properly, the researcher will conduct functional and non-functional testing, unit

testing, and integration testing.

6. Deployment

7. This step entails releasing the software into the world and allowing consumers to use it.

This happens only after the system has been thoroughly tested and all modules are fully

functional. The parallel deployment strategy will be used. Parallel strategy entails system

changeover, in which a new system gradually takes over the roles of the older system while

both systems operate concurrently. I will use the parallel strategy because it allows me to

compare results to ensure that the new system runs smoothly and without errors. It also

allows for staff training and helps them gain confidence in the new system.

8. Feedback

After deployment, software users will give their responses about the software. This

feedback will be used to define further requirements hence the iteration.

15
3.4: Data Collection

Any research project requires the collection of data. The researcher will collect data for this project

research using interviews, questionnaires, and a document record.

The methods listed below will be used:

i) Observation: The researcher will conduct his own observations from several health

institutions and patients. Observations are essential as we get correct data by judging

from non-verbal communications.

ii) Document review: The researcher will go through the documents from the various

organizations that afterwards will be used on analysis.

3.5: Data Analysis

This study will employ flowcharts and DFD diagrams to analyze the data gathered as well as the

entire software development process.

i) Data Flow Diagram (DFD): This represents a detailed and well explained diagram of

system components. This will ensure the developer understands the flow and processes

of the system.

ii) Flowchart: This will give a clear picture of how each system component and how users

of the system will implement each section of the system.

16
3.6 Chapter Conclusion

The primary focus of this chapter is on the software development methodologies that will be used

in the development of the Patient Management System. Throughout the process, the Agile

methodology will be applied.

17
CHAPTER FOUR: SYSTEM DESIGN

4.0 Introduction

This section centers on the necessary specifications for the system, the format of the input,

the design of the process, and the resulting output of the system.

4.1 System requirements

4.1.0 Hardware requirements

This refers to the hardware prerequisites that must be satisfied to ensure smooth operation of

the patient management system.

LAPTOP

This is a laptop that is intended for use in designing and developing the system. The computer

comes with the following specifications:

• 4GB of RAM.

• A 500GB hard disk drive.

4.1.1 Software requirements

Operating System: Windows 10 or higher versions of OS (either x86 or x64).

Database Management System: MS SQL server, MySQL Server

18
Programming languages

HTML, CSS, JavaScript,PHP, SQL

4.2 Functional requirements

4.2.0 User

REGISTER NEW USER

In order to access the system, a new user is required to register by providing necessary details. The

system is responsible for verifying and authenticating the provided information.

USER LOGIN

This feature enables users to login by entering a registered username and password. If the

credentials are invalid, access to the system is denied. The username and password are issued once

the registration is confirmed and must be entered discreetly to prevent others from viewing the

password field.

4.2.1 Admin

MANAGE USER

The administrator can add user, delete user, view user and block user reported as fraud.

NON-FUNCTIONAL REQUIREMENTS

19
i. Efficiency requirement

Customers can purchase product in an efficient manner.

ii. Reliability requirement

The system should provide a reliable environment to both customers and owner. All orders

should be reaching at the admin without any errors.

iii. . Usability requirement

iv. The website is designed for user friendly environment and ease of use.

v. Implementation requirement

Implementation of the system using CSS and html in front end with PHP as back end and

it will be used for database connectivity. And the database part is developed by MySQL.

Responsive web designing is used for making the website compatible for any type of

screen.

vi. Delivery requirement

The whole system is expected to be delivered in four months of time

wit.

4.4 System analysis

After carefully analyzing the requirements and functionality of the web application, I had two

important diagrams by the end of the analysis phase. They are the ER diagram and data flow

diagram which were the basis for finding out entities and relationships between them, the flow of

information.

20
4.6 Database design

4.6.0 Database Implementation

4.6.1 Database design tables

21
22
CHAPTER FIVE: SYSTEM TESTING AND IMPLEMENTATION

5.0 Introduction

Software testing is a process of running with intent of finding errors in software. Software

testing assures the quality of software and represents final review of other phases of software

like specification, design, code generation etc.

5.1 Construction

HOME PAGE

23
24
25
5.2 Unit testing

Unit testing emphasizes the verification effort on the smallest unit of software design i.e.; a

software component or module. Unit testing is a dynamic method for verification, where program

is actually compiled and executed. Unit testing is performed in parallel with the

coding phase. Unit testing tests units or modules not the whole software.

I have tested each view/module of the application individually. As the modules were built

up testing was carried out simultaneously, tracking out each and every kind of input and

checking the corresponding output until module is working correctly.

The functionality of the modules was also tested as separate units. Each of the three modules

was tested as separate units. In each module all the functionalities were tested in isolation.

Visual Studio 2008 has in built support for testing the application. The unit testing can be

done using visual studio 2008 without the need of any external application. Various methods

have been created for the purpose of unit testing. Test cases are automatically generated for

these methods. The tests run under the ASP.NET context which means settings from

Web.config file are automatically picked up once the test case starts running.

Methods were written to retrieve all the tables, strings that match a certain search term, , all

images that belong to a particular product etc. Unit test cases were automatically generated

for these methods.

26
5.3 Integration testing

In integration testing a system consisting of different modules is tested for problems arising

from component interaction. Integration testing should be developed from the system

specification. Firstly, a minimum configuration must be integrated and tested.

In my project I have done integration testing in a bottom-up fashion i.e., in this project I

have started construction and testing with atomic modules. After unit testing the modules

are integrated one by one and then tested the system for problems arising from component

interaction.

5.4 System testing

It provides final assurances that software meets all functional, behavioral & performance

requirement.

Test Cases- I have used a number of test cases for testing the product. There were different

cases for which different inputs were used to check whether desired output is produced or

not.

5.5 Acceptance testing

Acceptance testing was used to assess whether or not the final piece of software was ready for

delivery. It involves ensuring that the product was in compliance with all of the original business

criteria and that it meets the end user’s needs.

27
5.8 Conclusion

The application can be used for any hospital. It is easy to use, since it uses the GUI

provided in the user dialog. User friendly screens are provided. The application is easy

to use and interactive making it a recreational activity for users. It has been thoroughly

tested and implemented.

28
CHAPTER SIX: CONCLUSION AND RECOMMENDATION

6.0 Introduction

After successful build, test and functionality trial of the system, it can now be validated to

perform stated objectives but with limitations stated and scope for future work which will

help make the system’s functionality even more I interactive.

6.1 Conclusions

The Hospital Management System is designed to provide a web-based application that

would make hospital management easy.

6.2 Recommendation

An android application has to be integrated in to this systems.

6.3 Scope for future work

The following things can be done in future.

• The patient could subscribe for alerts which would enable them to receive

messages.

29
References
Adroitinfosystems.com. 2022. Welcome to eHospital Systems. [online] Available at:

<https://www.adroitinfosystems.com/eHospital/> [Accessed 1 February 2022].

AfyaServe. 2022. Hospital Management System (HMS) Kenya, Nairobi | AfyaServe. [online]

Available at: <https://www.afyaserve.com/> [Accessed 1 February 2022].

Hanmak Technologies. 2022. MedicentreV2 - Hospital Management Information System -

Hanmak Technologies. [online] Available at: <https://www.hanmak.co.ke/medicentre-

hospital-information-management-system-hims/> [Accessed 1 February 2022].

2022. [Online] Available at: <https://corebase.co.ke/clinicore.html> [Accessed 1 February 2022].

Mocdoc.in. 2022. Best Hospital Management Solution, Lab Management Solution and Clinic /

Pharmacy Software. [online] Available at: <https://mocdoc.in/> [Accessed 1 February

2022].

Adenuga, O. A., Ogunseye, A. O., & Oluwadare, O. A. (2018). Design and implementation of a

web-based hospital management system. Journal of Information Engineering and

Applications, 8(10), 33-43.

Al-Harbi, F., Alghamdi, R., & Al-Mubadel, F. (2017). The impact of Hospital Information

Systems on patient safety: A systematic review. Journal of Healthcare Engineering, 2017.

Almalki, M., Fitzgerald, G., & Clark, M. (2011). Health care system in Saudi Arabia: An

overview. Eastern Mediterranean Health Journal, 17(10), 784-793.

Asadullah, M. A., Rahman, M. M., & Islam, M. R. (2016). Design and development of a hospital

management system. International Journal of Advanced Computer Science and Applications,

7(1), 37-41.

30
Dhar, A., & Chatterjee, P. (2019). Development of a hospital management system using

machine learning techniques. International Journal of Advanced Research in Computer

Science, 10(4), 115-120.

Duong, T. M., Nguyen, T. T., Nguyen, H. M., Nguyen, T. M., & Tran, T. T. (2019). Hospital

management system using Internet of Things. International Journal of Computer Science and

Information Security, 17(6), 78-85.

Fasoro, A. A., & Adeniji, O. A. (2017). Design and implementation of a web-based hospital

management system for resource optimization in healthcare delivery. Journal of Health

Informatics in Developing Countries, 11(1).

Gnanaraj, J., & Rajaraman, V. (2018). Design and implementation of a web-based hospital

31
APPENDICES

Appendix I: Budget
Table 1: Budget

ITEM DESCPRITION QUALITY UNIT PRICE TOTAL

Hardware Laptop 1 20000 20000

Flash Disk 1 1000 1000

Software Vs code - Free

IBM Machine Learning - Free

Others Printing/stationery - 700 700

Miscellaneous - 9000 9000

Total 30700

32
Appendix II: Schedule

Table 2: Schedule

WEEK NO.
WEEK 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Project activities.
Design. Plan.
Actual.

Design. Plan.
Actual.
Integration. Plan.
Actual.
Implementing Plan.
Actual.
Testing. Plan.
Actual.

33