Software Requirements

Specification

Hospital Automation System

By

Varun Sharma (26312)

Date: 23/11/2018
Table of Contents

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 Description ....................................................................................2

2.1 Product Perspective ......................................................................................... 2
2.2 Product Functions ............................................................................................ 3
2.3 User Classes and Characteristics ..................................................................... 4
2.4 Operating Environment ................................................................................... 5
2.5 Assumtions and Dependencies ........................................................................ 6
3. External Interface Requirements ............................................................. 6
3.1 User Interfaces ................................................................................................. 6
3.2 Hardware Interfaces ......................................................................................... 6
3.3 Software Interfaces .......................................................................................... 7
3.4 Communications Interfaces ............................................................................. 7
4. System Features .......................................................................................... 8
4.1 Use Case Diagram……………………………………………………………8
4.2 Sequence Diagram…………………………………………………………...9
4.3 Class Diagram…………………………………………………………….....10
5 Conclusoin………………………………………………………………….....11
1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description of the project

titled “Hospital Automation System”. The document will explain the system
constraints, interfaces and interactions with other systems and external
factors. The document is primarily intended for users of the system and also
for potential developers.

1.2 Document Convention

This document was created based upon the IEEE standardized template for
System Requirements Specification Documents.

1.3 Intended Audience and Reading Suggestions

The document is strictly intended for developing and managing the system.
Thus, it is useful for people who are professionally involved with interacting
and enhancing the system constraints.

Further, the document can be useful for project managers, marketing staff,
Developers, testers and documentation writers to enhance the capability of the
system and to understand the ground bases on which the system has been
proposed.

1.4 Product Scope

The “Hospital Automation System” is a web based application which will

automate the traditional method of documenting information and data into
computerize method thus, keeping an efficient electronic track of day-to-day
activates in the hospital. The traditional method involved a lot of paper work
which were required to be handled and stored manually leading to a
cumbersome and error prone process. With the proposed system, all the data
can be stored electronically and can be shared and viewed whenever required
providing a paperless hospital up to 70%-80%. It also aims to provide low cost
reliable automation of the existing system. As far as the security is concerned,
the system is accessible by the concerned administrators of various
departments within the hospital.
Furthermore, the system needs Internet connection to fetch and display
results. All system information will be maintained within the database, which is
located over the web-server. It is an integrated end-to-end system that
provides relevant information across the hospital to support effective
decision making for patient care, hospital administration and critical financial
accounting, in a seamless flow.

1.5 References

1. https://web.cs.dal.ca/~hawkey/3130/srs_template-ieee.doc
2. http://cambiopfm.co.uk/solutions
3. http://makir.mak.ac.ug/bitstream/handle/10570/443/droma-fahad-cit-
bachelor-group-project.pdf?sequence=1
4. https://gephi.org/users/gephi_srs_document.pdf
5. https://www.youtube.com/watch?v=4WBsi6ChIAI
6. https://online.visual-paradigm.com

2. Overall Description

2.1 Product Perspective

The Hospital Automation System includes registration of patients, storing their

details into the system, and also computerized billing in the pharmacy, and
labs. The system generates a unique id for every patient and staff member and
stores those details automatically. It also includes a search facility on the basis
of unique id assigned to each patient or staff and can predict their current
status. User can also search availability of a doctor using the id and can make
appointments accordingly.

The system can be entered using corresponding username and password

assigned to each member. It is accessible by administrators or receptionist.
Only they can add and make changes into the database. The interfaced
designed would be user friendly and easy to understand.

Hospital Automation System (HAS), is designed for multispecialty hospital, to

cover wide range of hospital administration and management processes. It is
an integrated end-to-end system that provides relevant information across the
hospital to support effective decision making for patient care, hospital
administration and critical financial accounting, in a seamless flow. Hospital
Automation System will not only improve the quality and management of the
hospital, but will enhance various other aspects in operation of the hospital.
2.2 Product Functions

The system will allow access to only authorised users with specific roles like
administrators, receptionist or doctors. Depending upon the individual’s role
he/she will be allowed to access a particular module within the system.

The summary for major function that the system will perform has been
explained below:

1. A login interface depending upon the individual’s role and only

accessible to authorized members.

2. When a patient is admitted, the receptionist check to see whether the

patient is already registered with the hospital using the Patient ID if
available or else will try to pull up patient details using their registered
mobile number. If the patient is new, a new patient ID will be generated
by the system and will be allotted to the concerned patient after entering
their basic information like name, age, contact, gender and blood type.

3. Bills will be generated on the basis of prices for every facility being
availed by the patient and will be finally summed up.

4. Depending upon the situation in which the patient arrives at the hospital
the system will book an appointment with the doctor and will guide the
patient to the concerned rooms.

5. The Diagnosis information of the patient will be recorded over the

system which will hold the patient’s information and will also hold the
records for the medications prescribed by the doctor. If later the same
patient pays a visit to another doctor whether from same department or
another. The doctor will be able to pull up the patient’s case history using
the unique patient ID from the system.

6. The patient can avail the facility of buying medication within the hospital.
Using the patient ID, the pharmacist will be able to pull up details of the
medicines prescribed by doctor on the basis of latest updates made by
the doctor on the system.
 7. In case the patient is kept under observatory or is undergoing severe
medication. The system will monitor the various phases the patient is
going through and on the basis of results of the test conducted a
conclusion will be drawn. But, the final decision will be in the hands of
the medical staff.

2.3 User Classes and Characteristics

There are seven types of users that are interacting with the system. Each of
these types of users has different use for the system so each of them has their
own requirements. On the basis of the patient id each user will be able to pull
up data as per their concerned working department. The interaction of every
user using this system has been explained in detail as below:

1. Administrator(Admin):

 Manages various departments within the hospital

 Monitors appointment of doctors
 Monitors transactions reports of patients
 Keeps a track of various hospital inventories and medicines stock.

2. Patients:

 View appointment status with the doctors

 View prescription details
 View diagnoses and operation history
 Manage own basic data.

3. Doctors:

 Manage appointment with the patients

 Manage patients profile by updating their prescription or medication.
 Create new prescription or medication
 Manage patients medical history(operation details and diagnoses).
 Manage own profile
 4. Nurse:

 Manage patients data and updating

 Allot bedding facilities for the patient
 Provide medication as per patient prescription
 Keep record of patient’s information and update them
 Manage own profile

5. Pharmacist:

 Provide medication to patients as per prescription

 Manage and maintain medicines
 Keep track of all medicines and drugs and update their status

6. Medical Lab Technician

 Collect samples from patients as per prescription

 Provide preview of reports like X-Ray, CT-scan, MRI etc.
 Update patient’s information as per sample results for doctors
Preview.

7. Accountant(Receptionist)

 Collect general information from patient in-case of new

 Create invoice for payment as per facilities being redeem
 Order invoice to patients
 Monitor payment history of patients
 Assist and guide patients accordingly
 Mange own profile

2.4 Operating Environment

The software being developed is a web based application and would be only
accessible by authorised users only. Since, being a web based application the
first thing it would require would be an efficient browser. Google Chrome is
recommended to for this system as it is more feasible with java plugins. Also,
the system would require constant high speed internet connectivity from a
third party business partner or vendor. The system will be functional and
operable over any operating system (Windows, Mac OS) and also over portable
devices with significant WSP (Wireless System Protocols).
2.5 Assumptions and Dependencies

Hospital Automation System is a web based system and therefore would

require Java to be installed on user’s system from version 7 and above. The
system requires continuous internet connectivity in order to retrieve data from
the server and so the main dependency would be over the Internet Service
Provider (ISP).

3. External Interface Requirements

3.1 User Interface

This section has already been deeply explained section 2.3 User Classes and
Characteristics. The system as usual is accessible to authorised staff members
of the hospital. Each user will have separate view and modify access within
their dashboard and will be able to view and update data on the database
accordingly.

3.2 Hardware Interfaces

The most common set of requirements defined by any operating system or

software application is the physical computer resources, also known as
hardware. A hardware requirements list is often accompanied by a hardware
compatibility list (HCL), especially in case of operating systems. The following
sub-sections discuss the various aspects of hardware requirements.

Processor : Intel dual Core i3 (or higher)

RAM : 1 GB

Hard Disk : 500 GB (as per basic system specifications)

Input Devices : Keyboard, Mouse

Output Device : Monitor

3.3 Software Requirements

This section deals with the resource requirements which must be pre-
requisitely installed on the computer for its optimal functionality. These
requirements mentioned below are not a part of software installation package.

Operating system : Windows 7 or higher

Front End : HTML, java script,CSS

Server Side Script : PHP

Database : MySQL

3.4 Communication Interface

The system designed is a web based system and uses the client server
architecture as below, thus requires continuous operational network
connectivity. Also, it requires an efficient browser such as Google chrome
based on HTTP request-response protocol between client and server.
4. System Features

This section will demonstrate the features about the system and how they will
interact with the users and other modules within the system.

4.1 Use Case Diagram

The Use Case diagram in UML (Unified Modelling Language) is a behavioural

model diagram. The purpose is to represent a graphical overview of the system
in regards to its interaction with various authorised users and any
dependencies between those use case.
4.2 Sequence Diagram

The sequence diagram also known as event diagrams here depicts the object
interaction arranged in a timely sequence. It shows the object and classes
involved in the scenario and the sequence of messages exchanged between
objects needed to carry out the functionality of the scenario.
4.3 Class Diagram

Here the class diagram explains the structure of the system by showing the
system’s classes, their attributes, operations and relationship among the
objects.
5. Conclusion

The system developed will overcome the traditional method of storing data
over paper and thus will reduce the paper work by 70% to 80%. The software
will enable users to view and update the medical history and guide patients
accordingly to maintain health and on basis of doctor’s experience can also
help in predicting any health hazards which may occur in future. It increases
the processing speed and reduces the extra human effort in retrieving,
maintaining and modifying the data. The system also provides billing facility
and maintaining records of patient’s transactions. On basis of invoice
information the administrators of hospital can also assist patients in financing
or reducing the cost of facility being redeemed by the patients.