Hospital Management System

<Hospital Management System >

Software Requirements Specification

<Version 1.0>

<15-01-2020>

Prepared By

<Asad Nazeer Gondal,70062872>

<Bilal Ahmed Abbasi,70060601>

Software Requirements Specification

Hospital Management System

Revision History

Date Description Author Comments

<date> <Version 1> <Your Name> <First Revision>
1.0

Document Approval

The following Software Requirements Specification has been accepted and approved by the following:
Signature Printed Name Title Date
<Your Name> Software Eng.
Ijaz Khan Baig Lecturer, Cs322 15-01-2020

Software Requirements Specification

Hospital Management System

Table of Contents

REVISION HISTORY ...................................................................................................................................................... 2

DOCUMENT APPROVAL .............................................................................................................................................. 2
1. INTRODUCTION ......................................................................................................................................................... 4
1.1 PURPOSE.................................................................................................................................................................... 4
1.2 SCOPE........................................................................................................................................................................ 4
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS ...................................................................................................... 4
1.4 REFERENCES ............................................................................................................................................................. 5
1.5 OVERVIEW ................................................................................................................................................................ 5
2. GENERAL DESCRIPTION ........................................................................................................................................ 5
2.1 PRODUCT PERSPECTIVE ............................................................................................................................................. 5
2.2 PRODUCT FUNCTIONS ................................................................................................................................................ 5
2.3 USER CHARACTERISTICS ........................................................................................................................................... 6
2.4 GENERAL CONSTRAINTS ........................................................................................................................................... 6
2.5 ASSUMPTIONS AND DEPENDENCIES ........................................................................................................................... 6
3. SPECIFIC REQUIREMENTS .................................................................................................................................... 7
3.1 EXTERNAL INTERFACE REQUIREMENTS .................................................................................................................... 7
3.1.1 User Interfaces ................................................................................................................................................. 7
3.1.2 Hardware Interfaces ......................................................................................................................................... 7
3.1.3 Software Interfaces ......................................................................................................................................... 12
3.1.4 Communications Interfaces ............................................................................................................................ 12
3.2 FUNCTIONAL REQUIREMENTS ................................................................................................................................. 12
3.2.1 <Functional Requirement or Feature #1> ....................................................... Error! Bookmark not defined.
3.2.2 <Functional Requirement or Feature #2> ....................................................... Error! Bookmark not defined.
3.3 USE CASES .............................................................................................................................................................. 14
3.3.1 Use Case #1 .................................................................................................................................................... 14
3.3.2 Use Case #2 ...................................................................................................... Error! Bookmark not defined.
3.4 NON-FUNCTIONAL REQUIREMENTS......................................................................................................................... 18
3.4.1 Performance ................................................................................................................................................... 18
3.4.2 Reliability ....................................................................................................................................................... 18
3.4.3 Availability...................................................................................................................................................... 18
3.4.4 Security ........................................................................................................................................................... 18
3.4.5 Maintainability ............................................................................................................................................... 18
3.4.6 Portability ....................................................................................................................................................... 18
3.5 INVERSE REQUIREMENTS ........................................................................................................................................ 18
3.6 DESIGN CONSTRAINTS............................................................................................................................................. 19
3.7 LOGICAL DATABASE REQUIREMENTS ..................................................................................................................... 19
3.8 OTHER REQUIREMENTS ........................................................................................................................................... 19
4. ANALYSIS MODELS ................................................................................................................................................ 20
4.1 SEQUENCE DIAGRAMS ............................................................................................................................................. 20
4.2 DATA FLOW DIAGRAMS (DFD) ............................................................................................................................... 21
4.3 STATE-TRANSITION DIAGRAMS (STD).................................................................................................................... 22
5. CHANGE MANAGEMENT PROCESS ................................................................................................................... 22
A. APPENDICES ............................................................................................................................................................ 22
A.1 APPENDIX 1 ............................................................................................................................................................ 22
A.2 APPENDIX 2 ............................................................................................................................................................ 22

Software Requirements Specification

Hospital Management System

1. Introduction
The project Hospital Management system includes registration of patients, storing their details into the
system, and also computerized billing in the pharmacy, and labs. The software has the facility to give a
unique id for every patient and stores the details of every patient and the staff automatically. It includes a
search facility to know the current status of each room. User can search availability of a doctor and the
details of a patient using the id. The Hospital Management System can be entered using a username and
password. It is accessible either by an administrator or receptionist. Only they can add data into the database.
The data can be retrieved easily. The interface is very user-friendly. The data are well protected for personal
use and makes the data processing very fast. Hospital Management System is powerful, flexible, and easy
to use and is designed and developed to deliver real conceivable benefits to hospitals. Hospital Management
System is designed for multi specialty hospitals, to cover a wide range of hospital administration and
management processes. It is an integrated end-to-end Hospital Management 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 Management System is a software product
suite designed to improve the quality and management of hospital management in the areas of clinical
process analysis and activity-based costing. Hospital Management System enables you to develop your
organization and improve its effectiveness and quality of work. Managing the key processes efficiently is
critical to the success of the hospital helps you manage your processes.
1.1Purpose
The purpose is to describe all the requirements for the Hospital Management System. The following are
some of the stake holders:
• administrative staff
• doctors
• nurses
• surgeons
• developers.
The hospital management and its team members uses this document as the primary means to communicate
confirmed requirements to the development team. The development team expects many face-to-face
conversations that will undoubtedly be about requirements and ideas for requirements. However only the
requirements that appear in this document or a future revision, will be used to define the scope of the system.
1.2 Scope
The software product is the Hospital Management System. 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. 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.
1.3 Definitions, Acronyms, and Abbreviations
PHN Personal Health Number on health card
Report An account of patients
Database Collection of information in a structured form
Front-desk staff Administrative staff that work at reception desk
Logon ID A user identification number to enter the system
Password A word that enables one to gain admission into the system
ID Patient Identification number
GUI Graphical User Interface
SRS Software Requirements Specification.
Software Requirements Specification
Hospital Management System

1.4 References
http://docshare01.docshare.tips/files/5973/59736721.pdf
https://www.academia.edu/7149341/HOSPITAL_MANAGEMENT_SYSTEM_A_PROJECT_REPORT_
Submitted_in_Partial_Fulfillment_of_the_requirements_for_the_Award_of_the
http://flipkarma.com/media_dir/main_documents/locusproposal.pdf
file:///C:/Users/dtrdr/OneDrive/Desktop/HOSPITAL_MANAGEMENT_SYSTEM_Software_Requ.pdf
file:///C:/Users/dtrdr/OneDrive/Desktop/HOSPITAL_MANAGEMENT_SYSTEM_Software_Requ.pdf
http://www.itu.dk/~slauesen/Papers/IEEEtasks.pdf
https://aip.scitation.org/doi/pdf/10.1063/1.5039086
1.5 Overview
 Project is related to Hospital Management System.
 The project maintains two levels of users:- 1. Administrator Level-Doctor 2. User Level-Data Entry
Operator
 Main facilities available in this project are:-
1. Maintaining records of indoor/outdoor patients.
2. Maintaining patients diagnosis details, advised tests to be done.
3. Database of blood donors/blood group
4. Staff record maintenance
5. Providing different test facilities to a doctor for diagnosis of patients.
6. X-Ray
7. Urine Test
8. Stool Test
9. Blood Test
10. Biochemistry Test, etc.
11. Maintaining patient’s prescription, medicine and diet advice details.
12. Providing billing details for indoor/outdoor patients.
13. Maintaining backup of data as per user requirements (between mentioned dates).
14. Results of tests, prescription, precautions and diet advice will be automatically updated in the database.
15. Related test reports, patient details report, prescription and billing reports can be generated as per user
requirements.
16. User or Administrator can search a patient’s record by his/her name or their registration Number.
17. If user forgets his/her password then it can be retrieved by hint question

2. General Description
A hospital management system is a software designed to manage all the areas of a hospital such as
medical, financial, administrative and the corresponding processing of services.
2.1 Product Perspective
This Hospital Patient Management System is a self-contained system that manages activities of the
hospital as bed assignment, operations scheduling, personnel management and administrative issues.
Various stakeholders are involved in the hospital system.
2.2 Product Functions
The system functions can be described as follows:
Registration: When a patient is admitted, the front-desk staff checks to see if the patient is already registered
with the hospital. If he is, his/her Personal Health Number (PHN) is entered into the computer. Otherwise a
new Personal Health Number is given to this patient. The patient’s information such as date of birth, address
and telephone number is also entered into computer system.
Consultation: The patient goes to consultation-desk to explain his/her condition so that the consulting nurse
can determine what kind of ward and bed should be assigned to him/her. There are two possible
circumstances:
Software Requirements Specification
Hospital Management System

a) If there is a bed then the patient will be sent to the bed to wait for the doctor to come.
b) If there is no bed, the patient is put on a waiting list until a bed becomes available.
Patient check out. If a patient checks out, the administrative staff shall delete his PHN from the system
and the just evacuated bed is included in available-beds list.
Report Generation: The system generates reports on the following information: patients, bed availability
and staff schedules after every six hours. It prints out all the information on who has used which bed, when
and the doctor that is taking care of a given patient as well as expected medical expenses.
2.3 User Characteristics
The system will be used in the hospital. The administrators, doctors, nurses and front-desk staff will be the
main users. Given the condition that not all the users are computer-literate. Some users may have to be
trained on using the system. The system is also designed to be user-friendly. It uses a Graphical User
Interface (GUI).
Front-desk staff:
They all have general reception and secretarial duties. Every staff has some basic computer training. They
are responsible for patient’s check-in or notification of appropriate people (e.g. notify administrator or nurse
when an event occurs).
Administrators:
They all have post-secondary education relating to general business administration practices. Every
administrator has basic computer training. They are responsible for all of the scheduling and updating
day/night employee shifts. Administrators in the wards are responsible for assigning doctors and nurses to
patients.
Nurses:
All nurses have post-secondary education in nursing. Some nurses are computer literate. Consulting nurses
to whom patients give short descriptions of their conditions are also responsible for assigning patients to
appropriate wards if the beds are available, otherwise putting patients on the waiting list. Nurses in wards
will use the system to check their patient list.
Doctors:
All doctors have a medical degree. Some have further specialized training and are computer literate. Doctors
will use the system to check their patient’s list.
2.4 General Constraints
 The system must be delivered by deadline.
 The system must be user-friendly.
2.5 Assumptions and Dependencies
• It is assumed that compatible computers will be available before the system is installed and tested.
• It is assumed that the Hospital will have enough trained staff to take care of the system
Each user must have a valid user id and password
● Server must be running for the system to function
● Users must log in to the system to access any record.
● Only the Administrator can delete records.

Software Requirements Specification

Hospital Management System

3. Specific Requirements
Interfaces3.1 External Interface Requirements
3.1.1 User Interfaces

Software Requirements Specification

Hospital Management System

Bed allotment:

Software Requirements Specification

Hospital Management System

Software Requirements Specification

Hospital Management System

Software Requirements Specification

Hospital Management System

3.1.2 Hardware
 Laptop/Desktop
PC o core i5 processor o 4GB RAM o 500GB HDD Purpose of this pc is to give information when Patients
ask information about doctors, medicine available lab tests etc. To perform such Action it need very efficient
computer otherwise due to that reason patients have to wait for a long time to get what they ask for.
Software Requirements Specification
Hospital Management System

 Display Unit (LED/LCD Monitor/TV)

This unit is for display the channel number when the patients come to see their consultants. It will avoid
chaos. And also display Hospital welcome screen, video, information etc.
 Laser Printer (B/W)
Simply this device is for printing bills and view reports.
 Wi-Fi router
Wi-Fi router is used to for internetwork operations inside of a hospital and simply data transmission from
pc’s to sever.
3.1.3 Software Interfaces
Developing end
 JDK 1.8 - Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific
supercomputers, cell phones to the Internet,
 Netbeans 8.1 - IDE for Java developing.
 MySQL server - Database connectivity and management
 Adobe Photoshop cs4 - Logo and other designing such as User interfaces
Client End
 OS – Windows 7/8/8.1- Very user friendly and common OS
 JRE 1.8 - JAVA Runtime Environment for run Java Application and System
 MySQL server - Database connectivity
3.1.4 Communications Interfaces
NIC (Network Interface Card) - It is a computer hardware component that allows a computer to connect to
a network. NICs may be used for both wired and wireless connections.
 CAT 5 network cable- for high signal integrity
 TCP/IP protocol- Internet service provider to access and share information over the Internet
 Ethernet Communications Interface- Ethernet is a frame-based computer network technology for local area
networks (LANs)
 Ubiquitous, easy to set up and easy to use. Low cost and high data transmission rates.

3.2 Functional Requirements

Registration
Add patients
The system shall allow front-desk staff to add new patients to the system.
Assign ID
The system 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.
Consultation
Assign Ward
The consulting nurse shall use system to assign the patient to an appropriate ward.
Assign to Waiting List
The consulting nurse shall use system to assign Patient to a waiting list if no bed is available. Medical
matter management
Assign Doctor
The administrative staff in the ward shall use system to assign a doctor to a given patient. Assign Nurse
The administration staff in the ward shall use system to
assign a nurse to a given patient.
Inform Doctors
The system shall inform doctors of new patients.
Inform Nurses
The system shall inform nurses of new patients.
Emergency Case
Software Requirements Specification
Hospital Management System

In an emergency case, the administrative staff shall use system to assign an emergency room, doctors and
nurses to the patient immediately.
Surgery case
In a surgery case, the administrative staff shall use system to assign a surgery room, surgeon and nurses to
the patient.
Generate Report (normal)
The system shall generate the patient’s situation record every two hours for normal patients. Generate
Report(Severe) The system shall generate patient’s situation record every half hour for severe patients.
Record procedure
The whole treatment procedure for the patient shall be recorded by the system.
Inform patient
The system shall automatically inform the patients who are on the bed waiting list of available beds
whenever they become available.
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
Every six hours the system shall generate reports on patients about the following information: patient’s
PHN, patient’s name, ward name, bed number and the doctor’s name.
Bed Availability
Every six hours the system shall generate reports on bed availability about the following information:
ward name, bed number, occupied/unoccupied
Staff Schedule
Every six hours the system shall generate reports on staff schedule about the following information: staff
ID, staff name, staff type, duty shift.
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 system shall allow the user to update any of the patient’s information
Search for Patient
The system shall allow the user to search for patient’s information by last name or PHN or patient ID.
Staff Mandatory Information
Each staff in hospital shall have the following mandatory information: identification number, first name,
last name, phone number, address, postal code, city, country, employee type, duty schedule.
Update Staff Information
The system shall allow the user to update any of the staff’s information as described in SRS023.
Employee Information
The system shall allow the user to search for employee information by last name, or ID number. Ward
Types
The ward is categorized into four types: Maternity, Surgical, Cancer and Cardiac.
Ward Information
Each ward in system shall include the following mandatory information: ward name, ward number, list of
rooms in ward.
Room Information

Software Requirements Specification

Hospital Management System

Each room in system shall include the following mandatory information: room number, list of beds in
room, full/not full.
Bed Information
Each bed in system shall include the following information: bed number, occupied/unoccupied, patient
PHN.
3.3 Use Cases
3.3.1 Use Case #1

Name Add patient Entry

Description This function get details of a patient and add
record to the patient file and generate a patient
registration number
Actors Data entry operator, receptionist
Pre-conditions The operator should login with user account
Main flow of events 1. User selects “add patient entry “ at home
page
2. Patient entry form displayed
3. User enter data to required fields
4. User selects “Add entry” button
5. “Successfully record added” message
displayed.
6. System generates a patient Id and
display.

Extensions 3) A) if necessary fields left by user prompt user

to enter all required fields.

Post conditions Patient record added to patient file.

3.3.2 Use Case #2

Name Add prescription entry

Description This function records patients prescription details
Actors Data entry operator
Pre-conditions Doctor’s prescription chit must be issued.

Software Requirements Specification

Hospital Management System

Main flow of events 1. User selects “Prescription form ” from

patient module
2. System prompts to enter patient’s
registration number
3. User enter system registration number
4. Prescription form displayed with relevant
patient details.
5. User navigates to ‘tests’ field and selects
prescribed test details
6. User navigates to ‘vaccine’ field and
select prescribed vaccine details
7. User navigates to ‘medicine’ field and
enter medicine details.
8. User enter re-consolation date.
9. User selects Add button and add
prescription details.
10. User selects ‘print’ and print the
prescription details.

3.3.3 Use Case #3

Name Calculate bill

Description This function calculate total charge for the patient
Actors Receptionist, cashier
Pre-conditions THz patient must register to the system
Main flow of events 1. User selects patient receipt card
2. System prompts patient registration
number
3. User enter registration number
4. System prompts date and time , which
the total charge required for
5. User enter the date and time
6. Receipt form displayed with patient
details, lab tests details, X-ray details,
ECG details etc. and total fee in number
and in word.
7. User select print receipt.
8. The patient receipt is printed
Post conditions The payment details should updated in payments
file.

3.3.4 Use Case #4

Name Add Patient diagnosis history

Description This function add patient’s diagnosis details to
the system.
Actors Data entry operator
Pre-conditions Patient must register to the system

Software Requirements Specification

Hospital Management System

Main flow of events 1. User selects patient diagnosis card

2. System prompt patient Id
3. User enter patient Id
4. System display patient details in the form
5. User enter diagnosis details and date
6. User selects Add diagnosis record.
Post conditions The diagnosis record should added to the
diagnosis file.

3.3.5 Use Case #5

Name Schedule counselling doctors

Description This function mange’s counsellors charging details
Actors Accountant
Pre-conditions User sound login to the system
Main flow of events 1) user selects cancelling doctor form in
employee module
2) system prompts doctor’s Id
3) user enters id
4) system display councilor doctor details
5) user selects get visit hours and generated
sari details
6) user select generate counsellor charge
7) system calculates total counselor change to
be paired and display
Extensions 5 ) a) system generates total visit hours

5 ) b) 1 ) system prompts time period and field (lab

tests, ECG, all) to generate shares

5) B) 2) user select period and field.

5 )b) 3) system generates total share amount

Software Requirements Specification

Hospital Management System

3.3.6 Use Case #6

Name Register client –Sumba exercise

Description This function registers the clients for rumba
exercise classes
Actors Receptionist
Pre-conditions User should login to the system
Main flow of events 1) user selects rumba exercise
management form
2) system prompts to add client details
3) user add client details
4) system prompts to select package
5) user selected package
6) user selects generates costs system
prompts to select period(daily,
monthly)
7) user selected period
8) system generates and display fee
9) user confirm details and selects Add
client
10) system view successfully record
added message and generate Id

3.3.7 Use Case #7

Name Generate lab report
Description This function generates the report of a particular
test and print the report
Actors Lab assistance
Pre-conditions User should login
Relevant lab test results should be available
Main flow of events 1) user selects lab report form from lab
tests module
2) system prompts patient id
3) user enter patient id
4) system display patient details
5) system prompts to selects lab test
category
6) user selects category by navigating to
relevant tab and enter test results
7) user selects add lab test record
8) system display successfully added
message
9) user selects print report
10) system prints the report
extensions

Software Requirements Specification

Hospital Management System

3.4 Non-Functional Requirements

3.4.1 Performance
Response Time
The system shall give responses in 1 second after checking the patient’s information.
Capacity
The System must support 1000 people at a time.
User-interface
The user-interface screen shall respond within 5 seconds.
Conformity
The systems must conform to the Microsoft Accessibility guidelines.
3.4.2 Reliability
Availability
The system shall be available all the time.
3.4.3 Availability
The system shall be available all the time.
3.4.4 Security
Patient Identification
The system requires the patient to identify himself /herself using PHN
Logon ID
Any user who uses the system shall have a Logon ID and Password.
Modification
Any modification (insert, delete, update) for the Database shall be synchronized and done only
by the administrator in the ward.
Front Desk staff Rights
Front Desk staff shall be able to view all information in system, add new patients to system but
shall not be able to modify any information in it.
Administrators' Rights
Administrators shall be able to view and modify all information in system
Nurses' Rights
Nurses shall only be able to view all information in system.
Doctors Rights
Doctors shall only be able to view all information in system
3.4.5 Maintainability
Back Up
The system shall provide the capability to back-up the Data
Errors
The system shall keep a log of all the errors.
3.4.6 Portability
The Hospital Management System can easy to transfer the system from one environment to
another.
3.5 Inverse Requirements

Page 18 of 22
Hospital Management System

3.6 Design Constraints

Database
The system shall use the MySQL Database, which is open source and free.
Operating System
The Development environment shall be Windows 2000.
Web-Based
The system shall be a Web-based application.
3.7 Logical Database Requirements
3.8 Other Requirements
Accuracy We will ensure the accuracy of the software and the data entered to the database
3.8.1 Clarity
This SRS will be clearly stating what the user wants in the software.
3.8.2 Completeness
The software requirement specification contains all the the requirements stated in the business
requirements documentation that the user specified.
3.8.3 Consistency
The document is consistent from beginning till the end. It helps the readers understand the
requirements well.
3.8.4 Prioritizations of Requirements
The requirements will be full filled according to the order of priority and preference.
3.8.5 Verifiability
At the end of the project, the user/client will be able to verify that all that all the agreed deliverables
have in fact been produced and meet the project management requirements specified.
3.8.6 Modifiability
The SRS can be modified when the development team and user feel the need. 3.8.7 Traceability
Each requirement stated in the SRS is uniquely associated to a source such as a use case or
interaction document etc.

Page 19 of 22
Hospital Management System

4. Analysis Models
4.1 Sequence Diagrams

Page 20 of 22
Hospital Management System

4.3 Data Flow Diagrams (DFD)

Page 21 of 22
Hospital Management System

4.2 State-Transition Diagrams (STD)

5. Change Management Process

A. Appendices
A.1 Appendix 1
A.2 Appendix 2

Page 22 of 22