SRS Document OPD Management System
Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 3
ABC hospital is a state of art 300 bedded multispecialty hospital which is situated in Delhiwhich was open to public on 1
January 2011. The hospital has specialties which comprises of Cardiology, Neurology, Orthopedics, General Medicine, Nephrology, Pediatrics, Gynecology and many more (Source:www.abchospital.com). The hospital is having an Outpatient
Department with an average of 500 patients per day to visit to the consultants present in thehospital. The hospital is having totally manual based system which comprises of registering thepatient, Bill payment, providing appointment to the patient etc. The hospital is facing aproblem of longer queues in the OPD, more of the manual records, increased waiting time of the patient and sometime cancellation of the appointment after the patient arrives to thehospital. This has lead to less patient satisfaction and increase in paperwork (leading tomisplacing of the records from the records room). Also the hospital management seems a very daunting task to find out the exact numbers to get out with some inferences so that it leads toincrease in efficiency and effectiveness of the hospital.Another major problem that the hospital is facing that due to manual records, it has lead to lessaccountability of the different staff present in the OPD. Whether it is front desk personnel orbilling personnel, the more of manual work and handling more papers is not a easy task and
therefore, it leads to staff doesn’t take any responsibility for the work which is carried out extra
due to the manual process (paperwork). It has lead only to increase in consumption of stationery and space in the hospital (for storage).
The purpose of this document i
s to convey information about the application’s requirements,
both functional and nonfunctional of the Outpatient Management System for ABCmultispecialty hospital. It describes the functions, goals and task the system can perform.Software Development Team (SDT) would use this document to describe the scope of the
project and to plan for the system’s design and eventual implementation.
SDT should consultthis document and its revisions as the only source of requirements for the project. They shouldnot consider any requirement statements, written or verbal until they appear in this documentor its revision. It would also serve as a legal document to protect the interests of the solutionproviders once the requirements have been established.
This document is not only for the SDT’s but is intended to several groups which are as follows: