ACKNOWLEDGEMENT

The satisfaction that accompanies that the successful completion

of any task would be incomplete without the mention of people
whose ceaseless cooperation made it possible, whose constant
guidance and encouragement crown all efforts with success. We
are grateful to our project guide Maam Aliya for the guidance,
inspiration and constructive suggestions that were very helpful
for us in the preparation of this project.
We would also like to thank our colleagues who have helped in
successful completion of the project and most important Dr-Aziz
Ahmad Head of Gulraiz Medical Center for spent time and
provide a greatest opportunity for me to interview us

TABLE OF CONTENTS

SRS of Clinical Management System Page 1

Revision History 4
1. Introduction 4
1.1 Purpose 4
1.2 Document Conventions 4
1.3 Intended Audience and Reading Suggestions 4
1.4 Product Scope 5
1.5 References 5
2. Overall Description 5
2.1 Problems with the existing system 5
2.2 Designed Product Perspective 6
2.3 Product Functions 7
2.4 User Classes and Characteristics 7
2.5 Operating Environment 7
2.6 Design and Implementation Constraints 7
2.7 User Documentation 8
2.8 Assumptions and Dependencies 8
2.9 System Features 8
2.9.1 Login Account 8
2.9.1.1Description 8
2.9.1.2 Stimulus/response 8
2.9.1.3 Basic data flow 8
2.9.2 Functional requirements 8
2.9.2.1 Admin 8
2.9.2.2 Doctors Module 9
SRS of Clinical Management System Page 2
2.9.2.3 Receptionist 9
3. External Interface Requirements 9
3.1 User Interfaces 9
3.2 Hardware Interfaces 9
3.3 Software Interfaces 9
3.4 Communications Interfaces 10
4. System Features 10
4.1 System Feature 1 10
4.2 System Feature 2 (and so on) 10
5. Other Nonfunctional Requirements 10
5.1 Performance Requirements 10
5.2 Safety Requirements 10
5.3 Security Requirements 10
5.4 Software Quality Attributes 10
6. Other Requirements 11
Refrences 11

REVISION HISTORY

SRS of Clinical Management System Page 3

 NAME REASONS FOR CHANGES VERSION

Clinical Management Every record is in manual form Manual system every

System difficult to store and access record was on papers

INTRODUCTION
1.1 PURPOSE
The Software Requirement Specification document describes requirements and functionality of
the system. This document follows the IEEE Recommended Practice for Software Requirements
Specifications (IEEE Std 830-1998).

In the era of technology, where everything needs to be done efficiently and effectively the
existences of Clinic Management System (CMS) become necessary. The used of CMS can
enhance the services and also the work flow of all activity that happens in hospitals where it
helps in reducing the workload of medical staff.

1.2 DOCUMENT CONVENTIONS

When writing this document it was inherited that all requirements have the different priority
levels. The levels of authentication are provided in four different aspects i.e. The Admin, the
Receptionist, The Doctors and The Patients.

1.3 INTENDED USERS AND READING SUGGESTIONS

Developers:
In order to be sure they are developing the right project that fulfills requirements
provided in this document.
Testers:
In order to have an exact list of the features and functions that has to respond according
to requirements and provided diagrams.
Users:
In order to get familiar with the idea of the project and suggest other features that
would make it even more functional.
Documentation writers:

To know what features and in what way they have to explain. What security
technologies are required, how the system will response in each users action etc.

SRS of Clinical Management System Page 4

 Admin, Receptionist, Doctors and patients:
In order to know exactly what they have to expect from the system, right inputs and outputs
and response in error situations.

1.4 PROJECT SCOPE

The system has been facing problems due to its paper-based patient history and
appointment system. With the increase in the number of patients visiting, it has become
difficult to manage the system manually. Recording of appointments and creating registers
by pen and paper has become a tedious task. And also its difficult to manage huge number
of patient database.

In CMS the users will use the system to handle all the functionalities easily. Doctors will also
use the system to keep track of the patients consulting to them. 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.5 REFERENCES

Books: An Integrated Approach Software Engineering 3 Edition by PankajJalote.

rd

Website: http://www.W3shools.com/php/

http://in.php.net/

http://ignousupport.blogspot.in/p/clinic-management-system-project-
report.html

2. OVERALL DESCRIPTION

2.1 PROBLEMS WITH THE EXISTING SYSTEM

Since all the information is maintained in the registers so searching a piece of data from
those registers is definitely a time consuming and hectic task.
Every time a patient visits a doctor, after the visits he has to first come back to the
reception for entries of the treatment given, diagnosis and remarks, which of course
wastes the time of the patients as well as this is extra work. On the other hand the

SRS of Clinical Management System Page 5

 doctor can directly make these entries himself if the system is computerized and if there
is a PC in his office.
All entries are made manually which is of course a lengthy process. This again results in
people standing and waiting for their turns. The main problem with the system is that
the same data is being entered in the system again and again at different places by
different people. This might result in the inconsistency of data because the data is being
entered redundantly at many places, and inconsistency of the system can cause serious
problems.
There is a lot data redundancy. Data has to be copied for use by different departments.
Data updating is a major hurdle in such an environment where there are many people
that are to be serviced and to take care that no record is tempered.
Security provision is a serious issue relating to such a huge organization to make it work
efficiently. Records related to each patient need to be kept safe.
Extracting useful information from the current system is a very difficult task. A close
analysis makes it very certain that the existing system is time consuming. There are
greater chances of inconsistency of data and the frustration of the patients. So it can be
said that the existing system is not very reliable and needs to be changed to give the
patients and the doctors and the staff the higher degree of satisfaction. Keeping in view
all the problems mentioned above, we hereby propose a new and a computerized
system to meet all the requirements of user.

2.2 DESIGNED PROJECT PERSPECTIVE

Clinic Registration System is developed to improve the clinic management and automates the
workflow that happens in the clinic. This system is considering all the activities in the clinic.
Patient will make registration first. If the patient never registered before, patient information
collected and stored in the database. However, if it is an existing patient the patient data is
search-using IC (identification card) no. This will improve the record of the patient and save the
time during the registration. At this time, patient is assign to the doctor once the patient gets
the treatment, the doctor will send the report including the medicine name. The staff will view
the report and complete the patient record. After that, the staff will prepare the bills for the
patient. Then the staff will update the patient record will be kept in database. 2 The clinic
management system is very beneficial for a clinic/doctor. It wills stores complete patient
record. The most important thing is it will make it easier for the retrieval of history information
of the patient. In case, if patient is allergic for certain medicine, the doctor may detect what
type of medicine. For the security, before the user enters the system they have to input their
username and password before log in to the system. The system has different access for the
difference user. For the management of the clinic, they may view the daily report of clinic.

2.3 PRODUCT FEATURES

SRS of Clinical Management System Page 6

 Authentication for different users.
Real-time validation of all fields and database to prevent errors.
History of patients recorded in database.
Maintaining the billing section of the polyclinic.
Built in backup and restore facilities.
LAN compatible.
Compatible with any platform.

2.4 USER CLASSES AND CHARACTERISTICS

The admin, doctors and receptionists will be the main users. The system is also designed to be
user-friendly.

Admin
Receptionist
Doctors

Admin:
Admin should have prior knowledge of the system. Admin is able to control the whole system.
He/she can add, delete, update and modify the system.

Receptionists:
In order to add or delete the details of the patients come for the treatment and accordingly
provides identity to them.

Doctors:
Doctor should fairly know about the usage of the system. Doctors are able to see the respective
appointments taken. And also can view patients details and records.

2.5 OPERATING ENVIRONMENT

This proposed software will be used in Windows platform in the version of Windows 7.
Operating system: Windows 7
o Processor: Pentium 4
o Processor speed: 2.5 GHz
o RAM: 512MB
o Hard disk drive: 40GB

2.6 DESIGN AND IMPLEMENTATION CONSTRAINTS

The CMS system shall be a web based application system running in a windows
environment. A person who has no knowledge of computers will find it not so much difficult

SRS of Clinical Management System Page 7

 to understand the system. But with a little knowledge it will be very easy to handle the
project standard compliances. This document follows IEEE standard for software
requirement specification.

2.7 USER DOCUMENTATION

A file with a tutorial and full help on all features provided.
Help pages will be providing document with screen shots.
If the user has more queries regarding this then he/she can contact with the
administrator through contact no.

2.8 ASSUMPTIONS AND DEPENDENCIES

The software should be error free.
The product must have an interface which is simple enough to understand.

2.9 SYSTEM FEATURES

2.9.1 LOGIN ACCOUNT

2.9.1.1Description:
To open the user account the users have to enter login information.

2.9.1.2 Stimulus/response
User must enter valid user id and password to open user page. If it is valid then it links to
user account page.

2.9.1.3 Basic data flow

Here first the user enters login id and password.
After entering the login information system checks whether entered login id and
password is valid or not.

If it is valid then it is linked to the user account otherwise it does not.

2.9.2 FUNCTIONAL REQUIREMENTS

Here administrator, receptionist, and doctors are using the different pages.

2.9.2.1 Admin

Description

SRS of Clinical Management System Page 8

Admin is a super-user. He/she is able to control the whole system. Admin can add, delete,
update and modify the system. Doctor can also admin this if he/she wants.

2.9.2.2 Doctors Module:

Description:
Doctors can check appointments taken by patients. Doctors can view Patients Test reports and
he can enter and view suggested prescription details. And also insert or delete or update data.

2.9.2.3 Receptionist:

Description:
Receptionist can note down the patients appointments and guide them and manage them and
patient can also pay the bill at reception.

3. EXTERNALINTERFACEREQUIREMENT

All the interactions of the software with patients, doctors, receptionist, hardware and software
are specified here.

3.1 USER INTERFACES

The software provides good interface for the user and any administrator can operate on the
system performing the required task such as create, update etc.
The user of the product will get very user friendly page which will be very easy to work with.

3.2 HARDWARE INTERFACES

This system doesnt require any hardware interface. The one used here is monitor, keyboard
and mouse.
The system should have these hardware requirements:
Processor: Intel Pentium4 3.2GHz or above
Memory: 512MB or above
Hard Disk Drive: 40GB or above

3.3 SOFTWARE INTERFACES

Operating System: Windows 7 or 8

Microsoft excel

3.4 COMMUNICATIONS INTERFACES

SRS of Clinical Management System Page 9

 Window.

4. SYSTEM FEATURES
4.1 System Feature 1
Firstly it converts all manual system to software system and can store the
patient history easily in a small space and easily accessible
4.2 System Feature 2 (and so on)
It gives security to the patient data and can only access by authorized
person
Appointments are mentioned so everything was in a proper manner
Doctors can add more things about patient e.g. medicine, symptoms etc.
Easily manageable and less time consuming.
Portable

5.OTHER NON-FUNCTIONAL REQUIREMENTS

5.1 PERFORMANCE REQUIREMENTS
CMS manages facilities required by the casual users quickly and easily and patient
information collected and stored in the database.

5.2 SAFETY REQUIREMENTS

In case the user forgets or loses Password, the repair functionality helps by choosing
forgot password option in the main login window.
To avoid this kind of situations, backups can be done regularly.
While typing the password, if the caps lock is on it must be notified.
If the system is kept idle for 10 min the session will expire.

5.3 SECURITY REQUIREMENTS

This system is provided with authentication without which no user can pass. So only the
legitimate users are allowed to use the application. If the legitimate users share the
authentication information then the system is open to outsiders.

5.4 SOFTWARE QUALITY ATTRIBUTES

Reliability:
Good validations of user inputs will be done to avoid incorrect storage of records.

SRS of Clinical Management System Page 10

 Maintainability:
During the maintenance stage, SRS document can be referred for any validations.
Portability:
This system can be installed in any personal computers supporting windows operating
system platform.
Flexibility:
The system keeps on updating the data according to the transactions that takes place.
Timeless:
The system carries out all the operations with consumption of very less time.
Security:
Security of the system is maintained d by giving access to only authenticated user id and
password.

6. OTHER REQUIREMENTS
6.1 Other Requirements

Database: The records of all operations are stored in database.

REFRENCES

https://docs.google.com/document/d/1uwoGpDzkzTdA9n8COdPkLlx3fbirlk
AsV0rMeJMpWwo/edit
http://up-king.com/My/102/SWE%20387/Team%204%20Proposal.pdf
https://www.scribd.com/doc/310669306/Clinic-Management-System-
project-report-docx-docx
http://www.freestudentprojects.com/studentprojectreport/project-
srs/online-clinic-management-system-srs/
https://www.slideshare.net/kataria55/srs-for-hospital-management-
system
https://en.wikipedia.org/wiki/Clinic_management_system

. .

SRS of Clinical Management System Page 11