GOVERNMENT ENGINEERING COLLEGE, BIKANER

HOSPITAL MANAGEMENT SYSTEM

SOFTWARE REQUIREMENT SPECIFICATION
VERSION 1.0 APPROVED

SUBMITTED BY à

GROUP 2
1. AMIT AGARWAL(18EEBCS006)
2. ANJALI LADHA(18EEBCS008)
3. ANSH BADAYA(18EEBCS009)

SUBMITTED TO à

MISS.POONAM SHARMA
So ware Requirements Specifica on for Hospital Management System Page ii

Table of Contents
Table of Contents ............................................................................................... 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 ................................................................................ 1
1.5 References ..................................................................................... 2
2. Overall Descrip on ........................................................................................ 3
2.1 Product Perspective ....................................................................... 3
2.2 Product Functions .......................................................................... 3
2.3 User Classes and Characteristics .................................................... 4
2.4 Operating Environment.................................................................. 5
2.5 Design and Implementation Constraints ........................................ 6
2.6 User Documentation ...................................................................... 6
2.7 Assumptions and Dependencies .................................................... 7
3. External Interface Requirements ................................................................... 8
3.1 User Interfaces ............................................................................... 8
3.2 Hardware Interfaces....................................................................... 8
3.3 Software Interfaces ........................................................................ 8
3.4 Communications Interfaces ........................................................... 8
4. System Features ............................................................................................ 9
4.1 Intensive Care unit system ............................................................. 9
4.2 Outpatient Department System ................................................... 10
4.3Outpatient Department System ................................................... 11
So ware Requirements Specifica on for Hospital Management System Page iii

5. Other Nonfunc onal Requirements ............................................................. 12

5.1 Performance Requirements ......................................................... 12
5.2 Safety Requirements .................................................................... 12
5.3 Security Requirements ................................................................. 12
5.4 Software Quality Attributes ......................................................... 12
5.5 Business Rules .............................................................................. 13
So ware Requirements Specifica on for Hospital Management System
Page 1

1. INTRODUCTION

1.1 PURPOSE

The Aim of this PBM Hospital management System(PBM HMS) is to give a free and open
source software(FOSS)Hospital Management System developed for our client PBM
Hospital . The version of this SRS is 1.0 Approved, if updated will be mentioned above.
The scope of this product is to cover all the sub-systems mentioned below :-

I. Intensive Care Unit (ICU)

II. Outpatient Department (OPD)

III. Emergency Department (ED)

1.2 DOCUMENT CONVENTIONS

This document will use standard IEEE format. Design of the document is in Shaded
format,the format of the headings Is as follows :-

Major Headings are in 14pt font, and concurrent headings in 12pt font.

1.3 INTENDED AUDIENCE AND READING SUGGESTIONS

The SRS document is intended for software engineers, system testers and software
designer in developing, testing and producing the PBM HMS. It is suggested to the users
to read the sections mentioned in the right order.

1.4 PRODUCT SCOPE

Currently, the PBM hospital is using a manual method to handle their records, from patient
entry to patient’s treatment, all process is done manually ,which is somehow very risky as
it is file based one, as if we are in need of checking very old records and also when large
numbers of records are there, also in emergency like fire, natural disasters, the records
can’t be managed or handled.

So to overcome the above mentioned problems, we have made a standalone application

to handle all the process in PBM hospital digitally.

The scope of the ICU System is to save the maximum time in emergency cases like to
caters to patients with severe or life-threatening illness and injuries , as the software helps
So ware Requirements Specifica on for Hospital Management System
Page 2

in quick registration of the patient by registering online till reaching the hospital, quick
checking of availability of doctor and issuing ECG reports quickly.

The scope of the OPD system is used to register a new patient for the OPD consultation
i.e patient who require a bed and need to be admitted for overnight care and provide
appointment to the new and old patients for the doctor”s consultation in the department.
The system will also help the patient to be registered online and get appointment for a
doctor while sitting at their home.

The scope of the ED system is used to treat patients without prior appointment.The
function under ED gets details of patient and to assign them token no. & bed no.

1.5 REFERENCES

Wikipedia HIS page: h ps://en.wikipedia.org/wiki/Hospital_information_system

Wikipedia PBM Hospital:- https://wikimapia.org/1484128/PBM-Hospital-Bikaner

So ware Requirements Specifica on for Hospital Management System
Page 3

2. OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

The PBM Hospital Management System is an open source system comprising of

subsystems by which all the traditional and outdated means of tracking patient information
i.e in hard copy format is replaced by time conscientious, organised and monitorized by
digitally storing of data.

The fully functional automated hospital management system which will be developed
through this project will use a database to store patient, employee, stock details, etc. The
access limitations provided through across privilege levels will enhance the security of the
system.

2.2 PRODUCT FUNCTIONS

The PBM HMS has three subsystems and these subsystems shall perform the following
features :-

ICU Management Systemà

• Recording Patient details

• Assiging Doctor, nurse and ICU no.

• Patient ID Generated and Informing to family is done by receptionist.

OPD Management Systemà

• Recording Patient details

• Assigning Doctor, room no. And token no.

• Patient Id, token no. generated.

• Printing bill of payable fees.

So ware Requirements Specifica on for Hospital Management System
Page 4

ED Management Systemà

• Recording Patient details

• Assigning Doctor, room no. , bed no. And token no.

• Patient Id generated.

• Printing bill of payable fees.

2.3 USER CLASSES AND CHARACTERISTICS

The entire Free and open source software PBM hospital management system (FOSS
PBM HMS)suite program has a set of users, each with different security privileges. The
user types are :-

v Admin

Admin has full access to system, the highest privileged user. Key functions by
admin :-

Ø Manage patients and equipments

Ø Allocate resources

Ø Administer the charges

Ø Generate reports

Ø Manage Ambulances

Ø Manage doctors
So ware Requirements Specifica on for Hospital Management System
Page 5

v Nurse

Interacts with the system most often to supply service to patient, Key Function by
nurse:-

Ø Keep track of patient details

Ø Keep track of report details

Ø Keep track of progress of patients

Ø Maintain bill details

v Patient

Limited Access to patient, mainly non-editable, just like notifications :-

Ø Regular Report Updates

Ø Bill Details

Ø Appointment Time’s

Ø Emergency Button

Ø Medicine time reminder

2.4 OPERATING ENVIRONMENT

The PBM HMS program runs on :-

Software Requirements

• Windows 7 or above it.

• My SQL server

• GUI-Based
So ware Requirements Specifica on for Hospital Management System
Page 6

Hardware Requirements

• Core i3 processor

• 4GB Ram

• 20GB of hard disk space in terminal machines

• 1TB hard disk space in server machine

2.5 DESIGN AND IMPLEMENTATION CONSTRAINTS

Items and issues that may limit the options available to the software developers are legal
and ethical constraints with regard to PBM HMS development and medical practices.
Constraints :-

Ø Database is password protected

Ø System is wirelessly networked with an encryption

Ø Should use less RAM and processing power.

Ø Only administrator can access the whole system.

Ø System is highly protected, can’t be accessed without hospital premises.

2.6 USER DOCUMENTATION

Ø The application will come with an “About” tab, which will allow user to access the
offline and online HTML help manual(updated with each version)

Ø It will include full description of product, from installation of software to it’s working.

Ø User manual includes email address to contact us in need.

Ø All the tasks are listed alphabetically or grouped for easy looking of information for
user.
So ware Requirements Specifica on for Hospital Management System
Page 7

2.7 ASSUMPTIONS AND DEPENDENCIES

Ø Each user must have a valid user id and password

Ø As a open source project so it shall change overtime i.e regular change to this SRS.

Ø Only the administrator can delete records.

Ø It is assumed that the system will be networked and capable of routing to an

internet gateway.
So ware Requirements Specifica on for Hospital Management System
Page 8

3.1 EXTERNAL INTERFACE REQUIREMENTS

3.1 USER INTERFACES

Not Available

3.2 HARDWARE INTERFACES

Not Available

3.3 SOFTWARE INTERFACES

Not Available

3.4 COMMUNICATIONS INTERFACES

Not Available
So ware Requirements Specifica on for Hospital Management System
Page 9

4. SYSTEM FEATURES

4.1 INTENSIVE CARE UNIT

Nam Intensive Care Unit System (ICU System)

Description The func on under ICU gets mobile number of patient’s rela ves or who
are in the premises with the patient and create a record with patient
name. It also gets the availability of the doctor and nurse needed for ICU
treatment. It also allots the ICU no.

Data entry Operator, Receptionist

Actor

Pre-conditions The operator should login with user account

Main flow of events 1) User selects “ICU” at home page.

2) Patient data entry to required fields.

3) User enter data to required fields.

4) User assign doctor and nurse to the patient as per availability.

5) User assign ICU no. to the patient’s entry.

6) User selects “Add entry” button.

7) Message Displayed :- “Record created successfully”.

8) System generates a patient id and diplay it. contact the Doctor and
nurses for immediate treatment.

Extensions If mandatory fields left by user, prompt user to enter all mandatory fields

Non-Mandatory Patient’s Government ID

Field
So ware Requirements Specifica on for Hospital Management System
Page 10

4.2 OUTPATIENT DEPARTMENT

Nam Outpatient Department(OPD)

Description The func on under OPD gets name, mobile number, age, sex, address,
government verified id and description of the problem of the patient. It
also gets the availability of the doctor. It will generate a patient
registration number.

Data entry Operator, Receptionist

Actor

Pre-conditions The operator should login with user account

Main flow of events 1) User selects “OPD” at home page.

2) Patient data entry to required fields.

3) User enter data to required fields.

4) User assign doctor to the patient as per availability.

5) User assign Room no. and token no. to the patient’s entry.

6) User selects “Payable Amount” and enter the payable fees.

7) User selects “Add entry” button.

8) Message Displayed :- “Record created successfully”.

9) System generates a patient id and display it.

10) User selects “print” button and system order printer connected to
print 2 copies of the registration form

Extensions If mandatory fields left by user, prompt user to enter all mandatory fields
So ware Requirements Specifica on for Hospital Management System
Page 11

4.3 EMERGENCY DEPARTMENT

Nam Emergency Department(ED)

Description The func on under ED gets name, mobile numbe and government verified
id and description of the problem of the patient. It also gets the availability
of the doctor, bed and patients.

Data entry Operator, Receptionist

Actor

Pre-conditions The operator should login with user account

Main flow of events 1) User selects “ED” at home page.

2) Patient data entry to required fields.

3) User enter data to required fields.

4) User assign doctor and nurse to the patient as per availability.

5) User assign Room no. , bed no. and token no. to the patient’s entry.

6) User selects “Payable Amount” and enter the payable fees.

7) User selects “Add entry” button.

8) Message Displayed :- “Record created successfully”.

9) System generates a patient id and display it.

10) User selects “print” button and system order printer connected to
print 2 copies of the registration form

Extensions If mandatory fields left by user, prompt user to enter all mandatory fields
So ware Requirements Specifica on for Hospital Management System
Page 12

5. OTHER NONFUNCTIONAL REQUIREMENTS

5.1 PERFORMANCE REQUIREMENTS

• The so ware should have high performance.

• The hardware and so ware should be able to receive and transmit data correctly.

• Firewall should have been installed and no compromisation in security should be there.

• Machines should perform the specific task only to maximise the efficiency.

5.2 SAFETY REQUIREMENTS

• An offline mode should be provided to ease the process.

• Response to the query of the patient should be immediate.

• Toll-Free number should be provided and should work properly.

• In case of non-availability of connection, system should receive a notification about the

query.

5.3 SECURITY REQUIREMENTS

• Machines should have all recent windows updates installation.

• The machines should be virus free.

• All the confiden al data of the patients should be maintained properly.

• Before accessing the system, one should have to give identification to the system.

• Passwords of system should be changed yearly.

• Reporting of bugs and errors facility should be there.

So ware Requirements Specifica on for Hospital Management System
Page 13

5.4 SOFTWARE QUALITY ATTRIBUTES

Adaptability, Availability, Correctness, Flexibility, Interoperability, Maintainability, Portability,

Reliability, Reusability, Robustness, Testability, and Usability of the Hospital Management System
should be maximised.