The document provides a system requirement specification for a hospital management system (HMS). The HMS will manage information about patients, nurses, beds, and the scheduling and allocation of resources. It aims to automate the current manual hospital system. The key requirements include functionality for admissions, patient care, surgery/ward management, and a waiting list. The system must have a user-friendly graphical interface, integrate with standard database and operating systems, and meet quality standards for security, safety, and reliability.

1. Title
:
System Requirement Specification Document for Hospital Management System.
Objective
:
To get with preparing requirement document, which is used to capture and document
allthe requirements at the start of project. In the assignment we mainly focus on
functionalrequirements.
1. Introduction:
1.1 Purpose:
The main purpose of our system is to make hospital task easy and is to develop software
thatreplaces the manual hospital system into automated hospital management system.
Thisdocument serves as the unambiguous guide for the developers of this software system.
1.2 Document Conventions:
•
HMS - Hospital Management System
•
GUI - Graphical User Interface
•
PHID - Patient Hospital Identification Number
1.3 Scope of the Project:
The purpose of this specification is to document requirements for a system to manage
thehospital. The specification identifies what such a system is required to do. The
specification iswritten in a format conforming to the IEEE Standard 830-1984. Subject to
approval, thespecification will complete the Requirements phase and will be followed by
detailed design,implementation, and testing.The product will be labeled the Hospital
Management System (HMS). The Hospital ManagementSystem will manage a waiting list of
patients requiring different treatment. The availability of bedswill be determined and if
beds are available the next appropriate patient on the list will benotified. Nurses will be
allocated to wards depending on ward sizes, what type of nursing isneeded, operating
schedules, etc.The current manual method of managing patients, nurses, and beds is time
consuming and errorprone. It is also difficult to manage the large paper flow involved in
this process. The HospitalManagement System will allow hospital administrative staff to
access relevant informationefficiently and effectively.The goal of HMS is to manage nurses,
patients, beds, and patient medical information in anefficient cost-effective manner.All of
these sub-systems (managing nurses, beds, patient medical information) need to
bedesigned and implemented so that HMS can run effectively.
1.4 Reference:
•

2. 2. Overall Description:
2.1 Product Perspective:
The HMS is designed to help the hospital administrator to handle patient, nurse and
bedinformation. The current design goal is to build an internal system to achieve the
functionalityoutlined in this specification.
2.2 Product Functions:
The HMS will allow the user to manage information about patients, nurses, and beds.
Patientmanagement will include the checking-in and checking-out of patients to and from
the hospital.The HMS will also support the automatic backup and protection of data.
2.3 Operating Environment:
Following are the requirements for running the software successfully-
•
Processor – Pentium III or Higher.
•
Ram – 512 MB or Higher.
•
Disk Space – 10 GB or Higher.
•
OS – Windows XP or Above.
2.4 Design & Implementation Constraint:
•
GUI only in English.
•
Login and password is used for identification of user and there is no facility for guest.
2.5 Assumption & Dependencies:
•
It is assumed that one hundred compatible computers will be available before the system
isinstalled and tested.
•
It is assumed that Hospital will have enough trained staff to take care of the system.
3. External Interface Requirements:
3.1 User Interface:
Input from the user will be via keyboard input and mouse point and click. The user
willnavigate through the software by clicking on icons and links. The icons will
giveappropriate responses to the given input.
3.2 Hardware Interface:
These are the minimum hardware interfaces-

3. 3.3 Software Interface:
These are the minimum software interfaces-
•
Technologies: C# .Net 2.0
•
Database: SQL server (standard edition).
•
Operating system: Windows XP or above.
System Features:
4.1 System Features:
•
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
performin 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,
assigningthem to doctors and beds once these become available.
Other Non-functional Requirements:
The performance of our software is at its best when the following are regularly done:
•
Password Management
•
Regular Database Archiving
•
Virus Protection

4. 5.2 Safety Requirements:
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
theirintent or have the option to undo.
5.3 Security Requirements:
Each member is required to enter an individual Username & password when accessingthe
software. Administrators have the option of increasing the level of password securitytheir
members must use. The data in the database is secured through multiple layers
ofProtection. One of those security layers involves member passwords. For
maximumSecurity of your software, each member must protect their password.
5.4 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.