Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
2Activity
0 of .
Results for:
No results containing your search query
P. 1
Software Requirement OPD Management

Software Requirement OPD Management

Ratings: (0)|Views: 411 |Likes:
Published by Anindam Basu

More info:

Published by: Anindam Basu on Oct 25, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

08/30/2014

pdf

text

original

 
SRS Document OPD Management System
Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 1
 Mini project Requirements Management HIT- 403 Software requirement  specification document For Opd management system, Submitted to:Dr. Anandhi RamachandranPrepared By:Dr. Nitin prasher (pg/10/027)Anindam BAsu (pg/10/005)
 
SRS Document OPD Management System
Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 2
Index
S.No. Topic Name Page Number1. Introduction 31.1 Purpose 31.2 Scope of the work 41.3 Abbreviations Used 51.4 Overview 51.5 Manual Workflow 62. General Perspectives 72.1 Product Perspective 72.2 Stakeholders 72.3 Product Functions 82.4 General Constraints 92.5 Assumptions and Dependencies 93 Specific Requirements 103.1 Functional Requirements 103.2 Non Functional Requirements 134 Traceability Matrix 155 Appendix 165.1 Interview Question to the OPDAdministrator175.2 Focus Group Discussion with Other Users 185.3 Overview of the System 195.4 Overall OPD Management System & itsUsers205.5 Use Cases 215.5.1 Patient Registration 225.5.2
Doctor’s Schedule
235.5.3 Patient Appointment 265.5.4 Patient Online Registration andAppointment285.5.5 Generate Bill 305.5.6 Manage Patient Queue 326 Change Request Form 34
 
SRS Document OPD Management System
Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 3
1.
 
Introduction
ABC hospital is a state of art 300 bedded multispecialty hospital which is situated in Delhiwhich was open to public on 1
st
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).
1.1 Purpose 
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:
 

Activity (2)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->