Department of Software Engineering

Functional Requirements &

Non-Functional Requirements

Submitted By: Tabish Tariq, Arsalan Asghar

Submitted to: Ma’am Sadiya

LAHORE GARRISON UNIVERSITY SECTOR C,

PHASE VI, LAHORE
Functional & non-Functional
Requirements
For

Hospital Management
System
Version 1.0 approved
Prepared by:
Tabish Tariq (BSSE/SP21/023)

Arsalan Asghar (BSSE/SP21/036)

7-5-2022
 HOSPITAL MANAGEMENT SYSTEM
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. Users can search for the 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.
The purpose of the project entitled as “HOSPITAL MANAGEMENT SYSTEM” is to
computerize the Front Office Management of Hospital to develop software which is user
friendly, simple, fast, and cost – effective. It deals with the collection of patient’s information,
diagnosis details, etc.
Traditionally, it was done manually. The main function of the system is to register and
store patient details and doctor details and retrieve these details as and when required, and
also to manipulate these details meaningfully System input contains patient details, diagnosis
details; while system output is to get these details on to the CRT screen.

FUNCTIONAL REQUIREMENTS

● Adding Patients: The Hospital Management enables the staff in the front desk to
include new patients to the system.

● Assigning an ID to the patients: The HMS enables the staff in the front desk to provide a
unique ID for each patient and then add them to the record sheet of the patient. The patients
can utilize the ID throughout their hospital stay.

● Deleting Patient ID: The staff in the administration section of the ward can delete the
patient ID from the system when the patient's checkout from the hospital.
● Displaying the medical charges list: The Staff in the administration section of the ward is
capable of displaying all the bills, medicines charges, bed charges. Also, it also will print all
the total charges that was conducted in a particular time period.

● Information of the Patient: The Hospital Management System generates a report on every
patient regarding various information like patients name, Phone number, bed number, the
doctor's name whom its assigns, ward name, and more.

● Availability of the Bed: The Hospital Management system also helps in generating reports
on the availability of the bed regarding the information like bed number unoccupied or
occupied, ward name, and more.

NON FUNCTIONAL REQUIREMENTS

There are a lot of software requirements specifications included in the non-functional
requirements of the Hospital Management System, which contains various process, namely
Security, Performance, Maintainability, and Reliability.

1. Security:

● Patient Identification: The system needs the patient to recognize herself or himself using
the phone.

● Logon ID: Any users who make use of the system need to hold a Logon ID and password.

● Modifications: Any modifications like insert, delete, update, etc. for the database can be
synchronized quickly and executed only by the ward administrator.

● Front Desk Staff Rights: The staff in the front desk can view any data in the Hospital
Management system, add new patient’s record to the HMS but they don't have any rights alter
any data in it.

● Administrator rights: The administrator can view as well as alter any information in the
Hospital Management System.

Performance:

● Response Time: The system provides acknowledgment in just one second once the
'patient's information is checked.
● Capacity: The system needs to support at least 1000 people at once.

● User-Interface: The user interface acknowledges within five seconds.

● Conformity: The system needs to ensure that the guidelines of the Microsoft accessibilities
are followed.

Maintainability:

● Back-Up: The system offers the efficiency for data backup.

● Errors: The system will track every mistake as well as keep a log of it.

Reliability:

● Availability: The system is available all the time.

Hope you got a clear idea on the functional and non-functional requirements and the features
required by the hospital. Any other queries on the topic are welcome.

Inverse requirements:

They explain what the system shall not do. Many people find it convenient to describe their
needs in this manner.

Patient ID

The patient shall not be able to change their Patient ID as it is generated from admins.

Accessing personal information

No other person can see the patient's personal details; it must be kept private.only hospital
administration can access.

Comment only

The patient can only chat or comment with the doctor and not be call.

Domain requirements:

Requirements that come from the application domain and reflect fundamental characteristics
of that application domain. Domain requirements can impose strict constraints on solutions.
This is particularly true for scientific and engineering domains
Print Bills

The bill must be paid before assigning the patient ID.

according to the treatment,and the bill of the medicines paid after the doctor's compilition the
diagnosis.

Modules
The entire project mainly consists of , which are
⦁ Admin module
⦁ User module (patient)
⦁ Doctor Module
⦁ Nurse Module
⦁ Pharmacist module
⦁ Laboratories module
⦁ Accountant module
After developing these modules we can solve all the problem that we face.
PROBLEM STATEMENT

Lackack of immediate information storage: -

1. The information generated by various transactions takes time and efforts to be stored at
the right place.

2. Lack of prompt updating: -

3. Various changes to information like patient details or immunization details of child are
difficult to make as paperwork is involved.
 4. Manual calculations are error prone and take a lot of time this may result in incorrect
information. For example, calculation of patient’s bills based on various treatments.

5. Preparation of accurate and prompt reports: -

This becomes a difficult task as information is difficult to collect from various register of
immediate retrievals: -

6. The information is very difficult to retrieve and to find particular information like- E.g. - To
find out about the patient’s history, the user has to go through various registers. This
results in convenience and wastage of time.

7. L.

SOLUTIONS
● The HMS provides the complete details of patients including the medical history under the
single click .
● All the Datastore in cloud.can be accessed easily .
● The tramdctions of billing and medicines can be done by HMS have feature in which the user
can paid bills easily
● All the staff are connected online together under HMS .
● The HMS organized all the features in such a way there is no need for any paper work on all
the data in sequential way.
● There is the Accounting software used in HMS that minimized the chances of calculation and
work efficiently
● In HMS the detailed history or reports of the patient is present so this minimizes the chances
of error.
● HMS have very big amount of storage so the data store in drive so there is no need if registers
.