SOFTWARE REQUIREMENTS SPECIFICATION

 Hospital Patient Management System Software Requirements Specification

 Index:
1.Intoduction
1.1 Purpose
1.2 Scope
1.3 Definitions
1.4 Overview
2.Current System
2.1 History
2.2 Comparison of Existing System
3.Proposed system
3.1.1 Problem Statement
3.1.2 Product Position Statement
3.2 Product Overview
3.2.1 Product Perspective
3.2.2 Summary of Capabilities
3.2.3 Assumptions and Dependencies
3.3 Functional Requirements
3.3.1Objectives
3.3.2Feature set
3.3.3Procedure and priority
3.4 Non-functional Requirement
3.4.1Stakeholder summary
3.4.2User Summary
3.4.3User environment
3.5 Hardware Considerations
3.5.1System Requirements
3.5.2Environmental requirements
3.6 Error Handling and system modifications
3.7Security issues
3.8Logical database
 1. Introduction:

The purpose of this document is to describe all the requirements for the Hospital
Patient Management System (HPMS). The stakeholders are ,not necessarily limited to, the
following: administrative staff, doctors, nurses, surgeons and developers.It focuses on
capabilities needed by stakeholders, and the targeted users and why these needs exist.

 
1.1      Purpose:
 
The hospital management and its team members should use this document and its
revisions as the primary means to communicate confirmed requirements to the
development team. The development team expects many face-to-face conversations that
will be requirements and ideas for requirements.

1.2      Scope:
 
1.The proposed software product is the Hospital Patient Management System
(HPMS).

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

3.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.

4. Requirements statements in this document are both functional and non-

functional. 

 
 
1.3       Definitions, Acronyms, and Abbreviations:
 
HPMS                                     Hospital Patient Management System
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 Front-Desk desk
Logon ID                               a user identification number to enter the system
Password           a word that enables one to gain admission into
system
ID                                           Patient Identification number
SRS                                        Software Requirements Speficification

1.4     References:
 
No formal documents have been referenced in this document.
 
1.5     Overview:
 
The objective of this document is to formally describe the system’s high level
requirements including functional requirements, non-functional requirements and
business rules and constraints. The detail structure of this document is organized as
follows:
Section 2 of this document provides an overview of the business domain that the
proposed Hospital Patient Management System (HPMS) will support. These include a
general description of the product, user characteristics, general constraints, and any
assumptions for this system.
Section 3 presents the detail requirements, which comprise the domain model i.e an
overview of the Hospital Patient Management System and the relationships between
requirements.

2. Current System:
2.1 History-
The current system in use is a paper-based system. It is too slow and
cannot provide updated lists of patients within a reasonable timeframe. Doctors must
make rounds to pick up patients’ treatment cards in order to know whether they have
cases to treat or not.
 2.2 Comparisons of Existing systems-

1.The intentions of the system are to reduce over-time pay and increase the number of
patients that can be treated accurately.
2.It is reasonable fast system.
3.This system helps doctors to keep track of patients’s treatment easily.
4.As assigning of wards ,beds is automatically as well as the info about patients is
kept in computer ,it is more reliable and fast.
5.It reduces the task overload of administrative staff,doctors and nurses.

3.Proposed System:
3.1.1Problem Statement
The Problem of 1.Lack of security.(i.e who is entering data)

2.Lack of Reliability.

3.Difficult to maintain database

Affects Patients,Doctors,Admin staff,nurses etc.
The impact of which is Might be change in patients database as well
as change in other database also.
A successful solution The proposed system should provide a
locking system that will avoid access to
undesirable system.
Would Help the admin staff and doctors and nurses
to easily carry out their stuffs.

3.1.2 Product position statement

For Hospital staff

Who Need to maintain patients database
And other info like Registration
Consultation,Patient check out ,Report
Generation etc. 
The HPMS Is an database maintaining system.
That Will help to maintain Hospital related data.
 
3.2              Product overview:

3.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.

 3.2.2 Summary of capabilities:

The stakeholders will enter data quite easy .The important notices and attentions
will be provided with alert box.
3.2.3 Assumptions and Dependencies
 
       It is assumed that plenty of 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
3.3Functional Requirements:
3.3.1 Goals-
1.Process Data-
Objectives
-Organize Database
-Maintaining Database
-Optimizing Database

2.Generating Reports-
Objectives
-Generation of patient’s situation report every 1 hour
-Generating reports about staff shedule
-Generating report bed availability
3.Medical matter management-
Objectives
-Management of assigning nurses and doctors by
administrator staff.
 -Record treatement procedure
4.Provide Access control-
Objectives
-Providing User control
-Provide Access Right Services
3.3.2 Feature Set
1.Provision of access control
2.Provision of Screen Locking System to avoid non medical users.
3.Provision of notification window to all users.
3.4 Non-Functional Requirements-
3.4.1 Stakeholders Summary
Name Represents Role
Front-Desk staff: reception desk etc. They all have general
Front-Desk 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: All admin staff, 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: One who look after the All nurses have education
patients 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 HPMS to check their
patient list. 

Doctors: The individuals who All doctors have a medical

medicate the patients. degree. Some have further
specialized training and are
computer literate. Doctors
will use the HPMS to
check their patient’s list.

Designer Developers of software Designing the software in

accordance with the
requirements.

3.4.2 User summary

All stakeholders are the users.
3.4.3 User Environment-
The user interface should contain all the forms as by departments.The Mainwindow will
contain the links to each form.There will be provision of Help Menu as well as the user
manuals.Fast response time is the mandatory function.Scrren locking system which doesnwhich
doesn’’t allow undesirable users to access the equipment easily and provides necessary
protection as shown in above pictures. Touching the lock unlocks the screen.`
3.5 Hardware considerations
3.5.1 System requirements
-Windows xp onwards
-Set-up
-Oracle 8i onwards
3.5.6 Hardware requirements
-Intel Pentium IV onwards
-RAM 512 MB
-4MB Hard Disk space
-LAN wire
3.6 Error Handling and system modifications
1.The entered data within database is checked for errors.
2.The error messages and alert messages will be displayed.

3.7 Security Issues-

1.The senisitive data like prescription of drugs can’t be modified without appropriate
pivillege.
2.Locking system of screens for those who don’t belong to medical
background,trying to modify data.

3.8 Logical Database-

3.8.1 Patients Database
3.8.2 Staff Database
3.8.3 Ward related database
3.8.3 Drugs related Database