The main intention of this document is to illustrate the
requirements needed for the Patient Database. The participants includes
in the potential system are the following: Administrative
• Patient database two levels of the users: –
• The Software includes:-
Stores and Maintain Patient details.
Maintains all kinds of data related to patient
diagnostic tests and patient Billing
The proposed software product is the Patient database.The current system in usage
is a paper-based system. It is too slow and cannot not give updated patient
list in reasonable timeframe. The main intention of this system is to maintain
the patient records digitally. The Requirements in this document contain both
functional and non-functional.
1.3 – Definitions, Acronyms, and Abbreviations
Patient Data Base
Personal Health Number on health card
Report – an account and record of patients
staff – administrative staff that work at reception desk of
ID – a unique identification number of user to enter the
– a unique word gaining admission into the system
application – an application that runs on the Internet
a query language to interrogate the system
Graphical User Interface
SRS – Software
This Software Requirements Specification (SRS) is the requirements work product
that formally specifies Patient database. Various techniques were used to obtain
the requirements and we have identified needs, analyzed and refined them. The
intention of this document is to formally describe the system’s high level
requirements including functional requirements, non-functional requirements and
business rules and constraints.
2.1 Product Perspective
This PDB is a self-contained system that manages the records of patient.
2.2 Product Functions
The functions of the system can be described as follows:
Registration: When the patient is admitted into hospital the front-desk
staff see weather the patient is already
registered with the hospital. If he is already registered his PHN is considered
otherwise the patients data is entered into computer and new PHN is generated.
Patient check out: When the patient checks out from hospital his PHN is
deleted from the system and the bed that is evacuated is included in
Report Generation: A report is
going to be generated by the system about the information regarding the patients
admitted in the hospital.
2.3 User Characteristics
The hospital are going to use this system for storing patient data. The
administrators and front-desk staff are the participants. The system is designed
to be user-friendly.
They all have basic knowledge about
computer and they are handle checking in the patients.
The administrators has proficient knowledge on computers. They are one who has
right to update patient database.
3.1 Functional Requirements
The PDB will allow the reception staff in front desk to add patients
SRS02 Assign ID
The PDB will allow reception staff to give each patient a unique ID and add
it to the patient’s data. This unique ID will be helpful for the patient throughout
their stay in hospital.
SRS03 Delete Patient
When the patient checks out from the Hospital
then the administrative staff of the hospital has access to delete the unique ID from patient data base.
SRS04 Add to
The evacuated beds will be keep in
beds-available list by the administrative staff of Hospital.
The reports were generated by the PDB will about their data like patient’s PHN,
patient’s first and last name, ward
number, bed number and the doctor’s name who has treated them
SRS06 Bed Availability
The reports were generated by the PDB on availability of beds about the occupied/unoccupied beds in
Patient Mandatory Information
Every patient has to provide mandatory data such as their first name, last name,
phone number, PHN, address, ZIP code.
The Patient can update their data at any time that were given in SRS07.
3.2 Design Constraints
Free and open source software MYSQL
database is used by the system.
Windows 2000 is the operating system used.
The Database is going to be a Web-based application.
3.3 Non-Functional Requirements
The patient can identify
themselves by using their PHN.
Every user who uses the system has a unique Logon ID and Password.
Modifications like insert, delete, update can be done by administrative authority.
Desk staff Rights
Adding the patients in PDB can be done by Front desk staff
SRS016 Administrators’ Rights
The most powerful right of administrator is
to modify the data in PDB.
3.3.2 Performance Requirements
The responses is going to be given by the
system in 1 second after checking the patient’s data.
The System has to have the capability of storing large amount of data.
The user interface screen has to respond
as fast as possible.
The data has to be back up by the system .
A log of all the errors are maintained by
The system must be available all the time
in the hospital.
The SRS document gives details related to patient database. Functional
and non-functional requirements are specified to get a complex idea to develop