PATIENT MANAGEMENT INFORMATION SYSTEM

(Case of Edrogan Hospital Management System)

By

Mustafe Hussein Mohamoud

(Reg.No: 8873)

A Project Proposal Submitted to the Faculty of Computing

and ICT for partial fulfillment of the requirements of a
Bachelors Degree in Business Information Technology of
Amoud University

29th Sept, 2018

i
 DECLARATION AND APPROVAL

Declaration

I the undersigned hereby declare that the project proposal entitled “Patient Management
System”, for Edrogan Hospital is the work of my effort and to the best of my knowledge has not
been done by any other person or submitted to any other institution for examination purposes

Name: Mustafe Hussein Mohamoud Signature: ___________ Date: __________

Approval

We the undersigned hereby declare that this project entitled “Patient Management System”, for
Edrogan Hospital has been carried out through our guidance.

Name: Signature: __________ Date: __________

Subject Lecturer

Name: Signature: __________ Date: __________

Project Supervisor

ii
 ACKNOWLEDGEMENT

First of all I am grateful for a ALLAH who made Everything Every time.

Mr. Richard he is my teacher support me so I say thank you very much.

Second person to say thanks is my friend Abdiwahab Osman Farah..

I would like to acknowledge all the support I received from my classmates.

I especially appreciate to acknowledge all the support I received from my best friends.

Finally, thanks my parents for their support my study.

iii
 DEDICATION

I dedicate this project to God Almighty my creator, my strong pillar, my source of inspiration,
Wisdom, knowledge and understanding, He has been the source of my strength throughout this
program and on His wings only have I soared, I also dedicate this work to my mother; who’s she
encouraged me all the way and whose encouragement has made sure that I give it all it takes to
start my project, And also I would like to thank my mother for providing me with delicious food
when I came home late from the university, I also dedicate this work to my father, Who has
encouraged me all the way and whose encouragement has made sure that I Give it all it takes to
finished my final project ,Finally I also thankful to my dear friends who always support me

iv
 ABSTRACT

This the Patient management systems in hospital today necessitate a competent administration
when handling patients, generating reports from cashier patient details which serves as a key
factor for the flow of business transactions in Edrogan Hospital . Unfortunately the current
Record management system leads to misplacement of drug details, payment details and late
release of reports and insecurity to records. This research project is aimed ta computerizing all
the records about patients, staff and drug suppliers. In order to achieve this goal, a thorough
System Study and investigation was carried out and data was collected and analyzed about the
current system using document and data flow diagrams.

v
 Table of Contents
DECLARATION AND APPROVAL .......................................................................................................... ii
Declaration ................................................................................................................................................ ii
Approval ................................................................................................................................................... ii
ACKNOWLEDGEMENT ........................................................................................................................... iii
DEDICATION ............................................................................................................................................. iv
ABSTRACT.................................................................................................................................................. v
TABLE OF FIGURES ................................................................................... Error! Bookmark not defined.
LIST OF ABBREVIATION ......................................................................................................................... x
CHAPTER ONE: INTRODUCTION ........................................................................................................... 1
1.1 Historical Background of Edrogan Hospital ................................................................................. 1
1.2 Problem Statement ........................................................................................................................ 2
1.3 Main Objective/Goal ..................................................................................................................... 2
1.3.1 Specific Objectives ................................................................................................................... 2
1.4 Significance................................................................................................................................... 2
1.5 Justification ................................................................................................................................... 2
1.6 Scope ............................................................................................................................................. 2
CHAPTER TWO: LITERATURE REVIEW ............................................................................................... 3
2.1 Introduction to Patient Management Information System ............................................................ 3
2.2 Current Edrogan Hospital System................................................................................................. 4
2.3 Ordakhan Hospital System............................................................................................................ 5
2.4 Shifo Hospital System................................................................................................................... 5
2.5 Alorstar hospital System ............................................................................................................... 6
2.6 AL-Dar Hospital Management Information System ..................................................................... 7
2.7 Proposed Edrogan Hospital Management Information System .................................................... 7
CHAPTER THREE: METHODOLOGY ..................................................................................................... 9
3.1 Patient management system development life cycle of methodologies ........................................ 9
3.1.1 System development life cycle models ..................................................................................... 9
3.1.2 Waterfall model....................................................................................................................... 10
3.1.3 Incremental/Iterative model .................................................................................................... 10
3.1.4 V-shaped model ...................................................................................................................... 11
3.1.5 Agile model:............................................................................................................................ 12

vi
3.1.6 Spiral model ............................................................................................................................ 13
3.2 Planning and Requirement Collection Method ........................................................................... 13
3.2.1 Observation ............................................................................................................................. 14
3.2.2 Interview ................................................................................................................................. 14
3.3 Requirements Analysis and Specification Methods .................................................................... 14
3.3.1 System Structure Analysis ...................................................................................................... 14
3.3.1.1 Flow Chart Diagram................................................................................................................ 15
3.3.1.2 Data Flow Diagram ................................................................................................................. 15
3.3.1.3 Entity Relationship Diagram ................................................................................................... 15
3.3.1.4 Object-Oriented Analysis ........................................................................................................ 15
3.3.1.5 Unified Modeling Language ................................................................................................... 15
3.3.1.6 Class diagram .......................................................................................................................... 16
3.3.2 Requirements Specifications ................................................................................................... 16
3.3.3 User requirement ..................................................................................................................... 16
3.3.4 Functional Requirement .......................................................................................................... 17
3.3.5 Non Functional Requirement .................................................................................................. 17
3.3.6 System Requirements .............................................................................................................. 17
3.3.7 Hardware Interfaces ................................................................................................................ 17
3.3.8 Software Interfaces ................................................................................................................. 17
3.4 System Design& Architecture .................................................................................................... 18
3.4.1 Logical model ..................................................................................................................... 18
3.4.2 Data Flow Diagram (DFD) ................................................. 19
3.4.3 Entity Relationship Diagram (ERD) ....................................................................................... 19
3.4.4 Class diagram .......................................................................................................................... 20
3.4.5 case diagram................................................................................................................................. 20
3.4.5 System Architecture ................................................................................................................ 21
3.5 System Implementation............................................................................................................... 21
3.5.1 Front End ................................................................................................................................ 22
3.5.2 Back End ................................................................................................................................. 22
3.6 System testing ............................................................................................................................. 23
3.6.1 System Unit Testing ................................................................................................................ 23
3.6.2 Integration Testing .................................................................................................................. 23

vii
 3.6.3 System Testing ........................................................................................................................ 23
3.7 System Change over Methods..................................................................................................... 24
3.7.1 Direct cutover:......................................................................................................................... 24
3.7.2 Parallel operation: ................................................................................................................... 24
3.7.3 Pilot operation ......................................................................................................................... 24
3.7.4 Phased operation: .................................................................................................................... 24
CONCLUSION ........................................................................................................................................... 25
REFERENCES ........................................................................................................................................... 26
APPENDICES ............................................................................................................................................ 27
APPENDIX A ............................................................................................................................................. 27
APPENDX B .......................................................................................................................................... 27
APPENDIX C ......................................................................................................................................... 27

viii
 TABLE OF FIGURES

Figure 1: SDLC ............................................................................................................................................. 9

Figure 2: waterfall model ............................................................................................................................ 10
Figure 3: Iterative model ............................................................................................................................. 11
Figure 4: V-shaped model ........................................................................................................................... 12
Figure 5: Agile model, ................................................................................................................................ 12
Figure 6: Spiral model ................................................................................................................................ 13
Figure 7: logical flow of data in PRMS......................................................................................................... 18
Figure 8: Data flow diagram ....................................................................................................................... 19
Figure 9: Entity Relation Diagram (ERD) .................................................................................................. 19
Figure 10: Class diagram ............................................................................................................................ 20
Figure 11: case diagram .............................................................................................................................. 20
Figure 12: system Architecture of Edrogan hospital................................................................................... 21

ix
 LIST OF ABBREVIATION

PMIS: Patient Management Information System

EHS: Edrogan Hospital System

GUI: graphic user interface

SDLC: System Development Life Cycle

SSADM: Structured Systems Analysis and Design Methodology

ER: Entity Relationship

x
 CHAPTER ONE: INTRODUCTION

1.1 Historical Background of Edrogan Hospital

Edrogan Hospital, also known as the Digfer Hospital and the Somalia-Turkey Training and
Research Hospital, is a hospital in Mogadishu Somalia. The Digfer Hospital was constructed in
the 1960s, with Italian engineers (Cooperative Architetti e Ingegneri, Reggio Emilia) contracted
to build its premises. The name comes from the Italian construction company Digfer (Degola and
Ferretti): the time has modified it in Digfer or Digfer. It served as an important historic
institution in Somalia's capital. Following the start of the civil war in the early 1990s, the
hospital intermittently closed down. It also briefly operated under the aegis of the International
Medical Corps

In 2013, the Federal Government of Somalia reached an agreement with the Turkish authorities
to refurbish and modernize the Digfer Hospital's infrastructure and services in keeping with
international standards In January 2015, the hospital was officially reopened at an inauguration
ceremony in Mogadishu led by President of Somalia Hassan Sheikh Mohamoud and President of
TurkeyRecepTayyipErdoğan.TheDigfer Hospital was concurrently renamed Edrogan Hospital in
honour of Edrogan. The renovated 200-bed Somalia-Turkey Training and Research Hospital was
constructed by Turkeys international development body, the Turkish InternationalCooperation
and Development Agency (TIKA) It has a $135.7 million operating budget, $85.6 million of
which is slated to be covered by the Turkish authorities over the next five years.

Facilities and services includes the 13,500 square-meter indoor premises includes 20
neonatal incubators, 14 newborn intensive care beds, 12 intensive care beds, 4 operating rooms,
and laboratory and radiology units. Additionally, it has general surgery, neurosurgery, plastic
surgery, childcare, obstetrics, urology,medicine, anesthesia, dentistry and optometry department.
As of January 2015, the hospital had about 91 Somali and 52 Turkish hospital administrators,
head doctors, administrative directors or financial directors, as well as 40 Somali and 5 Turkish
security personnel. Around 36 Somali assistants are also scheduled to participate in the facility's
annual training program.The area also recovery is patient area patient area is large area I think
and most important part in hospital is how to take care patient. There is no network it is just has
one branch and that branch headquarter is Mogadishu Somalia.

1
1.2 Problem Statement

Edrogan Hospital currentlydo not have a good software to record their data. That is why I
decided to develop Edrogan Hospital Information Management System called Patient
Management System.

1.3 Main Objective/Goal

To build a more advanced Database and Secure Patient Management System in Muqdisho City.

1.3.1 Specific Objectives

i) To register all Edrogan Hospital Patient into the System

ii) To register all Erdoğan Members of Staff, especially those in the Patient Section

iii) To capture all the daily patient transactions as they occur at Erdoğan hospital

iv) To generate Patient Reports, Quarterly, Biannually and Weekly

v) To keeping record patient information

vi) To have consistency in record keeping

1.4 Significance

The proposed system will be available every time and this will reduce loses time it also improves
the system and will be one of the best in term of other system

1.5 Justification
They use old software for their record in hospital especially for patient and other sick people.
They also didn’t give the answers early their system is to slow. That is why I developing this
system to help them.

1.6 Scope
The system will be about the aspect of creation of advanced Database consumption by the
Patient of Edrogan Hospital.

2
 CHAPTER TWO: LITERATURE REVIEW

2.1 Introduction to Patient Management Information System

A system is a group of elements that are integrated with the common purpose of achieving an
objective and solving problem according to (Raymond, 2001)

According to (Mc graw, 2004)systemis group of interrelated components working together

toward a common goal by accepting input and producing output in an organized transformation
process

According to (O'Brien, 2001)Information System (IS) is set of people procedures and resource
that collect transform and disseminates information in an organization. Information system
knowledge is essential for manager because most organizations need information system can
help company extend their reach too far away location.

According (Mc leod, 2000)Management Information System (MIS) as a computer-based system

that make information available to users with similar needs.

According (Raymond m. , 2002)Management Information System (MIS) deal with the planning
for development management and use of information technology tool to help people perform all
task related to information processing and management.

According to (Patrick., 2014)Patient Management Information Systems (PMISs) are

comprehensive, integrated information systems designed to manage the information of patients
of a hospital and manage the service processes. Hospitals are becoming more reliant on the
capability of patient management information system to assist in the diagnosis process and
management, for better and improved services and practices. The main goal of PMISs is to
streamline the flow of information across the hospital towards effective decision making for
patient care, in an optimized and efficient manner. Recording of patient information, be it
medical, personal, financial or legal, or recording of medical personnel information on paper is at
risk of thievery, fire outbreaks, misplacement by employees and even petty things such as
handwriting legibility. An automated PMIS will be necessary because there are a lot of
difficulties in maintaining a large amount of information on paper, especially as there is usually

3
no back-up for the information, access to information can prove difficult and time-consuming if
it has to be searched for, and accuracy is needed in the recording of vital information, and chief
medical personnel cannot oversee all that is written on the vast amount of paper to be used. It is,
therefore, vital for a healthcare organization such as a hospital to have an automated patient
management information system

2.2 Current Edrogan Hospital System

According to (Mohamed, 2018)Edrogan Hospital, also known as the Digfer Hospital and
the Somalia-Turkey Training and Research Hospital, is a hospital in Mogadishu Somalia. The
Digfer Hospital was constructed in the 1960s, with Italian engineers (Cooperative Architetti e
Ingegneri, Reggio Emilia) contracted to build its premises. The name comes from the Italian
construction company Digfer (Degola and Ferretti): the time has modified it in Digfer or Digfer.
It served as an important historic institution in Somalia's capital. Following the start of the civil
war in the early 1990s, the hospital intermittently closed down. It also briefly operated under the
aegis of the International Medical Corps

(Mohamed, 2018) In 2013, the Federal Government of Somalia reached an agreement with the
Turkish authorities to refurbish and modernize the Digfer Hospital's infrastructure and services
in keeping with international standards In January 2015, the hospital was officially reopened at
an inauguration ceremony in Mogadishu led by President of Somalia Hassan Sheikh Mohamoud
and President of TurkeyRecepTayyipErdoğan.TheDigfer Hospital was concurrently
renamed Edrogan Hospital in honour of Edrogan. The renovated 200-bed Somalia-Turkey
Training and Research Hospital was constructed by Turkeys international development body,
the Turkish InternationalCooperation and Development Agency (TIKA) It has a $135.7 million
operating budget, $85.6 million of which is slated to be covered by the Turkish authorities over
the next five years.

Facilities and services includes the 13,500 square-meter indoor premises includes 20
neonatal incubators, 14 newborn intensive care beds, 12 intensive care beds, 4 operating rooms,
and laboratory and radiology units. Additionally, it has general surgery, neurosurgery, plastic
surgery, childcare, obstetrics, urology,medicine, anesthesia, dentistry and optometry department.
As of January 2015, the hospital had about 91 Somali and 52 Turkish hospital administrators,

4
head doctors, administrative directors or financial directors, as well as 40 Somali and 5 Turkish
security personnel. Around 36 Somali assistants are also scheduled to participate in the facility's
annual training program.The area also recovery is patient area patient area is large area I think
and most important part in hospital is how to take care patient. There is no network it is just has
one branch and that branch headquarter is Mogadishu Somalia.

2.3 Ordakhan Hospital System

According to (Kenneth, 2015) Ordakhan Hospital Management System, the Hospital uses
hospital management system which is user friendly simple, fast, and cost – effective. It deals
with the collection of patient’s information, diagnosis details, etc. Traditionally, it was done
manually. It is use system that is register and store patient details and doctor details and retrieves
these details as and when required, and also to manipulate these details meaningfully System
input contains patient details, diagnosis details, while system output is to get these details on to
the screen.

The Hospital Management System can be entered using a username and password. It is
accessible either by an administrator or receptionist. Only they can add data into the database.
The data can be retrieved easily. The data are well protected for personal use and makes the data
processing very fast. This hospital management system is an integrated healthcare solution which
includes Outpatient and Inpatient Management, Pharmacy, Laboratory, Radiology, Ward
Management, Online Appointments Scheduling, Secured Messaging, Doctor Portal, Patient and
Family Portals, Medical Electronic Billing. The system sends the text or email and improves the
quality of patient care. The system have advanced electronic medical record (EMR Systems)
which helps to be aware of revenue stream, patient records and other key metrics at your
fingertips. This system contains the follow modules: Admission (Inpatient and Outpatient); Staff
Details Payroll Personnel Details, Attendance. On Duty Shift Billing Inpatient Outpatient,
Consultation, Ward Details Ambulance Service Drive Ambulance

2.4 Shifo Hospital System

According to (R.BALAJI, 2010)Shifo hospital system was created by PHP programming

language and manages information in that hospital perfectly. The system have good quality of
user-interface, secure aspects, updates, deletes, retrieves of records. The system also has data

5
consistence and well relationship among the modules or tables. The system contains many
modules which specified what function they are doing. Shifo Hospital system contains these
Modules.

Patient Table: It keeps track of all details about both in-patient and out-patient. Patient id, patient
name, address, admitted date, doctor name, and room no are entered in a form and stored for
future reference. Also particular patient details can be viewed in the table using a separate form
with an attribute patient id.

Outpatient Table: This module manages activities related to patient who visits the Hospital
Resident Doctor or Consultant Doctor for Medical Consultations, diagnosis and treatment.

Inpatient Table: Admission request will be made here. Request for admission is made before
patient admitting the hospital.

Salary Table: This module contains the details salary for the doctors and nurse. This salary
calculated basic salary, PF, HRA, and year increment for the staffs from date of joining
automatically calculated.

Ward Details: This module enters and stores the details about each ward of the hospital for future
reference. Individual ward detail can be viewed in the table using ward id .The attributes used in
storing a ward detail is ward id, ward name, floor no, no of rooms.

2.5 Alorstar hospital System

According to (Georgio, 2014)This system is based Content Management System especially

Word press and this system contains these modules: The entire project mainly consists of 7
modules, which are Admin module: Manage department of hospitals, user, doctor, nurse,
pharmacist, Laboratorist ,accounts; Watch appointment of doctors; Watch transaction reports of
patient payment; Bed ,ward, cabin status; watch blood bank report; Watch medicine status of
hospital stock; Watch operation report watch birth report; Watch diagnosis report; watch death
report.User module (patient): View appointment list and status with doctors; View prescription
details; View medication from doctor; View doctor list; View blood bank status; View operation
history; View admit history, like bed, ward icu etc; Manage own profile

6
Doctor module: Manage patient account opening and updating; create, manage appointment with
patient; Create prescription for patient; Provide medication for patients; Issue for operation of
patients and creates operation report; Manage own profile.Nurse module: Manage patient.
account opening and updating; Allot bed, ward, cabin for patients; Provide medication according
to patient prescription; Manage blood bank and update status; Keep record of patient operation,
baby born and death of patient; Manage own profile.Pharmacist module: Maintain medicine;
Keep records of hospitals stock medicines and status; Manage medicine categories; Watch
prescription of patient; Provide medication to prescriptions.Laboratorist module: Watch
prescription list; Upload diagnostic report; Preview of report files, like x-ray images, ct scan, mri
reports; Manage own profile.Accountant module: Create invoice for payment; Order invoice to
patient; Take cash payment; Watch payment history of patients; Manage own profile.

2.6 AL-Dar Hospital Management Information System

According to (Helson, 2001)Function of the system is to register and store patient details and
doctor details and retrieve these details as and when required, and also to manipulate these
details. which are widely used in many hospitals in Burma mainly to provide easier and faster
way for daily medical tasks /activities with a GUI and provides for overcoming some of the
Hospital Management Information(HMIS

2.7 Proposed Edrogan Hospital Management Information System

The proposed Edrogan Hospital Management System is designed for any hospital to replace their
existing manual paper based system. The new system is to control the information of patients,
room availability, staff and operating room schedules and patient invoices. These services are to
be provided in an efficient, user friendly simple, fast, secure, cost effective manner, with the goal
of reducing the time and resources currently required for such tasks. This hospital management
system is an integrated healthcare solution which includes Outpatient and Inpatient Management,
Pharmacy, Laboratory, Radiology, Ward Management, Online Appointments Scheduling,
Secured Messaging, Doctor Portal, Patient and Family Portals, Medical Electronic Billing. The
system sends the text or email and does not improve the quality of patient care. The new system
have advanced electronic medical record (EMR Systems) which helps to be aware of revenue

7
stream, patient records and other key metrics at your fingertips. I want the new system have same
feature the above system (Ordakhan Hospital System).

8
 CHAPTER THREE: METHODOLOGY

3.1 Patient management system development life cycle of methodologies

System Development Life Cycle (SDLC) is a methodology that is typically used to develop,

maintain and replace information systems for improving the quality of the system design and

development process. The typical phases are analysis, estimation, design, development,

integration and testing and implementation. The success of software largely depends on proper

analysis, estimation, design and testing before the same is implemented. This article discusses

SDLC in detail and provides guidance for building successful system.

Figure 1: SDLC

3.1.1 System development life cycle models

SDLC models which stands for System Development Life Cycle models. SDLC – is a
continuous process, which starts from the moment, when it’s made a decision to launch the
project, and it ends at the moment of its full remove from the exploitation. There is no one single
SDLC model. They are divided into main groups, each with its features and weaknesses

9
The most used, popular and important SDLC models are given below:

3.1.2 Waterfall model

The Waterfall Model was the first Process Model to be introduced. It is also referred to as
a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model,
each phase must be completed before the next phase can begin and there is no overlapping in the
phases.

Figure 2: waterfall model

3.1.3 Incremental/Iterative model

The iterative model is repetition incarnate. Instead of starting with fully known requirements,
project teams implement a set of software requirements, then test, evaluate and pinpoint further
requirements. A new version of the software is produced with each phase, or iteration. Rinse and
repeat until the complete system is ready. Advantages of the iterative model over other common
SDLC methodologies is that it produces a working version of the project early in the process,
and makes it less expensive to implement changes. One disadvantage: repetitive processes can
consume resources quickly

10
Figure 3: Iterative model

3.1.4 V-shaped model

The V-Model, also called the Vee-Model, is a product-development process originally developed
in Germany for government defense projects. It has become a common standard
in software development. The V-Model gets its name from the fact that the process is often
mapped out as a flowchart that takes the form of the letter V. The V-Model, also called the Vee-
Model, is a product-development process originally developed in Germany for government
defense projects. It has become a common standard in software development. The V-Model gets
its name from the fact that the process is often mapped out as a flowchart that takes the form of
the letter V.

11
Figure 4: V-shaped model

3.1.5 Agile model:

. In the agile model, “fast failure” is a good thing. The approach produces ongoing release cycles,
each featuring small, incremental changes from the previous release. At each Iteration, the
product is tested. The agile model helps teams identify and address small issues on projects
before they evolve into more significant problems, and engage business stakeholders and get
their feedback throughout the development process.

Figure 5: Agile model,

12
3.1.6 Spiral model

The spiral model combines the idea of iterative development with the systematic, controlled
aspects of the waterfall model. This Spiral model is a combination of iterative development
process model and sequential linear development model i.e. the waterfall model with a very high
emphasis on risk analysis. It allows incremental releases of the product or incremental
refinement through each iteration around the spiral.

The spiral model has four phases. A software project repeatedly passes through these phases in
iterations called Spirals

Figure 6: Spiral model

3.2 Planning and Requirement Collection Method

Planning for the quality assurance requirement and identification of the risk associated with the
project is also done in the planning stage. The outcome of the technical feasibility study is the
define the various technical approaches that can be follow to implement the project successfully
with minimum risk.

Requirement collection methods are Observation, Interviewing and Questionnaires as my

research methods. Through this I was able to collect raw data on PRMS at Edrogan Hospital
where existing reports on the current system were obtained. Verbal interview techniques were
used to interview employees from the hospital

13
3.2.1 Observation

I went to the hospital and observed their daily as regards their current system and they were
manually recording the patients‟ records as specified by the receptionists, doctors, pharmacist
and cashier. The observation was made to determine the time it took to carry out the patient
record Management. I observed the system’s weaknesses like it was vulnerable to errors.

3.2.2 Interview

Interview was my choice to collect data and with it I was able to collect raw data of patient
Management system. In Interview there was interaction between us, the researcher and the staff.
Interviews will be conducted within the Financial Office and some of the potential employees to
find out what difficulties they encountered with the existing manual system. These interviews
where held to verify the information collected using in the questionnaires method

3.3 Requirements Analysis and Specification Methods

A Software requirements Analysis, a requirements specification for a software system, is a

complete description of the behavior of a system to be developed and may include a set of use
cases that describe interactions the users will have with the software. In addition it also contains
non-functional requirements. Non-functional requirements impose constraints on the design or
implementation (such as performance engineering requirements, quality standards, or design
constraints).

3.3.1 System Structure Analysis

System structure analysis is a development method that allows the analyst to understand the
system and its activities in a logical way. It is a systematic approach, which uses graphical tools
that analyze and refine the objectives of an existing system and develop a new system
specification which can be easily understandable by user. It has following attributes .

The tools, which were employed during this methodology stage, were tables, Flow Charts, Data
Flow Diagrams (DFDs), Entity Relationship Diagrams (ERDs), Unified Modeling Language
(UML), Use Case, Activity, Class Diagram. The design ensures that only allows authorized users
to access the systems information

14
3.3.1.1 Flow Chart Diagram

Flowcharts are used in designing and documenting simple processes or programs. Like other
types of diagrams, they help visualize what is going on and thereby help understand a process,
and perhaps also find less-obvious features within the process, like flaws and bottlenecks. There
are different types of flowcharts: each type has its own set of boxes and notations. The two most
common types of boxes in a flowchart are: a processing step, usually called activity, and denoted
as a rectangular box. a decision, usually denoted as a diamond.

3.3.1.2 Data Flow Diagram

Data Flow Diagram is a graphical representation of the "flow" of data through an information
system, modeling its process aspects. A DFD is often used as a preliminary step to create an
overview of the system without going into great detail, which can later be elaborated. DFDs can
also be used for the visualization of data processing viewed in structured design. DFD is easy to
understand the flow of data through systems with the right data flow diagram software.

3.3.1.3 Entity Relationship Diagram

An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.
An entity in this context is an object, a component of data. An entity set is a collection of similar
entities. These entities can have attributes that define its properties.

3.3.2 Object-Oriented Analysis

Object-Oriented Analysis This phase concerns with determining the system requirements and to
understand the system requirements build a use-case model. A use-case is a scenario to describe
the interaction between user and computer system. This model represents the user needs or user
view of system. It also includes identifying the classes and their relationships to the other classes
in the problem domain, that make up an application.

3.3.2.1 Unified Modeling Language

Unified Modeling Language is a standardized modeling language consisting of an integrated set

of diagrams, developed to help system and software developers for specifying, visualizing,

15
constructing, and documenting the artifacts of software systems, as well as for business modeling
and other non-software systems. The UML represents a collection of best engineering practices

3.3.2.2 Class diagram

A Class diagram in the Unified Modeling Language (UML) is a type of static structure diagram
that describes the structure of a system by showing the system's classes, their attributes,
operations (or methods), and the relationships among objects.The class diagram is the main
building block of object-oriented modeling. It is used for general conceptual modeling of the
systematic of the application, and for detailed modeling translating the models into programming
code. Class diagrams can also be used for data modeling. The classes in a class diagram
represent both the main elements, interactions in the application, and the classes to be
programmed.

3.3.3 Requirements Specifications

After analyzing the data collected, we formulated a number of requirements namely user
requirement, system hardware software attribute. These were grouped as user, functional, non-
functional and systems requirements.

3.3.3.1 User requirement

For effective use of the system, it is important that users are fully involved and are given
opportunities to participate as much as possible This rectifies numerous problems associated with
change management, users getting accustomed to using new way of doing things as opposed to

traditional system of patient records management system. During data collection, the researcher
investigated and found out how the current system operates, not only that but also tried out
which problems are faced and how best they can be settled. The users described some of the

basic requirements of the system as; Search for patients, Register staff., Update, staff records,
patients, View all types of reports., Assign access rights and privileges to the system users

16
3.3.3.2 Functional Requirement

The following is the desired functionality of the new system. The system should accept have
submissions in form of raw patients, staff, and drug supply at the submitting point. The system
should perform analysis of financial, drug inventory, patients, and drug supply. The system
should authenticate the users of the system. The system should generation of reports on request.
The system should only allow the administrator to delete records in the database.

3.3.3.3 Non Functional Requirement

The system should must verify and validate all user input and users must be notified in case of
errors detected in the course of using the system. The system should allow room for expansion
.A system should have a high performance and reliability level

3.3.3.4 System Requirements

A system requirement is done by the system such as store the necessary information of drugs,
prepare bill for patient, give weekly reports easily searching of patient

3.3.3.4.1 Hardware Interfaces

Processor: AMD C-60 APU With Radeon(tm) HD Graphic 1.00GHz

RAM: 2.00 GB or above

Hard Disk: 350GB or above

3.3.3.4.2 Software Interfaces

OPERATING SYSTEM: Windows 7

FRONT END: Microsoft Visual Studio (VB.NET) 2010

Microsoft SQL SERVER, 2014.

BACK END: MYSQL

17
3.4 System Design& Architecture

After interpretation of the data, tables were drawn and process of data determined to guide the
researcher of the implementation stage of the project. The tools, which were employed during
this methodology stage, were mainly tables, Data Flow Diagrams (DFDs) and Entity
Relationship Diagrams (ERDs).The design ensures that only allows authorized users to access
the system’s information.

3.4.1 Logical model

Figure 7: logical flow of data in PRMS

18
 3.4.1.1 Data Flow Diagram (DFD)

IPD&OPD

Admin Level-0 Patient

Personal Personal details
Hospital
report, bills generate
Management
Bill, Report Detail System Patient
Admin

1.0 Patient
Admin Personal details of patient Detail Update Patient db

Update

Personal Details of doctor 2.0 Doctor

Admin Detail

Figure 8: Data flow diagram

3.4.1.2 Entity Relationship Diagram (ERD)

Departmen
Address Address Age
Name t Name
D id
P_id
1 m
Patient phone
Doctor Treats

Phone Gender
Gende Figure 9: Entity Relation Diagram (ERD)
r

19
3.4.2.1 Class Diagram

Figure 10: Class diagram

3.4.2.2 Case Diagram

Figure 11: case diagram

20
3.4.3 System Architecture

This gives a high level view of the new system with the main components of the system and the
services they provide and how they communicate. The system is implemented using a three tier
architecture that comprises of user interface, process management and DBMS as illustrated
below.

Figure 12: system Architecture of Edrogan hospital

3.5 System Implementation

This describes the tools used to implement the graphical user interface and the database. MySQL
was used to create and connect relational tables to the database. was used to develop the GUI.
Vb.net was used to process queries and integrate interfaces was done to develop the model that
meets all the requirements of this system.

Front end vb.net, java, c#, c++

Back end MySQL, SQL server, Access, oracle , xampp

21
3.5.1 Front End
VB.Net is a simple, modern, object-oriented computer programming language developed by
Microsoft to combine the power of .NET Framework and the common language runtime with
the productivity benefits that are the hallmark of Visual Basic.
This tutorial will teach you basic VB.Net programming and will also take you through various
advanced concepts related to VB.Net programming language

3.5.2 Back End

SQL Server 2014 was released to manufacturing on March 18, 2014, and released to the general public
on April 1, 2014 and the build number was 12.0.2000.8 at release. Until November 2013 there were
two CTP revisions, CTP1 and CTP2. SQL Server 2014 provides a new in-memory capability for tables
that can fit entirely in memory (also known as Hekaton). Whilst small tables may be entirely resident
in memory in all versions of SQL Server, they also may reside on disk, so work is involved in
reserving RAM, writing evicted pages to disk, loading new pages from disk, locking the pages in
RAM while they are being operated on, and many other tasks.

For disk-based SQL Server applications, it also provides the SSD Buffer Pool Extension, which
can improve performance by cache between RAM and spinning media. SQL Server 2014 also
enhances the Always On (HADR) solution by increasing the readable secondaries count and
sustaining read operations upon secondary-primary disconnections, and it provides new hybrid
disaster recovery and backup solutions with Microsoft Azure, enabling customers to use existing
skills with the on-premises version of SQL Server to take advantage of Microsoft's global

Datacenters In addition, it takes advantage of new Windows Server 2012 and Windows Server
2012 R2 capabilities for database application scalability in a physical or virtual environment.
Microsoft provides three versions of SQL Server 2014 for downloading: the one that runs
on Microsoft the SQL Server 2014 CAB, and SQL Server 2014 ISO. SQL Server 2014 SP1,
consisting primarily of bug fixes, was released on May 15, 2015. SQL Server 2014 is the last
version available on x86/IA32 architecture. SQL Server is the best back end program because he
is good in database creating special in hospital and other database creating.

Deployment of system − once the functional and non-functional testing is done; the product is
deployed in the customer environment or released into the market.

22
Maintenance − there are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer environment.

3.6 System testing

System testing is testing conducted on a complete integrated system to evaluate the system's
compliance with its specified requirements System testing takes, as its input, all of the integrated
components that have passed integration testing. The purpose of integration testing is to detect
any inconsistencies between the units that are integrated together (called assemblages). System
testing seeks to detect defects both within the "inter-assemblages" and also within the system as
a whole .System testing is performed on the entire system in the context of a Functional
Requirement Specification(s) (FRS) and/or a System Requirement Specification (SRS). System
testing tests not only the design, but also the behavior and even the believed expectations of the
customer. It is also intended to test up to and beyond the bounds defined in the software/hardware

3.6.1 System Unit Testing

Unit testing was carried out on individual modules of the system to ensure that they are fully
functional units. We did this by examining each unit, for example the Underwriter’s page. It was
checked to ensure that it functions as required and that it adds electricity data and other details
and also ensured that this data is sent to the database. The success of each individual unit gave us
the go ahead to carryout integration testing. All identified errors were dealt with.

3.6.2 Integration Testing

We carried out integration testing after different modules had been put together to make a
complete system. Integration was aimed at ensuring that modules are compatible and they can be
integrated to form a complete working system. For example we tested to ensure that when a user
is logged in, he/she is linked to the appropriate page, and also could access the database.

3.6.3 System Testing

As one of the specific objectives of this study, validation of the system was very important.
Validation of the system was done by comparing it to the questions asked by the users Aloog

23
electricity Most of their answers matched with what the system can do. Vb.net was used to
validate user input and the respective input. For example the system does not accept blank field;
the system also discriminate between numerical and numerical character

3.7 System Change over Methods

The process of putting the new information system online and retiring the old system is known as
system changeover. There are four changeover methods which are:

3.7.1 Direct cutover:

The direct cutover approach causes the changeover from the old system to the new system to
occur immediately when the new system becomes operational. It is the least expensive but
involves more risks than other changeover methods.

3.7.2 Parallel operation:

The parallel operation changeover method requires that both the old and the new information
systems operate fully for a specified period. Data is input to both systems and output generated
by the new system is compared with the equivalent output from the old system. When users,
management, and IT group are satisfied that the new system operates correctly then the old
system is terminated. It is the most costly changeover method and involves lower risks.

3.7.3 Pilot operation

The pilot changeover method involves implementing the complete new system at a selected
location of a company. Direct cutover method and operating both systems for only the pilot site.
The group that uses the new system first is called the pilot site. By restricting the implementation
to a pilot site reduces the risk of system failure as compared with is less expensive than a parallel
system.

3.7.4 Phased operation:

The phased operation changeover method involves implementing the new system in stages, or
modules. We can implement each subsystem by using any of the other three changeover
methods. In this approach risk of errors or failures is limited to the implemented module only as
well as it is less expensive than the full parallel operation.

24
 CONCLUSION

The project Hospital Management System (HMS) is for computerizing the working in a hospital.
It is a great improvement over the manual system. The computerization of the system has speed
up the process. In the current system, the front office managing is very slow. The hospital
managing system was thoroughly checked and tested with dummy data and thus is found to be
very reliable. The software takes care of all the requirements of an average hospital and is
capable to provide easy and effective storage of information related to patients that come up to
the hospital. It generates test reports and also provides the facility for searching the details of the
patient. It also provides billing facility on the basis of patient’s status whether it is an indoor or
outdoor patient. The system also provides the facility of backup as per the requirement. The
study findings and limitations give rise to a number of recommendations for research and
implications for practice. Recommendations are identified for future research in the general area
of patient involvement in patient safety, together with suggestions for further development and
evaluation of the interventions from this programmer to help explore further aspects of the
programmer’s potential

25
 REFERENCES

Georgio, M. (2014). Software pragramming. newyork: Adventure works Press.

Helson, A. (2001). Wattanosoth. Bangkok: Wariang.

Kenneth, C. (2015, july 23). system of software. Retrieved november 12, 2018, from Ordokhan
Hospital management system: http//:www.Ordokhan hospital.org

Mc graw, h. (2004). management system of college . london: george werthman.

Mc leod, r. (2000). management information sytem/ray mc leod,george schell. texas: prentice-

hill,inc.

Mohamed, A. (2018, november 3). manager to erdogan hospital system. (m. h. mohamoud,
Interviewer)

O'Brien, J. A. (2001). computer information system in the collage of bussiness adminstration at

northerm arizona un. oregan: von,hoffman press.

Patrick. (2014, january 4). patient managent report. Retrieved november 3, 2018, from
patient.com: http://www.pateint system.com

R.BALAJI. (2010, juun 23). shifo hspital. Retrieved november 2, 2018, from shifo hospital
system: http://www.shifo hospital.com

Raymond, M. (2001). george schell university of texas at austin. texas: works press.

Raymond, m. (2002). george schell,university of texas at austin. texas: adventure.

26
 APPENDICES

APPENDIX A

APPENDX B

APPENDIX C

27
28