Aim:-​Software Requirements Specification for Hospital Management

System

Prepared by

​ AXA DEVDA (49)

L
SHURTI MENON (50)
SONALI AGARWAL (51)
Theory 
 

1. Introduction
1.1 Purpose
The Software is for the automation of Hospital Management.It maintains two levels of
users:-Administrator Level,User Level.The Software includes:-Maintaining Patient details,
Providing Prescription, Precautions and Diet advice,Providing and maintaining all kinds of tests
for a patient,Billing and Report generation.

1.2 Scope
The proposed software product is the Hospital Management System (HMS). The system will be
used to get the information from the patients and then storing that data for future usage. The
current system in use is a paper-based system. It is too slow and cannot provide updated lists of
patients within a reasonable timeframe.The intentions of the system are to reduce over-time
pay and increase the number of patients that can be treated accurately. Requirements
statements in this document are both functional and non-functional.

1.3 - Definitions, Acronyms, and Abbreviations

HMS - Hospital Management System

1.4 References
http://www.dotnetfunda.com/articles/show/1052/sample-software-requirements-specification
-for-hospital-info-managemen

http://www.dotnetfunda.com/articles/show/1052/sample-software-requirements-specification
-for-hospital-info-managemen

2. Overall Description:
2.1 Product Perspective:
The HMS is designed to help the hospital administrator to handle patient, nurse and bed
information. The current design goal is to build an internal system to achieve the functionality
outlined in this specification.

2.2 Product Functions:

The HMS will allow the user to manage information about patients, nurses, and beds. Patient
management will include the checking-in and checking-out of patients to and from the hospital.
The HMS will also support the automatic backup and protection of data.

2​.​3 User Classes and Characteristics

Admin :-Admin has the full access to the system which means he is able to manage any
activity with regard to the system. He is the highest privileged user who can access to
the system.Key functions:​Manage employees, patients and equipment,Allocate 
resource,Administer the charges,Generate reports,Manage ambulances,Manage doctors, 
Manage salaries 
  
Employee:-Interacts with the systems most often to supply service to customers 
Key functions Keep track of patient details,Keep track of test detail, Make ambulance 
reservations,Keep track of progress of patients , Maintain bill details,Manage inventory 
  
2.4 Operating Environment:
Following are the requirements for running the software successfully-
Processor – Pentium III or Higher.
Ram – 512 MB or Higher.
Disk Space – 10 GB or Higher.
OS – Windows XP or Above.
2.5 Design & Implementation Constraint:
GUI only in English.
Login and password is used for identification of user and there is no facility for guest.
2.6 Assumption & Dependencies:
It is assumed that one hundred compatible computers will be available before the system is
installed and tested.
It is assumed that Hospital will have enough trained staff to take care of the system.

3.Specific Requirements 
 
3.1 External Interface Requirements:
3.1.1 User Interface:
Input from the user will be via keyboard input and mouse point and click. The user will navigate
through the software by clicking on icons and links. The icons will give appropriate responses to
the given input.

3.1.2 Hardware Interface:

These are the minimum hardware interfaces-
Processor – Pentium III or Higher.
Ram – 512 MB or Higher.
Disk Space – 10 GB or Higher.

3.1.3 Software Interface:

These are the minimum software interfaces-
Technologies: C# .Net 2.0
Database: SQL server (standard edition).
Operating system: Windows XP or above.

3.2 Functional Requirements:

Registration-
Add patients
The HMS shall allow front-desk staff to add new patients to the system.
Assign ID
The HMS shall allow front-desk staff to give each patient a ID and add it to the patient’s record.
This ID shall be used by the patient throughout his/her stay in hospital.

Check Out-
Delete Patient ID
The administrative staff in the ward shall be allowed to delete the ID of the patient from the
system when the patient checks out.

Add to beds-available list

The administrative staff in the ward shall be allowed to put the beds just evacuated in
beds-available list.

Report Generation-
Patient information
The HPIMS shall generate reports on patients about the following information: patient’s PHN,
patient’s name, ward name, bed number and the doctor’s name which was assigned.

Bed Availability
The HPIMS shall generate reports on bed availability about the following information: ward
name, bed number, occupied/unoccupied.

Database-
Patient Mandatory Information
Each patient shall have the following mandatory information: first name, last name, phone
number, personal health number, address, postal code, city, country, patient identification
number.
Update Patient Information
The HMS shall allow the user to update any of the patient’s information as described in SRS007.

3.3 Non Functional Requirements

3.3.1 Performance Requirements
The performance of our software is at its best when the following regularly are
done:
Password management
Regular Database Archiving
Virus Protection

3.3.2 Safety Requirements

Humans are error prone ,but the negative effects of common errors should be
limited example user should realize that a given command will delete data ,and
be asked to confirm their intend or have the option to undo.

3.3.3 Security Requirements

Each member is required to enter an individual Username and password when
accessing the software . Administrators have the option of increasing the level of
password security their member use.
The data in the database is secured through multiple layers of protection.
One of those security layers involves member passwords. For maximum Security
of your software , each member must protect their password.

3.3.4 Software Quality Attributes

The Quality of the system is maintained in such a wat that it can be very
user-friendly. The software quality attributes are assumed as follows:
Accurate and hence reliable
Secured
Fast Speed
Compatibility

4.Other Requirements
4​.1 Database
Doctor

D_Id Dname Specialization Salary D_Phno Address Experience

Patient
P_id Pname Diagnosis P_phno age Paddress

Staff

S_id Salary Qualification

Department

De_id De_name No. of doctors No. of staff Facilities

Medicine

code price quantity

Ward

Ward_no Ward_name
4.2 Schedule and Budget

Schedule:
Sr No. Assigned Person Task Week
1. Sonali Srs 1
2. Laxa User Interface 2
3. Shruti Coding 2
4. Shanaya Testing 1
Total 6 Weeks

Budget Table:

Sr no Software used Cost Estimation(in dollaors)

1. Visual basic 6.0 30.21

2. Microsoft Visio 530

Total 560.21

Conclusion:-

Thus we have successfully implemented software requirement

specification document for hospital management system.