Software Requirements

Specification (SRS)
Doctor-Patient Appointment System
Submitted By:

Amna Shah (Roll No. 30)

Javeria Ilyas (Roll No. 65)

Submitted To:
Sir Umar Hyat
Abdul Wali Khan University, Mardan

Table of Contents
Introduction
1.1 Purpose of the Project
1.2 Scope of the Project
1.3 Objectives
1.4 Target Audience

Scope and Objectives

2.1 Scope
2.2 Objectives

Target Audience
3.1 Patients
3.2 Doctors
3.3 Administrators
3.4 Stakeholders

Features and Functionalities

4.1 For Patients
4.2 For Doctors
4.3 For Admins
 User Roles and Interactions
5.1 Patient
5.2 Doctor
5.3 Admin

Key Modules or Components

6.1 Authentication Module
6.2 Appointment Management Module
6.3 Search and Filtering Module
6.4 Notification Module
6.5 Admin Dashboard
6.6 Reporting Module
6.7 Medical History Module (Optional)

Non-Functional Requirements
7.1 Performance
7.2 Security
7.3 Usability
7.4 Maintainability

Use Case Diagram

8.1 Overview
8.2 Detailed Use Cases

1. Introduction
1.1 Purpose of the Project

The purpose of the Doctor-Patient Appointment System is to

streamline and automate the process of scheduling appointments
between patients and doctors. This web-based application aims to
eliminate the inefficiencies of manual appointment booking, reduce
waiting times, and enhance the overall experience for both patients
and healthcare providers. By providing a centralized platform, the
system ensures seamless communication, better time management,
and improved accessibility to healthcare services.

1.2 Scope of the Project

The scope of the project includes:

 Developing a user-friendly web application where patients can view

available doctors, book appointments, and manage their schedules.
 Allowing doctors to manage their availability, view upcoming
appointments, and update their profiles.
 Providing an admin panel to oversee the system, manage user roles, and
generate reports.
 Ensuring data security and privacy for all users.
  The system will be accessible via web browsers on desktops, tablets, and
mobile devices.

1.3 Objectives

The primary objectives of the project are:

1. To simplify the appointment booking process for patients.

2. To improve the efficiency of doctors' schedules and reduce no-shows.
3. To provide a centralized platform for managing appointments and patient
records.
4. To enhance communication between patients and healthcare providers.
5. To ensure scalability and adaptability for future enhancements.

1.4 Target Audience

The target audience for the Doctor-Patient Appointment System

includes:

1. Patients: Individuals seeking to book appointments with doctors for

consultations, check-ups, or treatments.
2. Doctors: Healthcare professionals who want to manage their schedules,
view patient details, and accept/reject appointments.
3. Administrators: Personnel responsible for managing the system, user
accounts, and generating reports.
4. Healthcare Organizations: Clinics, hospitals, or medical centers that
want to adopt a digital solution for appointment management.

2. Scope and Objectives

2.1 Scope

The system will allow patients to:

 Register and log in to their accounts.

 Search for doctors based on specialty, availability, or location.
 Book, reschedule, or cancel appointments.
 Receive reminders for upcoming appointments.

The system will allow doctors to:

 Manage their availability and schedules.

 View and confirm patient appointments.
 Access patient medical history (if integrated with a medical records
system).

The system will include an admin panel for:

 Managing user accounts (patients and doctors).

 Generating reports on appointments and system usage.
Out of Scope:

 The system will not handle medical diagnosis or treatment

recommendations.
 The system will not handle billing or payment processing for appointments.
 The system will not integrate with external medical devices or wearables.

2.2 Objectives
 To provide a user-friendly platform for patients to book appointments
easily.
 To help doctors manage their schedules efficiently.
 To reduce no-shows and missed appointments through reminders and
notifications.
 To ensure data privacy and security for patient information.

3. Target Audience
This section identifies who will use the system and who the
stakeholders are.

3.1 Patients

Individuals seeking to book appointments with healthcare providers.

Users may include people of all ages, with varying levels of technical
expertise.

3.2 Doctors

Healthcare providers who will use the system to manage their

schedules and appointments. Doctors may include general
practitioners, specialists, and other medical professionals.

3.3 Administrators

System admins who will manage user accounts, monitor system

performance, and generate reports.

3.4 Stakeholders
 Hospitals or clinics that will implement the system.
 Project sponsors or investors funding the development of the system.

4. Features and Functionalities

4.1 For Patients
  User Registration and Login: Patients can create an account using their
email or phone number and log in securely.
 Search for Doctors: Patients can search for doctors by specialty,
location, or availability.
 Appointment Booking: Patients can book, reschedule, or cancel
appointments.
 Appointment Reminders: Patients receive reminders via email or SMS.
 Medical History Access (Optional): Patients can view their medical
history if integrated with a medical records system.

4.2 For Doctors

 Doctor Registration and Login: Doctors can create an account and log
in securely.
 Schedule Management: Doctors can set their availability and working
hours.
 Patient Management: Doctors can view patient details and appointment
history.
 Appointment Confirmation: Doctors can confirm or reject appointment
requests.

4.3 For Admins

 User Management: Admins can manage patient and doctor accounts.
 Appointment Management: Admins can view and manage all
appointments.
 Reporting and Analytics: Admins can generate reports on appointments
and system usage.

5. User Roles and Interactions

5.1 Patient
 Register and log in.
 Search for doctors and book appointments.
 View appointment history and receive reminders.
 Update personal information.

5.2 Doctor
 Register and log in.
 Manage availability and schedules.
 View and confirm appointment requests.
 Access patient details and medical history (if applicable).

5.3 Admin
 Manage user accounts (patients and doctors).
 Monitor and manage all appointments.
 Generate system reports and analytics.
6. Key Modules or Components
6.1 Authentication Module

Handles user registration, login, and password management for

patients, doctors, and admins.

6.2 Appointment Management Module

Allows patients to book, reschedule, or cancel appointments. Allows

doctors to manage their schedules and confirm appointments.

6.3 Search and Filtering Module

Enables patients to search for doctors by specialty, location, or

availability.

6.4 Notification Module

Sends appointment reminders and notifications to patients and

doctors via email or SMS.

6.5 Admin Dashboard

Provides admins with tools to manage users, appointments, and

system settings.

6.6 Reporting Module

Generates reports on appointments, system usage, and other

metrics.

6.7 Medical History Module (Optional)

Allows patients and doctors to view and manage medical records (if
integrated with a medical records system).

7. Non-Functional Requirements
7.1 Performance
 Response Time: Pages should load within 2 seconds under normal load
conditions.
 Scalability: The system should handle up to 10,000 concurrent users.
 Availability: The system should have an uptime of 99.9%.
7.2 Security
 Authentication: Secure login mechanisms (e.g., email/password or OTP).
 Data Encryption: Sensitive data must be encrypted during transmission
and at rest.
 Audit and Logging: Critical actions should be logged for auditing
purposes.

7.3 Usability
 Intuitive Interface: Key features should be accessible within 3 clicks.
 Accessibility: The system should comply with WCAG 2.1 standards.
 Responsive Design: The system should work seamlessly on desktops,
tablets, and mobile devices.

7.4 Maintainability
 Modularity: The system should be built using a modular architecture.
 Documentation: Comprehensive technical and user documentation
should be provided.
 Backup and Recovery: Regular backups should be performed, with a
recovery plan in place.

8. Use Case Diagram

8.1 Overview

The system includes the following use cases:

 Patient Use Cases: Registration, Login, Search for Doctors, Book

Appointment, View Appointment History, Receive Reminders.
 Doctor Use Cases: Registration, Login, Manage Schedule, View
Appointments, Confirm/Cancel Appointments.
 Admin Use Cases: Manage Users, Generate Reports.

8.2 Detailed Use Cases

Patient Use Cases:

o Registration: Patients can create an account using their email or

phone number.
o Login: Patients can log in securely using their credentials.
o Search for Doctors: Patients can search for doctors by specialty,
location, or availability.
o Book Appointment: Patients can book appointments based on
available time slots.
o View Appointment History: Patients can view past and upcoming
appointments.
o Receive Reminders: Patients receive reminders for upcoming
appointments via email or SMS.
 Doctor Use Cases:

o Registration: Doctors can create an account and provide their

professional details.
o Login: Doctors can log in securely using their credentials.
o Manage Schedule: Doctors can set their availability and working
hours.
o View Appointments: Doctors can view upcoming appointments.
o Confirm/Cancel Appointments: Doctors can confirm or cancel
appointments.

Admin Use Cases:

o Manage Users: Admins can add, edit, or delete patient and doctor
accounts.
o Generate Reports: Admins can generate reports on system
usage, appointments, and other metrics.

9. Conclusion
The Doctor-Patient Appointment System provides an efficient,
secure, and scalable platform for healthcare scheduling. The system
enhances doctor-patient interactions, optimizes appointment
management, and ensures high standards of security and usability.
Designed for scalability and future integration, it serves as a robust
solution for modern healthcare needs.