DESIGN AND IMPLEMENTATION OF DATA BASE SYSTEM FOR PATIENT MANAGEMENT A CASE STUDY OF DELTA HOSPITAL ONITSHA

ABSTRACT

Patient that has been admitted in the hospital, has to be issued a card and his or her name will be registered in a sheet of paper. The manually oriented sheet will not contain enough information that will describe the normal existence of the so called admit even the written of the symptoms of the disease suffered by the admit-ant will not be only written in the same file of the patient. So the project being carried out has to go details of data correction the admit- ant both the picture and the symptoms that cursed the disease has to be critically written. The ongoing project has to be computer oriented one for future recognition of the named patient. That has been existed in the hospital. We also go further to implement the use of the new software that will be helpful for well entry of data and retrieval.

ORGANISATION OF WORK

 This project work is primarily designed to give an insight into computerized aided medical diagnosis system on patient data base system used in hospitals. Chapter one talks about introduction to computerized aided medical diagnosis system on patient database system, study of problem and objectives as well as definition of the scope. Chapter two comprises the interview. Chapter three gives the detailed information about the existing (old) system while chapter four and five deals with the design and implementation of the new system. Chapter six documents the project work, while in chapter seven summarizes, conclusion and suggestions were made

TABLE OF CONTENTS

TITLE PAGE…………………………………………………………………………… i

CERTIFICATION PAGE…………………………………………………………… ii

APPROVAL PAGE……..…………………………………………………………… iii

DEDICATION PAGE………………………………..……………………………… iv

ACKNOWLEDGEMENT…………………………………………………………… v

ABSTRACT……………………………………………………………………………. vi

ORGANISATION OF WORK…………………………………………………… vii

TABLE OF CONTENTS….………………………………………………………. viii

CHAPTER ONE

1.0 INTRODUCTION…………………………………………………………………1

1.1 STATEMENT OF PROBLEM………………………………………………. 1

1.2 AIMS AND OBJECTIVES……………………………………………………. 1

1.3 PURPOSE OF STUDY………………………………………………………… 2

1.4 SIGNIFICANCE OF THE STUDY………………………………………….. 2

1.5 SCOPE/DELIMITATION….……………………………………………..….. 2

1.6 LIMITATION/ CONSTRAINTS……….……………………………………. 2

1.7 ASSUMPTION OF STUDY……………………………………………….…. 3

1.8 DEFINITION OF TERMS………………………………………………….…. 3

CHAPTER TWO

REVIEW OF RELEVANT LITERATURE………………………………….……. 5

CHAPTER THREE

3.0 DISCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM.…… 7

3.1 FACT FINDING METHOD/ METHODOLOGY………………………. 7

3.2 ORGANISATIONAL STRUCTURE/ ORGANOGRAM…………….. 8

3.3 OBJECTIVES OF THE EXISTING SYSTEM..…………………….……. 8

3.4 INPUT, PROCESS, AND OUTPUT ANALYSES……………………… 9

3.4.1 INPUT ANALYSIS…………………………………………………………… 9

3.4.2 PROCESS ANALYSIS…………………………………………………….… 9

3.4.3 OUTPUT ANALYSIS…….………………………………………………… 10

3.5 INFORMATION FLOW DIAGRAM………………….…………………. 10

3.6 PROBLEMS OF THE EXISTING SYSTEM……..…………………..…. 11

3.7 JUSTIFICATION FOR THE NEW SYSTEM………………….……….. 11

CHAPTER FOUR

4.0 DESIGN OF THE NEW SYSTEM…..…………………………………….. 13

4.1 DESIGN STANDARD…………………………………………………………. 13

4.2 OUTPUT SPECIFICATION AND DESIGN……………………………… 13

4.3 INPUT SPECIFICATION AND DESIGN…………………………………. 14

4.3.1 FILE DESIGN………………………..…………………………………….….. 15

4.4 PROCEDURE CHART…………………………………………………………. 16

4.5 SYSTEM FLOW CHART………………..…………………………………..… 17

4.6 SYSTEM REQUIREMENT………………………………………………….… 18

4.6.1 HARDWARE REQUIREMENTS……..……………………………..…… 18

4.6.2 SOFTWARE REQUIREMENTS………………………………………..…. 18

4.6.3 OPERATIONAL REQUIREMENTS…………….……………………..…. 18

4.6.4 PERSONNEL REQUIREMENTS………………………………..…………. 18

CHAPTER FIVE

5.0 IMPLEMENTATION….………………………………………………………..… 19

5.1 DESIGN STANDARD…………………………………………………………….. 19

5.2 PROGRAM DESIGN…………………….………………………………..……… 19

5.2.1 PROGRAM FLOW CHART……………………………………..………….. 21

5.2.2 PSEUDOCODE…………………………………………………………………. 23

5.3 CODING…….…………………………………………………………………..…… 24

5.4 TEST DATE/ TEST RUN………………………………………………………… 24

5.5 USER TRAINING – AN OVERVIEW……………………………………….. 24

5.6 CUTOVER PROCESS…………..……………………………………………….. 25

CHAPTER SIX

6.0 DOCUMENTATION……………………………………………………..……… 26

6.1 PROGRAM DOCUMENTATION……………………………………………. 26

6.2 USER DOCUMENTATION……………………………………………………. 27

CHAPTER SEVEN

7.0 RECOMMENDATIONS, SUMMARY AND CONCLUSION…….…. 28

7.1 RECOMMENDATION……..……………………………………………..……. 28

7.2 SUMMARY………..…………………………………………………………..…… 28

7.3 CONCLUSION…..………………………………………………………..………. 29

REFERENCES………………………….………………………………………………… 30

SOURCE LISTING…….. ……………………………………………….…………….. 31

CHAPTER ONE

1.0 INTRODUCTION

  In patient database, the system that is being used is manually oriented and was documented in the files (Head copy) for saving. It is not well cared for future retrieval; even data being corrected are not well handle d so they always lost the written files. Some of data for recognition like picture, village or home town of the patient are not been collected so we need an efficient one to make registration more trusted, easy retrieve, and identification and secured. Here new software is to be organized (programmed) in other to accept data that has well details of the patients capable of storing and protecting of the information for feature use retrievals.

1.1 STATEMENT OF PROBLEM

    Although many hospitals try as much as to provide an identity of the admitting. Their database system are still poor not every information are being collected because of lack of techniques of correcting even though their storage capability was also low because of file being stored manually can’t be retrieve fast as possible so making the nurses that is in charge of database to register the patient again by so doing the information about the patient that suppose to be provided to enable the doctor operate (treat) very well will be left gaped. So it might cause much inadequate treatment.

   In a view of these assumptions, that motivates the researcher to critically create software that will enable registration to be easy and oriented.

1.2 AIM AND OBJECTIVES

  The purpose this study (work) is to critically examine the existing system/ method that is being used, list up the problem and provide a necessary solution to eradicate them and produce a reliable software which can be used in a system that can be easy an trustworthy.

1.3 PURPOSE OF STUDY

The aim of the research is to critically examine:-

The former way of patient database and how to improve it’s functionality

To produce a new one which will suit the modern way of data collections?

And also to make the system more reliable to use.

1.4 SIGINIFICANCE OF THE STUDY

   Since not much work has been done in providing suitable software for patient database, this study/research intend to serve as a valuable source reference to the practitioners and those who want to develop their own software about the database of patient in the hospital to carry on from were I stop.  The project will also help the programmer, or those who want to research more and my curlicue to know how to carry on with their own point of view.

1.5 SCOPE/DELIMTATION

  The aim of this program is to create computerized software in administering, retrieving and documentation of patient.

1.6 LIMITATION/CONSTRAINTS

  It always being said that know good thing come easily, so this work was little delayed by insufficient finance to transport from my home to the case study area and also time factors to carry some necessary correction that I assumed will help this work to greater light

1.7 ASSUMPTION OF STUDY

  The software will contribute immensely to the hospital in organization of patient database in a good format and also work efficiently in storage of the information for future use.   It also assumed that the former system is manually operated and a new software which is computer oriented will be developed.