Vedas College
Department of Computer Science and Information Technology
Project Proposal on:
Hospital Management System
Submitted by:
Hemant Bhandari (23695)
Manish Timalsina (23698)
Sandeep Sanjel (23719
Submitted to:
Vedas College
Department of Computer Science and Technology
Jawalakhel, Lalitpur
October 2023
1
Abstract:
The Hospital Management System project is a computer based software designed to manage
the front desk operations of a hospital. It offers a user interface ensuring ease of use, speed
and cost effectiveness. Its primary function is to register and maintain patient and doctor
information securely. Whenever necessary the system allows access to update this
information well. Patient details and diagnoses are entered into the system after which they
can be displayed on the screen as required. To access the Hospital Management System one
must provide a username and password which're exclusive to receptionists or administrators
who have authorized :access, to the database. The system ensures that personal data remains
well protected while allowing for data processing, for needs.
2
Acknowledgement:
We extend our heartfelt gratitude to all individuals and organizations who have
contributed to this Hospital Management System (HMS) proposal. We appreciate the
hospital staff, technical and project management teams, and the hospital leadership for
their invaluable input and support. Your collaboration and insights have been crucial in
shaping this project. We look forward to your continued involvement as we work toward
implementing the HMS for enhanced patient care and operational efficiency.
Sincerely,
Hemant Bhandari (23695)
Manish Timalsina (23698)
Sandip Sanjel (23719)
3
Table of Contents
Chapter 1........................................................................................................................................6
Introduction................................................................................................................................6
Objectives...................................................................................................................................6
Chapter 2........................................................................................................................................7
Problem Statement.....................................................................................................................7
Solution.......................................................................................................................................7
Scope of project..........................................................................................................................7
Chapter 3 : Project Management....................................................................................................9
Project Planning and Scheduling.................................................................................................9
Methodology..........................................................................................................................9
Project Management Life Cycle..............................................................................................9
Project Schedule................................................................................................................... 10
Schedule Representation...................................................................................................... 10
Requirement Specifictaion........................................................................................................ 10
Introduction.......................................................................................................................... 10
Hardware Requirement........................................................................................................ 10
Software Requirement.......................................................................................................... 11
Risk Management..................................................................................................................... 11
Chapter 4 : System Analysis.......................................................................................................... 12
Background Study..................................................................................................................... 12
Existing System......................................................................................................................... 12
Proposed System...................................................................................................................... 12
Feasibility Study........................................................................................................................ 13
Technical Feasibility.............................................................................................................. 13
Operational Feasibility.......................................................................................................... 13
Economic Feasibility.............................................................................................................. 13
Management Feasibility........................................................................................................ 13
Social Feasibility.................................................................................................................... 13
Architectural Design.................................................................................................................. 14
Use case Diagram...................................................................................................................... 14
Data Flow Diagram.................................................................................................................... 15
Chapter 5 Conclusion.................................................................................................................... 17
4
List of Figures:
Figure 1:Architectural Design........................................................................................................ 14
Figure 2:Use Case Diagram........................................................................................................... 15
Figure 3:0th level Data Flow Diagram........................................................................................... 16
Figure 4:1st level Data Flow Diagram............................................................................................ 16
1
Chapter 1
Introduction
Modern healthcare and technology are advancing at a breakneck pace, making
effective hospital management essential. It is now necessary to provide patients with
high-quality care, efficient administrative procedures, and an improved overall
healthcare experience.
Our plan is committed to tackling these requirements by creating and executing an all-
inclusive Hospital Management System (HMS). With a focus on a renowned healthcare
provider, this system is pain stakingly created to meet the specific needs of healthcare
facilities. With the goal of streamlining hospital operations and raising the bar for patient
care, it tries to provide a broad range of features and capabilities, including staff
management, appointment scheduling, billing, and patient records management.
We will go into more detail about our suggested HMS in this proposal, showing how
it can transform hospital administration and guarantee a smooth, patient-centered
healthcare experience.
Objectives
The project attempts to fulfill the following objectives:
To enhance the quality of patient care by providing a systematic and organized
approach to medical processes and ensure timely and accurate access to patient
records, treatment histories, and diagnostic information.
2
Chapter 2
Problem Statement
For everyone, medical care is one of the most important and sought-after services. It
necessitates meticulous attention to detail and superior care, which demands a lot of
labor from healthcare professionals. These problems also include circumstances in
which each patient need a personal attendant, even though this might be done
automatically and with technology.
Solution
The Hospital Management method is a method that is suggested to address the
problems that hospitals encounter. Prescriptions and patents with mild diagnoses will
be handled by this system. The concept of automated patient management greatly
facilitates the monitoring and appropriate care of our patients by our medical
professionals.
Scope of project
The following essential elements are included in the Hospital Management System
project's scope:
1.Patient management: involves creating and keeping track of patients' demographics,
medical histories, prescriptions, and test results in electronic health records (EHRs).
2.Appointment Scheduling: Establish an online platform for patients to make
appointments with medical professionals, cutting down on wait times and raising
patient satisfaction.
3.Billing and Finance: Create a billing module with the ability to interface with
multiple payment gateways in order to handle insurance claims, patient billing, and
financial transactions.
4.Inventory management: Facilitate effective administration of medications, medical
equipment, and supplies, guaranteeing sufficient stock levels and cutting down on
waste.
5.Staff management: Improve resource allocation and workforce management by
keeping an eye on employees' performance, managing their schedules, and creating a
staff directory.
6.Security and privacy: To safeguard patient data and ensure adherence to healthcare
privacy laws, put strong security measures in place, such as encryption, role-based
access control, and audit logs.
7.Communication and Notifications: Include tools for secure messaging between
patients and healthcare professionals, appointment reminders, and emergency alerts.
3
8.Analytics and Reporting: Give hospital management customized dashboards and
reporting capabilities so they can keep an eye on important performance indicators
and spot patterns.
4
Chapter 3 : Project Management
Project Planning and Scheduling
Project planning is a subset of project management, which deals with organizing and
reporting progress inside the project environment using timetables like Gantt charts.
The first steps in the process involve defining the project scope and choosing the best
approaches to finish the work. After this, a work breakdown structure is created by
listing and grouping the times needed for each activity that must be completed in
order to finish the project. An activity network diagram is used to define the logical
relationships among tasks, allowing the critical path to be identified.
Methodology
For the development of our projects, we have employed the Iterative and Incremental
Development (IID) paradigm. The Iterative Waterfall Development Method is another
name for this development methodology. A software development process called iterative
and incremental development was created in reaction to the more conventional waterfall
model. This model is intended to handle a project of such magnitude. Better development
and testing procedures are mostly required for this vast and complex project. The
waterfall model's iterative testing procedure is widely recognised. For this reason, we
decided to design our software using the waterfall paradigm.
Project Management Life Cycle
The Project Management Life Cycle has four phases. Each project life cycle phase is
described along with the tasks need to complete it.The four phases is
1. Initiation
2. Planning
3. Execution
4. Closure
5
Project Schedule
The following is the approximate timetable for the Hospital Management
System project:
1.prerequisites Compilation: 4 weeks
2.System Design:4 weeks
3.System development: 4 weeks
4.Testing: 3 week
5.Training and Deployment: 1 weeks
Schedule Representation
One of the most crucial aspects of project planning is task scheduling. It entails
choosing which things to tackle when. To plan the project's activities, a software
project manager must adhere to the following guidelines.
Requirement Specifictaion
Introduction
All computer software requires specific hardware parts or other software resources to
function properly on a computer. These prerequisites are referred to as (computer)
system requirements, and they are frequently used as recommendations rather than
strict guidelines. The majority of software specifies minimum and recommended
system requirements. System requirements typically rise with time due to the
growing need for more processing power and resources in newer software versions.
Industry observers contend that rather than technological breakthroughs, this trend is
a more significant factor in the upgrades of current computer systems.
Hardware Requirement
Hardware, or physical computer resources, is the most common set of
requirements defined by any operating system or software application. A hardware
6
compatibility list (HCL), particularly when it comes to operating systems, is frequently
included with a hardware requirements list. Hardware devices tested for compatibility
and occasionally incompatibility with a specific operating system or application are listed
in an HCL. Subsections that follow go over the different facets of hardware requirements.
minimum hardware requirements for present project:
PROCESSOR : Intel dual Core ,i5
RAM : 4 GB
HARD DISK : 80 GB
Software Requirement
The term "software requirements" refers to the specifications of software resources and
prerequisites that must be installed on a computer in order for an application to operate
as well as possible. Usually not included in the software installation package, these
prerequisites must be installed individually before the software can be installed.
Software Requirements For Present Project:
OPERATING SYSTEM : Windows 11/ 10/8
FRONT END : Html,css,javaScript.
SERVER SIDE SCRIPT : Php/Laravel Framework
DATABASE : Mysql
Risk Management
A proactive strategy for reducing project uncertainty and possible loss is software risk
management. Product size, business impact, customer-related, process, technology,
development environment, staffing (number and experience), schedule, and cost are a few
risk categories. The practise of controlling risks in a project through procedures,
techniques, and equipment is known as risk management.
The methodical process of identifying risks involves identifying potential threats to the
project plan. We can start the process of preventing risks when we can and controlling
them when needed by identifying known and predictable risks.To perform the risk
identification, we categorized the risk into different categories as:
1. Project Risk
2. Technical Risk
3. Business Risk
4. Known Risk
5. Predictable Risk
6. Unpredictable
7
Chapter 4 : System Analysis
Background Study
System analysis is the division of a material into components for analysis,
implementation, and in-depth inspection. Understanding the nature of the business
and how it currently functions is crucial before developing any system. The thorough
analysis offers the precise information needed for designing to guarantee that all of
the client's requirements are met. The feasibility study forms the basis for a large
portion of the investigation or study carried out during the analysis phase. It would be
more accurate to argue that the phases of analysis and feasibility overlap. The
feasibility study is when high-level analysis gets started. Although it is sometimes
stated that analysis is a single stage of the system development lifecycle (SDLC), this
is untrue. Analysis starts when the system is first started and doesn't end until it is
maintained. Even after successful implementation of the system, analysis may play its
role for periodic maintenance and up gradation of the system. One of the main causes
of project failures is in adequate understanding, and one of the main causes of
inadequate understanding of the requirements is the poor planning of system analysis.
1.1. Scope of Working
The Hospital Management System (HMS) is the software product that is being
proposed. Any hospital, clinic, pharmacy, or pathology lab will use the system.
gathering patient information from a clinic, pharmacy, or pathology department and
preserving it for later use. The system that is currently in use is based on paper. It
moves too slowly and is unable to deliver updated patient lists in a timely manner.
The system's goals are to decrease overtime compensation and raise the number of
patients who can receive precise treatment. These documents contain both functional
and non-functional requirement statements.
Existing System
Currently, hospitals manage and maintain vital information using a manual system. Many
paper forms are needed under the current system, and data stores are dispersed throughout
the hospital administration infrastructure. Information is frequently lacking or does not
adhere to management standards. Since forms are frequently misplaced during
departmental transfers, a thorough auditing procedure is necessary to guarantee that no
important data is overlooked. The hospital has multiple copies of the same data, which
could cause discrepancies in the information across different data stores.
Proposed System
The 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
8
services are to be provided in an efficient, cost effective manner, with the goal of
reducing the time and resources currently required for such tasks .
Feasibility Study
Technical Feasibility
This is concerned with specifying equipment and software that willsuccessfully
satisfy the user requirement; the technical needs of the system may vary considerably,
but might include:The facility to produce outputs in a given time:
1. Response time under conditions.
2. Ability to process a certain volume of transaction at a particular seep.
3. Facility to communicate data to distant location.
Operational Feasibility
It is mainly related to human organization and political aspects. The points to be
considered are:
1. What changes will be brought with the system?
2. What organizational structures are distributed?
3. What new skills will be required? Do the existing staff members have these skills?
If not, can then the trained due course of time.
Economic Feasibility
Economic analysis is the most frequently used technique for evaluatingthe
effectiveness of a proposed system. More frequently known as cost/benefit system
and comparethem with costs. If benefits outweigh costs, a decision is taken to design
and implement the system.
Management Feasibility
It is a determination of whether a proposed project will beacceptable to management.
If does not accept a project of gives a negligible support to it; the analystwill tend to
view the project as a no feasible one.
Social Feasibility
Social feasibility is a determination of whether the project will beacceptable to the
people or not. This determination typically examines the probability of the
projectaccepted by the group directly affected by the proposed system change.
9
Architectural Design
An architectural diagram is a diagram of a system that is used to abstract the overall
outline of the software system and the relationships, constraints, and boundaries
between components. It is an important tool as it provides an overall view of the
physical deployment of the software system and its evolution roadmap.
Figure 1:Architectural Design
Use case Diagram
A use case diagram in the Unified Modelling Language (UML) is a type of behavioural
diagram defined by and created from a use-case analysis. Its purpose is to present a
graphical overview of the functionality provided by a system in terms of actors, their
goals (represented as use cases), and any dependencies between those use cases.
10
Figure 2:Use Case Diagram
Data Flow Diagram
The context diagram is the most abstract data flow representation of a system. It
represents the entire system as a single bubble and. The various external entities with
which the system interacts and the data flows occurring between the system and the
external entities are also represented. The name context diagram is well justified
because it represents the context in which the system is to exist i.e. the external
entities (users) that would interact with the system and specific data items they would
be receiving from the system.
11
Figure 3:0th level Data Flow Diagram
Figure 4:1st level Data Flow Diagram
12
Chapter 5 Conclusion
To improve hospital operations and patient care, the proposed Hospital Management
System (HMS) is a revolutionary solution. We have developed a thorough project
plan and determined the project's technical, operational, and financial viability. Our
goals in putting this HMS into use are to safeguard data, expedite procedures, and
enhance healthcare delivery. We are dedicated to achieving success through
collaboration and are eager to see this system's advantages for our hospital and
neighbourhood. Your participation and support are essential to the project's success.
13
References
[1] N. Patil, 2020. [Online]. Available: https://www.slideshare.net/NikhilPatil156288/hospital-
management-systemdocx.
[2] “Academia,” [Online]. Available: https://www.academia.edu/36406675/.
[3] “Free Projectz,” [Online]. Available: https://www.freeprojectz.com/dfd/hospital-
management-system-dataflow-diagram.
14
