DESIGN AND IMPLEMENTATION OF AN OUTPATIENT MANAGEMENT QUEUE SYSTEM (A CASE STUDY OF UNIVERSITY OF MAIDUGURI TEACHING HOSPITAL)

  • 0 Review(s)

Product Category: Projects

Product Code: 00005913

No of Pages: 67

No of Chapters: 5

File Format: Microsoft Word

Price :

₦3000

  • $

ABSTRACT

A common problem associated with hospitals especially the nontertiary hospitals (primary and secondary hospitals) is long queue. Attempts have been made to address this using the ticket approach, however, this does not minimize crowd in and around hospitals. In the wake of the consciousness of the need to avoid crowd with the emergence of the Corona Virus (COVID-19), it has become important to note that some diseases are transmissible when people clinch close within a vicinity especially in the hospital environment, traditionally outpatient hospital faces various problems and difficulties due to a manual system like keeping patient history, filing and other factors that affect the interest of an individual patient. It is therefore imperative to devise a means to reduce the usual crowd witnessed at the different units/sections in the hospital, precisely by outpatients. In this study, a centralized queue control system was developed that can be used in the different sections of hospitals. To overcome these issues, this research work has designed and developed an outpatient management system. The main objectives of the project are, to design and develop a web-based outpatient management system for the efficient management of outpatients of the hospital. This research work has studied various kinds of the literature of relevant software. After reviewing literature, the research work has found limitations in many relevant software. The research strategy was design and created, the software development model used was the incremental. The system was implemented using scripting languages and MySQL. The researched study revealed that many of the software being used in hospitals are not online based and specifically, case study area is a remote area in term of modern technology, whereas to overcome the burden of patients waiting long in a queue, as such system was not implemented in the target area. Therefore, this motivates the research work to develop the proposed system to overcome these limitations. However, there is scope of further research in areas like lack of co-ordination between hospital interfaces, waiting time of patients queuing for special treatments in this field. Finally, the systems have been tested under different conditions to evaluate its performance





TABLE OF CONTENTS

Contents                                                                                                              Pages

Cover Page      -           -           -           -           -           -           -           -           -           -           I

Title page        -           -           -           -           -           -           -           -           -           -           II

Declaration-    -           -           -           -           -           -           -           -           -           -           III

Certification                -           -           -           -           -           -           -           -           -           IV

Dedication                  -           -           -           -           -           -           -           -           -           V

Acknowledgement                  -           -           -           -           -           -           -           -           VI

Abstract                      -           -           -           -           -           -           -           -           -           VII

Table of content                      -           -           -           -           -           -           -           -           IX

List of Tables -           -           -           -           -           -           -           -            -          -           X

 List of Figures -         -           -           -           -           -           -           -            -          -           XI

CHAPTER ONE

INTRODUCTION

1.1              Introduction    -           -           -           -           -           -           -           -           -           1

1.2       Statement of the Problem       -           -           -           -           -           -           -           1

1.3       Aim and Objectives    -           -           -           -           -           -           -           -           2

1.4       Scope of the Study     -           -           -           -           -           -           -           -           2

1.5       Significance of the study        -           -           -           -           -           -           -           2

1.6       Definitions of Terms   -           -           -           -           -           -           -           -           3


CHAPTER TWO

LITERATURE REVIEW

2.1       Introduction    -           -           -           -           -           -           -           -           -           4

2.2        Smart Queue Processing System        -           -           -           -           -           -           4

2.3       Queuing Theory          -           -           -           -           -           -           -           -           5

2.3.1    Types of Queuing System       -           -           -           -           -           -           -           7

2.3.2    Queuing Service Disciplines   -           -           -           -           -           -           -           8

2.3.3      Queuing Management Mechanism   -           -           -           -           -           -           9

2.3.4    Time Based Management       -           -           -           -           -           -           -           10

2.4       Outpatient Management System        -           -           -           -           -           -           11

2.4.2    Emergence of Bottlenecks in Outpatient Departments          -           -           -           11

2.5       Benefits of Outpatient Management System -           -           -           -           -           13

2.6       Brief History of UMTH Maiduguri    -           -           -           -           -           -           13

2.7       Related Works            -           -           -           -           -           -           -           -           14

2.8       The Summary of the Chapter  -           -           -           -           -           -           -           17


CHAPTER THREE

METHODOLOGY

3.1       Introduction    -           -           -           -           -           -           -           -           -           18

3.2       System Development Methodology   -           -           -           -           -           -           18

3.2.1    Justification of Methodology -           -           -           -           -           -           -           18

3.2.2    Graphical Representation of Incremental Model        -           -           -           -           18

3.2.3    Description of Methodology -           -           -           -           -           -           -           18

3.3       Analysis of the Existing System         -           -           -           -           -           -           20

3.3.1    Existing System Characterization       -           -           -           -           -           -           20

3.4       Analysis of the New System  -           -           -           -           -           -           -          20

3.4.1    New System Characterization            -           -           -           -           -           -           21

3.4.2    Algorithm for the proposed system    -           -           -           -           -           -           21

3.4.3    Proposed System Flowchart   -           -           -           -           -           -           -           22

3.4.4    New System Requirements     -           -           -           -           -           -           -           22

3.4.4.1 Hardware Requirement           -           -           -           -           -           -           -           23

3.4.4.2 Software Requirement            -           -           -           -           -           -           -           23

3.4.5    New System Data Flow Diagram       -           -           -           -           -           -           24

3.4.6    New system E-R Diagram      -           -           -           -           -           -           -           25

3.5       System Design            -           -           -           -           -           -           -           -           26

3.5.1    Logical Design            -           -           -           -           -           -           -           -           26

3.5.2    Input Design   -           -           -           -           -           -           -           -           -           26

3.5.3    Output Design -           -           -           -           -           -           -           -           -           27

3.5.4    Physical Design           -           -           -           -           -           -           -           -           27

3.5.5    Modular Design          -           -           -           -           -           -           -           -           27

3.5.6    Database Design         -           -           -           -           -           -           -           -           27

3.6       Unified Modeling Language  -           -           -           -           -           -           -           29

3.6.1    Use Case Diagram      -           -           -           -           -           -           -           -           30

3.7       Summary of the Chapter         -           -           -           -           -           -           -           31


CHAPTER FOUR

SYSTEM IMPLEMENTATION AND TESTING

4.1       Introduction    -           -           -           -           -           -           -           -           -           32

4.2       Implementation          -           -           -           -           -           -           -           -           32

4.2.1    Choice of programming language and IDE    -           -           -           -          32

4.3       Testing            -           -           -           -           -           -           -           -           -           33

4.3.1    Objectives of Testing              -           -           -           -           -           -           -           33

4.3.2    Testing Plan                -           -           -           -           -           -           -           -           33

4.3.3    Testing Strategy                      -           -           -           -           -           -           -           34

4.3.4    Testing Procedure                   -           -           -           -           -           -           -           34

4.3.5    Testing Methodology              -           -           -           -           -           -           -           35

4.3.6    Testing of Modules and Forms          35

4.4       Overall Issues with Implementation   -           -           -           -           -           -           39

4.5       Summary of the Chapter         -           -           -           -           -           -           -           39


CHAPTER FIVE

SUMMARY, CONCLUSION AND RECOMMENDATION

5.1              Summary         -           -           -           -           -           -           -           -           -           -           40

5.2              Conclusion      -           -           -           -           -           -           -           -           -           -           40

5.3              Recommendations      -           -           -           -           -           -           -           -           -           41

References                  -           -           -           -           -           -           -           -           -           42

Appendix A (Source Code)     -           -           -           -           -           -           -           -           45

Appendix B (Source Code)      -           -           -           -           -           -           -           -           53

 

 

 

LIST OF TABLES

 

Table 2.1: Table of summary of related works           -           -           -           -           -           16

Table 4.1: Software Development Environment        -           -           -           -           -           32

 

 

 

LIST OF FIGURES

Fig. 2.1: The single channel- single phase system.     -           -           -           -           -           7

Fig. 2.2: The single channel- multiple phase system   -           -           -           -           -           7

Fig. 2.3: The multiple channel- single phase system -           -           -           -           8

Fig. 2.4: The multiple channel- multiple phase system           -           -           -           -           8

Fig 3.1: Incremental Model    -           -           -           -           -           -           -           -           18

Fig 3.2: Incremental Life Cycle         -           -           -           -           -           -           -           19

Fig 3.3: New System Flow chart       -           -           -           -           -           -           -           22

Fig 3.4: New System Data Flow Diagram     -           -           -           -           -           -           24

Fig 3.5: E-R Diagram             -           -           -           -           -           -           -           -           25

Fig. 3.6: Database design       -           -           -           -           -           -           -           -           29

Fig. 3.7: New System Use case          -           -           -           -           -           -           -           30

Fig 4.1: Home Page    -           -           -           -           -           -           -           -           -           36

Fig 4.2: Admin Control Page -           -           -           -           -           -           -           -           36

Fig 4.3: Desk Officer Home Page-                 -           -          -           -           -           -           37

Fig 4.4: Doctors Home Page  -           -           -           -           -           -           -           -           37

Fig 4.5: Register New Patient Page   -           -           -           -           -           -           -           38

Fig 4.6: View waiting queue  -           -           -           -           -           -           -           -           38



 


CHAPTER ONE

INTRODUCTION

1.1     Introduction

The medical field has made remarkable progress in end of twentieth and the initial twenty first centuries. This emerges high specialized hospitals for serving patients. Nowadays most of the hospitals are overcrowded with patients. It may affect patients’ symptoms, clinical outcome, and satisfaction. It can also affect physician’s effectiveness, causing frustration among medical staff. This overcrowding is due to lack of effective queue management system in hospitals, which is due time required for each patient would be uneven based on how much time doctor takes and other tasks such as scanning, pharmacy, testing, and others. (Varkevisser, 2020). This is a challenging and complicated job because every patient in queue may came just for consultation of doctor or check-up or test etc. Each treatment task can have varying time requirements for each patient of different age groups. (Burungale, 2018).

According to Titarmare (2018), time is a quantity that should be efficiently managed. Standing in a long queue consumes a lot of time of patients and so, the Patient Queue Management System provides the solution for it. Most hospitals and clinics try to improve their wait time by scheduling appointments.

Queuing theory is a potent mathematical approach to the analysis of waiting lines performance parameters in healthcare delivery systems (Ozcan, 2006). It has increasingly become a common management tool for decision making in the developed world. This vital tool is unfortunately minimally used in most healthcare systems in Nigeria and other African countries. Application of queuing theory to model hospital settings has been widely published (Ivalis & Millard, 2003) Also, the use of queuing analysis and simulation to enhance performance at various hospital departments has been widely researched (Green, 2002).


1.2     Problem Statement      

Usually when people go to the governmental hospital, they must wait for a number of times before being served. The waiting time is based on their arrival and the situation. Unlike a hospital, in some cases there are options, whether they go to government or private hospitals to get better services.

Therefore, this research intends to solve the following problems:

1.      The overcrowding is due to lack of effective queue management system in hospitals, which is due time required for each patient would be uneven based on how much time doctor takes and other tasks such as scanning, pharmacy, testing, etc. 

2.      The records kept manually of which are prone to lost, damages and manipulation by unauthorized user, are aimed to be kept in computerized forms for easier and quicker access thereby minimizing the waiting and consultation times of patients in a hospital.

3.      The burden of waiting long in a queue.


1.3    Aim and Objectives

The aim of this project is to design and implement an Outpatient Queuing Managing System.

The following objectives shall be achieved in this research work;

i.        To design a smart queue processing system to inform patients about their tentative waiting time.

ii.      To develop a web-based outpatient management system for the efficient management of outpatients of the hospital.

iii.     To evaluate the performance of the proposed system using different performance metrics.


1.4     Scope of study

This project will only focus on the outpatient department in University of Maiduguri Teaching Hospital Maiduguri. A web-based application which is proposed to be implemented using HTML, PHP, JAVASCRIPT while MySQL as back-end.


1.5     Significance of the Study

Queuing system have been applied in numerous industrial settings and service industries. The number of applications in healthcare however, is relatively small. This is probably due to a number of unique healthcare related features that make queuing problems particularly difficult to solve. Therefore, the proposed program will be designed to study the various alternatives in scheduling and would be used to optimize patients and their visiting schedules, alleviating the problem of waiting. Also, the system will overcome patient long waiting time that is one of the main disadvantages in outpatient clinics.


1.6     Definitions of Terms

Design: Realization of a concept or idea into a configuration, drawing, model, mould, pattern, plan or specification.

Implementation:  is the carrying out, execution, or practice of a plan, a method, or any design, idea, model, specification, standard or policy for doing something.

Queue: is a line of people, cars etc. waiting for something or to do something.

Outpatient: is a person who goes to a hospital for treatment but does not stay there.

Patient: is a person who is receiving medical treatment, especially in a hospital

Hospital: an institution that is built, staffed, and equipped for the diagnosis of disease; for the treatment, both medical and surgical, of the sick and the injured



Click “DOWNLOAD NOW” below to get the complete Projects

FOR QUICK HELP CHAT WITH US NOW!

+(234) 0814 780 1594

Buyers has the right to create dispute within seven (7) days of purchase for 100% refund request when you experience issue with the file received. 

Dispute can only be created when you receive a corrupt file, a wrong file or irregularities in the table of contents and content of the file you received. 

ProjectShelve.com shall either provide the appropriate file within 48hrs or send refund excluding your bank transaction charges. Term and Conditions are applied.

Buyers are expected to confirm that the material you are paying for is available on our website ProjectShelve.com and you have selected the right material, you have also gone through the preliminary pages and it interests you before payment. DO NOT MAKE BANK PAYMENT IF YOUR TOPIC IS NOT ON THE WEBSITE.

In case of payment for a material not available on ProjectShelve.com, the management of ProjectShelve.com has the right to keep your money until you send a topic that is available on our website within 48 hours.

You cannot change topic after receiving material of the topic you ordered and paid for.

Ratings & Reviews

0.0

No Review Found.


To Review


To Comment