Software Requirement Specification document for Hospital Management System

1.Introduction: 1.1 Purpose

This document is a Software Requirements Specification (SRS) for the Hospital Management System (HMS). It describes the functions, goals and tasks that the system can perform. Software Team Development Inc. (STD) will use this document to describe the scope of the project and to plan for the systems design and eventual implementation. This document forms the basis for the contract between the hospital and Software Team Development Inc. (STD). The purpose of this document is to describe all the requirements for the Hospital Management System (HPMS). The intended audience includes all stakeholders in the potential system. These include, but are not necessarily limited to, the following:

administrative staff, doctors, nurses, surgeons and developers. Developers should consult this document and its revisions as the only source of requirements for the project. 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.

1.2 Scope
The proposed software product is the Hospital Patient Management System (HPMS). 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. 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. 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. The intentions of the system are to reduce overtime pay and increase the number of patients that can be treated accurately. Requirements statements in this document are both functional and non-functional.

Leads to better patient care. Leads to efficient and smooth working of the hospital. 1.3 Definitions, Acronyms and abbreviations
HPMS PHN Report Database Front-desk staff E-CODE Password system Web-based application Windows 2000 Hospital Patient Management System Personal Health Number on health card an account of patients collection of information in a structured form administrative staff that work at reception desk a user identification number to enter the system a word that enables one to gain admission into the an application that runs on the Internet an operating system produced by Microsoft Corporation that is Used to operate the computer using a graphical user interface. a query language to interrogate the system Patient Identification number Graphical User Interface Software Requirements Speficification

MySQL ID GUI SRS

1.4 References 1.Software Engineering a practical approach By-Roger S Pressman 2.Software Engineering By-Rajib Mall 3. 1.5 Overview

This Software Requirements Specification (SRS) is the requirements work product that formally specifies Hospital Patient Management System (HPMS). It includes the results of both business analysis and systems analysis efforts. Various techniques were used to elicit the requirements and we have identified your needs, analyzed and refined them. The objective of this document therefore is to formally describe the systemshigh 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 Management System (HMS) will support. These include a general description of the product, user characteristics, general constraints, and any assumptions for this system. This model demonstrates the development team's understanding of the business domain and serves to maximize the team's ability to build a system that truly does support the business. Section 3 presents the detail requirements, which comprise the domain model.

2.Overall Description

2.1 Product perspective

This Hospital Patient Management System is a selfcontained 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.

2.1.1 Hardware interfaces: processor- core 2 duo Installed memory- 3 GB RAM 2.1.2 Software interfaces:
Oracle 9i, JAVA 2.1.3 Communication interfaces: The performance of the product is at its best if stored locally, as the response time will be optimum.So, it is not a network related software. 2.1.4 Memory constraints: 3 GB RAM

2.2 Product functions

The system functions can be described as follows

The various major modules are:

1. Scheduling Doctors 2. Salary System 3. Patients Registration 4. IPD Patient Report 5. IPD Patient Management 6. OPD Patient 7. Investigations Reporting System 8. Pharmacy 9. Bill System Description of the Modules in the system: 1. Scheduling Doctors: In case the user is the senior doctor/doctors of the hospital he works on this submodule. He schedules the doctors according to the departments. 2.Salary system: The head of the hospital keeps track of all staff members attendance; there leave record and deductions. Generates salary slip and other related reports. Employees recognized by their E-CODE may get their salary statement. 3. Patients Registration: Every patient who visits the hospital has to get registered.Registration of patients involves accepting certain general and demographic

information about the patient. The patient is allocated a unique 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. 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. An Admission form is printed with all the registration details for Indoor patients, which serves as the cover page of the patient file. 4.IPD patient Management: During his stay in the hospital, every patient is provided various services in terms of consultants visits, investigations, procedures, medicines & consumable, room services, diet, etc. All these services are entered to the patient record through nursing station. It also interacts with the Investigation and reporting module, Pharmacy and sends the requisitions to these departments. 5.IPD patient report : With the help of the registration Id the IPD patients may get their daily report. 6. OPD patient : The history, diagnosis and prescribed medicines & investigations and next visit of the patient

is recorded. The record helps in generating the patients card. 7. Investigations Reporting System: In the routine functioning of a hospital, various types of investigations are carried out. Carrying out number of tests and making the results available promptly is very crucial for assessing the patient's medical status and deciding on the further course of action. The payment details are also recorded. 8. Pharmacy: The Pharmacy Module deals with the Retail Sale of medicines to OPD patients and Issue of medicines to the IPD patients in the hospital. Its function includes, inventory management and billing of drugs, consumables and sutures. This module is closely linked to the Billing Module and IPD patient Module. All the drugs required by the patient can be indented from the various sub stores.

9.Bill System: For billing of any OPD service like Pathology Tests, or any imaging investigation, the patient moves to OPD billing counter. Here the services are charged as per the rates already defined for various categories/ penal/ time etc to

the patient with his Patient ID. The Payment is collected for the service provided and a receipt is generated. This module works as an interface with the diagnostic modules. All services will be automatically entered into the respective modules wherever required like lab& Imaging reporting. IPD billing has a supervisory role. The entries for billing are automatically transferred to the patient bill by the respective departments, which provide the service. The services are charged as per the category/panel/ package applicable. Here the bill is compiled and the payment collected from time to time. Provisional and Final bills are generated which provides complete information about the Services availed, its Charges, Advance collected, appropriate Receipts, Refunds,Concession allowed, etc. 9. Rules: This module contains all the rules and regulations of the hospital which can be referred by the employees. 2.3 User characteristics The users should have the basic knowledge of the functioning of the computer as careless usage may produce errors and reduce the efficiency of the working of the hospital. 2.4 Constraints

3. Specific Requirements

3.1 Functional Requirements: 1.The Hospital needs to give E-CODE and password to each of its doctor. The Head of the hospital (or any authorized person) schedules the doctors . Gives his E-CODE and password and then
Selects for all the doctors : dept-name , doctors name ECODE and date. Enters doctors type, selects visiting hours and finally clicks on submit button. 2.Salary System: User selects E-CODE from drop down list then all salary related information display. A hard copy of the salary statement may also be generated. 3.Patients Registration: Patient Details like Name, Age, Sex, Address, Contact number, Nationality, etc. Referring Source Department & Consultant to be visited. In case of IPD patients : 1. Room / bed requirement. 2. Consultant In charge

3. Treatment required The patients information along with its registration id is recorded in the database. 4. All the details required(as mentioned in section 2.2 point 3) are entered and updated in the database. 5.user selects registration-id from drop down list and click on submit button; then IPD patient Daily report generates. 6. The history, diagnosis , prescribed medicines, investigations and next visit of the patient is recorded in the database for future reference. 7.The registration id is inputed along with the tests to be performed. After the tests the report is recorded and also given to the patients.The cost is recorded in the Bill system. 8. The list of drugs is already entered and updated for pharmacy module. The total cost of purchase of drugs by patients is given to the bill system. 9. The Investigations Reporting System module and the Pharmacy module provide the total cost to the Bill System. Any error detected or suspected can be verified by checking the pharmacy module data and the Investigation Reporting System module data. 3.2 Performance Requirements:

The HMS is reliable as less manual interference is required/allowed. The calculations for the bills etc. are also done by the computer so there is less chance of errors. The rules and regulations are also listed in the HMS and the employees have the access to it. The HMS is efficient as all the modules have clear functions to performs. The working is also fast due to machine computations. Failure may occur in case of overloading of data of frequent wrong usage. 3.3 Logical Database requirements: The HMS database consist of following tables:1) Employee :-This table maintains employees details.It contais following entities E-code : alphanumeric Password : alphanumeric Dept : characters DName : characters DType : characters VstHrs : (digit)(digit):(digit)(digit) Sal : digits PId : alphanumeric Attendance : boolean

This database can contain a maximum of 500 records. 2) Patients:-This table maintains patients details. It contains following entities PE-code : number PName : characters Age : digits Sex : characters Address : alphanumeric Contact : number Nationality : characters DocVst : characters BedNo : digits This table can contain a maximum of 1 lac records. 3) DocSalary:-This table contains information on doctors salary.It consists of following entities DE-code : number Basic : number Incr : number HRA : number OtherAlwance : numbers This table contains a maximum of 500 records.

4)Report: This table contains details about the patients case investigation.It can cosist of a maximum of 1 lac records. Diagnosis Test : Med : Invstgn : NxtVst : : characters characters characters characters dd/mm/yy

This table can contain a maximum of 1 lac records. 4) Investigation Report System:-This table contains report for each test performed for each patient. This table contains following entities: PE-code Test : Report : Charge : : digits characters Boolean digits

This table can list a maximum of 10 lac records. 5)Bill:- This table contains details of the bill to be paid by the patient on completion of the treatment.

It contains the following entities: PE-code DocFee MedFee SrvTax ; : : : digits digits digits digits

This table can contain a maximum of 1 lac records. 6)Pharmacy:-This table contains information about medicine details. Drug : QntyAvl : Cost : QntySold alphanumeric digits digits : digits

This table contain a maximum of 50 lacs records. 3.4 S/W system attributes: 3.5 Additional comments : 4. Change Management Process: Owing to the frequently changing management requirement of the hospital, the HMS is adaptable to changes.

 The maximum number of employees and patient can be increased by expanding the database to more number of records. The particulars viz.password, salary ,address individuals, drug details etc. can be altered using the edit module incorporated in the HMS. Additio nal functional modules can be added to the system according to the hospitals requirement by drawing information from exsisting database or expanding the same. 5. Document Approvals: 6. Supporting Information: The HMS works on a GUI and hence, is easy to operate. The HMS has a well specified database capacity which should not be exceeded in order to prevent any misfunctions. HMS ensures security of data by preventing unauthorized access by using user verification system.