“Hospital Management System”

A Project Progress Report submitted

In partial fulfillment of requirements for the degree of

B.Sc. Engineering
in
Computer Science and Engineering

Submitted by
Samiul Basher
Student ID: 170127
Session: 2017-18
Supervised by
Dr. Md. Nasim Adnan
Assistant Professor
Department of Computer Science and Engineering,
Faculty of Engineering and Technology,
Jashore University of Science & Technology.
5 October, 2024.
 CIRTIFICATE

This project titled “Hospital Management System”, submitted by

Samiul Basher (ID: 170127) as mentioned below has been accepted as
Final Report in partial fulfillment of the requirements for the degree
of BSc in Computer Science and Engineering in 5 October, 2024.

Submitted By:

Samiul Basher
Student ID: 170127
Session: 2017-18

Supervisor

Dr. Md. Nasim Adnan

Assistant Professor,
Department of Computer Science and Engineering
Jashore University of Science and Technology
Jashore-7408, Bangladesh.

i
 ACKNOLEDGEMENT
First of all, I would like to express our greatest and deepest gratitude to Almighty
and Most Merciful Allah, by whose full praise we have been able to complete this
work. I would like to express my deep and sincere gratitude, sincere respect, and
deep respect to our own project supervisor Dr. Md. Nasim Adnan, Assistant
Professor, Department of Computer Science and Engineering, Jashore University
of Science and Technology, Jessore-7408. Also, I would like to express my deep
and sincere gratitude, sincere respect and deep respect to our own department
Chairman Dr. Syed Md. Galib, Professor, Department of Computer Science and
Engineering, Jashore University of Science and Technology, Jessore-7408,
Bangladesh and their skillful supervision, invaluable advice and support,
educational guidance, tireless support, constructive criticism, valuable
suggestions and constant encouragement in every aspect from the beginning to
the end of this research work.

Also, I want to express my sincere thanks to Dr. Anu Radha Das, MBBS, Intern
Doctor, Khulna Medical College, Murshid Kuly Khan, Medical Technologist
(Lab), Upazila Health Complex, Fultola, Khulna, which took me one step ahead
to finish the project. Finally, all respectful thanks and gratitude to the pillar of our
success, my parents and wife for their endless blessings, endless love, constant
inspiration, and financial support throughout this project.

Author

ii
 Preface
On the eve of the beginning of civilization, human beings had been trying their
level best to discover and innovate unknown things. Because of these inherent
characteristics, human beings are marching toward the ends of civilization. They
have been achieving practical knowledge along with theoretical knowledge.
Theoretical knowledge cannot bring actual achievement until and unless it is with
practical knowledge. The philosophy of the Computer Science and Engineering
department has arranged the thesis/project program with a view to conquering
practical knowledge associated with different fields and I think the project
program is the best way to achieve practical knowledge. To meet requirements, I
have worked on a web application named “Hospital Management System”.
Through careful study and observation, I have gathered a lot of information about
its overall project (Attached in Appendix). I have tried to represent information
consciously but completely in this report, due to the methodologies used to collect
information experience, writing mistakes, or other reasons, there may happen
some unexpected mistakes in this report. We are extremely sorry deep in our
hearts for such mistakes if any.

iii
 Abstract

The Hospital Management System (HMS) is a comprehensive software solution

designed to automate various administrative, clinical, and operational processes

within a healthcare facility. The system aims to enhance the overall efficiency,

accuracy, and quality of healthcare services, ultimately improving patient care

and organizational effectiveness. The Hospital Management System is a valuable

tool for healthcare providers seeking to modernize their operations, enhance

patient care, and improve overall organizational efficiency. By embracing

technological advancements, hospitals can optimize resource utilization,

minimize errors, and provide a higher standard of care to their patients.

iv
 Table of Contents

Chapter 1 Introduction --------------------------------------------------------------1-3

1.1 Background ----------------------------------------------------------------------------------------- 1

1.2 Motivation ------------------------------------------------------------------------------------------- 1

1.3 Objectives --------------------------------------------------------------------------------------------2

Chapter 2 Software Requirement Specification ----------------------------- 4-10

2.1 Introduction --------------------------------------------------------------------------------------- 4

2.2 Overall Description -------------------------------------------------------------------------------5

2.3 External Interface Requirements --------------------------------------------------------------8

2.4 System features ------------------------------------------------------------------------------------8

2.5 Other Nonfunctional Requirements -----------------------------------------------------------9

Chapter 3 System Design----------------------------------------------------------11-90

3.1 Use Case Diagram------------------------------------------------------------------------------11-52

3.1.1 Use Case Diagram for Patient--------------------------------------------------------11

3.1.2 Use Case Diagram for Admin---------------------------------------------------------16

3.1.1 Use Case Diagram for Staff-----------------------------------------------------------36

3.2 Activity Diagram and Swimlane Diagram------------------------------------------------53-86

3.2.1 Activity Diagram and Swimlane Diagram for Patient -------------------------53

v
 3.2.2 Activity Diagram and Swimlane Diagram for Admin (Author) -------------58

3.2.3 Activity Diagram and Swimlane Diagram for Staff ----------------------------74

3.3 Schema Diagram-----------------------------------------------------------------------------------87

3.4 Entity Relationship(ER) Diagram-------------------------------------------------------------88

3.5 Data Flow Modeling------------------------------------------------------------------------------89

Chapter 4-Implementation details----------------------------------------------90-91

4.1 Patient’s Pages-------------------------------------------------------------------------------------90

4.2 Admin’s Pages--------------------------------------------------------------------------------------90

4.3 Staff (General) pages------------------------------------------------------------------------------91

4.4 Staff (Doctor) pages--------------------------------------------------------------------------------91

Chapter 5-Testing----------------------------------------------------------------------92

5.1 White Box Testing---------------------------------------------------------------------------------92

5.1 Black Box Testing----------------------------------------------------------------------------------92

Chapter 6-Deploy and Delivery----------------------------------------------------93

References-----------------------------------------------------------------------------------------------94

vi
 Chapter-1

Introduction
1.1 Background
Designing a Hospital Management System (HMS) requires a thorough understanding of the
healthcare industry, encompassing the ecosystem of hospitals, clinics, and regulatory
compliance. An in-depth exploration of hospital operations, including departmental workflows,
patient lifecycle, and billing processes, is crucial. Key functionalities such as patient
management, appointment scheduling, billing, inventory, and laboratory management need to
be studied. Security, interoperability, and user experience considerations, including roles,
permissions, and interface design, play pivotal roles. Additionally, awareness of scalability,
technological trends, and continuous improvement through case studies and user feedback are
essential for the successful development and implementation of an effective HMS.

1.2 Motivation

1.2.1 Existing System

The existing system for the Hospital Management Project relies on manual and paper-based
processes, contributing to inefficiencies and errors in patient data management, appointment
scheduling, and billing. Patient records are stored in physical files, making retrieval time-
consuming, and communication between different departments is often disjointed.
Appointment scheduling is done manually, leading to scheduling conflicts and delays. Billing
processes lack automation, resulting in potential errors and delays in reimbursement. The
absence of an integrated system hampers overall efficiency, and the system is not aligned with
modern healthcare standards, such as necessitating the development of a comprehensive
Hospital Management System to streamline operations and enhance patient care.

1.2.2 Limitations of System

The Hospital Management System project may face several limitations, including technical,
operational, and organizational challenges. Technical limitations could arise from the
complexity of integrating with existing healthcare systems, potential data migration issues, and
the need for continuous adaptation to evolving technologies. Operational challenges may
include resistance to change among staff, requiring extensive training and change management

1|Page
efforts. Additionally, constraints related to budget and time may limit the project's scope and
features. Organizational barriers, such as bureaucratic processes and varying levels of IT
literacy among healthcare professionals, could hinder seamless implementation. Privacy and
security concerns, especially regarding patient data, may pose regulatory compliance
challenges. Furthermore, external factors like changes in healthcare policies and regulations
may impact the project's effectiveness. Addressing these limitations will be crucial to ensuring
the successful development and implementation of the Hospital Management System.

1.2.3 Opportunities

The Hospital Management System project presents several opportunities for improvement and
innovation in healthcare management. Firstly, the implementation of an integrated system
offers the opportunity to enhance overall operational efficiency by automating and streamlining
processes such as patient registration, appointment scheduling, billing, and inventory
management. Opportunities for data-driven insights and analytics can arise, allowing
healthcare providers to make informed decisions and enhance the quality of care. Moreover,
the system can facilitate better communication and collaboration among different departments
within the hospital. In the long term, the project provides a foundation for scalability and
adaptability to future technological advancements, promoting a more agile and responsive
healthcare infrastructure. Additionally, the adoption of best practices and compliance with
healthcare standards can position the hospital as a leader in providing modern and efficient
healthcare services.

1.3 Objectives

The objectives of a Hospital Management System (HMS) are multifaceted, aiming to enhance
the overall efficiency, effectiveness, and quality of healthcare delivery within a hospital or
healthcare organization. By achieving these objectives, a Hospital Management System aims
to create a more streamlined, patient-centric, and efficient healthcare environment, ultimately
improving the quality of care provided by the hospital. Here are detailed objectives of an HMS:

● Efficient Patient Management

● Efficient Appointment and Schedule Management
● Accurate Billing Management
● Enhanced Clinical Management
● Diagnostic Management

2|Page
● Improved Human Resource Management
● Quality and Compliance
● Data Security and Access Control
● Enhanced Reporting and Analytics
● Improved Communication
● Cost Reduction and Resource Optimization
● Patient Engagement and Satisfaction

3|Page
 Chapter 2
Software Requirement Specification
2.1 Introduction

2.1.1 Purpose

Hospitals are the essential part of our lives, providing best medical facilities to people suffering
from various ailments, which may be due to change in climatic conditions, increased work-
load, emotional trauma stress etc. It is necessary for the hospitals to keep track of its day-to-
day activities & records of its patients, doctors, nurses, ward boys and other staff personals that
keep the hospital running smoothly and successfully.
But keeping track of all the activities and their records on paper is very complex and error
prone. It also is very inefficient and a time-consuming process observing the continuous
increase in population and number of people visiting the hospital. Recording and maintaining
all these records is highly unreliable, inefficient and error-prone. It is also not economically &
technically feasible to maintain these records on paper. Thus keeping the working of the manual
system as the basis of our project. We have developed an automated version of the manual
system, named as Hospital management system.
The main purpose of our system is to make hospital task easy and is to develop software that
replaces the manual hospital system into automated hospital management system. This
document serves as the unambiguous guide for the developers of this software system. The aim
of our project is to provide a paper-less hospital up to 90%. It also aims at providing low-cost
reliable automation of the existing systems. The system also provides excellent security of data
at every level of user-system interaction and also provides robust & reliable storage and backup
facilities.
2.1.2 Document Conventions

The followings are the list of standards and typographical conventions that used in this
document-

Name Font Face Size

Main Section Titles Times New Roman Bold 18

Sub Section Titles: Times New Roman Bold 14

4|Page
 Other Text Explanations: Times New Roman Normal 12

Text Sub headings: Times New Roman Bold 12

Table and image figure Explanations: Times New Roman Normal 12

2.1.3 Intended Audience and Reading Suggestions

The system is being made for both hall authorities (admin), staffs (semi admin users) and the
patients (users). The software will be made available to the users for update or add patient,
managing their dashboard and generating bills, request for an appointment etc. The admins will
be able to keep track of the patients. Staffs, appointment requests etc.

2.2 Overall Description

2.2.1 Product Perspective

The Hospital Management system is fully independent product. Our product is not a part of
any other system. We have three types of user interfaces .User interfaces will be divided like

● Administrator Interfaces
● Staff Interfaces Software
● Patient Interfaces Software

2.2.1.1 Interfaces for Administrator:

Authentication: At the start there will be a login screen where the user has to enter its login
email & password to authenticate himself or herself.

Admin Panel: After the login a dashboard for admin will be displayed showing all the
information and operations provided by hospital Management System.

Account management: In this view, admin will add, edit or remove staffs, medicines, room
details, Lab test, and departments in the system. In administrator view, administrator will
confirm newly added department. Administrator will be able to access all information about
hospital staff, patients and manage them.

2.2.1.2 Interfaces for Staff:

5|Page
Authentication: At the start there will be a login screen where the user has to enter its login
email & password to authenticate himself or herself.

Staff Panel: After the login a dashboard for staff will be displayed showing all the information
and operations provided by Hospital Management System.

Functionalities: Staff functionalities will be added here as menus where the can select and
work like generating bills, generating appointments for patients etc.

2.2.1.3 Interfaces for Patient:

Authentication: At the start there will be a login screen where the user has to enter its login
email & password to authenticate himself or herself.

Patient Panel: After the login a dashboard for Patient will be displayed showing all the
information and operations provided by Hospital Management System.

Functionalities: Patient functionalities will be added here as menus where the can request an
appointment and view appointment etc.

2.2.2 Operating Environment

Hospital management system operates in any digital smart devices. Such as PC’s and
smartphones as it’s a web application. Operating environment for Hospital Management
System is as listed below:

o Operating System: Any

o Database: MYSQL
o Platform: Web

2.2.3 Design and Implementation Constraints

The constraints for design and implementation are:

o Internet connection is needed to use the software

o Language: English.
o All mandatory fields should be filled by an individual

2.2.4 User Documentation

User documentations are:

o Login or Sign Up
o Add, Update and Delete admin, staffs or patients etc.

6|Page
o Create billing.

2.2.5 Assumptions and dependencies

o Admin is created in the database already

o The details related to the patients, appointments, admission, billing
o Roles and tasks are predefined.

2.3 External Interface Requirements

2.3.1 User Interfaces

The Hospital Management System will typically include a user interface that allows
administrators to configure and manage the system. This interface must be easy to use and
intuitive, with clear instructions and guidance for administrators. User interfaces should be
designed by following access level of users.

2.3.2 Integration with the Existing System

The Hospital Management System will need to be able to access and retrieve data and other
assets from the existing system or platform, and may also need to be able to write data back to
the existing system in certain cases.

2.3.3 Integration with the New System

The Hospital Management System will also need to be able to access and write data to the new
system or platform, in order to facilitate the admission process of Hospital Management
System.

2.3.4 User Authentication and Authorization

The Hospital Management System may need to be able to authenticate users and ensure that
they have the appropriate permissions to access and use the system.

2.3.5 Hardware Interfaces

A computer or a smart device (like-smartphone or tablet etc.) is required to use the system.

2.3.6 Software Interfaces

Software Used Description

Operating system Any operating System

Database MySQL database.

7|Page
 Programming To implement the project I have chosen HTML, CSS, JavaScript, SQL and PHP
Languages Used language and Laravel 10.x framework for its more interactive support.

2.3.7 Communications Interfaces

✔ Client on Internet will be using HTTP/HTTPS Protocol.

✔ Client on intranet will be using TCP/IP protocol.

2.4 System Features

Quality Function Deployment (QFD):

It is a technique that translates the needs of the customer into technical requirements for
software. It concentrates on maximizing customer satisfaction from the Software engineering
process. With respect to our project the following requirements are identified by a QFD.

Normal Requirements:

These are the basic, fundamental requirements that are essential for the system to fulfill its
primary functions.

For HMS:

Patient Registration: Capture and store basic patient information.

Appointment Scheduling: Allow for the scheduling and management of appointments.

Billing and Invoicing: Generate bills for medical services provided.

Expected Requirements:

These requirements go beyond the basics and are considered standard features that users would
anticipate in a well-developed system.

For HMS:

Inventory Management: Track and manage the stock of medicines and medical equipment.

Reporting and Analytics: Provide standard reports and analytics for hospital management.

Exciting Requirements:

These are innovative or advanced features that, while not strictly necessary, can set the system
apart and provide additional value to users.

For HMS:

8|Page
Predictive Analytics: Use data analytics to predict trends and optimize hospital operations.

2.5 Other Nonfunctional Requirements

2.5.1 Performance Requirements

The Hospital management system operates its function in small amount of time which is less
than two seconds and can be accessed by one user at a time or concurrently. To access the user
must first login to the system which must have the a user system privileged .When the system
may be busy due to malfunction operation one may have to wait up to one to five minutes.

2.5.2 Safety Requirements

• In Hospital Management System admin must be careful to add staffs.

• In Hospital Management System we used MYSQL database to store data.

• In case the user forgets or loses Password, the repair functionality helps by choosing
“forgot password” option in the main login page

2.5.3 Security Requirements

All the administrative and data entry operators have unique logins so system can understand
who is login in to system right now no intruders allowed except system administrative nobody
cannot change record and valuable data. Because, here many information of patients, staffs,
admin will be given. So only the legitimate users are allowed to use the application and
legitimate admins are given authorities to maintain the system.

2.5.4 Software Quality Attributes

• Usability: Any familiar in using windows operation or website can operate the system
since it has user friendly user interface. Which have the instruction menu’s how to use it which
self-directive application then can be used the system without ambiguity.

• Reliability: The hall automation system is available based on the user needs, can work
properly, and do transactions efficiently including safe data management of the hall and
students. For invalid and malfunctioned operation, the system will restart in order to prevent
data loose as well as safe operation within 5 seconds. The hall automation system is password
protected to change things on the system. Here the super admin control over the system by
login to the hall automation system. Any user can’t use the system but the guest user can only
see homepage, login or registration page nothing else. As result data is protected and controlled
by only the administrator and maintained by staffs.

9|Page
• User interface: The user interface is friendly which is easy to use. And having attractive
frame structure which is prepared in assumption with other related systems. Also the user can
change him/her user favorite interfaces that Is available in the system.

• Operation: The hall automation system is operated and controlled by the staffs for safe
work.

• Supportability: This Hospital Management system operates in any digital smart

devices. Such as PC’s and smartphones as it’s a web application. The system can be easily
maintained by the admin of the hall automation system by using the prepared documents of the
system for easy maintenance. Other ways it is maintained by the system developers for
corrective and other heavy problems.

• Timeless: The system carries out all the operations with consumption of very less time.

• Security: Security of the system is maintained by giving access to only authenticated

user id and password.

10 | P a g e
 Chapter 3

System Design
3.1 Use Case Diagram

3.1.1 Use Case Diagram for Patient

Fig 3.1.1: Use Case Diagram for Patient

3.1.1.1 Register

Registration System for all Patients.

Description and Priority

A Patient must register or added by authenticated and performed certain actions.

Stimulus/Response Sequences

Use case: Registration

Actor: Patient

Goal: Access the general system of Hospital Management system for Patients

Precondition: The registration page must be displayed

Trigger: User decides to register into the system

11 | P a g e
Scenario:

• The user goes to the register page menu by clicking on Register.

• User enters email, password for the required fields.

• The system checks the email

• If the input were valid value, then system will display general system of the Hospital
Management system for that Patient after verifying the email. Or the system displays error
message.

Exceptions:

• Invalid Password

• Invalid email

Functional Requirements

REQ-1: A smartphone / digital computing device

REQ-2: Internet Connection

3.1.1.2 Login

Login System for all users.

Description and Priority
All patients must login to perform certain actions.
Stimulus/Response Sequences
Use case: Login (Authentication)
Actor: patient
Goal: Access the general system of Hospital Management system
Precondition: The login page must be displayed
Trigger: User decides to enter into the system
Scenario:
● The user goes to the login menu by clicking on Login or entering a URL.
● User enters email and password for the required fields.
● The system checks the email and password.
● If the input were valid value, then system will display general system of
the Hospital Management system for that type of user. Or the system
displays error message.

12 | P a g e
Exceptions:
● Invalid email
● Invalid Password
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.1.3 View Appointment

View appointment from the system.

Description and Priority
All users must login to perform certain actions.
Stimulus/Response Sequences
Use case: View appointment
Actor: patient
Goal: See the appointment from the general system of Hospital Management system
Precondition: View appointment page should be displayed.
Trigger: User decides to see the appointments from the system
Scenario:
● The patient login into the system.
● After login navigates to system.
● Select on add view appointment
● The system displays all the appointments.
Exceptions:
● Invalid email
● Invalid Password
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.1.4 Add support message

Add new support message to the system.
Description and Priority
A patient send a support message.

13 | P a g e
Stimulus/Response Sequences
Use case: Add new support
Actor: Patient
Goal: Record New support message Data
Precondition: Patient must be logged in
Trigger: The Patient decides to add new support message to the system
Scenario:
• The Patient login into the system.
• After login navigates to system support
• Select on add new support
• The system displays the new support form
• Then he/she fills the form of support message
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid Password
• Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.1.5 Update Profile

Update profile information from the system.

Description and Priority
A patient need to update his profile.
Stimulus/Response Sequences
Use case: Update profile
Actor: Patient
Goal: Record update profile Data
Precondition: Patient must be logged in
Trigger: The Patient decides to update profile to the system
Scenario:

14 | P a g e
 • The Patient login into the system.
• After login navigates to system ‘Profile’
• Select on edit profile
• The system displays the update form
• Then he/she fills the form of profile
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid Password
• Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.1.6 Log out

Logout System for all users.

Description and Priority
All users must logout to exit from the system
Stimulus/Response Sequences
Use case: Logout
Actor: Any Type of User
Goal: Logout from Hospital management system
Precondition: User must be logged in
Trigger: User decides to exit from the system
Scenario:
● The user clicks on “LOGOUT” button and a confirm popup shows.
● System displays “Logged out”.
Exceptions:
● Invalid request
● No Internet
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection
15 | P a g e
3.1.2 Use Case Diagram for Admin

Fig 3.1.2: Use Case Diagram for Admin

3.1.2.1 Log in

Login System for admin.

Description and Priority
All admin must login to perform certain actions.
Stimulus/Response Sequences
Use case: Login (Authentication)
Actor: Admin
Goal: Access the general system of Hospital Management system
Precondition: The login page must be displayed
Trigger: User decides to enter into the system
Scenario:
● The user goes to the login menu by clicking on Login or entering a URL.

16 | P a g e
 ● User enters email and password for the required fields.
● The system checks the email and password.
● If the input were valid value, then system will display general system of
the Hospital Management system for that type of user. Or the system
displays error message.
Exceptions:
● Invalid email
● Invalid Password
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.2 Update Profile

Update profile information from the system.

Description and Priority
An Admin needs to update his profile.
Stimulus/Response Sequences
Use case: Update profile
Actor: Admin
Goal: Record update profile Data
Precondition: Admin must be logged in
Trigger: The Admin decides to update profile to the system
Scenario:
• The Admin login into the system.
• After login navigates to system ‘Profile’
• Select on edit profile
• The system displays the update form
• Then he/she fills the form of profile
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid Password
• Invalid email
Functional Requirements
17 | P a g e
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.3 Update System settings

Update system settings information from the system.

Description and Priority
An Admin need to update system settings information.
Stimulus/Response Sequences
Use case: Update system settings
Actor: Admin
Goal: Record update profile Data
Precondition: Admin must be logged in
Trigger: The Admin decides to update system settings into the system
Scenario:
• The Admin login into the system.
• After login navigates to system ‘Profile’
• Select on setting
• The system displays the update form
• Then he/she fills the form of system settings
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid Password
• Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.4 Add patient

Add new Patient to the system.

Description and Priority
A user must be added by an admin/staff to use the system and perform certain actions.
Stimulus/Response Sequences
18 | P a g e
Use case: Add New Patient
Actor: Admin
Goal: Record New User Data
Precondition: Admin must be logged in
Trigger: The Admin decides to add new users to the system
Scenario:
• The Admin login into the system.
• After login navigates to system settings and menus.
• Select on add new Patient
• The system displays the new user form
• Then he/she fills the form of that user.
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid Password
• Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.5 Update patient’s profile

Update existing user of the system.
Description and Priority
Update existing user information in the system.
Stimulus/Response Sequences
Use case: Update User
Actor: Admin
Goal: Update user data
Precondition: User must be logged in
Trigger: Admin decides to update information
Scenario:
• The admin login into the system.
• After login navigates to system settings and menus.
19 | P a g e
 • The system displays the available users which were added or recorded
before.
• Then selects and edit user which he/she wants to update.
• Finally press the update button.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid Password
• Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.6 Add staff

Add new staff to the system.

Description and Priority
A staff must be added by an admin to add rooms.
Stimulus/Response Sequences
Use case: Add staff
Actor: Admin
Goal: Record New staff Data
Precondition: Admin must be logged in
Trigger: The admin decides to add new staff to the system
Scenario:
• The admin login into the system.
• After login navigates to staff.
• Click on the option: Add New.
• Select on Add New.
• The system displays the new room details form.
• Then he/she fills the form of that staff type and add information.
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
20 | P a g e
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.7 Update staff

Add update Staff to the system.

Description and Priority
Update Staff information.
Stimulus/Response Sequences
Use case: Update Staff
Actor: Admin
Goal: Update Staff
Precondition: Admin must be logged in
Trigger: The admin decides to update Staff to the system.
Scenario:
• The admin login into the system.
• After login navigates to Staff.
• Click on the option: View All.
• Select the Staff you want to update.
• The system displays the Staff update form.
• Then he/she fills or changes the form of that Staff and update information.
• Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.6 Add department

Add Departments to the system.

Description and Priority
A Department must be added by an admin.

21 | P a g e
Stimulus/Response Sequences
Use case: Add Departments
Actor: Admin
Goal: Record New Departments Data
Precondition: Admin must be logged in
Trigger: The admin decides to add new Departments to the system
Scenario:
• The admin login into the system.
• After login navigates to Departments.
• Click on the option: Add New.
• Select on Add New.
• The system displays the new room details form.
• Then he/she fills the form of that Departments and add information.
• Finally press the submit button. System checks whether the form is filled up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.8 Update department

Add update Departments to the system.

Description and Priority
Update Departments information.
Stimulus/Response Sequences
Use case: Update Departments
Actor: Admin
Goal: Update Departments
Precondition: Admin must be logged in
Trigger: The admin decides to update Departments to the system.

22 | P a g e
Scenario:
• The admin login into the system.
• After login, navigate to Departments.
• Click on the option: View All.
• Select the Departments you want to update.
• The system displays the Departments update form.
• Then he/she fills or changes the form of that Departments and update
information.
• Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.9 Add test data

Add a new Lab test to the system.

Description and Priority
A Lab test must be added by an admin to manage tests for Patients.
Stimulus/Response Sequences
Use case: Add New Lab test
Actor: Admin
Goal: Record New Lab test Data
Precondition: Admin must be logged in
Trigger: The admin decides to add new Lab test to the system
Scenario:
• The admin login into the system.
• After login navigates to Lab test.
• Click on the option: Add New.
• Select on Add New.
• The system displays the new Lab test form.
• Then he/she fills the form of that Lab test and add information.
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
23 | P a g e
 • Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.10 Update test data

Add an updated Lab test to the system.

Description and Priority
Update Lab test information.
Stimulus/Response Sequences
Use case: Update Lab test
Actor: Admin
Goal: Update Lab test Data
Precondition: Admin must be logged in
Trigger: The admin decides to update Lab test to the system.
Scenario:
• The admin login into the system.
• After login navigates to Lab test.
• Click on the option: View All.
• Select the Lab test you want to update.
• The system displays the Lab test update form.
• Then he/she fills or changes the form of that Lab test and update
information.
• Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.11 Add operation data

Add new operation for patient feature to the system.

24 | P a g e
Description and Priority
A new operation for patient features must be added further to specific Patients.
Stimulus/Response Sequences
Use case: Add new operation
Actor: Admin
Goal: Record New operation
Precondition: Staff must be logged in
Trigger: The Staff decides to add new operation to the system
Scenario:
● The Staff login into the system.
● After login navigates to operations.
● Click on the option: Add New.
● The system displays the new operation form.
● Then he/she fills the form of that operation and add information
● Finally press the submit button. System checks whether the form is filled up
correctly.
Exceptions:
● Invalid data.
● Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.12 Update operation data

Add update operation to the system.

Description and Priority
Update operation information.
Stimulus/Response Sequences
Use case: Update operation
Actor: Admin
Goal: Update operation Data
Precondition: Admin must be logged in
Trigger: The admin decides to update operation to the system

25 | P a g e
Scenario:
• The admin login into the system.
• After login navigates to operation.
• Click on the option: View All.
• Select the operation you want to update.
• The system displays the operation update form.
• Then he/she fills or changes the form of that operation and update
information.
• Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.13Add medicine data

Add new medicine for patient features to the system.

Description and Priority
A new medicine for patient features must be added further to specific Patients.
Stimulus/Response Sequences
Use case: Add new medicine
Actor: Admin
Goal: Record New medicine
Precondition: Staff must be logged in
Trigger: The Staff decides to add new medicine to the system
Scenario:
● The Staff login into the system.
● After login navigates to medicine.
● Click on the option: Add New.
● The system displays the new medicine form.
● Then he/she fills the form of that medicine and add information
● Finally press the submit button. System checks whether the form is filled up
correctly.
Exceptions:

26 | P a g e
 ● Invalid data.
● Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.14 Update medicine data

Add update medicine to the system.

Description and Priority
Update medicine information.
Stimulus/Response Sequences
Use case: Update medicine
Actor: Admin
Goal: Update medicine Data
Precondition: Admin must be logged in
Trigger: The admin decides to update medicine to the system
Scenario:
• The admin login into the system.
• After login navigates to medicine.
• Click on the option: View All.
• Select the medicine you want to update.
• The system displays the medicine update form.
• Then he/she fills or changes the form of that medicine and update
information.
• Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.15 Add room type data

27 | P a g e
Add new room type to the system.
Description and Priority
A room type must be added by an admin to add room types.
Stimulus/Response Sequences
Use case: Add new room type
Actor: Admin
Goal: Record New room type Data
Precondition: Admin must be logged in
Trigger: The admin decides to add new room type to the system
Scenario:
• The admin login into the system.
• After login navigates to Room type.
• Click on the option: Add New.
• Select on Add New.
• The system displays the new room details form.
• Then he/she fills the form of that room type and add information.
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.16 Update room type data

Add update room type to the system.
Description and Priority
Update room type information.
Stimulus/Response Sequences
Use case: Update room type
Actor: Admin
Goal: Update Room Type Data
Precondition: Admin must be logged in
28 | P a g e
Trigger: The admin decides to update room details to the system
Scenario:
• The admin login into the system.
• After login navigates to Room type.
• Click on the option: View All.
• Select the room details you want to update.
• The system displays the room type update form.
• Then he/she fills or changes the form of that room type and update
information.
• Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.17 Add room data

Add new room to the system.

Description and Priority
A room must be added by an admin to add room.
Stimulus/Response Sequences
Use case: Add new room
Actor: Admin
Goal: Record New Room
Precondition: Admin must be logged in
Trigger: The admin decides to add new room to the system
Scenario:
• The admin login into the system.
• After login navigates to Rooms.
• Click on the option: Add New.
• Select on Add New.
• The system displays the new room details form.
• Then he/she fills the form of that room and add information.
29 | P a g e
 • Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.18 Update room data

Add update rooms to the system.

Description and Priority
Update room information.
Stimulus/Response Sequences
Use case: Update Room data
Actor: Admin
Goal: Update Room Data
Precondition: Admin must be logged in
Trigger: The admin decides to update room to the system
Scenario:
• The admin login into the system.
• After login navigates to Rooms.
• Click on the option: View All.
• Select the room you want to update.
• The system displays the room details update form.
• Then he/she fills or changes the form of that room and update information.
• Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

30 | P a g e
3.1.2.19 Add degree

Add new degree to the system.

Description and Priority
A degree must be added by an admin to add degree
Stimulus/Response Sequences
Use case: Add degree
Actor: Admin
Goal: Record New degree Data
Precondition: Admin must be logged in
Trigger: The admin decides to add new degree to the system
Scenario:
• The admin login into the system.
• After login navigates to degree.
• Click on the option: Add New.
• Select on Add New.
• The system displays the new degree form.
• Then he/she fills the form of that degree and add information.
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.20 Update degree

Add update degree to the system.
Description and Priority
Update degree information.
Stimulus/Response Sequences
Use case: Update degree

31 | P a g e
Actor: Admin
Goal: Update degree Data
Precondition: Admin must be logged in
Trigger: The admin decides to update degree to the system
Scenario:
• The admin login into the system.
• After login navigates to degree.
• Click on the option: View All.
• Select the degree you want to update.
• The system displays the degree update form.
• Then he/she fills or changes the form of that degree and update
information.
• Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.21 Add speciality

Add new speciality to the system.
Description and Priority
A speciality must be added by an admin to add speciality.
Stimulus/Response Sequences
Use case: Add new speciality
Actor: Admin
Goal: Record New speciality Data
Precondition: Admin must be logged in
Trigger: The admin decides to add new speciality to the system
Scenario:
• The admin login into the system.
• After login navigates to speciality.
• Click on the option: Add New.
32 | P a g e
 • Select on Add New.
• The system displays the new speciality form.
• Then he/she fills the form of that room type and add information.
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.22 Update speciality

Add update speciality for doctors to the system.

Description and Priority
Update speciality information.
Stimulus/Response Sequences
Use case: Update speciality
Actor: Admin
Goal: Update speciality Data
Precondition: Admin must be logged in
Trigger: The admin decides to update speciality to the system
Scenario:
• The admin login into the system.
• After login navigates to speciality.
• Click on the option: View All.
• Select the speciality you want to update.
• The system displays the speciality update form.
• Then he/she fills or changes the form of that speciality and update
information.
• Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
33 | P a g e
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.23 Monitor Feedback system

Admin wants to view feedback system.
Description and Priority
Admin wants to view feedback in the system
Stimulus/Response Sequences
Use case: Monitor feedback system
Actor: Admin
Goal: Monitor patient and staff feedback from hospital management system.
Precondition: Admin must be logged in
Trigger: admin decides to view feedback
Scenario:
● The admin into the system.
● After login navigates to support > view.
Exceptions:
● Invalid request
● No Internet
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.24 Send email

Send new email for admin feature to the system.

Description and Priority
A new mail for admin feature must be added for Admin and it should be sent to staff.
Stimulus/Response Sequences
Use case: Send email
Actor: Admin

34 | P a g e
Goal: Record New email Data to staff
Precondition: Admin must be logged in
Trigger: The Admin decides to send new email to the system
Scenario:
● The Admin login into the system.
● After login navigates to Email service.
● Click on the option: Add New.
● The system displays the new email service form.
● Then he/she fills the form of that email service and add information.
● Finally press the submit button. System checks whether the form is filled up
correctly.
Exceptions:
● Invalid data.
● Form is not filled up correctly.
● Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.2.25 Log out

Logout System for all users.

Description and Priority
All users must logout to exit from the system
Stimulus/Response Sequences
Use case: Logout
Actor: Admin
Goal: Logout from Hospital management system
Precondition: User must be logged in
Trigger: User decides to exit from the system
Scenario:
● The user clicks on “LOGOUT” button and a confirm popup shows.
● System displays “Logged out”.
Exceptions:
● Invalid request
35 | P a g e
 ● No Internet
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3 Use Case Diagram for Staff

Fig 3.1.3: Use Case Diagram for Staff

3.1.3.1 Log in
Login System for all type of staffs.
Description and Priority
All users must login to perform certain actions.
Stimulus/Response Sequences
Use case: Login (Authentication)
Actor: Staff
Goal: Access the general system of Hospital Management System
Precondition: The login page must be displayed
Trigger: User decides to enter into the system

36 | P a g e
Scenario:
● The user goes to the login menu by clicking on Login or entering a URL.
● User enters email and password for the required fields.
● The system checks the email and password.
● If the input were valid value, then system will display general system of
the Hospital Management system for that type of user. Or the system
displays error message.
Exceptions:
● Invalid email
● Invalid Password
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.2 Update profile

Update profile information from the system.

Description and Priority
A staff need to update his profile.
Stimulus/Response Sequences
Use case: Update profile
Actor: Staff
Goal: Record update profile Data
Precondition: Staff must be logged in
Trigger: The Staff decides to update profile to the system
Scenario:
• The Staff login into the system.
• After login navigates to system ‘Profile’
• Select on edit profile
• The system displays the update form
• Then he/she fills the form of profile
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid Password
37 | P a g e
 • Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.3 Add patient

Add new Patient to the system.

Description and Priority
A user must be added by a staff to use the system and perform certain actions.
Stimulus/Response Sequences
Use case: Add New Patient
Actor: Staff
Goal: Record New Patient Data
Precondition: Staff must be logged in
Trigger: The Staff decides to add new users to the system
Scenario:
• The Staff login into the system.
• After login navigates to system settings and menus.
• Select on add new Patient
• The system displays the new user form
• Then he/she fills the form of that user.
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid Password
• Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.5 Update patient

Update existing Patient of the system.
38 | P a g e
Description and Priority
Update existing Patient information in the system.
Stimulus/Response Sequences
Use case: Update Patient
Actor: Staff
Goal: Update user data
Precondition: User must be logged in
Trigger: Staff decides to update information
Scenario:
• The Staff login into the system.
• After login navigates to system settings and menus.
• The system displays the available users which were added or recorded
before.
• Then selects and edit user which he/she wants to update.
• Finally press the update button.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid Password
• Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.6 Add appointment

Add new Appointment for patient feature to the system.

Description and Priority
A new Appointment for patient feature must be added further to Patients.
Stimulus/Response Sequences
Use case: Add New Appointment
Actor: Staff
Goal: Record New Appointment

39 | P a g e
Precondition: Staff must be logged in
Trigger: The Staff decides to add new Appointment to the system
Scenario:
• The Staff login into the system.
• After login navigates to Appointments.
• Click on the option: Add New.
• The system displays the new Appointment form.
• Then he/she fills the form of that Appointment and add information.
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid patient
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.7 Update appointment

Add update Appointment feature to the system.

Description and Priority
Update Appointment feature must be added to update appointment data of Patients.
Stimulus/Response Sequences
Use case: Update Appointment
Actor: Staff (Doctor)
Goal: Update Appointment Data
Precondition: Staff must be logged in
Trigger: The staff decides to update Appointments to the system
Scenario:
• The staff login into the system.
• After login navigates to Appointments
• Select the edit button from the Appointment data that you want to update.
• The system displays the update Appointment data form.
• Then he/she fills the form of that Appointment and update information.
40 | P a g e
 • Finally press the update button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.8 Add Visit

Add new visit for patient feature to the system.

Description and Priority
A new visit for patient feature must be added further to Patients.
Stimulus/Response Sequences
Use case: Add new visit
Actor: Staff (Doctor)
Goal: Record New visit
Precondition: Staff must be logged in
Trigger: The Staff decides to add new visit to the system
Scenario:
• The Staff login into the system.
• After login navigates to visits.
• Click on the option: Add New.
• The system displays the new visit form.
• Then he/she fills the form of that visit and add information
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid patient
Functional Requirements
REQ-1: A smartphone / digital computing device

41 | P a g e
REQ-2: Internet Connection

3.1.3.9 View Visits

Add view visitor patients to the system.

Description and Priority
View visit feature must be added to see visit data of Patients.
Stimulus/Response Sequences
Use case: View visit
Actor: Staff (Doctor)
Goal: View visit Data
Precondition: Staff must be logged in
Trigger: The staff decides to View visit to the system
Scenario:
• The staff login into the system.
• After login navigates to visits
• Select the View button from the visit data that you want to View.
• The system displays the View visit data form.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.10 Add Admission

Add new admission for patient management feature to the system.
Description and Priority
A new admission for patient feature must be added further to Patients.
Stimulus/Response Sequences
Use case: Add new admission

42 | P a g e
Actor: Staff
Goal: Record New admission
Precondition: Staff must be logged in
Trigger: The Staff decides to add new admission to the system
Scenario:
• The Staff login into the system.
• After login navigates to admission.
• Click on the option: Add New.
• The system displays the new admission form.
• Then he/she fills the form of that admission and add information
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid patient
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.11 Update Admission

Add update admission feature to the system.

Description and Priority
Update admission feature must be added to update admission data of Patients.
Stimulus/Response Sequences
Use case: Update admission
Actor: Staff
Goal: Update admission Data
Precondition: Staff must be logged in
Trigger: The staff decides to update admission to the system
Scenario:
● The staff login into the system.
● After login navigates to admission
43 | P a g e
 ● Select the edit button from the admission data that you want to update.
● The system displays the update admission data form.
● Then he/she fills the form of that admission and update information.
● Finally press the update button. System checks whether the form is filled up
correctly.
Exceptions:
● Invalid data.
● Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.12 Add lab test

Add new lab test for patient management feature to the system.
Description and Priority
A new lab test for patient feature must be added further to Patients.
Stimulus/Response Sequences
Use case: Add new lab test
Actor: Staff
Goal: Record New lab test
Precondition: Staff must be logged in
Trigger: The Staff decides to add new lab test for a patient.
Scenario:
• The Staff login into the system.
• After login navigates to lab test.
• Click on the option: Add New.
• The system displays the new lab test form.
• Then he/she fills the form of that lab test and add information
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid patient
Functional Requirements

44 | P a g e
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.13 Update lab test

Add update lab test feature to the system.

Description and Priority
Update lab test feature must be added to update admission data of Patients.
Stimulus/Response Sequences
Use case: Update lab test
Actor: Staff
Goal: Update lab test Data
Precondition: Staff must be logged in
Trigger: The staff decides to update lab test to the system
Scenario:
● The staff login into the system.
● After login navigates to lab test
● Select the edit button from the lab test data that you want to update.
● The system displays the update lab test data form.
● Then he/she fills the form of that lab test and update information.
● Finally press the update button. System checks whether the form is filled up
correctly.
Exceptions:
● Invalid data.
● Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.14 Add Operation

Add new Operation for patient management feature to the system.
Description and Priority
A new Operation for patient feature must be added further to Patients.
Stimulus/Response Sequences
45 | P a g e
Use case: Add new Operation
Actor: Staff
Goal: Record New Operation
Precondition: Staff must be logged in
Trigger: The Staff decides to add new Operation to the system
Scenario:
• The Staff login into the system.
• After login navigates to Operation.
• Click on the option: Add New.
• The system displays the new Operation form.
• Then he/she fills the form of that Operation and add information
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid patient
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.15 View Operation

View Operation for patients to the system.
Description and Priority
View Operation feature must be added to see Operation data of Patients.
Stimulus/Response Sequences
Use case: View Operation
Actor: Staff
Goal: View Operation Data
Precondition: Staff must be logged in
Trigger: The staff decides to View Operation to the system
Scenario:

46 | P a g e
 • The staff login into the system.
• After login navigates to Operation
• Select the View button from the Operation data that you want to View.
• The system displays the View Operation data form.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.16 Add Emergency patient

Add new Emergency patient for emergency feature to the system.

Description and Priority
A new Emergency patient for patient feature must be added further to Patients.
Stimulus/Response Sequences
Use case: Add new Emergency patient
Actor: Staff
Goal: Record New Emergency patient
Precondition: Staff must be logged in
Trigger: The Staff decides to add new Emergency patient to the system
Scenario:
● The Staff login into the system.
● After login navigates to Emergency patient.
● Click on the option: Add New.
● The system displays the new Emergency patient form.
● Then he/she fills the form of that Emergency patient and add information
● Finally press the submit button. System checks whether the form is filled up
correctly.
Exceptions:
● Invalid data.
● Form is not filled up correctly.
Functional Requirements

47 | P a g e
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.17 View Emergency patient

View Emergency patient for emergency feature to the system.

Description and Priority
An Emergency patient for patient feature must be viewed further to Patients.
Stimulus/Response Sequences
Use case: View Emergency patient
Actor: Staff
Goal: View Recorded Emergency patient
Precondition: Staff must be logged in
Trigger: The Staff decides to View Emergency patient to the system
Scenario:
● The Staff login into the system.
● After login navigates to Emergency patient.
● Click on the option: View all.
● Then click on any patient View
● The system displays the new Emergency patient details.
Exceptions:
● Invalid data.
● Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.18 Create billing

Create new invoice for all patients.

Description and Priority
A new invoice for patient must be added for specific Patient.
Stimulus/Response Sequences
Use case: Add new invoice

48 | P a g e
Actor: Staff
Goal: Create new invoice.
Precondition: Staff must be logged in
Trigger: The Staff decides to create new invoice from the system
Scenario:
● The Staff login into the system.
● After login navigates to bills.
● Click on the option: Add New.
● The system displays the new invoice form.
● Then he/she fills the form of add information.
● Finally press the submit button. System checks whether the form is filled up
correctly.
Exceptions:
● Invalid data.
● Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.19 Send Mail

Send new email for staff’s feature to the system.

Description and Priority
A new mail for staff’s feature must be added for Admin and it should be sent to any user.
Stimulus/Response Sequences
Use case: Send email
Actor: Staff
Goal: Record New email Data to staff
Precondition: Staff must be logged in
Trigger: The Staff decides to send new email to the system
Scenario:
● The Staff login into the system.
● After login navigates to Email service.
● Click on the option: Add New.
● The system displays the new email service form.

49 | P a g e
 ● Then he/she fills the form of that email service and add information.
● Finally press the submit button. System checks whether the form is filled up
correctly.
Exceptions:
● Invalid data.
● Form is not filled up correctly.
● Invalid email
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.18 Add Support Message

Add new Support for patient management feature to the system.
Description and Priority
A new Support for patient feature must be added further to Patients.
Stimulus/Response Sequences
Use case: Add new admission
Actor: Staff
Goal: Record New Support
Precondition: Staff must be logged in
Trigger: The Staff decides to add new Support to the system
Scenario:
• The Staff login into the system.
• After login navigates to Support.
• Click on the option: Add New.
• The system displays the new Support form.
• Then he/she fills the form of that Support and add information
• Finally press the submit button. System checks whether the form is filled
up correctly.
Exceptions:
• Invalid data.
• Form is not filled up correctly.
• Invalid patient
Functional Requirements

50 | P a g e
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.19 Update Support Message

Add update Support feature to the system.

Description and Priority
Update Support message feature must be added to update admission data of Patients.
Stimulus/Response Sequences
Use case: Update Support message
Actor: Staff
Goal: Update Support message Data
Precondition: Staff must be logged in
Trigger: The staff decides to update Support message to the system
Scenario:
● The staff login into the system.
● After login navigates to Support message
● Select the edit button from the Support message data that you want to update.
● The system displays the update Support message data form.
● Then he/she fills the form of that Support message and update information.
● Finally press the update button. System checks whether the form is filled up
correctly.
Exceptions:
● Invalid data.
● Form is not filled up correctly.
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

3.1.3.20 Log out

Logout System for all types of staffs.
Description and Priority
All users must logout to exit from the system
Stimulus/Response Sequences
51 | P a g e
Use case: Logout
Actor: Staff
Goal: Logout from Hospital management system
Precondition: Staff must be logged in
Trigger: Staff decides to exit from the system
Scenario:
● The user clicks on “LOGOUT” button and a confirm popup shows.
● System displays “Logged out”.
Exceptions:
● Invalid request
● No Internet
Functional Requirements
REQ-1: A smartphone / digital computing device
REQ-2: Internet Connection

52 | P a g e
3.2 Activity Diagram and Swimlane Diagram
3.2.1 Activity Diagram and Swimlane Diagram for Patient (General User)

3.2.1.1 Register

Activity Diagram:

Fig 3.2.1.1: Activity Diagram for Registration to System

Swimlane Diagram:

Fig. 3.2.1.2: Swimlane Diagram for Registration to System

53 | P a g e
3.2.1.2 Log in
Activity Diagram:

Fig. 3.2.1.3: Activity Diagram for Login to System

Swimlane Diagram:

Fig. 3.2.1.4: Swimlane Diagram for Login to System

54 | P a g e
3.2.1.3 View Appointments

Activity Diagram:

Fig. 3.2.1.5: Activity Diagram for View Appointment

Swimlane Diagram:

Fig. 3.2.1.6: Swimlane Diagram for View Appointment

55 | P a g e
3.2.1.4 Update profile
Activity Diagram:

Fig 3.2.1.7: Swimlane Diagram for Update profile

Swimlane Diagram:

Fig: Fig 3.2.1.8: Swimlane Diagram for Update profile

56 | P a g e
3.2.1.5 Log out
Activity Diagram:

Fig.3.2.1.9: Activity Diagram for Logout

Swimlane Diagram:

Fig. 3.2.1.10: Swimlane Diagram for Logout

57 | P a g e
3.2.2 Activity Diagram and Swimlane Diagram for Admin (Author

3.2.2.1 Log in

Activity Diagram:

Fig. 3.2.2.1: Activity Diagram for Login to System

Swimlane Diagram:

Fig. 3.2.2.2: Swimlane Diagram for Login to System

58 | P a g e
3.2.2.2 Update profile

Activity Diagram:

Fig 3.2.2.3: Activity Diagram for Update profile

Swimlane Diagram:

Fig 3.2.2.4: Swimlane Diagram for Update profile

59 | P a g e
3.2.2.3 Update system settings

Activity Diagram:

Fig 3.2.2.5: Activity Diagram for Update profile

Swimlane Diagram:

Fig 3.2.2.6: Activity Diagram for Update profile

60 | P a g e
3.2.2.4 Add new patient

Activity Diagram:

Fig. 3.2.2.7: Activity Diagram for Add New Patient to System

Swimlane Diagram:

Fig. 3.2.2.8: Swimlane Diagram for Add New patient to System

61 | P a g e
3.2.2.5 Add new Staff

Activity Diagram:

Fig.3.2.2.9: Activity Diagram for Add new staff to System

Swimlane Diagram:

Fig. 3.2.2.10: Swimlane Diagram for Add new staff to System

62 | P a g e
3.2.2.6 Add new department

Activity Diagram:

Fig. 3.2.2.11: Activity Diagram for Add New Departments to System

Swimlane Diagram:

Fig 3.2.2.12: Swimlane Diagram for Add New Room

63 | P a g e
3.2.2.7 Add new test data

Activity Diagram:

Fig 3.2.2.13: Activity Diagram for Add new test data

Swimlane diagram:

Fig 3.2.2.14: Swimlane Diagram for Add new test data

64 | P a g e
3.2.2.8 Add new Operation data

Activity Diagram:

Fig. 3.2.2.15: Activity Diagram for Add operation

Swimlane Diagram:

Fig. 3.2.2.16: Swimlane Diagram for Add operation

65 | P a g e
3.2.2.9 Add new medicine data

Activity Diagram:

Fig 3.2.2.17: Activity Diagram for Add new medicine data

Swimlane Diagram:

Fig 3.2.2.18: Activity Diagram for Add new medicine data

66 | P a g e
3.2.2.10 Add new room type data
Activity Diagram:

Fig 3.2.2.19: Activity Diagram for Add new room type data
Swimlane Diagram:

Fig 3.2.2.20: Activity Diagram for Add new room type data

67 | P a g e
3.2.2.11 Add new room data

Activity Diagram:

Fig 3.2.2.21: Activity Diagram for Add new room data

Swimlane Diagram:

Fig 3.2.2.22: Swimlane Diagram for Add new room data

68 | P a g e
3.2.2.12 Add new degree

Activity Diagram:

Fig 3.2.2.23: Activity Diagram for Add new degree

Swimlane Diagram:

Fig 3.2.2.24: Swimlane Diagram for Add new degree

69 | P a g e
3.2.2.13 Add new speciality

Activity Diagram:

Fig 3.2.2.25: Activity Diagram for Add new speciality

Swimlane Diagram:

Fig 3.2.2.26: Swimlane Diagram for Add new speciality

70 | P a g e
3.2.2.14 Monitor feedback system

Activity Diagram:

Fig 3.2.2.27: Activity Diagram for Monitor Feedback System

Swimlane Diagram:

Fig 3.2.2.27: Swimlane Diagram for Monitor Feedback System

71 | P a g e
3.2.2.15 Send email

Activity Diagram:

Fig. 3.2.2.29: Activity Diagram for Send mail

Swimlane Diagram:

Fig. 3.2.2.30: Swimlane Diagram for Send mail

72 | P a g e
3.2.2.16 Log out

Activity Diagram:

Fig. 3.2.2.31: Activity Diagram for Logout

Swimlane Diagram:

Fig. 3.2.2.32: Swimlane Diagram for Logout

73 | P a g e
3.2.3 Activity Diagram and Swimlane Diagram for Staff (General staff,
Doctor, Nurse)
3.2.3.1 Log in

Activity Diagram:

Fig. 3.2.3.1: Activity Diagram for Login to System

Swimlane Diagram:

Fig. 3.2.3.2: Swimlane Diagram for Login to System

74 | P a g e
3.2.3.2 Update profile

Activity Diagram:

Fig. 3.2.3.3: Activity Diagram for Update profile

Swimlane Diagram:

Fig. 3.2.3.4: Activity Diagram for Update profile

75 | P a g e
3.2.3.3 Add new patient

Activity Diagram:

Fig. 3.2.3.5: Activity Diagram for Add New Patient to System

Swimlane Diagram:

Fig. 3.2.3.6: Swimlane Diagram for Add New patient to System

76 | P a g e
3.2.3.4 Add new appointment

Activity Diagram:

Fig. 3.2.3.7: Activity Diagram for Add New Appointment

Swimlane Diagram:

Fig. 3.2.3.8: Swimlane Diagram for Add New Appointment

77 | P a g e
3.2.3.5 Add new visits

Activity Diagram:

Fig. 3.2.3.9: Activity Diagram for Add New Visit

Swimlane Diagram:

Fig. 3.2.3.10: Swimlane Diagram for Add New Visit

78 | P a g e
3.2.3.6 Add new admission

Activity Diagram:

Fig. 3.2.3.11: Activity Diagram for Add New Admission

Swimlane Diagram:

Fig. 3.2.3.12: Swimlane Diagram for Add New Admission

79 | P a g e
3.2.3.7 Add new lab test for patient

Activity Diagram:

Fig. 3.2.3.13: Activity Diagram for Add lab test for patient

Swimlane Diagram:

Fig. 3.2.3.14: Swimlane Diagram for Add lab test for patient

80 | P a g e
3.2.3.8 Add new operation

Activity Diagram:

Fig. 3.2.3.15: Activity Diagram for Add operation

Swimlane Diagram:

Fig3.2.3.16: Swimlane Diagram for Add operation

81 | P a g e
3.2.3.9 Add new Emergency patient

Activity Diagram:

Fig. 3.2.3.17: Activity Diagram for Add emergency patient

Swimlane Diagram:

Fig. 3.2.3.18: Swimlane Diagram for Add emergency patient

82 | P a g e
3.2.3.10 Create new bill

Activity Diagram:

Fig. 3.2.3.19: Activity Diagram for Create invoice

Swimlane Diagram:

Fig. 3.2.3.20: Swimlane Diagram for Create invoice

83 | P a g e
3.2.3.11 Send mail
Activity Diagram:

Fig. 3.2.3.21: Activity Diagram for Send mail

Swimlane Diagram:

Fig. 3.2.3.22: Swimlane Diagram for Send mail

84 | P a g e
3.2.3.12 Add new support message

Activity Diagram:

Fig. 3.2.3.23: Activity Diagram for Add message

Swimlane Diagram:

Fig. 3.2.3.24: Swimlane Diagram for Add message

85 | P a g e
3.2.3.13 Log out
Activity Diagram:

Fig 3.2.3.25: Activity Diagram for Logout

Swimlane Diagram:

Fig 3.2.3.26: Swimlane Diagram for Logout

86 | P a g e
3.3 Schema Diagram

Figure 3.3: Schema Diagram

87 | P a g e
3.4 Entity Relationship(ER) Diagram

Figure 3.4: Entity Relationship(ER) Diagram

88 | P a g e
3.5 Data Flow Modeling

The Data Flow Diagram (DFD) takes an input-process-output view of a system. In the figures,
data objects are represented by labeled arrows and transformations are represented by circles.

Fig 3.5: Level 0

89 | P a g e
 Chapter 4
Implementation details
4.1 Patient’s Panel

Fig 4.1 Patient’s Panel

4.2 Admin’s Panel

90 | P a g e
 Fig 4.2 Admin’s Panel

4.3 Staff (General) Panel

4.3 Staff (General) Panel

4.4 Doctor Panel

Fig 4.4 Doctor Panel

91 | P a g e
 Chapter 5

Testing

5.1 White Box Testing

White box testing is a type of testing that focuses on the internal structure of a software
application.

✔ Unit testing: This involves testing individual units of code, such as functions or
methods, to ensure that they are working correctly.
✔ Integration testing: This involves testing how different units of code work together, to
ensure that they are integrated correctly and produce the expected results.
✔ Code coverage testing: This involves testing how much of the code is executed during
testing, to ensure that all code paths are exercised and that the entire application is
tested.
✔ Mutation testing: This involves making small, deliberate changes to the code (called
"mutations"), and then rerunning the tests to ensure that they fail. This helps to
ensure that the tests are actually able to detect defects in the code.

5.2 Black Box Testing

Black box testing is a type of testing that focuses on the external behavior of a software
application, without looking at its internal structure or implementation details.

✔ Functional testing: This involves testing the application's functions and features to
ensure that they are working correctly and as expected.
✔ Usability testing: This involves testing the user experience of the application, to ensure
that it is easy to use and understand.
✔ Compatibility testing: This involves testing the application on different devices,
browsers, and operating systems to ensure that it works correctly in different
environments.
✔ Performance testing: This involves testing the application's performance, such as its
response time and stability under different load conditions.

92 | P a g e
 Chapter 6

Deploy and Delivery

Deploying a web application typically involves the following steps:

Building and testing the application: This typically involves writing and testing the code, and
packaging it into a deployable form (such as a WAR file for Java applications). Setting up the
production environment: This involves setting up the servers, databases, and other
infrastructure needed to run the application in production. This may involve configuring load
balancers, web servers, and other components.

Deploying the application: This involves transferring the application code and any necessary
dependencies (such as libraries or configuration files) to the production environment and
installing it on the servers.

Configuring the application: This involves setting any necessary application-specific

configuration, such as database connection strings or environment-specific settings. Testing
the deployment: After the application is deployed, it is important to test it to ensure that it is
working correctly in the production environment. This may involve running automated tests or
manually testing the application's functions.

Maintaining and monitoring the application: After the application is deployed, it is important
to monitor it for any issues or performance problems, and to perform regular maintenance to
keep it up to date and running smoothly.

93 | P a g e
References
1. Lu, Y., Li, Y., Skibniewski, M., Wu, Z., Wang, R., & Le, Y. (2015). Information and
commu nication technology applications in architecture, engineering, and construction
organizations: A 15-year review. Journal of Management in Engineering, 31(1), A4014010.

2. Lin, Y. C., Su, Y. C., Lo, N. H., Cheung, W. F., & Chen, Y. P. (2013). Application of Mobile
RFID-Based Safety Inspection Management at Construction Jobsite. Radio Frequency
Identifi cation from System to Applications, 10, 53176.

3. Kim, S. M., Shin, S. J., Seo, H. G., Kim, J., Han, M. C., & Han, C. G. (2020). Prediction of
Strength Development of the Concrete at Jobsite Applying Wireless Sensor Network (CIMS)
based on Maturity. In Proceedings of the Korean Institute of Building Construction Conference
(pp. 25-26). The Korean Institute of Building Construction.

4. Barlow, P. L. (2011). Development of an Integrated Project-Based Course: A Jobsite

Management Class Case Study. In Associated Schools of Construction 47th Annual
Conference Proceedings: Omaha, Nebraska.

5. de la Garza, J. M., & Howitt, I. (1998). Wireless communication and computing at the
construction jobsite. Automation in Construction, 7(4), 327-347.

94 | P a g e