Hospital Management System

Software Requirements Specification

INT –221
MVC Programming
Section-K22AU

Aniket Kumar Himanshu

Reg No: 12224161
Roll no- 31

Varad Patil
Reg No: 12217695
Roll no- 71

Subham
Reg No: 12205589
Roll no- 46

Prepared for
Continuous Assessment 3
Spring 2025
 Hospital Management System

Table of Contents
REVISION HISTORY................................................................................ERROR! BOOKMARK NOT DEFINED.
1. INTRODUCTION...................................................................................ERROR! BOOKMARK NOT DEFINED.
1.1 PURPOSE......................................................................................................ERROR! BOOKMARK NOT DEFINED.
1.2 SCOPE..........................................................................................................ERROR! BOOKMARK NOT DEFINED.
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS.......................................ERROR! BOOKMARK NOT DEFINED.
1.4 REFERENCES................................................................................................ERROR! BOOKMARK NOT DEFINED.
1.5 OVERVIEW...................................................................................................ERROR! BOOKMARK NOT DEFINED.
2. GENERAL DESCRIPTION...................................................................ERROR! BOOKMARK NOT DEFINED.
2.1 PRODUCT PERSPECTIVE...............................................................................ERROR! BOOKMARK NOT DEFINED.
2.2 PRODUCT FUNCTIONS..................................................................................ERROR! BOOKMARK NOT DEFINED.
2.3 USER CHARACTERISTICS.............................................................................ERROR! BOOKMARK NOT DEFINED.
2.4 GENERAL CONSTRAINTS..............................................................................ERROR! BOOKMARK NOT DEFINED.
2.5 ASSUMPTIONS AND DEPENDENCIES.............................................................ERROR! BOOKMARK NOT DEFINED.
3. SPECIFIC REQUIREMENTS...............................................................ERROR! BOOKMARK NOT DEFINED.
3.1 EXTERNAL INTERFACE REQUIREMENTS......................................................ERROR! BOOKMARK NOT DEFINED.
3.1.1 User Interfaces.............................................................................................Error! Bookmark not defined.
3.1.2 Hardware Interfaces....................................................................................Error! Bookmark not defined.
3.1.3 Software Interfaces.......................................................................................Error! Bookmark not defined.
3.1.4 Communications Interfaces..........................................................................Error! Bookmark not defined.
3.2 FUNCTIONAL REQUIREMENTS......................................................................ERROR! BOOKMARK NOT DEFINED.
3.2.1 <Functional Requirement or Feature #1>..................................................Error! Bookmark not defined.
3.2.2 <Functional Requirement or Feature #2>..................................................Error! Bookmark not defined.
3.5 NON-FUNCTIONAL REQUIREMENTS......................................................................................................................3
3.5.1 Performance.................................................................................................................................................3
3.5.2 Reliability.....................................................................................................................................................3
3.5.3 Availability...................................................................................................................................................3
3.5.4 Security........................................................................................................................................................3
3.5.5 Maintainability.............................................................................................................................................3
3.5.6 Portability....................................................................................................................................................3
3.7 DESIGN CONSTRAINTS..........................................................................................................................................3
3.9 OTHER REQUIREMENTS........................................................................................................................................3
4. ANALYSIS MODELS.............................................................................ERROR! BOOKMARK NOT DEFINED.
4.1 DATA FLOW DIAGRAMS (DFD)…………………………………………………………………………………4
5. GITHUB LINK…………………………………………………………………………………………………….5
6. CLIENT APPROVAL PROOF……………..…………………………………………………………………….6
7. CLIENT LOCATION PROOF…………………………………………………………………………………...7
8. TRANSACTION ID PROOF……………………………………………………………………………………..8
9. EMAIL ACKNOWLEDGEMENT…………………………………………………………………………….....9
A. APPENDICES............................................................................................................................................................
A.1 APPENDIX 1...........................................................................................................................................................
A.2 APPENDIX 2...........................................................................................................................................................

Software Requirements Specification Page ii

 Hospital Management System

1. Introduction
1.1 Purpose

The purpose of this document is to provide a comprehensive overview of the Hospital

Management System (HMS) developed using the Laravel PHP framework. This report outlines
the system's objectives, functionalities, and technical structure to support efficient management
of hospital operations such as patient records, doctor scheduling, appointments, and
administrative tasks. The documentation is intended for stakeholders, developers, and
administrators involved in the development, deployment, and maintenance of the system

1.2 Scope

The Hospital Management System is a web-based platform designed to streamline and digitize
healthcare operations. It facilitates role-based access for administrators, doctors, and patients.
Key features include user authentication, patient registration, doctor management, appointment
scheduling, prescription records, and medical reports. The system ensures data integrity, efficient
workflow, and secure access to sensitive health information.

1.3 Definitions, Acronyms, and Abbreviations

HMS Hospital Management System

UI User Interface
DB Database
CRUD Create, Read, Update, Delete
MVC Model-View-Controller (software architectural pattern)
Laravel A PHP framework used for web application development
PHP Hypertext Preprocessor, a scripting language used for web development
SQL Structured Query Language used for managing data in a relational database

1.4 References

 Laravel Official Documentation: [Link]

 MySQL Reference Manual: [Link]

 PHP Documentation: [Link]

 Tailwind CSS Documentation: [Link]

Software Requirements Specification Page iii

 Hospital Management System

1.5 Overview

This document follows the IEEE standard structure for Software Requirements Specification and
provides a complete, detailed description of the Hospital Management System (HMS) built using
Laravel. It aims to establish a mutual understanding among developers, testers, clients, and
stakeholders of what the system will accomplish, how it will behave, and under what constraints.
The structure of the document is as follows:
 Section 1 – Introduction: Covers the purpose, scope, definitions, references, and a
general overview of the system.
 Section 2 – General Description: Describes the system's environment, functionalities,
user characteristics, and constraints.
 Section 3 – Specific Requirements: Details functional and non-functional requirements,
external interface needs, and design limitations.
 Section 4 – Analysis Models: Includes diagrams like DFDs (Data Flow Diagrams) to
visually represent system processes.
 Sections 5–11: Include deployment links, approval and location proofs, and other
verification details.
 Appendices: Supplementary materials supporting the main document.
This structure ensures completeness and traceability throughout the software development
lifecycle.

2. General Description
2.1 Product Perspective

The Hospital Management System (HMS) is a standalone, web-based software application

developed using the Laravel PHP framework. It is designed to automate and streamline
administrative and clinical processes in a hospital setting. The system follows the MVC (Model-
View-Controller) architectural pattern and operates as a central platform for managing patients,
doctors, appointments, and medical records.

This system is intended to replace manual, paper-based hospital operations with a secure, role-
based digital interface that provides distinct access for administrators, doctors, and patients. It is
built with scalability and modularity in mind and can be extended to integrate with third-party
APIs (e.g., billing, pharmacy, insurance) if required.

2.2 Product Functions

The major functions of the system include:

 User registration and login for admins, doctors, and patients.

 Doctor profile and schedule management.
 Patient record creation and update.
 Appointment booking and status tracking.

Software Requirements Specification Page iv

 Hospital Management System

 Prescription and diagnosis management.

 Dashboard with key statistics and summaries.
 Notification system (e.g., appointment confirmations).
 Role-based access control and permissions.

2.3 User Characteristics

 Administrator: Manages user accounts, hospital departments, and overall system

configuration. Requires a strong understanding of hospital workflows.

 Doctor: Manages appointments, medical histories, and prescriptions. Expected to be

comfortable using web-based systems for data entry and patient management.

 Patient: Can book appointments, view prescriptions, and medical records. Basic digital
literacy is assumed.

 Support Staff (optional): May assist with data entry or scheduling if included in hospital
operations.

2.4 General Constraints

 The system must be deployed on a LAMP/LEMP stack (Linux, Apache/Nginx, MySQL,

PHP).

 Developed using Laravel 8+ with PHP 7.4+ or newer.

 Compatible with modern web browsers (Chrome, Firefox, Edge).

 Internet connectivity is required for remote access.

 The system must comply with data protection and privacy standards (e.g., HIPAA, if
applicable).

2.5 Assumptions and Dependencies

 Users will have access to compatible devices (desktop/laptop with modern browsers).

 A database server (MySQL) will be pre-configured for system installation.

 SMTP/email services are available for notifications.

 The hospital will provide accurate data for initial population (doctors, departments, etc.).

Software Requirements Specification Page v

 Hospital Management System

 Future integrations (e.g., billing, pharmacy) may require additional APIs and development
work.

3. Specific Requirements
This section outlines the detailed software requirements that the system must fulfill. It includes
interface specifications, functional requirements, non-functional requirements, and constraints
that define the expected behavior and characteristics of the Hospital Management System.

3.1 External Interface Requirements

3.1.1 User Interfaces

 A responsive web interface accessible via modern browsers.

 Separate dashboards for Admins, Doctors, and Patients.
 Intuitive navigation menus for appointment management, profile updates, and reports.
 Forms for login, registration, appointment booking, and record updates.
 Real-time feedback (e.g., success/error messages) on user actions.
 Secure session management with logout functionality.

3.1.2 Hardware Interfaces

 Standard computing devices: Desktop, Laptop.

 No direct hardware interfacing (e.g., biometric, sensors) is currently implemented.

 Requires stable internet and a device with a modern web browser.

3.1.3 Software Interfaces

 Database: MySQL for persistent data storage.

 Server-Side: Laravel (PHP framework) handles business logic.

 Frontend: Blade templating with optional use of Tailwind CSS and JavaScript for
interactivity.

 Mailer: SMTP or Laravel-compatible mail drivers for sending email notifications.

3.1.4 Communications Interfaces

 HTTP/HTTPS protocols for client-server communication.

 RESTful endpoints may be used internally or for future external integrations.

Software Requirements Specification Page vi

 Hospital Management System

 Potential integration with third-party APIs (e.g., SMS or payment gateway) in future
versions.

3.2 Functional Requirements

3.2.1 User Authentication and Roles

 FR1.1: The system shall allow users to register and log in.
 FR1.2: The system shall differentiate user roles (Admin, Doctor, Patient) upon login.
 FR1.3: The system shall enforce access restrictions based on roles.

3.2.2 Appointment Management

 FR2.1: Patients shall be able to request appointments with available doctors.

 FR2.2: Doctors shall be able to approve, reject, or reschedule appointments.

 FR2.3: Admins can view all appointments across the system.

3.2.3 Patient Records

 FR3.1: Doctors shall be able to view and update patient medical histories.
 FR3.2: The system shall maintain a log of all patient visits and diagnoses.

3.2.4 Prescription Management

 FR4.1: Doctors shall be able to create and edit prescriptions for patients.
 FR4.2: Patients shall be able to view their prescription history.

3.2.5 Admin Panel

 FR5.1: Admins shall be able to manage users (CRUD operations).

 FR5.2: Admins shall be able to manage departments, doctors, and general hospital data.

3.5 Non-Functional Requirements

3.5.1 Performance

 The system shall respond to user actions within 2 seconds under normal load.

3.5.2 Reliability

 The system shall maintain at least 99.5% uptime.

Software Requirements Specification Page vii

 Hospital Management System

3.5.3 Availability

 The system shall be accessible 24/7, barring maintenance windows.

3.5.4 Security

 All user data shall be encrypted at rest and in transit.

 The system shall implement CSRF, XSS, and SQL injection protection.

3.5.5 Maintainability

 The codebase shall follow Laravel best practices for modularity and ease of updates.

3.5.6 Portability

 The system shall be deployable on any LAMP/LEMP stack without major configuration
changes.

3.7 Design Constraints

 Development must follow Laravel framework conventions.

 Blade templating engine is used for rendering views.
 Tailwind CSS is used for frontend styling.

3.9 Other Requirements

 All system logs must be stored for audit purposes.

 Email notifications must be triggered for appointment actions (creation, approval,

cancellation).

 A backup of the database shall be taken periodically (e.g., daily).

Software Requirements Specification Page viii

 Hospital Management System

4. Analysis Models
4.1 Data Flow Diagrams (DFD)

5. GitHub Link
GitHub Link:- [Link]

Software Requirements Specification Page ix

 Hospital Management System

6. Client Approval Proof

Software Requirements Specification Page x

 Hospital Management System

7. Client Location Proof

Google Maps Link :- [Link]

8. Transaction Id Proof

9. Email Acknowledgement
Software Requirements Specification Page xi
 Hospital Management System

Software Requirements Specification Page xii

 Hospital Management System

A. Appendices
Appendices may be used to provide additional (and hopefully helpful) information. If present,
the SRS should explicitly state whether the information contained within an appendix is to be
considered as a part of the SRS’s overall set of requirements.

Example Appendices could include (initial) conceptual documents for the software project,
marketing materials, minutes of meetings with the customer(s), etc.

A.1 Appendix 1
A.1 Appendix 1: Complaint Categories
Code, Category
SAN, Sanitation
EDU, Education
A.2 Appendix 2: SLA Policies
Tier 1: Resolve within 7 days (e.g., "Sanitation").

SCREENSHOTS OF HOSPITAL MANAGEMENT SYSTEM

Software Requirements Specification Page 1

 Hospital Management System

Software Requirements Specification Page 2

 Hospital Management System

Software Requirements Specification Page 3

 Hospital Management System

Software Requirements Specification Page 4

 Hospital Management System

Software Requirements Specification Page 5

 Hospital Management System

Software Requirements Specification Page 6

 Hospital Management System

Software Requirements Specification Page 7