Software Requirements

Specification
for

Hospital Management
System
Prepared by

332070 Riddhi Pawar

332068 Namrata Thakur

332054 Prathamesh Sangai

Vishwakarma Institute of Information Technology

08-09-2021
SRS for Hospital Management System Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions .................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................Error! Bookmark not defined.
2. Overall Description ..................................................................................................................2
2.1 Product Perspective.......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 2
2.4 Operating Environment .................................................................................................................... 2
2.5 Design and Implementation Constraints .......................................................................................... 3
2.6 User Documentation ........................................................................................................................ 3
3. External Interface Requirements ...........................................................................................4
3.1 User Interfaces ................................................................................................................................. 4
3.2 Hardware Interfaces ......................................................................................................................... 4
3.3 Software Interfaces .......................................................................................................................... 4
3.4 Communications Interfaces ............................................................................................................. 4
4. System Features .......................................................................................................................5
5. Other Nonfunctional Requirements .....................................................................................10
5.1 Performance Requirements ............................................................................................................ 10
5.2 Safety Requirements ...................................................................................................................... 10
5.3 Security Requirements ................................................................................................................... 10
5.4 Software Quality Attributes ........................................................................................................... 10
Appendix A: Glossary..................................................................................................................11

Revision History
Name Date Reason For Changes Version
SRS for Hospital Management System Page 1

1. Introduction

1.1 Purpose

The purpose of this Software Requirements Specifications (SRS) is to fully document the
specifications and requirements for the Hospital Management System (HMS).
The purpose of this HMS software is to develop a Web-application to optimize and digitalize all
sort of operations from patient registration to appointment scheduling, document management,
consultation management, prescription generation, staff management etc.

1.2 Document Conventions

The document is prepared using Microsoft Word and has used the font type 'Times New Roman'.
Major headings are in bold 18pt font size, and concurrent headings in bold 14 pt font size. Sections
are in 12pt font size.

1.3 Intended Audience and Reading Suggestions

This document is intended for clients, developers, project managers, marketing staff, users, testers,
and documentation writers. It is suggested to read the sections sequentially.

1.4 Product Scope

This software is mainly for Small to Medium scale Hospitals with OPD facility. The scope of this
software is to create a digital system to handle hospital processes. Currently, SARU hospital is
using a manual system to handle the hospital process. The process includes keeping records of
patient’s appointment to consult a doctor, patient’s previous visits and prescription details,
diagnosed symptoms, prescribed medicines as well as details of currently working employees in the
hospital. The software allows patients to access their prescriptions, all doctors contact details for
emergency situations and remind next follow up date.
SRS for Hospital Management System Page 2

2. Overall Description

2.1 Product Perspective

This software is an entirely new product. The fully functional hospital management system will
eliminate the drawbacks of the manual system by improving the reliability, efficiency, security and
performance. The usage of a database to store details will accommodate easy access, retrieval,
search and manipulation of data while maintaining ACID properties. The access limitations
provided through the login facility will enhance the security of the system. The system will
facilitate concurrent access and convenience to the patients, doctors and receptions.

2.2 Product Functions

• Secure Sign In.

• Manage OPD queue.
• Access OPD details.
• Generate prescription.
• Store and retrieve patients and employee details.

2.3 User Classes and Characteristics

• Administrator- Admin can add, edit and remove employees, display list of all active
employees.
• Doctor- He can access patients previous visits history, generate prescription and it will be
automatically sent to receptionist.
• Receptionist- She can add new patients, search existing patients, modify patient’s details,
manage OPD queue, take printout of prescriptions.
• Patient- They can access their prescriptions, have all doctors contact details, get reminder of
next follow up date.

2.4 Operating Environment

2.4.1 Software requirements (Minimum)

• Windows 7
• JRE 1.8
• MySQL server

2.4.2 Hardware Requirements (Minimum)

• Core i5 processor
• 4GB Ram
• 10GB of hard disk space
SRS for Hospital Management System Page 3

2.5 Design and Implementation Constraints

• Should use less RAM and processing power.

• Each user should have unique ID and password to login.
• Software is accessible through internet.

2.6 User Documentation

On the Sign In page, in bottom right corner a help link is given. It will allow users to access online
help manual.
SRS for Hospital Management System Page 4

3. External Interface Requirements

3.1 User Interfaces

The system will provide a Sign In page to allow users to login into their respective accounts. After
successful login, users will be presented with an easy to use dashboard interface to access different
functionalities of the system as per their role and assigned permissions. The errors that occur during
database operations are displayed at the top of the dashboard interface.

3.2 Hardware Interfaces

There are no special hardware interface requirements.

3.3 Software Interfaces

• Operating System: Windows 7 Ultimate or above

• Back End: MySQL, JRE 1.8 or above
• Front End: Bootstrap, jQuery

3.4 Communications Interfaces

• Web Browser: Microsoft Edge, Chrome or Firefox
SRS for Hospital Management System Page 5

4. System Features

4.1 User Sign In

4.1.1 Description and Priority

The employees that are working in the hospital and the patients should be able to
login and access their dashboard.
Priority: High
4.1.2 Stimulus/Response Sequences
This is the first page of the software which is presented to the user.
4.1.3 Functional Requirements
Success:
When the user selects valid role, enters correct login credentials i.e. username and
password, he/she must be able to login into their account and access the dashboard.
Failure:
When the user selects incorrect role or provides invalid login credentials, he/she
should not be able to login into the system as well as an error should be displayed
‘No such account exists. Please insert valid credentials’.

4.2 Dashboard

4.2.1 Description and Priority

The employees and the patients should be able to access different functionalities of
the system as per their role and assigned permissions.
Priority: High
4.2.2 Stimulus/Response Sequences
The user has to first login using login form. Then if login is successful, user can
access his dashboard.
4.2.3 Functional Requirements
The user should be able to access different functionalities of the system as per their
role and assigned permissions.

4.3 Add/Remove Employee

4.3.1 Description and Priority

The administrator can see list of all active employees in the hospital, add new
employee, remove existing employee, edit particular employee details.
Priority: High
SRS for Hospital Management System Page 6

4.3.2 Stimulus/Response Sequences

The admin logs into his account using valid login credentials. Then click on the ‘Add
Employee’ option on side navbar to add new employee details. Click on ‘All
Employees’ option to see list of employees. Then click ‘View’ button in front of
his/her name and then click on ‘Delete’ button to remove employee or ‘Edit’ button
to edit his details.
4.3.3 Functional Requirements
Success:
When the administrator adds new employee details in the system, an account is
created for him/her and login credentials are set to employee id (as username) and
Aadhar number (as password).
When administrator remove an employee account, his/her account must be closed
and he/she should not be able to login.
Failure:
When administrator is not able to add or remove an employee, an error message
should be displayed describing what caused the problem.

4.4 Edit User Login Credentials and Details

4.4.1 Description and Priority

The employees and the patients can change their login as well as personal details.
Priority: Medium
4.4.2 Stimulus/Response Sequences
The user accesses his/her dashboard by logging in. Then choose ‘edit’ option to
change login credentials and then enter username and new password. Choose
‘personal info’ option to see and edit personal details.
4.4.3 Functional Requirements
Success:
When user enters new login credentials, he must be able to log in using new
credentials not the previous one.
When user changes his/her personal details those changes should be reflected to
his/her profile and patients details section in doctor’s dashboard in case of patients.
Failure:
When the user enters different password in password and confirm password fields
while changing login credentials an error should be displayed ‘password and confirm
password must match’.
When the user tries to change his own unique id provided by system while updating
personal details error should be displayed.
SRS for Hospital Management System Page 7

4.5 Add new patient

4.5.1 Description and Priority

The receptionist can add new patient’s data in the system.
Priority: High
4.5.2 Stimulus/Response Sequences
The receptionist logs in his/her account. Then click on ‘add patient’ option to add
new patients details and assign a doctor.
4.5.3 Functional Requirements
Success:
When the patient details are filled and submitted patients account must be created
and he/she must be assigned unique id and should be able to login into their account
and access their dashboard.
Failure:
When receptionist is not able to add patient’s details, an error message should be
displayed describing what caused the problem.

4.6 Search existing patient

4.6.1 Description and Priority

The receptionist can search for existing patient’s data in the system.
Priority: High
4.6.2 Stimulus/Response Sequences
The receptionist logs in his/her account. Then click on ‘search patient’ option to
search existing patients’ details using either of following, their name, id, mobile no
or Aadhar no.
4.6.3 Functional Requirements
Success:
When the receptionist enters patient’s name or id or mobile no or Aadhar no and
clicks on submit button, system should display patient’s details along with options to
add the patient in OPD queue or edit details.
Failure:
When receptionist is not able to search patient’s details, an error message should be
displayed describing what caused the problem.

4.7 Manage OPD Queue

4.7.1 Description and Priority

The receptionist can add, remove and check patient’s in OPD queue.
Priority: High
SRS for Hospital Management System Page 8

4.7.2 Stimulus/Response Sequences

The receptionist logs in his/her account. Then click on ‘search patient’ option to
search existing patient then click on ‘add to OPD’ button. To check OPD queue
choose ‘OPD queue’ option. Then to remove patient from OPD queue click on
‘cancel’ button.
4.7.3 Functional Requirements
Success:
When the receptionist clicks on ‘add to OPD’ or ‘cancel’ button patient should be
added in OPD or removed respectively. At the same time, OPD queue should be
updated at doctor’s login as well. When receptionist choose ‘OPD queue’ option
OPD queue of all doctors should be visible to receptionist.
Failure:
When receptionist is not able to search patient’s details, an error message should be
displayed describing what caused the problem.

4.8 Patient’s Visits History

4.8.1 Description and Priority

The doctor can get a particular patient’s previous visits details in the system.
Priority: High
4.8.2 Stimulus/Response Sequences
The doctor logs in his/her account. Then click on ‘OPD queue’ option. Selects
particular patient by clicking ‘view’ button. Then choose ‘history’ option to see
patient’s previous records.
4.8.3 Functional Requirements
Success:
When the doctor chooses ‘history’ option of particular patient, patient’s previous
visits details should be displayed with date.
Failure:
When doctor is not able to access patient’s visit details, an error message should be
displayed describing what caused the problem.

4.9 Prescription and Observations

4.9.1 Description and Priority

The doctor can record patient’s observations and prescription data in the system.
Priority: High
4.9.2 Stimulus/Response Sequences
The doctor logs in his/her account. Then click on ‘OPD queue’ option. Selects
particular patient by clicking ‘view’ button. Then choose ‘observations and
prescription’ option.
SRS for Hospital Management System Page 9

4.9.3 Functional Requirements

Success:
When the doctor chooses observations and prescription option, he/she should be able
to record the patient’s symptoms and diagnosis which will be accessible only to the
doctor alongside he/she should be able to note down prescription for patient i.e.
medicine’s and dosage, do’s, don’ts, investigations, follow-up, fees. When clicked on
submit prescription should be generated and sent to receptionist.
Failure:
When doctor is not able to note patient’s observations and prescription, an error
message should be displayed describing what caused the problem.

4.10 Print Prescription

4.10.1 Description and Priority

The receptionist can take printout of the prescription given by doctor.
Priority: High
4.10.2 Stimulus/Response Sequences
The receptionist logs in his/her account. Then choose the ‘prescriptions’ option. Then
click on ‘print’ button to get printout of particular patient’s prescription.
4.10.3 Functional Requirements
Success:
When the receptionist clicks on ‘print’ button print of prescription is generated.
Printer can be attached to get copy of the prescription.
Failure:
When receptionist is not able to print patient’s prescription, an error message should
be displayed describing what caused the problem.
SRS for Hospital Management System Page 10

5. Other Nonfunctional Requirements

5.1 Performance Requirements

• Response time-The system will give responses within 2 second after checking the patient
information and other information.
• Capacity-The system must support 100 people at a time.
• User interface- User interface screen will response within 5 seconds.

5.2 Safety Requirements

If there is extensive damage to a wide portion of the database due to catastrophic failure, such as a
disk crash, the recovery can be done by a past copy of the database.

5.3 Security Requirements

To prevent security or privacy issues and allow protection of the user data, login form is provided.
After login, users access different functionalities of the system as per their role and assigned
permissions. Users login credentials i.e. password is stored in hashed form using Bcrypt algorithm.

5.4 Software Quality Attributes

5.4.1. Security-
Users will be able to access only those functionalities of the system as per their role and
assigned permissions and not that of other users.

5.4.2. Availability-
The hospital management system shall be available to users 24 hours a day, 7 days a week,
with the exception of being down for maintenance no more than one hour in a month.

5.4.3. Reliability-
The average time to failure shall be 30 days. In the event that a server does crash, a backup
server will be up and running within the hour.

5.4.4. Maintainability-
Any updates or defect fixes should be made on server-side computers only without any
patches required by the user.

5.4.5. Usability-
The system is designed keeping in mind ease of use for the end user. This HMS system is
user-friendly.
SRS for Hospital Management System Page 11

Appendix A: Glossary
• HMS- Hospital Management System
• JRE- Java Runtime Environment
• JSP- Java Server Pages