Software Engineering Report

Hospital Management System

Prepared by
Sanchita Devi
[email protected]
 1

Overview

The Hospital Management System (HMS) is designed to streamline the process of patient
appointment scheduling in a hospital. It ensures efficient handling of patient details,
appointment requests, and doctor availability. The system is intended to improve the overall
patient experience by providing a seamless interface for appointment booking and
management.

Objectives

1. Efficient Appointment Scheduling: Automate the process of scheduling appointments

for patients with available doctors, reducing manual work and minimizing errors.
2. Patient Data Management: Maintain a comprehensive database of patient details,
including both existing and new patients, to ensure accurate and quick retrieval of
information.
3. Availability Tracking: Track the availability of doctors in real-time to facilitate
appointment bookings and cancellations efficiently.
4. User-friendly Interface: Provide an intuitive interface for patients to request
appointments and for assistants to manage these requests effectively.
5. Flexible Appointment Management: Allow assistants to confirm, reschedule, or cancel
appointments based on the needs of both patients and doctors.

Methodology

The system will be developed using the Agile methodology, allowing for iterative development and
regular feedback. Key phases will include:

1. Requirement Gathering: Collecting detailed requirements from stakeholders.

2. Analysis: Analyzing the requirements to define system specifications.
3. Design: Creating the system architecture, including ER models, DFDs, and use case diagrams.
4. Implementation: Coding the system based on the design specifications.
5. Testing: Verifying that the system meets all requirements and functions correctly.
6. Deployment: Deploying the system for use in the hospital.
7. Maintenance: Providing ongoing support and updates.
 2

Functional Requirements

1. Patient Registration:
○ New patients can register by providing their details.
○ Existing patients can log in to their accounts.
2. Appointment Scheduling:
○ Patients can request appointments with specific doctors.
○ The system checks the doctor's availability and schedules the appointment.
○ The system confirms the appointment with the patient.
3. Appointment Management:
○ Assistants can view and manage appointments.
○ Assistants can cancel appointments and notify patients.
○ Patients can view their appointment status and details.
4. Patient Records Management:
○ The system stores patient information securely.
○ The system retrieves patient details for appointment scheduling and
consultations.

Non-Functional Requirements

1. Security: Ensure that patient data is stored securely and access is controlled.
2. Performance: The system should handle multiple simultaneous appointment requests
efficiently.
3. Reliability: The system should be reliable and available during hospital working hours.
4. Scalability: The system should be able to scale to accommodate a growing number of
patients and doctors.

Design

Data Flow Diagram:

Fig: Data flow Diagram

 3

Use Case Diagram:

● Register/Update Patient Details:

○ Actors: Patient
○ Description: Patients enter or update their personal details.
● Request Appointment:
○ Actors: Patient
○ Description: Patients request an appointment with a doctor.
● Confirm/Cancel Appointment:
○ Actors: Assistant
○ Description: The assistant confirms or cancels patient appointments based on
doctor availability.
● Manage Doctor Schedule:
○ Actors: Assistant, Doctor
○ Description: Doctors or assistants update the availability and schedule of doctors
● View Medical Records
○ A patient or doctor views medical records.

Fig: Use case Diagram

 4

Class Diagram

1. Classes:
○ Patient
■ Attributes: patientID, name, contactDetails, medicalHistory
○ Appointment
■ Attributes: appointmentID, patientID, doctorID, appointmentDate,
appointmentTime, status
○ Doctor
■ Attributes: doctorID, name, specialization, availableSlots
○ Assistant
■ Attributes: assistantID, name, contactDetails

Sequence Diagram

1. Patient Registration Sequence:

● Patient → Assistant: Provide details.

● Assistant → HMS: Enter details.
● HMS → Database: Store details.
● HMS → Assistant: Confirmation.

2. Appointment Scheduling Sequence:

● Patient → HMS: Request appointment.

● HMS → Assistant: Notify request.
● Assistant → HMS: Check availability.
● HMS → Database: Retrieve availability.
● HMS → Assistant: Show available slots.
● Assistant → Patient: Confirm slot.
● Patient → Assistant: Confirm appointment.
● Assistant → HMS: Finalize appointment.
● HMS → Database: Store appointment.
 5

Fig: Sequence Diagram for booking an appointment

Entity-Relationship Model

Entities with Single Line Details

1. Patient: Stores patient details including name, age, contact info, and medical history.
2. Doctor: Stores doctor details including name, specialty, and availability schedule.
3. Appointment: Stores appointment details including patient ID, doctor ID, date, time,
and status.
4. Assistant: Stores assistant details including name, contact info, and role.
5. MedicalRecord: Stores detailed patient medical records linked to appointments.

Relationships

1. Patient - Appointment: One-to-Many (A patient can have multiple appointments).

2. Doctor - Appointment: One-to-Many (A doctor can have multiple appointments).
3. Assistant - Appointment: One-to-Many (An assistant can handle multiple
appointments).
4. Patient - MedicalRecord: One-to-Many (A patient can have multiple medical records)
 6

Fig: ER Diagram

User Interface Design

1. Patient Portal:
○ Registration Form
○ Login Form
○ Appointment Request Form
○ Appointment Status View

2. Assistant Portal:
○ Appointment Management Dashboard
○ Appointment Cancellation Option

3. Doctor Portal:
○ View Appointments
 7

Implementation Plan

● Frontend:
○ Technologies: HTML, CSS, JavaScript, React/Angular/Vue.js
○ Features: Patient and Assistant interfaces for managing appointments and personal
details.

● Backend:
○ Technologies: Node.js/Java, Spring Boot, Django, Ruby on Rails
○ Features: APIs for handling patient registration, appointment requests, and schedule
management.

● Database:
○ Technologies: MySQL/PostgreSQL
○ Features: Store and manage patient, doctor, and appointment information.

● Security:
○ Implement encryption for sensitive data.
○ User authentication and authorization mechanisms.

Testing

● Unit Testing: Test individual components (e.g., patient registration, appointment

scheduling).
● Integration Testing: Test interactions between components (e.g., end-to-end
appointment request and confirmation).
● User Acceptance Testing (UAT): Ensure the system meets user requirements and
expectations.

Conclusion

The Hospital Management System will significantly improve the efficiency and accuracy of
patient appointment scheduling and record management. This will enhance patient experience
and allow medical staff to focus on providing quality care.