Software Requirements Specification for Hospital Management System
Page 1
Software Requirements Specification For
Hospital Management Prepared by Darshit Patel
VU4F0910044
[email protected]
Navin Sanan
VU4F0910050
[email protected]
Varun Patil
VU4F0910048
[email protected]
Instructor :
Supriya Maam.
Course :
I.T.
Teaching Assistant :
Supriya Maam.
Date:
Software Requirements Specification for Hospital Management System
Page 2
ACKNOWLEGEMENT 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 Mrs. Supriya C for the guidance, inspiration and constructive suggestions that helpful us in the preparation of this project. We also thank our colleagues who have helped in successful completion of the project.
Darshit Patel Navin Sanan Varun Patil
Software Requirements Specification for Hospital Management System
Page 3
Contents 1 INTRODUCTION...........................................................................................................................................................4 1.1 DOCUMENT PURPOSE ............................................................................................................................................4 1.2 PRODUCT SCOPE...................................................................................................................................................4 1.3 GLOSSARY ..........................................................................................................................................................4 1.4 REFERENCES ......................................................................................................................................................4 2 OVERALL DESCRIPTION...........................................................................................................................................5 2.1 PRODUCT PERSPECTIVE...........................................................................................................................................5 2.2 PRODUCT FUNCTIONALITY ......................................................................................................................................6 2.3 USERS AND CHARACTERISTICS .................................................................................................................................6 2.4 OPERATING ENVIRONMENT......................................................................................................................................6 2.5 DESIGN AND IMPLEMENTATION CONSTRAINTS.............................................................................................................6 2.6 USER DOCUMENTATION..........................................................................................................................................6 2.7 ASSUMPTIONS AND DEPENDENCIES............................................................................................................................6 3 SPECIFIC REQUIREMENTS.......................................................................................................................................7 3.1 EXTERNAL INTERFACE REQUIREMENTS......................................................................................................................7 3.2 FUNCTIONAL REQUIREMENTS...................................................................................................................................7 3.3 BEHAVIOUR REQUIREMENTS....................................................................................................................................9 4 OTHER NON-FUNCTIONAL REQUIREMENTS..................................................................................................11 4.1 PERFORMANCE REQUIREMENTS...............................................................................................................................11 4.2 SAFETY AND SECURITY REQUIREMENTS...................................................................................................................12 4.3 SOFTWARE QUALITY ATTRIBUTES ...........................................................................................................................12
Software Requirements Specification for Hospital Management System
Page 4
1 Introduction 1.1 Document Purpose Due to budget cutbacks and general co[ncern for providing best service possible to the public, we as a hospital would like to ensure that we are using our scarce hospital resources in most efficient manner possible. With this in mind we would like you to design a system which will help us manage our hospital in an efficient, effective manner. Specifically the system should help us schedule and monitor the various resources that we have at the hospital. This includes keeping track of available beds, waiting list for patients, patients expected length of stay, scheduling of surgeries, patient notification and billing, scheduling of nurses and doctors.
1.2 Product Scope In our proposed system , we are going to provide solutions to all the above mentioned problems by automating the whole hospital management by using an integrated software that handles the whole system. The proposed system provides one integrated view to patients for billing , collection , discharge detail , patient medical history , easy query handling for instant decision of bed allocation for patients , and request for the bed transfers. Effective search facility to search any type of information related to patient history.
1.3 Glossary
Term User Database Software Requirements Specification Stakeholder
Definition Person who access the system eg. Receptionist Collection of all the information stored by this system. A document that completely describes all of the functions of a proposed system and the constraints under which it must operate. For example, this document. Any person with an interest in the project who is not a developer.eg. Doctor, Patient, Nurse
1.4 References IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications. IEEE Computer Society, 1998.
Software Requirements Specification for Hospital Management System
Page 5
2 Overall Description 2.1 Product Perspective This Hospital 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. A general picture of the system and the relationship between various stakeholders in the hospital is shown in Picture.
Software Requirements Specification for Hospital Management System
Page 6
2.2 Product Functionality
Integrated patient database. Provide patient medical history. Easy query handling. Effective search facility for patients. Handle bed transfer details. Bill calculation and collection
2.3 Users and Characteristics Receptionist – They make changes to database based on the doctor’s orders. They are the most frequent users of this product. They must be comfortable working with computer. Nurse – They must make changes to routine according to the changes in database. They must have knowledge of the medical field and must have basic knowledge of English too.
2.4 Operating Environment Following are the requirements for running the software successfully Processor – Pentium III or Higher. Ram – 512 MB or Higher. Disk Space – 80 GB or Higher. OS – Windows XP or Latest.
2.5 Design and Implementation Constraints GUI only in English Login and password is used for identification of user and there is no facility for guest.
2.6 User Documentation The Product will include user manual. The user manual will include product overview, complete configuration of the used software technical details, backup procedures and contact information which will include email address. The product will be compatible with the Internet Explorer 6.0 or higher.
2.7 Assumptions and Dependencies It is assumed that one hundred IBM compatible computers will be available before the system is installed and tested. It is assumed that Hospital will have enough trained staff to take care of the system.
Software Requirements Specification for Hospital Management System
3 Specific Requirements 3.1 External Interface Requirements 3.1.1 User Interfaces Input from the user will be via keyboard input and mouse point and click. The user will navigate through the software by clicking on icons and links. The icons will give appropriate responses to the given input
3.1.2 Hardware Interfaces These are the minimum hardware interfaces. Hard disk: 80 GB. Ram: 512 MB. Processor: Intel Pentium4 or above.
3.1.3 Software Interfaces These are the minimum software interfaces. Technologies: C# .Net 2.0 Database: SQL server (standard edition). Operating system: Windows XP or above.
3.1.4 Communications Interfaces The performance of our software is at its best when the following are regularly done: 1. Password Management 2. Regular Database Archiving. 3. Virus Protection
3.2 Functional Requirements The various modules are:
Page 7
Software Requirements Specification for Hospital Management System
1. 2. 3. 4.
Reception Management Patient Registration In Patient Management Out Patient Management
Reception Management: Reception is the first point of interaction for anybody coming to the Hospital. It has all the information of the patients, doctors, departments and activities of the Hospital. All enquiries and appointments are scheduled through this module. 1. Patient Related Enquires: 2. Bed Allotment 3. Admission Details 4. Payment Details 5. Discharge Details 6. Doctor Related Enquires: 7. Availability Details 8. Appointment Schedules 9. Operation Schedules
Patient Registration: Every patient who visits the hospital has to get registered prior to getting any consultation, treatment or investigations done. Registration of patients involves accepting certain general and demographic information about the patient. The patient is allocated a unique Registration number and a Patient Identification number. The Patient ID will remain same for his all subsequent visits to the hospital whereas he will be allocated a new registration number on every visit. The consultation charges, if applicable can also be collected for the OPD patients during registration and a receipt will be generated. The following information is required for the registration of OPD Patient: 1. Patient details like Name, Age, Sex, Address, Contact number, etc. 2. Department and Consultant to be visited. For In Patient the additional information requirements are: 1. Room / Bed requirements 2. Consultant Incharged 3. Treatment required After registration an OPD Card is printed for the OPD patients, which list all his registration information. This card is used for the prescription writing by the consultant.
In Patient Management: The In Patient module is designed to take care of all the activities and functions pertaining to Inpatient Management. This module automates the day-to-day administrative actives and provides instant access to other modules, which leads to a better patient care. It provides comprehensive data pertaining to Admission of Patients &
Page 8
Software Requirements Specification for Hospital Management System
Ward Management: Availability of beds, Estimation, Collection of advance, Planned admission, Emergency admission and so on. It provides some queries like: 1. In Patient Admission. 2. Consultant Visit Entries. 3. Bed Transfer Details. 4. Daily Drug Requisition. 4. Daily Progress. 5. Advance Collections. 6. Patient Operation Details. 7. Discharge Intimation. 8. Discharge Notification Summary. 9. Patient Attended Details.
Out Patient Management: After the registration the patient comes to the consultation chamber, where the consultant records his history, diagnose and prescribe medicines & investigation The Consultant notes down the following details on Patients OPD Card: i. Complaints. ii. History. iii. Diagnosis. iv. Investigation. v. Medicines. vi. Advice. vii. Next Visit. This information is then entered into the patient data by the consultant or the operator at the OPD Counter. It serves the purpose of tracing patient’s visits history and also as a feedback for research & analysis. The prescription can also be scanned and saved. The scanned data can be entered later into various fields by the operator.
3.3 Behaviour Requirements 3.3.1 Use Case View
Page 9
Software Requirements Specification for Hospital Management System
Page 10
Inhouse
Consultant
Add Diagnose data View Diagnose Data Prescribe Login tests Doctor
Patient
Patient Info Test Appointments Ward-wise Bed Status Doctor Appointments Add/delete staff/Doc info
Receptionist
Admissio n Description
Sr. No.
Entity
Attributes
1.
Doctor
Doc_id, Name, Age, Phn_no,
Operations
Information System
Staff/Nurse
Doctor logs into the software, adds the diagnosis data, views it, prescribes the medicines. Bed Allotment
Software Requirements Specification for Hospital Management System
2.
Patient
Patient_id, name, age, illness
3.
Receptionist
Name, id
4.
Staff/Nurse
Staff_id, Name, Age
5.
Information system
Page 11
The doctors are generalized as in-house doctors and visiting doctors. Patient gets admitted into the hospital .He/she submits the patient information during form filling and views the diagnosis later. Receptionist logs into the software schedules the tests and doctor’s appointments .He/she also handles the work of bed allotment and perform the operation of altering the staff and doctor information. The staff members log-in to the system, assist the patient during allotment of beds.The nurse should see to it that the tests proceed according to the schedule and provide able assistance to the doctors. It maintains the patient information and updates the same accordingly. It also checks the ward-wise bed status. It makes the necessary changes to the staff and doctor’s database.
4 Other Non-functional Requirements 4.1 Performance Requirements The performance of our software is at its best when the following are regularly done: 1. Password Management 2. Regular Database Archiving 3. Virus Protection
Software Requirements Specification for Hospital Management System
4.2 Safety and Security Requirements Safety:
Humans are error-prone, but the negative effects of common errors should be limited. E.g., users should realize that a given command will delete data, and be asked to Confirm their intent or have the option to undo. Security: Each member is required to enter an individual Username & password when accessing the software. Administrators have the option of increasing the level of password security their members must use. The data in the database is secured through multiple layers of Protection. One of those security layers involves member passwords. For maximum Security of your software, each member must protect their password
4.3 Software Quality Attributes The Quality of the system is maintained in such a way so that it can be very user-friendly. The software quality attributes are assumed as under: Accurate and hence reliable. Secured. Fast Speed. Compatibility.
Page 12
