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 Irshad Ali
29/10/2024 1.0 modules, such as patient
registration, electronic medical Adiba Saif
records (EMR), 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.1Patient 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. Clinical 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.

1.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 Pre-Conditions Post- Author Exceptions
Title Case Paths Conditions
ID
Manage UC-01 - Doctor This use case allows None Patient medical Medical Author's Doctor lacks
Medical views patient doctors to view and records exist in the records are Name access
Records records update patients' system updated or permissions or
- Doctor medical history, accessed the system is
updates diagnoses, successfully temporarily
medical treatments, and unavailable
records prescriptions.
Appointment UC-02 - Patient Patients can request Patient requests Patient is registered, Appointment is Author's Requested time
Scheduling requests appointments, and specific doctor or and confirmed or Name slot unavailable;
appointment receptionists can time; appointment doctor/receptionist rescheduled Doctor not
- schedule or not available; is logged in available for
Receptionist reschedule them. receptionist requested
schedules suggests appointment
appointment alternatives
Billing and UC-03 - Patient Generates bills for Payment plans; Patient has Payment is Author's Payment gateway
Payment receives bill services provided discounts for undergone a service processed and Name unavailable;
- Admin and enables specific cases that requires billing bill status is incorrect billing
processes payment processing updated information
payment through admin staff.
Patient UC-04 - New patients are None Receptionist and Patient record Author's Missing
Registration Receptionist registered with admin logged into is created and Name information;
collects personal details, the system available for duplicate records
patient contact information, use detected
details and health history
- Admin by the receptionist,
verifies verified by the
registration admin.
Discharge UC-05 - Doctor This process Discharge delayed Patient completed Patient Author's Final payments
Management prepares handles patient due to pending treatment plan and is discharged; Name pending;
discharge discharge, including treatments or tests ready for discharge records incomplete
summary creating summaries, updated discharge
- Admin updating records, summary or
finalizes and processing final missing
discharge payments. discharge
authorization
Staff UC-06 - Admin Allows admin to None Admin has Staff records Author's Insufficient
Management adds/removes manage hospital appropriate access updated Name access
staff staff, including permissions permissions for
members adding, updating, or changes; staff
- Admin removing members already assigned
updates staff and assigning roles. to specific roles
roles
Pharmacy UC-07 - Pharmacist Manages Emergency stock Pharmacist has Inventory Author's Medication out
Management manages medication request due to access to inventory updated; Name of stock;
medication inventory, including shortages prescriptions prescription not
inventory adding new stock, fulfilled authorized for
- Pharmacist removing expired fulfillment
fulfills stock, and fulfilling
prescription patient
requests prescriptions.
Inventory UC-08 - Admin Manages inventory Priority orders for Stock and usage Inventory Author's Supplier
Management tracks of hospital supplies, emergency items data available levels updated; Name unavailable;
inventory ensuring critical order placed insufficient
levels items are stocked budget for
- Admin and tracking usage reordering
places orders trends.
for low stock
items
User Roles UC-09 - Admin Admin configures Role Admin logged in User access Author's Unauthorized
and assigns roles system access levels customization with proper access levels updated Name access; system
Permissions to staff by assigning roles based on specific rights error in updating
- Admin sets and permissions to department needs permissions
permissions users based on their
for system job requirements.
access

5. Adopted Methodology
Agile Method

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

<Provide Gantt chart of your final project>