System Requirement Specification

Hospital Management System

Contents

1. Document Detail ....................................................................................................................................... 3

1.1 Revision & Approval History ......................................................................................................... 3
1.2 Definition, Acronyms and Abbreviations ...................................................................................... 3
1.3 References .................................................................................................................................... 3
2. Introduction .............................................................................................................................................. 4
2.1 Purpose of the Document ............................................................................................................. 4
2.2 Intended Audience ........................................................................................................................ 4
3. System Overview....................................................................................................................................... 5
3.1 Scope ............................................................................................................................................. 5
3.2 Objective ............................................................................................................................................. 5
3.3 Overall Description............................................................................................................................ 5
3.3.1 Product Perspective .................................................................................................................. 5
3.3.2 Product Description .................................................................................................................. 5
4. Functional Requirement ....................................................................................................................... 7
5. UML Diagrams ..................................................................................................................................... 10
5.1 Use Case Diagram ....................................................................................................................... 10
5.2 Class Diagram .............................................................................................................................. 13
5.3 Sequence Diagram ...................................................................................................................... 14
5.4 Activity Diagram .......................................................................................................................... 15
6. External Interface ................................................................................................................................ 19
6.1 User Interface ............................................................................................................................. 19
6.2 Hardware Interface ..................................................................................................................... 19
6.3 Software Interface ...................................................................................................................... 19
7. Special User Requirements ................................................................................................................. 19
7.1 Non-Functional Requirement ..................................................................................................... 19
7.2 Performance Requirement ......................................................................................................... 19
7.3 Software System attributes ........................................................................................................ 19
7.3.1 Reliability ........................................................................................................ 19
7.3.2 Availability ...................................................................................................... 19
7.3.3 Security ........................................................................................................... 19
7.3.4 Maintainability ................................................................................................ 20
7.3.5 Portability ....................................................................................................... 20
 eiTRA

1. Document Detail
1.1 Revision & Approval History

Author Reviewer Approver

Version Date Date Date

Name (DD-MM- Name (DD-MM- Name (DD-MM-
YYYY) YYYY) YYYY)
Divya Ahuja,
Hardik Duva,
13th Mr.
Jimi Patel,
Issue 1.0 February Saurabh - -
Kiran Ezhava,
2017 Soni
Pratik Solanki,
Ritu Fichadiya

Version Description of Change

Issue 1.0 Created initial draft version (Mantis ID : 0001)

1.2 Definition, Acronyms and Abbreviations

Definition/Acronym/Abbreviation Description
HMS Hospital Management System
HR Human resource
OPD Out Patient Department
IPD In Patient Department
EMR Electronic Medical Record
OT Operation Theatre
TPA Third Party Administrator
CSSD Central Sterile Stores Department
MySQL a query language to interrogate the system
GUI Graphical User Interface
MIS management information system

1.3 References

Hospital Management System

 eiTRA

No. Document Version Remarks

2. Introduction

2.1 Purpose of the Document

The purpose of this document is to give a detailed description of the requirements
for the "Hospital Management System". It will illustrate the purpose and complete
requirement for the system. It will also explain system constraints, interface and
interactions with other external applications. This document is primarily intended to
be submitted to a customer for its approval as a reference for developing the first
version of the system for the development team.
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.
These include following: Administrative Staff, patients and developers.

2.2 Intended Audience

The intended audience of this document includes the client, requirements team,
requirements analyst, design team, testers, and other members of the developing
organization to provide guidance.

Hospital Management System

 eiTRA

3. System Overview

3.1 Scope
The proposed software product is the Hospital Management System (HMS). The
system will be used to allocate beds to patients on a priority basis, and to assign
doctors to patients in designated wards as need arises. Doctors will also use the
system to keep track of the patients assigned to them. Nurses who are in direct
contact with the patients will use the system to keep track of available beds, the
patients in the different wards, and the types of medication required for each patient.
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.
Doctors must make rounds to pick up patients treatment cards in order to know
whether they have cases to treat or not.
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.
It also keeps track for the equipment, sterile tools and linen.

3.2 Objective
It is user friendly which reduces the burden and helps to manage all sections of
hospital like reception, lab, inpatient, outpatient management, billing, etc. which
improves the efficiency of the system.
It improves patient services through efficient use of available resources including
human and financial.

3.3 Overall Description

3.3.1 Product Perspective

This Hospital Management System is a self-contained system that manages
activities of the hospital as Patient Info, Staff info, Billing etc. Various stakeholders
are involved in the hospital management system.

3.3.2 Product Description

When the users wants to use system, first they need to register themselves. After
registration and login, there are several options and the user chooses the option based
on his/her requirement.
It includes the clinical, back office and generic management of all activities. It
integrates the entire resources of the hospital into one integrated web application.

Hospital Management System

 eiTRA

Hospital Management System

 eiTRA

4. Functional Requirement

Out Date Appro

Req. No. Requirements Description Input Priority
Put Reviewed ved By
First time
R1 Registration connection on
the network

ABOUT
DETAILS
Register on the First name, Registration
add network by Last name, Details
R1.1 Registration adding Email-id, recorded and High
Details Registration Contact, unique ID is
Details Address assigned

Connect to
LOGIN DETAILS
network
R2 Login Username,
whenever
Password
wanted
User logged
Connect to the
Username, in and gets
R2.1 get Login network using High
Password the home
Login Details
page.
Login Details
reset link
Request for
sent to email
Login after Email id,
R2.2 forget Password id or contact, High
proper Contact.
Using this
authentication
link edit
Login Details.

Profile Managing
R3
Management Profile Details
Details
R3.1 edit Details Change Details. Any Details Medium
updated
Change
edit Login Change login Login Details
R3.2 Username or Medium
Details details updated
Password
Shows
Details about Patients name
R3.3 Prehistory history Medium
patient history and ID
report

Hospital Management System

 eiTRA

Diagnoses and
R4 Consultation High
Prescription
Patients ID,
Check-up and Disease
General check- Report is
R4.1 asks patient for Symptoms,
up generated
tests if required Diagnosis and
prescription
Patient ID and
Assigning ward Ward is
R4.2 Assign Ward other
to patient assigned
information
Assign to
Patient ID and Patient
Assign to waiting list if no
R4.3 other added to
waiting list bed/ward is
information waiting list
available

Staff
R5 High
Management
Administrative
staff will assign
R5.1 Assign Doctor - -
doctor as per
schedule
Administrative
staff will assign
R5.2 Assign Nurse - -
nurse as per
requirement
HMS will inform
R5.3 Inform Doctors doctors about - -
new patients
Doctors and
Inform about
nurse are Reports are
R5.4 Inform Patients availability of
assigned to the created
bed
patients

After diagnosis
R6 Check out procedure and High
payment
After diagnosis,
Remove patient remove ID of Removed ID
R6.1 ID from current the patient but Patients ID from current
list keep that in list
record
The bill is
Patient is
generated in
discharged
R6.2 Payment accordance Patients details
and payment
with medical
is done
insurance

Report
R7 High
Generation

Hospital Management System

 eiTRA

Patients ID,
Patients Details of Name, ward no, Report is
R7.1
Information patient doctors name , generated
services

Hospital Management System

 eiTRA

5. UML Diagrams

5.1 Use Case Diagram

1) Staff Use Case Diagram

Hospital Management System

 eiTRA

2) Diagnose Use Case

Hospital Management System

 eiTRA

3) Finance Use Case

Hospital Management System

 eiTRA

5.2 Class Diagram

Hospital Management System

 eiTRA

5.3 Sequence Diagram

Hospital Management System

 eiTRA

5.4 Activity Diagram

1. Registration Activity diagram

Hospital Management System

 eiTRA

2. Ward Allocation Activity Diagram

3. Lab Activity Diagram

Hospital Management System

 eiTRA

Hospital Management System

 eiTRA

4. Cashier Activity Diagram

Hospital Management System

 eiTRA

6. External Interface

6.1 User Interface

Admin can create an account of user, then allowed to login and can use the
application.
User can view details of hospital services.
User can track their records.
User can use permitted modules.

6.2 Hardware Interface

RFID Tag
RAM : 512 MB or above
Hard Disk: 40 GB or above
Input Device: Keyboard, Mouse
Processor: Pentium IV and Motherboard
Android version : Any

6.3 Software Interface

For Application Technology : Android Tools : Android studio or eclipse
For web portal Technology : JAVA Tools : xampp or wamp server
Eclipse or NetBeans
7. Special User Requirements

7.1 Non-Functional Requirement

i. The application should not take more than one minute to open.
ii. The application should not allow the patients to track other patients info through
single ID.

7.2 Performance Requirement

The system should be compatible. It should not get hang or show some other
problems arising out due to large no of concurrent user.

7.3 Software System attributes

7.3.1 Reliability
The application should be highly reliable and it should generate all the updated
information in correct order.

7.3.2 Availability
Any information about the patients should be quickly available to the authorized user.

7.3.3 Security
The HM system must be fully accessible to only authentic users.

Hospital Management System

 eiTRA

7.3.4 Maintainability
The application should be maintainable in such a manner that if any new requirement
occurs then it should be easily incorporated in an individual module.

7.3.5 Portability
The application should be portable on any platform.

Hospital Management System