SOFTWARE REQUIREMENTS SPECIFICATION Revision History

Version Draft Revision1 Revision 2 Author(s) Shao Jingqiu, Chad Cyprian, Li, Jingqiu Cyprian, Li, Jingqiu, Flip, Chad Description of Version Initial draft created for early distribution and review Date Completed 16-Oct-2002

Revision of draft and adding of necessary 22-October 2002 omissions Final revision 23- October-2001

Executive Summary
This document is a Software Requirements Specification (SRS) for the Hospital Patient Management System (HPMS). 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 system¶s design and eventual implementation. This document forms the basis for the contract between the hospital and Software Team Development Inc. (STD). The document lists the following features as the high-level requirements that the Hospital Patient Management System will satisfy:
y y y y y y

Work Scheduling ± assigning nurses to doctors and doctors to patients Admissions - Admitting patients, assigning the patients to appropriate wards Patient Care - Monitoring patients while they are in the hospital Surgery Management - Planning and organizing the work that surgeons and nurses perform in the operating rooms Ward Management - Planning and coordinating the management of wards and rooms Waiting list: Monitoring to see if there are any patients waiting for available beds, assigning them to doctors and beds once these become available

The document also presents a number of requirements that can be classified into two categories: functional and non-functional requirements. Non-functional requirements can be used to improve the functioning of the computer system, but not the management of the hospital as a whole. For these requirements, Software Team Development recommends that the Hospital management identify a set of experts from their computer department and their legal department to formally accept the requirements. The primary areas of concern are performance, security and userinterface. Functional requirements, on the other hand, are requirements directly related to the hospital management. Software Team Development Inc. (STD) also recommends that the hospital management identify a set of experts in the different domains to examine and formally accept these requirements.

Introduction 1. the following: administrative staff. 1. and to assign doctors to patients in designated wards as need arises. Please note that only the requirements that appear in this document or a future revision. They should not consider any requirements statements. doctors. If you have any questions about this document please contact Chad La Fournie at (403) 210 7545 between 9 a. will be used to define the scope of the system. The intended audience includes all stakeholders in the potential system. Nurses who are in direct contact with the patients . Hospital Patient Management System Software Requirements Specification 1. nurses. 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. but are not necessarily limited to.1 Purpose The purpose of this document is to describe all the requirements for the Hospital Patient Management System (HPMS). The development team expects many face-to-face conversations that will undoubtedly be about requirements and ideas for requirements. m. These include. written or verbal as valid until they appear in this document or its revision.m. on weekdays. and 4 p. The system will be used to allocate beds to patients on a priority basis.2 Scope The proposed software product is the Hospital Patient Management System (HPMS). however. Developers should consult this document and its revisions as the only source of requirements for the project.We would be grateful if you accept this document as the beginning of the process for approving the requirements and launching the design phase of the project. surgeons and developers. Your prompt response will be highly appreciated. Doctors will also use the system to keep track of the patients assigned to them.

and Abbreviations HPMS PHN Report Database Front-desk staff Logon ID Password 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 system 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. The current system in use is a paperbased system. Doctors must make rounds to pick up patients¶ treatment cards in order to know whether they have cases to treat or not. Requirements statements in this document are both functional and non-functional.will use the system to keep track of available beds. Acronyms. the patients in the different wards. The intentions of the system are to reduce over-time pay and increase the number of patients that can be treated accurately.3 Definitions. a query language to interrogate the system Patient Identification number Graphical User Interface Software Requirements Speficification MySQL ID GUI SRS . 1. and the types of medication required for each patient. It is too slow and cannot provide updated lists of patients within a reasonable timeframe.

A general picture of the system and the relationship between various stakeholders in the hospital is shown in Picture 2. 2. 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. It includes the results of both business analysis and systems analysis efforts. non-functional requirements and business rules and constraints.1 Product Perspective This Hospital Patient Management System is a self-contained system that manages activities of the hospital as bed assignment. General Description 2. general constraints. . 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.1.5 Overview This Software Requirements Specification (SRS) is the requirements work product that formally specifies Hospital Patient Management System (HPMS).4 References No formal documents have been referenced in this document. The objective of this document therefore is to formally describe the system¶s high level requirements including functional requirements. user characteristics. analyzed and refined them. Various techniques were used to elicit the requirements and we have identified your needs. and any assumptions for this system. Section 3 presents the detail requirements. Various stakeholders are involved in the hospital system. which comprise the domain model. 1. operations scheduling. Picture 1 shows an overview of the Hospital Patient Management System and the relationships between requirements. personnel management and administrative issues. These include a general description of the product.

Patient check out. The patient¶s information such as date of birth. If he is. . Report Generation: The system generates reports on the following information: patients. Otherwise a new Personal Health Number is given to this patient. the patient is put on a waiting list until a bed becomes available. the front-desk staff checks to see if the patient is already registered with the hospital. There are two possible circumstances: a) If there is a bed then the patient will be sent to the bed to wait for the doctor to come.2 Product Functions The system functions can be described as follows: Registration: When a patient is admitted. address and telephone number is also entered into computer system. If a patient checks out.2. the administrative staff shall delete his PHN from the system and the just evacuated bed is included in available-beds list. It prints out all the information on who has used which bed. bed availability and staff schedules after every six hours. Consultation: The patient goes to consultation-desk to explain his/her condition so that the consulting nurse can determine what kind of ward and bed should be assigned to him/her. b) If there is no bed. when and the doctor that is taking care of a given patient as well as expected medical expenses. his/her Personal Health Number (PHN) is entered into the computer.

Administrators: They all have post-secondary education relating to general business administration practices. It uses a Graphical User Interface (GUI). They are responsible for all of the scheduling and updating day/night employee shifts. doctors. Nurses in wards will use the HPMS to check their patient list. otherwise putting patients on the waiting list. Every staff has some basic computer training. The system is also designed to be user-friendly. Given the condition that not all the users are computer-literate. Doctors: All doctors have a medical degree. 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. notify administrator or nurse when an event occurs). The administrators.g. Some have further specialized training and are computer literate. nurses and front-desk staff will be the main users. Every administrator has basic computer training. Some nurses are computer literate. .2. Front-desk staff: They all have general reception and secretarial duties. Doctors will use the HPMS to check their patient¶s list. Nurses: All nurses have post-secondary education in nursing. Administrators in the wards are responsible for assigning doctors and nurses to patients. They are responsible for patient¶s check-in or notification of appropriate people (e.3 User Characteristics The system will be used in the hospital. Some users may have to be trained on using the system.

This ID shall be used by the patient throughout his/her stay in hospital. SRS002 Consultation .1 Functional Requirements Registration SRS001 Add patients The HPMS shall allow front-desk staff to add new patients to the system. Specific Requirements 3. It is assumed that the Hospital will have enough trained staff to take care of the system y 3. y The existing Telecommunication infrastructure is based on IEEE100802.2.4 General Constraints y The system must be delivered by January 1st 2003. Assign ID The HPMS shall allow front-desk staff to give each patient a ID and add it to the patient¶s record.3 standards and the system must conform to this standard using category 5 cables for networking y The system must be user-friendly 2.5 Assumptions and Dependencies y It is assumed that one hundred IBM compatible computers will be available before the system is installed and tested.

SRS004 Assign to Waiting List The consulting nurse shall use HPMS to assign Patient to a waiting list if no bed is available. surgeon and nurses to the patient. Assign Nurse The administration staff in the ward shall use HPMS to assign a nurse to a given patient. Inform Doctors The HPMS shall inform doctors of new patients. the administrative staff shall use HPMS to assign a surgery room. doctors and nurses to the patient immediately. Inform Nurses The HPMS shall inform nurses of new patients. SRS006 SRS007 SRS008 SRS009 SRS010 SRS011 . Generate Report (normal) The HPMS shall generate the patient¶s situation record every two hours for normal patients. Emergency Case In an emergency case. Surgery case In a surgery case. the administrative staff shall use HPMS to assign an emergency room.SRS003 Assign Ward The consulting nurse shall use HPMS to assign the patient to an appropriate ward. Medical matter management SRS005 Assign Doctor The administrative staff in the ward shall use HPMS to assign a doctor to a given patient.

patient¶s name. SRS016 Report Generation SRS017 Patient information Every six hours the HPMS shall generate reports on patients about the following information: patient¶s PHN. bed number and the doctor¶s name. Add to beds-available list The administrative staff in the ward shall be allowed to put the beds just evacuated in beds-available list.SRS012 Generate Report(Severe) The HPMS shall generate patient¶s situation record every half hour for severe patients. ward name. bed number. SRS018 SRS019 . Record procedure The whole treatment procedure for the patient shall be recorded by the system. staff type. occupied/unoccupied Staff Schedule Every six hours the HPMS shall generate reports on staff schedule about the following information: staff ID. Inform patient The HPMS shall automatically inform the patients who are on the bed waiting list of available beds whenever they become available. duty shift. SRS013 SRS014 Check Out SRS015 Delete Patient ID The administrative staff in the ward shall be allowed to delete the ID of the patient from the system when the patient checks out. Bed Aavailability Every six hours the HPMS shall generate reports on bed availability about the following information: ward name. staff name.

full/not full. Surgical. employee type. first name. city. or ID number. patient identification number. list of beds in room. Room Information Each room in HPMS shall include the following mandatory information: room number. Update Staff Information The HPMS shall allow the user to update any of the staff¶s information as described in SRS023. Ward Types The ward is categorized into four types: Maternity. postal code. country. Update Patient Information The HPMS shall allow the user to update any of the patient¶s information as described in SRS020 Search for Patient The HPMS shall allow the user to search for patient¶s information by last name or PHN or patient ID. address. country. Employee Information The HPMS shall allow the user to search for employee information by last name. list of rooms in ward. phone number. last name. ward number. postal code. address.Database SRS020 Patient Mandatory Information Each patient shall have the following mandatory information: first name. personal health number. Ward Information Each ward in HPMS shall include the following mandatory information: ward name. Staff Mandatory Information Each staff in hospital shall have the following mandatory information: identification number. city. duty schedule. phone number. Cancer and Cardiac. SRS021 SRS022 SRS023 SRS024 SRS025 SRS026 SRS027 SRS028 . last name.

Web-Based The system shall be a Web-based application. or by hierarchal hyperlinks from ward to bed. Modification Any modification (insert. room number and bed number respectively.1 Security SRS034 Patient Identification The system requires the patient to identify himself /herself using PHN Logon ID Any user who uses the system shall have a Logon ID and Password. and bed directly by ward number. SRS032 SRS033 3. update) for the Database shall be synchronized and done only by the administrator in the ward.SRS029 Bed Information Each bed in HPMS shall include the following information: bed number. patient PHN.3. room. SRS030 3. delete.3 Non-Functional Requirements 3. Ward Search The HPMS shall allow users to search the ward. SRS035 SRS036 .2 Design Constraints SRS031 Database The system shall use the MySQL Database. which is open source and free. occupied/unoccupied. Operating System The Development environment shall be Windows 2000.

SRS043 Capacity The System must support 1000 people at a time. Doctors Rights Doctors shall only be able to view all information in HPMS SRS041 3.2RHA/2000/v78 Front Desk staff Rights Front Desk staff shall be able to view all information in HPMS. section 703.SRS037 Compliance The system must comply with the Regional Health Authority Regulations concerning privacy. add new patients to HPMS but shall not be able to modify any information in it. Administrators' Rights Administrators shall be able to view and modify all information in SRS038 SRS039 HPMS SRS040 Nurses' Rights Nurses shall only be able to view all information in HPMS.3.3.2 Performance Requirements Response Time The system shall give responses in 1 second after checking the patient¶s information. User-interface The user-interface screen shall respond within 5 seconds.3 Maintainability . Conformity The systems must conform to the Microsoft Accessibility SRS042 SRS044 SRS045 guidelines 3.

SRS046 Back Up The system shall provide the capability to back-up the Data Errors The system shall keep a log of all the errors.4 Reliability SRS048 Availability The system shall be available all the time. APPENDIX . SRS047 3.3.

Picture 1: Relationships between entities in the hospital Patient Management System .

Picture 2 Overview of Hospital Patient Management System .

Sign up to vote on this title
UsefulNot useful