AN

PROJECT REPORT
ON
HOSPITAL MANAGEMENT SYSTEM PROJECT
BY
KAMAL ACHARYA
(Tribhuvan University)

Date: 2020/08/10
TABLE OF CONTENTS
1.1 Introduction: .................................................................................................................... 2
1.2 Problem Introduction: ...................................................................................................... 2
1.3 Goals ............................................................................................................................... 2
1.4 Objective ......................................................................................................................... 3
1.5 Scope of the Project ......................................................................................................... 3
1.6 Modules .......................................................................................................................... 3
1.7 Views .............................................................................................................................. 3
1.8 Viewpoints ...................................................................................................................... 4
1.9 Perspective ...................................................................................................................... 5
1.10 Implementation ............................................................................................................. 5
1.11 Diagrams ....................................................................................................................... 6
Use Case Diagram ............................................................................................................. 6
Activity Diagram ............................................................................................................... 7
Class Diagram ................................................................................................................... 8
Communication Diagram ................................................................................................... 8
Component Diagram.......................................................................................................... 9
Deployment Diagram ........................................................................................................ 9
ER-Diagram .................................................................................................................... 10
Package Diagram ............................................................................................................. 11
Sequence Diagram ........................................................................................................... 12
State Diagram .................................................................................................................. 13
1.12 Selected Pattern ........................................................................................................... 13
1.13 Architecture Diagram .................................................................................................. 13
1.14 REASON FOR CHOOSING LAYERED PATTERN ................................................... 14
1.15 Conclusion and Reference ........................................................................................... 15

1|Page
1.1 Introduction:
The project Hospital Management system includes registration of patients, storing their details
into the system, and also computerized billing in the pharmacy, and labs. The software has the
facility to give a unique id for every patient and stores the details of every patient and the staff
automatically. It includes a search facility to know the current status of each room. User can
search availability of a doctor and the details of a patient using the id. 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 interface is very user-friendly. The data are well protected for personal use
and makes the data processing very fast. Hospital Management System is powerful, flexible,
and easy to use and is designed and developed to deliver real conceivable benefits to hospitals.
Hospital Management System is designed for multispecialty hospitals, to cover a wide range
of hospital administration and management processes. It is an integrated end-to-end Hospital
Management System that provides relevant information across the hospital to support effective
decision making for patient care, hospital administration and critical financial accounting, in a
seamless flow. Hospital Management System is a software product suite designed to improve
the quality and management of hospital management in the areas of clinical process analysis
and activity-based costing. Hospital Management System enables you to develop your
organization and improve its effectiveness and quality of work. Managing the key processes
efficiently is critical to the success of the hospital helps you manage your processes.

1.2 Problem Introduction:

Lack of immediate retrievals The information is very difficult to retrieve and to find particular
information like- E.g. - To find out about the patient’s history, the user has to go through various
registers. This results in in convenience and wastage of time.

Lack of immediate information storage The information generated by various transactions

takes time and efforts to be stored at right place.

Lack of prompt updating Various changes to information like patient details or immunization
details of child are difficult to make as paper work is involved.
Error prone manual calculation Manual calculations are error prone and take a lot of time
this may result in incorrect information. For example, calculation of patient’s bill based on
various treatments. Preparation of accurate and prompt reports: - This becomes a difficult
task as information is difficult to collect from various register.

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

2|Page
1.4 Objective
1) Define hospital
2) Recording information about the Patients that come.
3) Generating bills.
4) Recording information related to diagnosis given to Patients.
5) Keeping record of the immunization provided to children/patients.
6) Keeping information about various diseases and medicines available to cure them.
These are the various jobs that need to be done in a Hospital by the operational staff and
Doctors. All these works are done on papers.

1.5 Scope of the Project

1) Information about Patients is done by just writing the Patients name, age and
gender. Whenever the Patient comes up his information is stored freshly.
2) Bills are generated by recording price for each facility provided to Patient on a
separate sheet and at last they all are summed up.
3) Diagnosis information to patients is generally recorded on the document, which
contains Patient information. It is destroyed after some time period to decrease
the paper load in the office.
4) Immunization records of children are maintained in pre-formatted sheets, which
are kept in a file.
5) Information about various diseases is not kept as any document. Doctors
themselves do this job by remembering various medicines.

All this work is done manually by the receptionist and other operational staff and lot of papers
are needed to be handled and taken care of. Doctors have to remember various medicines
available for diagnosis and sometimes miss better alternatives as they can’t remember them at
that time.

1.6 Modules
 Admin module
 Doctor module
 Nurse module
 Pharmacist module
 Laboratory’s module
 Accountant module

1.7 Views
1. Functional View This view defines the functional requirements of the HMS. It
specifies the tasks that the system should be able to perform, the roles of different users,
and the interactions between users and the system. The functional view documents the
features and capabilities of the system, such as patient registration, appointment
scheduling, billing, and medical records management.
2. Technical View This view describes the technical aspects of the HMS. It includes the
system architecture, hardware and software requirements, and the integration of the

3|Page
 system with other hospital systems. The technical view documents the technical
specifications of the system and provides guidelines for system installation,
configuration, and maintenance.
3. Process View This view focuses on the processes involved in the HMS. It describes the
workflows, procedures, and policies that govern the operation of the system. The
process views document the steps involved in each process, including the inputs,
outputs, and the roles of the users involved.
4. User View This view presents the system from the perspective of the users. It includes
user manuals, training materials, and user interface design guidelines. The user view
documents the user interface, the interactions between the users and the system, and the
user experience.
5. Data View This view defines the data structures and relationships within the HMS. It
includes the database schema, data dictionaries, and data flow diagrams. The data view
documents the data elements, their attributes, and their relationships.
6. Security View This view addresses the security aspects of the HMS. It includes security
policies, access control mechanisms, and encryption techniques. The security view
documents the security features of the system and provides guidelines for ensuring the
confidentiality, integrity, and availability of the data.

1.8 Viewpoints
1. Functional Viewpoint This viewpoint focuses on the system's functional requirements
and represents the system's functionality from the perspective of hospital staff and
patients. Some views that can be included in this viewpoint are patient management,
appointment scheduling, billing, prescription management, inventory management, and
medical records management.
2. Technical Viewpoint This viewpoint focuses on the technical infrastructure that
supports the hospital management system. It includes views of the hardware, software,
and network architecture that make up the system, as well as the protocols and standards
used for data communication and storage.
3. Process Viewpoint This viewpoint focuses on the processes that are used to manage
and operate the hospital management system. It includes views of the workflows,
procedures, and policies that govern the use of the system, as well as the roles and
responsibilities of the various users and stakeholders.
4. User Viewpoint This viewpoint focuses on the needs and requirements of the users of
the hospital management system. It includes views of the user interface design, user
experience, and usability testing, as well as user training and support.
5. Data Viewpoint This viewpoint focuses on the data that is managed and processed by
the hospital management system. It includes views of the data models, data dictionaries,
and data flow diagrams, as well as data security and privacy policies.
6. Security Viewpoint This viewpoint focuses on the security and privacy of the hospital
management system. It includes views of the security policies, procedures, and
protocols that are used to protect the system from unauthorized access, data breaches,
and other security threats.

4|Page
1.9 Perspective
1. Functional Perspective This perspective outlines the functional requirements of the
HMS, including the tasks the system should be able to perform, roles of different users,
and interactions between users and the system. It provides documentation for system
features and capabilities such as patient registration, appointment scheduling, billing,
and medical records management.
2. Technical Perspective The technical perspective outlines the technical aspects of the
HMS, including system architecture, hardware and software requirements, and system
integration with other hospital systems. This perspective provides documentation for
the technical specifications of the system and provides guidelines for installation,
configuration, and maintenance.
3. Process Perspective The process perspective outlines the workflows, procedures, and
policies that govern the operation of the HMS. It provides documentation for the steps
involved in each process, including inputs, outputs, and user roles.
4. User Perspective The user perspective focuses on the system from the perspective of
the users, including user manuals, training materials, and user interface design
guidelines. It provides documentation for the user interface, user-system interactions,
and user experience.
5. Data Perspective The data perspective defines the data structures and relationships
within the HMS, including database schema, data dictionaries, and data flow diagrams.
It provides documentation for data elements, attributes, and their relationships.
6. Security Perspective The security perspective focuses on the security aspects of the
HMS, including security policies, access control mechanisms, and encryption
techniques. It provides documentation for security features and guidelines for ensuring
data confidentiality, integrity, and availability.

1.10 Implementation
1. Functional Viewpoint To implement the functional perspective to the functional
viewpoint, identify the functional requirements of the system from the perspective of
the hospital staff and patients. Then design views, such as use case diagrams, sequence
diagrams, and activity diagrams, to represent those functional requirements.
2. Technical Viewpoint To implement the technical perspective to the technical
viewpoint, identify the hardware, software, and network infrastructure needed to
support the hospital management system. Then design views, such as system
architecture diagrams and network topology diagrams, to represent the technical
infrastructure.
3. Process Viewpoint To implement the process perspective to the process viewpoint,
identify the workflows, procedures, and policies that govern the use of the hospital
management system. Then design views, such as process flow diagrams, swimlane
diagrams, and state machine diagrams, to represent those processes.
4. User Viewpoint To implement the user perspective to the user viewpoint, identify the
needs and requirements of the different types of users who will interact with the hospital
management system, such as hospital staff and patients. Then design views, such as
wireframes, user interface mockups, and user flow diagrams, to represent the user
interface and user experience.

5|Page
 5. Data Viewpoint To implement the data perspective to the data viewpoint, identify the
types of data that will be managed and processed by the hospital management system,
such as patient records, medical histories, and billing information. Then design views,
such as ER diagrams, data flow diagrams, and data dictionaries, to represent the data
models and data flows.
6. Security Viewpoint To implement the security perspective to the security viewpoint,
identify the security and privacy policies, procedures, and protocols that are needed to
protect the hospital management system from unauthorized access, data breaches, and
other security threats. Then design views, such as security architecture diagrams, threat
models, and access control matrices, to represent the security infrastructure and
protocols.

1.11 Diagrams
Use Case Diagram

6|Page
Activity Diagram

7|Page
Class Diagram

Communication Diagram

8|Page
Component Diagram

Deployment Diagram

9|Page
ER-Diagram

10 | P a g e
Package Diagram

11 | P a g e
Sequence Diagram

12 | P a g e
State Diagram

1.12 Selected Pattern

We have chosen layered architecture pattern for our project hospital management system.
The layered architecture pattern is a popular software design pattern that involves organizing
the software system into different layers based on their functionality and responsibilities. Each
layer is responsible for performing a specific set of tasks and communicates with the adjacent
layers in a defined manner.
To summarize, the architecture of a hospital management system is typically designed using
the layered architecture pattern, which involves separating the system into three main layers:
the presentation layer, business logic layer, data management layer and security layer. Each
layer has well-defined responsibilities and communicates with adjacent layers through well-
defined interfaces and protocols.

1.13 Architecture Diagram

13 | P a g e
1.14 REASON FOR CHOOSING LAYERED PATTERN
The layered architecture pattern is a popular software design pattern that involves organizing
the software system into different layers based on their functionality and responsibilities. Each
layer is responsible for performing a specific set of tasks and communicates with the adjacent
layers in a defined manner.
Here are a few reasons why it might be a good choice:
Separation of concerns The layered architecture pattern allows for a clear separation of
concerns between different parts of the system. Each layer can focus on a specific set of tasks,
which makes the code more modular, easier to maintain, and less prone to errors.
Scalability A layered architecture pattern can make it easier to scale the system horizontally or
vertically. Each layer can be scaled independently, which makes it easier to add new features
or improve performance.

14 | P a g e
Reusability The layered architecture pattern promotes code reuse by making it easier to isolate
and reuse specific components of the system. This can lead to faster development times, higher
code quality, and a more maintainable system.

1.15 Conclusion
The Hospital Management System is a powerful solution that can help hospitals improve their
operations, enhance patient satisfaction, and boost revenue. Its user-friendly interface and
intuitive workflows make it easy for healthcare professionals to access and manage patient
information, track resources, and optimize resource utilization. With its robust reporting and
analytics capabilities, hospitals can gain insights into their performance and make data-driven
decisions to drive continuous improvement.

Reference
Acharya, Kamal. "STUDENT INFORMATION MANAGEMENT
SYSTEM." Authorea Preprints (2023).
Acharya, Kamal. "Library Management System." Available at SSRN4807104 (2019).
ACHARYA, KAMAL, et al. "LIBRARY MANAGEMENT SYSTEM." (2019).
Acharya, Kamal. "Online bus reservation system project report." Authorea
Preprints (2024).
Acharya, Kamal. "Online bus reservation system project report." (2024).
Acharya, Kamal. “Online Bus Reservation System.” SSRN ElectroNIC ASIA
Journal (2024): n. pag.
Acharya, Kamal. “Student Information Management System Project.” SSRN
ElectroNIC ASIA Journal (2024): n. pag.
Acharya, Kamal. “ATTENDANCE MANAGEMENT SYSTEM.” International
Research Journal of Modernization in Engineering Technology and
Science (2023): n. pag.
Acharya, Kamal. “College Information Management System.” SSRN ElectroNIC
ASIA Journal (2024): n. pag.
Acharya, Kamal, Attendance Management System Project (April 28, 2024).
Available at
SSRN: https://ssrn.com/abstract=4810251 or http://dx.doi.org/10.2139/ssrn.4810251
Acharya, Kamal, Online Food Order System (May 2, 2024). Available at
SSRN: https://ssrn.com/abstract=4814732 or http://dx.doi.org/10.2139/ssrn.4814732
Acharya, Kamal, University management system project. (May 1, 2024). Availableat

15 | P a g e
SSRN: https://ssrn.com/abstract=4814103 or http://dx.doi.org/10.2139/ssrn.4814103
Acharya, Kamal, Online banking management system. (May 1, 2024). Available at
SSRN: https://ssrn.com/abstract=4813597 or http://dx.doi.org/10.2139/ssrn.4813597
Acharya, Kamal, Online Job Portal Management System (May 5, 2024). Available at
SSRN: https://ssrn.com/abstract=4817534 or http://dx.doi.org/10.2139/ssrn.4817534
Acharya, Kamal, Employee leave management system. (May 7, 2024). Available
at SSRN: https://ssrn.com/abstract=4819626 or http://dx.doi.org/10.2139/ssrn.4819626
Acharya, Kamal, Online electricity billing project report. (May 7, 2024). Available at
SSRN: https://ssrn.com/abstract=4819630 or http://dx.doi.org/10.2139/ssrn.4819630

16 | P a g e