HOSPITAL MANAGEMENT SYSTEM

A PROJECT REPORT
Name:Omar Mohamed mahmoud
Id: 12100479

Name: Zakaria Elsayed Salama

Id: 12100337

Name: Ayman Awad Mostafa

Id:12100210
 Preface
In this study, we will examine the implementation of a hospital
management system, the implementation of the principles of
good design, customisation, and software engineering, as well as
the principles of the system's success and its proper
implementation. Moreover, the reasons why the regulations
failed.
System requirements, device specifications that will function with
the System, and an agent's perspective on the System's ongoing
development to ensure high efficiency
Table of contents
Chapter 1: INTRODUCTION
1.1 ABSTRACT .............................................................................................3.
1.2 Introduction.................................................................................3.
1.3 Goals..................................................................................5.
1.4 Objective.................................................................................5.
1.5 Scope of the Project..................................................................................5.
1.6 DefinItions and abbreviations……………………………………………………6.
1.7 Modules.................................................................................7.
1.8 user module................................................................................7.
1.9 Admin module................................................................................7.
1.10 Doctor module.................................................................................8
1.11 Nurse module.................................................................................8
1.12 Pharmacist module................................................................................ 8
1.13 User Requirements Definition.............................................9

Chapter 2: DESIGN

2.1 SYSTEM DESIGN:........................................................................................11

2.1.INTRODUCTION TO UML............................................................................................…11
2.2 UML Approach....................................................................................................12
2.3 Use case diagram of our project..............................................12
2.4 Class Diagram:..........................................................................13
2.5 Sequence diagram............................................................................13
2.6 Activity diagram................................................................ 14
2.7 Data flow diagram:..........................................................................…14

CHAPTER 1 INTRODUCTION

1.1 ABSTRAC:
An structured computerised system called a hospital management
system was created and configured to handle the day-to-day
management and operations of the hospital.
activities. The software can handle inpatients, outpatients, records, and
databases.
therapies, current illnesses, lab and pharmaceutical billings. The
hospital is also maintained.
 information such the name of the ward, the doctors in charge, and the
department in charge. The
getting a report after a session is a serious issue for patients these
days, numerous
The hospital manages reports on their system, but the patient cannot
access them when they are needed.
She's out there. We will include an additional facility to store the
materials in this project.
database and make it accessible from anywhere in the world.
1.2 Introduction:
The hospital management system project comprises automated billing
in the labs and pharmacy as well as patient registration and data
storage. Every patient can receive a unique ID from the software, which
also automatically stores staff and patient information. It has a search
feature so you can see how each room is doing right now. Using the ID,
a user can look up a doctor's availability and a patient's information.
With the use of a login and password, one can access the Hospital
Management System. A receptionist or an administrator can access it.
They alone are able to add data to the database. The information is
simple to retrieve. The user experience is excellent. Data processing is
quick because the data are well safeguarded for personal use.
The Hospital Management System was created with the intention of
providing hospitals with tangible, imaginable advantages. It is strong,
adaptable, and simple to use. A comprehensive variety of hospital
management and administrative processes are covered by the Hospital
 Management System, which is developed for multispecialty facilities. It
is an integrated end-to-end hospital management system that offers
pertinent data throughout the facility to enable efficient decision-
making for patient care, hospital operations, and crucial financial
accounting in a smooth flow. Clinical process analysis and activity-
based pricing are two areas where the Hospital Management System, a
software product package, is intended to improve the quality and
management of hospital management. With the aid of a hospital
management system, you may grow your business and enhance its
productivity and level of service. You may manage your processes by
effectively managing the core processes that are essential to the
hospital's performance.

1.3 Goals:
1-User friendly
2-Simple fast
3-Low cost and effective
4-It deals with the collection of patient’s information
5- Diagnosis

1.4 Objective:
1) What is a hospital?
2) Documenting data about the patients who arrive.
3) Producing invoices.
4) Documenting the details of the diagnostic provided to patients.
 5) Maintaining a record of the vaccinations given to patients or
children.
6) Keeping knowledge of various illnesses and treatments available.

These are the different tasks that the operational staff and doctors
must complete in a hospital. These projects are all completed on paper.

1.5 Scope of the Project:

1) The patient's name, age, and gender are all that are needed to
provide information about the patient. Every time the patient comes
up, new data is stored about him.
2) To create bills, prices for all services rendered to patients are listed
separately on different sheets, and the total is then calculated.
3) Patients are typically informed of their diagnoses via a paper that
also incorporates patient data. To reduce the amount of paper in the
office, it is destroyed after a certain amount of time.
4) Children's immunisation records are stored on pre-formatted sheets
that are retained in a file.
5) No records of information on various ailments are retained. Doctors
themselves carry out this work by keeping track of numerous
medications.

1.6 DEFINITIONS and Abbreviations

 A class diagram is a specific kind of static structural diagram that
demonstrates a system's classes, properties, operations, and
relationships between the classes in order to illustrate the structure of
the system.
Efficiency is a software product's capacity to deliver adequate
performance in relation to the quantity of resources used under
specified conditions.
Reliability: The capability of the software product to carry out its given
functions under specified circumstances for a predetermined amount
of time or predetermined actions.
Redundancy: Repeating the same information in many places.
Scalability: The software product's capacity to be upgraded to handle
rising loads.
Security: A software product's capacity to prevent unauthorised access,
whether intentional or unintentional, to programmes and data

1.7 MODULES:
The seven modules that make up the complete project are: Admin
module
▪ Module for users (patient)
▪ Admin module
▪ Module for doctors
▪ Nursing module
▪ Pharmaceutical module
1.8 Module for users (patient):
▪ View your doctor's appointment schedule and status.
▪ View prescription details
▪ View medication from doctor
▪ View doctor list
▪ View blood bank status
▪ View operation history
▪ View admit history. like bed

1.9 Admin module:

▪ control user, doctor, nurse, pharmacist, and lab technician accounts for the
hospital department.
▪ watch the doctor's appointment.
▪ watch transaction reports of patient payment.
▪ watch blood bank report.
▪ operational report.
▪ watch birth report.

1.10 Module for doctors:

▪ Make and manage patient appointments.
▪ Write the patient a prescription.
▪ Give patients their medications.
▪ Issue for operation of patients and creates operation report

1.11 Nursing module:

 ▪ Provide medication according to patient prescription.
▪ Give a bed, ward.
▪ Manage the blood bank and the statistics.
▪ Keep records of patient births, operations, and deaths.
1.12 Pharmacist module:
▪ Maintain medicine.
▪ Maintain records of hospital drug supplies and patient status.
▪ Track the patient's prescriptions.
▪ Provide medication to prescriptions.

1.13User Requirements Definition:

The framework will be used in all emergency rooms, medical facilities,

pharmacies, and pathology labs. Using the data collected from patients and
storing it for later use in the facility's dispensary or pathology The currently
employed framework is a paper-based structure. The system is designed to
reduce overtime compensation and increase the number of patients who
can be treated accurately, however it is overly conservative and unable to
provide updated patient arrangements in a timely manner. In these
publications, necessity is expressed in both beneficial and ineffective, The
system will offer a variety of services, including registering the names of
patients, employees, doctors, officials, medical services, payment
operations, reservations, and personal information specific to each patient,
as well as examination rooms, patients, discounts, and doctor specialties, as
well as non-essential services like data protection and backup. additionally,
keep the system updated regular reports on patients, employees, and
physicians The system will provide patient reports, appointments, and
approval of the reservation by email to doctors with addiction-related
powers.

Requirements :

1- Patient database

2 -Security

3 -Checkout

4 -Registration

5 -Doctor database

6 -Nurse database

7 -Assign department database

8 -Testing

9-Documentation
Chapter 2: DESIGN
2.1.1 INTRODUCTION TO UML:
The software system and its components can be specified, visualised,
built, and documented using the Unified Modeling Language (UML),
which is a standard language. It is a graphical language that offers a
lexicon and set of grammar rules.grammar and rules. The UML is
primarily concerned with the conceptual and actual representation
ofthe programme. It records the choices and perceptions of the
necessary systems.constructed. It is utilised for comprehension, design,
configuration, upkeep, and administration.details regarding the systems

2.2 UML Approach:

UML Diagram

Using a connected graph of vertices and arcs, a diagram provides a

visual representation of a set of items. Diagrams are projections into
systems that you create to see a system from different angles. A
diagram represents an obfuscated view of the system's constituent parts
for all but the most elementary systems. The same element could be
depicted in every diagram, just a few diagrams, or not at all. A diagram
might theoretically include any assortment of elements and
connections.
 The five most practical viewpoints that make up the architecture of a
software-intensive system are consistent with a small number of
common combinations that emerge in practise. Due to this, the UML
features nine such diagrams:

1. Use case diagram

2. Class diagram
3. Sequence diagram
4. Activity diagram
5. Data flow diagram

2.3 Use case diagram of our project:

2.4 Class Diagram:

2.5 Sequence diagram:

2.6 Activity diagram:
2.7 Data flow diagram: Level Zero

Data flow diagram: Level one

Data flow diagram: Level Two
Time plan for hospital management system