HMS

Software Requirements Specification

Version 1.0

Group Members:

1. Irshad Ali

2. Adiba Saif

3. Amina Ashraf

Supervisor Name: Syed Iqbal Haider

 Revision History
Date Version Description Author
(dd/mm/yyyy)

The Hospital Management System

(HMS) is a comprehensive
software solution designed to
streamline the administrative and
clinical operations of hospitals. It
enables efficient management of
patient records, appointments,
billing, and staff schedules. The Amina Ashraf
system integrates various modules, Irshad Ali
29/10/2024 1.0 such as patient registration,
electronic medical records (EMR), Adiba Saif
and pharmacy management to
facilitate seamless communication
and data sharing across
departments. HMS aims to improve
patient care, reduce administrative
overhead, and enhance overall
operational efficiency within the
healthcare facility.
 Table of Contents

1. Scope (of the project)

2. Functional Requirements Non Functional requirements

3. Use Case Diagram

4. Usage Scenarios

5. Adopted Methodology

6. Work Plan (Use MS Project to create Schedule/Work Plan)

 SRS Document

1. Scope of Project:

Scope of the Hospital Management System (HMS)

The scope of the Hospital Management System (HMS) encompasses a wide
range of functionalities and services designed to improve the efficiency and
effectiveness of hospital operations. Here’s a detailed look at the various
aspects it covers:

1.1 Patient Management

1.1.1 Registration: Comprehensive patient registration system to capture

and manage patient information.

1.1.2 Appointment Scheduling: Tools for scheduling, rescheduling, and

canceling appointments.

1.1.3 Medical Records: Centralized electronic medical records (EMR) for

storing patient history, diagnoses, treatments, and test results.

1.2. Receptionist Management

1.2.1 Outpatient Management: Managing outpatient services including

consultations, follow-ups, and outpatient procedures.

1.2.2 Inpatient Management: Admission, bed allocation, discharge, and

transfer processes.

1.3. Billing and Finance

1.3.1Billing Management: Automated billing processes for inpatient and

outpatient services.

1i.4. Pharmacy Management

1.4.1 Inventory Management: Tracking and managing the inventory of

medicines and medical supplies.
1.5. Human Resources Management

1.5.1 Staff Scheduling: Managing schedules and shifts for hospital staff.

1.5.2 Payroll: Processing staff payroll, leaves, and attendance.(doctor’s

availability)

1.6. Administration and Reporting

1.6.1 User Roles and Permissions: Defining user roles and access
permissions.

1.6.2 Reporting: Generating various administrative and clinical reports for

decision-making.

1.6.3 Compliance: Ensuring adherence to healthcare regulations and

standards.

This scope outlines the major components and functionalities that the HMS
aims to provide, contributing to a more efficient, organized, and patient-
centric healthcare environment.

2. Functional and non Functional Requirements:

2.1 Functional Requirements

2.1.1 Patient Management

2.1.1.1 Registration: The system must provide a comprehensive patient

registration system to capture and manage patient information.

2.1.1.2 Appointment Scheduling: The system must include tools for

scheduling, rescheduling, and canceling appointments.

2.1.1.3 Medical Records: The system must offer centralized electronic

medical records (EMR) for storing patient history, diagnoses, treatments,
and test results.

2.1.2 Clinical Management

2.1.2.1 Outpatient Management: The system must manage outpatient
services including consultations, follow-ups, and outpatient procedures.

2.1.2.2 Inpatient Management: The system must handle admission, bed

allocation, discharge, and transfer processes.

2.1.3 Billing and Finance

2.1.3.1 Billing Management: The system must support automated billing

processes for inpatient and outpatient services.

2.1.4 Pharmacy Management

2.1.4.1 Inventory Management: The system must track and manage the
inventory of medicines and medical supplies.

2.1.5 Human Resources Management

2.1.5.1 Staff Scheduling: The system must manage schedules and shifts for
hospital staff.

2.1.5.2 Payroll: The system must process staff payroll, leaves, and
attendance.

2.1.6 Administration and Reporting

2.1.6.1 User Roles and Permissions: The system must define user roles and
access permissions.

2.1.6.2 Reporting: The system must generate various administrative and

clinical reports for decision-making.

2.1.6.3 Compliance: The system must ensure adherence to healthcare

regulations and standards.
2.2 Non-Functional Requirements

2.2.1 Performance
2.2.1.1 Scalability: The system must be scalable to handle an increasing
number of users, patients, and data without performance degradation.
2.2.1.2 Response Time: The system should provide a response time of less
than 3 seconds for any user action under normal load conditions.

2.2.2 Security

2.2.2.1 Data Encryption: All sensitive data, including patient records, must
be encrypted in transit and at rest to ensure data privacy.

2.2.2.2 Access Control: The system must implement role-based access

control to ensure that only authorized users can access specific
functionalities and data.

2.2.3 Usability

2.2.3.1 User Interface: The system should have an intuitive and user-
friendly interface that requires minimal training for new users.

2.2.4 Reliability

2.2.4.1 Uptime: The system should have an uptime of 99.9%, ensuring it is

available for use almost all the time.

2.2.4.2 Backup: Regular data backups must be performed to prevent data

loss, and there should be a disaster recovery plan in place.

2.2.5 Maintainability

2.2.5.1 Modular Design: The system should have a modular architecture to

facilitate easy maintenance and updates.

2.2.5.2 Documentation: Comprehensive documentation should be provided

for both users and developers to ensure ease of use and efficient
maintenance.

These non-functional requirements address the quality attributes that the

Hospital Management System must meet to ensure its effectiveness,
security, and user satisfaction.
3. Use Case Diagram(s):
 4. Usage Scenarios:

Use Case Use Actions Description Alternative Paths Pre-Conditions Post- Author Exceptions
Title Case ID Conditions

Manage UC-01 - Doctor views This use case allows doctors to None Patient medical records Medical records Author's Doctor lacks access
Medical patient records view and update patients' exist in the system are updated or Name permissions or the
Records - Doctor updates medical history, diagnoses, accessed system is temporarily
medical records treatments, and prescriptions. successfully unavailable

Appointment UC-02 - Patient requests Patients can request Patient requests specific Patient is registered, and Appointment is Author's Requested time slot
Scheduling appointment appointments, and receptionists doctor or time; doctor/receptionist is confirmed or Name unavailable; Doctor not
- Receptionist can schedule or reschedule appointment not available; logged in rescheduled available for requested
schedules them. receptionist suggests appointment
appointment alternatives

Billing and UC-03 - Patient receives Generates bills for services Payment plans; discounts Patient has undergone a Payment is Author's Payment gateway
Payment bill provided and enables payment for specific cases service that requires processed and bill Name unavailable; incorrect
- Admin processing through admin staff. billing status is updated billing information
processes
payment

Patient UC-04 - Receptionist New patients are registered None Receptionist and admin Patient record is Author's Missing information;
Registration collects patient with personal details, contact logged into the system created and Name duplicate records
details information, and health history available for use detected
- Admin verifies by the receptionist, verified by
registration the admin.

Discharge UC-05 - Doctor prepares This process handles patient Discharge delayed due to Patient completed Patient discharged; Author's Final payments pending;
Management discharge discharge, including creating pending treatments or treatment plan and is records updated Name incomplete discharge
summary summaries, updating records, tests ready for discharge summary or missing
- Admin finalizes and processing final payments. discharge authorization
discharge

Staff UC-06 - Admin Allows admin to manage None Admin has appropriate Staff records Author's Insufficient access
Management adds/removes hospital staff, including access permissions updated Name permissions for changes;
staff members adding, updating, or removing staff already assigned to
- Admin updates members and assigning roles. specific roles
staff roles

Pharmacy UC-07 - Pharmacist Manages medication inventory, Emergency stock request Pharmacist has access to Inventory updated; Author's Medication out of stock;
Management manages including adding new stock, due to shortages inventory prescriptions Name prescription not
medication removing expired stock, and fulfilled authorized for
inventory fulfilling patient prescriptions. fulfillment
- Pharmacist
fulfills
prescription
requests

Inventory UC-08 - Admin tracks Manages inventory of hospital Priority orders for Stock and usage data Inventory levels Author's Supplier unavailable;
Management inventory levels supplies, ensuring critical items emergency items available updated; order Name insufficient budget for
- Admin places are stocked and tracking usage placed reordering
orders for low trends.
stock items

User Roles and UC-09 - Admin assigns Admin configures system Role customization based Admin logged in with User access levels Author's Unauthorized access;
Permissions roles to staff access levels by assigning roles on specific department proper access rights updated Name system error in updating
- Admin sets and permissions to users based needs permissions
permissions for on their job requirements.
system access
5. Adopted Methodology
 Agile Method

6. Work Plan (Use MS Project to create Schedule/Work Plan)