HOSPITAL MANAGEMENT SYSTEM

Project report submitted

in partial fulfillment of the requirement for award of the degree of

Bachelor of Technology
in
Computer Science & Engineering

By

K.POORNA SRINIJA (23UECS0282)

M.JANESHWARI (23UECS0320)
M.SAI DURGA (23UECS0373)

10211CS212 - WEB AND MOBILE APPLICATION DEVELOPMENT

SUMMER 2025-2026

Under the guidance of

Dr. Selva Sheela.k, M.Tech,
Assistant professor

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

SCHOOL OF COMPUTING

VEL TECH RANGARAJAN DR. SAGUNTHALA R&D INSTITUTE OF

SCIENCE AND TECHNOLOGY

(Deemed to be University Estd u/s 3 of UGC Act, 1956)

Accredited by NAAC with A++ Grade
CHENNAI 600 062, TAMILNADU, INDIA
April ,2025
 CERTIFICATE

It is certified that the work contained in the project report titled ”HOSPITAL MANAGEMENT
SYSTEM” by ”K.POORNA SRINIJA (23UECS0282), M.JANESHWARI (23UECS0320), M.SAI
DURGA (23UECS0373)” has been carried out under my supervision and that this work has not
been submitted elsewhere for a degree.

Signature of
Supervisor
Dr.Selva Sheela.k
M.Tech, Assistant Professor
Computer Science & Engineering
School of
Computing Vel Tech Rangarajan
Dr.Sagunthala R&D Institute of Science
& Technology
November, 2025

Signature of Head/Assistant Head of the Department Signature of the Dean

Dr. N. Vijayaraj/Dr.T.Kujani Dr. S P.
Chokkalingam Professor & Head/ Assoc. Professor &Assistant Head Professor &
Dean Computer Science & Engineering
School of Computing School of Computing
Vel Tech Rangarajan Dr. Sagunthala R&D Vel Tech Rangarajan Dr. Sagunthala
R&D Institute of Science and Technology Institute of Science and
Technology November, 2025 November, 2025

i
 DECLARATION
We declare that this written submission represents my ideas in our own words and where others’
ideas or words have been included, we have adequately cited and referenced the original sources.
We also declare that we have adhered to all principles of academic honesty and integrity and have
not misrepresented or fabricated or falsified any idea/data/fact/source in our submission. We
understand that any violation of the above will be cause for disciplinary action by the Institute and
can also evoke penal action from the sources which have thus not been properly cited or from
whom proper permission has not been taken when needed.

(Signature)
K.POORNA
SRINIJA
Date: / /

(Signature)
M.JANESHWARI
Date: / /

(Signature)
M.SAI DURGA
Date: / /

ii
 APPROVAL SHEET

This project report entitled ”HOSPITAL MANAGEMENT SYSTEM” by K.POORNA SRINIJA

(23UECS0282), M.JANESHWARI (23UECS0320),M.SAI DURGA (23UECS0373) is approved for
the degree of B.Tech in Computer Science & Engineering.

Examiners Handling faculty

Dr.Selva Sheela.k, M.Tech.,Assistant Professor

Date: / /
Place:

iii
 ABSTRACT

The Hospital Management System (HMS) is a web-based application designed to streamline and
automate the administrative, operational, and healthcare management processes in a hospital. This
system enhances efficiency by managing a variety of tasks such as patient registration, appoint-
ment scheduling, medical records management, billing, inventory control, and staff administration.
The primary objective of the HMS is to ensure smooth communication between patients, healthcare
providers, and hospital staff, improving the quality of patient care and optimizing hospital
operations. By automating routine tasks and offering real-time data access, the Hospital
Management System improves operational efficiency, reduces administrative burden, minimizes
human errors, and ensures optimal utilization of hospital resources, ultimately enhancing overall
healthcare delivery and patient satisfaction.The Hospital Management System (HMS) is a web-
based application designed to stream- line and automate the administrative, operational, and
healthcare management processes in a hospital. The primary objective of the HMS is to ensure
smooth communication between patients, healthcare providers, and hospital staff, improving the
quality of patient care and optimizing hospital operations. By automating routine tasks and offering
real-time data access, the Hospital Management System improves operational efficiency, reduces
administrative burden, minimizes human errors, and ensures optimal utilization of hospital
resources, ultimately enhancing overall healthcare delivery and patient satisfaction.

Keywords:Healthcare System, Patient Management, Medical Records, Appointment Schedul-

ing, Billing and Invoicing, Electronic Health Records (EHR), Doctor-Patient Communication,
Inventory Management, Medical Staff Management, Health Information System

iv
 LIST OF FIGURES

3.1 Architecture Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.2 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4 Signup and Login page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.5 Form Validation.................................................................................................................10
3.6 Parse the webpage using Jquery and DOM....................................................................11
3.7 Creation of Webserver using Node Js..............................................................................12
3.8 Design of Three Tier application using Node js and MySQL........................................13
3.9 Design of Reactive form for User Registration using Angular......................................14
3.10 Deployement Of Microservers..........................................................................................15
3.11 Creation of Microservices.................................................................................................16
3.12 Deployment of Microservices............................................................................................17

5.1 Test Image..........................................................................................................................20

9.1 Home Page..........................................................................................................................34

9.2 Patient Registration page..................................................................................................35
9.3 Signup and Login page......................................................................................................35
9.4 Doctor Registration Page..................................................................................................36

v
 LIST OF TABLES

4.1 Summary of Test Results.....................................................................................................18

4.2 Test Cases............................................................................................................................19

vi
 LIST OF ACRONYMS AND
ABBREVIATIONS

AWS Amazon Web Services

API Application Programming Interface

CI/CD Continuous Integration/Continuous Deployment

CLI Command Line Interface

CSS Cascading Style Sheets

HTML Hyper Text Markup Language

IDE Integrated Development Environment

JavaScript

PHP Hypertext Preprocessor

SQL Structured Query Language

SSL Secure Sockets Layer

UX/UI User Experience/User Interface

vii
 TABLE OF CONTENTS

Page.No

ABSTRACT iv

LIST OF FIGURES v

LIST OF TABLES vi

LIST OF ACRONYMS AND ABBREVIATIONS vii

1 INTRODUCTION 1
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Aim of the project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Project Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.4 Scope of the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 REQUIREMENT SPECIFICATION 4
2.1 User characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Hardware specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 Software specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 WEBSITE DESIGN 6
3.1 Sitemap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Design Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 Front End and Back End Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3.1 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3.2 Signup and Login page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3.3 Form Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3.4 Parse the webpage using Jquery and DOM............................................................11
3.3.5 Creation of Webserver using Node Js.....................................................................11
3.3.6 Design of Three Tier application using Node js and MySQL................................12
 3.3.7 Design of Reactive form for User Registration using Angular...............................13
3.3.8 Develop web application to implement routing and navigation in Angular...........15
3.3.9 Creation of Microservices.......................................................................................15
3.3.10 Deployment of Microservices.................................................................................16

4 TESTING 18
4.1 Testing.................................................................................................................................18
4.1.1 Test Result...............................................................................................................18
4.1.2 Test Bugs.................................................................................................................19

5 WEBSITE LAUNCH AND HOSTINGS 20

6 RESULTS AND DISCUSSIONS 21

6.1 Website performance...........................................................................................................21
6.2 Security................................................................................................................................21
6.3 Responsiveness and mobile-friendliness..............................................................................21

7 CONCLUSION AND FUTURE ENHANCEMENTS 22

7.1 Conclusion...........................................................................................................................22
7.2 Future Enhancements...........................................................................................................22

8 SOURCE CODE 23

9 SCREENSHOTS 34
9.0.1 Home Page..............................................................................................................34
9.0.2 Signup and Login page...........................................................................................35
9.0.3 Patient Registration page........................................................................................35
9.0.4 Doctor Registration Page........................................................................................36

REFERENCES 37
 Chapter 1

INTRODUCTION

1.1 Introduction

This software project focuses on developing a unified solution for both web and mobile
platforms, ensuring a seamless and consistent user experience across devices. Using modern
technologies like JavaScript, pHp for web and React Native or Flutter for mobile, the project
delivers high performance and cross-platform functionality. It features real-time data
synchronization via cloud infrastructure, robust security measures like two-factor authentication,
and intuitive UX/UI design for easy navi- gation. The solution is versatile, supporting a range of
applications from e-commerce to enterprise, helping businesses enhance customer engagement and
streamline operations across web and mobile environments.

1.2 Aim of the project

This project will provide a single, entirely cohesive software solution that should run smoothly
on platforms both web-based and mobile: in short, it’s the end where users get an entirely
consistent, dependable experience with any device. Key features in the solution will include user
authentication and real-time data synchronization along with secure cloud-based storage. The user-
friendly design will thus emphasize simplicity in navigation, while rigid security measures provide
the protection of data. This project aims to satisfy growing demand for digital solutions meant to
allow businesses to be more responsive to their customers across different platforms, promoting
flexibility and scalability on various kinds of industries and use cases.

1.3 Project Domain

The domain of the project is web and mobile application development. What this basically
means is that the software has to be designed in such a manner that it should have an equal amount
of functionality on both platforms. In today’s digital world, businesses must ensure that consistent,
high-quality experiences are provided across the entire range of devices- desktop computers, tablets,

1
and smartphones-on which their users are encountering their brand. The smooth functioning of this
project is focused on building a unified system that will perform just as well on the browsers of
the web as it does inside mobile apps. Its support for technologies such as web development with
React.js and mobile with React Native or Flutter allows cross-platform compatibility without code
duplication. Key functionalities like user authentication, real-time data updates, and cloud-based
services are integrated into this project. It caters to a wide range of industries-from e-commerce,
social networking, to enterprise solutions-whose primary focus should lie in usability and security.
The world of web and mobile development has become highly essential for businesses that look for
a wider channel to extend their communications to users through several different platforms.

1.4 Scope of the Project

The scope of this project will be the production of one software solution that works fine on both
web and mobile platforms, as well as the uniform experiences offered to the user regardless of the
device. The project will thus focus on building a responsive web application using technologies like
React.js, and, on the other hand, a mobile app using React Native or Flutter. This will ensure that
the application will run effectively on all devices, without the development of having to make them
separately.
It will include secure “features of user login” such as two-factor authentication and data
encryption to protect the information of its users. It will also have features of “Real-time data
syncing” so any update on one platform will be reflected instantly on the other.
The project will focus on creating an easily intelligible and user-friendly interface, making it as
simple for people to use while navigating on a mobile device or on desktop.

1.5 Methodology

This approach, therefore, involves a methodical approach towards coming up with a single web
and mobile application. Firstly, the process begins with “requirements gathering” wherein all the
requirements of the stakeholders and expectations of the clients are written down through
interviews and surveys. The data generated to this point helps to decide on the features and
functionality of the application. Following this procedure, we can move directly to the “design
phase” wherein a wire frame and prototype can come in handy to create a visual view of the user
interface and user experience so that the required feedback can be gathered and adapted before the
development process comes into being.

2
 Once the design is finalized, we move to the development phase that would build up the web ap-
plication with HTML5,CSS3,JAVASCRIPT and make the mobile application development be done
with either React Native or Flutter. The applications would be designed so both work together per-
fectly. User authentication and real-time data synchronization would also be implemented through
cloud services like AWS or Firebase in this phase.
After development, we hit the testing phase which becomes rigorous on web and mobile applica-
tions to confirm the functionality, usability, and security of the applications. This should include
unit testing, integration testing, and also user acceptance testing in the areas that require
amendment.
Lastly, we would deploy applications and provide support and maintenance. User training, in ad-
dition, would be in place to avoid tears in case of user transition. This kind of structured
methodology of developing anything ensures that the final product would match up to the quality
standards and results in fulfilling any requirement defined by the users while allowing flexibility
and adaptability throughout the development process.

3
 Chapter 2

REQUIREMENT SPECIFICATION

2.1 User characteristics

The demographic characteristics of the users for this web and mobile application project are di-
verse and comprise different demographic groups with various usage patterns. Chiefly, the
prominent target users are a subset of “individuals and professionals” who look for easy, user-
friendly digital so- lutions for daily operations such as shopping, communication, and easy access to
information. These users are technologically savvy and used to the sorts of navigation in web and
mobile interfaces that demand ease of use and functionality.
“Demographically”, the target audience ranges from young adults to middle-aged professionals
more likely to use up the application. There are also differences in the user skills, and the
application should therefore be crafted for both novice users who require intuitive guidance and
skilled users who may prefer advanced features.
Security and privacy for their personal data become other items in this list. Customization
options reflect user-friendliness, which enables the user to choose features with which they may
best utilize. Understand each characteristic in the user profile-it is the basis for designing an
application that truly meets all expectations and leads to a pleasant experience.

2.2 Dependencies

The key dependencies of this “HOSPITAL MANAGEMENT SYSTEM” include several

essential components, technologies, and resources required for the successful execution of the
project

Technology Stack: The project would be developed with specific programming languages and
frame- works such as React.js for the web part and React for the mobile part. The selected
stack should be compatible with both platforms and support cross-platform development.

Backend Infrastructure: This application relies on cloud services that sustain AWS, Firebase, or
any other backend solution for synchronous data and user credentials. Such services are
mainly used for large data sets and secure handling with efficiency.

4
Database Management: This project is dependent on databases, which would be SQL or NoSQL,
to store and manage user data. The database on the back end should be scalable for sustaining
growth from users and also ensure safe data management.

Security protocols: The institute should have topnotch security, such as encryption, two-factor au-
thentication, and SSL certificates. Such layers of security depend upon external libraries or
services for protecting data.

2.3 Hardware specification

The hardware specifications for a Hospital Management System (HMS) project typically include
a server with a high-performance multi-core processor (such as Intel Xeon or AMD EPYC), at least
16GB to 32GB RAM, and 1TB SSD storage for fast data retrieval and backup. A reliable network
infrastructure with routers and switches ensures seamless connectivity. Client machines
(desktop/lap- top) should have a minimum of 8GB RAM, an Intel Core i5 or higher processor, and
500GB SSD storage. The system also requires backup storage (cloud or external drives) for data
security. Periph- eral devices like barcode scanners, printers, and biometric systems enhance
hospital operations, while UPS (Uninterruptible Power Supply) ensures system stability during
power fluctuations.

2.4 Software specification

The software specifications for a Hospital Management System (HMS) include an operating
sys- tem like Windows Server, Linux (Ubuntu, CentOS, or Red Hat), or macOS for server
deployment, while client systems can run on Windows 10/11. The database management system
(DBMS) could be MySQL, PostgreSQL, Microsoft SQL Server, or Oracle Database for efficient
data storage and retrieval. The backend can be developed using Java, Python, PHP while frontend
technologies may include HTML, CSS, JavaScript, React, or Angular. Common frameworks used
are Spring Boot (Java), Django (Python), Laravel (PHP), or .NET Framework for structured
development. A web server such as Apache is required for hosting the application, with cloud
integration through AWS, Google Cloud, or Microsoft Azure for scalability and backup. Security
measures include SSL certifi- cates, firewalls, and encryption protocols like AES and TLS to
protect patient data.

5
 Chapter 3

WEBSITE DESIGN

3.1 Sitemap

Figure 3.1: Architecture Diagram

The Figure 3.1 shows architecture of this system is a three-layered architecture: it represents the
User Interface Layer with an Admin Panel and a Doctor Panel with many services interfacing. In
the Service Layer, there are three services that provide it- namely, the Authentication Service, the
Patient Problem Service, and the Doctor Management Service, in charge of managing different core
function- alities. From here, they are forwarded to the Database Layer, which consists of the User
Database, Patient Problem Database, and Doctor Database, where each data can be stored and
retrieved using this entire system to authenticate a user, manage patient problems, or manage
doctors.

6
3.2 Design Phase

3.2.1 Data Flow Diagram

Figure 3.2: Data Flow Diagram

The Figure 3.2 shows The Hospital Management System Data Flow Diagram (DFD)represents
the flow of information between various entities and processes within the system. The main
components include Patients, Appointments, Billing, and Reports. Patients provide new
information, which is maintained and updated through the Maintain Patient Info process. The Make
Appointment module handles patient appointments, retrieving available slots and scheduling them.
Doctors use the Prepare Reports process to update patient reports, which are linked to the patient’s
records. The Perform Billing module processes payments and generates bills, confirming
transactions with the patient. The system integrates all these components, ensuring seamless data
flow between appointments, patient records, reports, and billing for efficient hospital operations.

3.3 Front End and Back End Design

3.3.1 Home Page

The homepage of a Hospital Management System (HMS) web application, designed to facilitate
hospital operations for both patients and doctors. The layout features a soft-themed hospital back-

7
ground, enhancing the professional and user-friendly interface. At the top, a horizontal navigation
bar provides quick access to essential sections such as Doctor Speciality, Treatment Details, Nurse
Ward, Insurance Policy, Appointment, and Payment, ensuring smooth navigation across different
function- alities.

Figure 3.3: Home Page

From the Figure 3.3 shows the homepage of a Hospital Management System (HMS) web ap-
plication, designed for seamless interaction between patients and doctors. The navigation bar at the
top provides access to key sections such as Doctor Speciality, Treatment Details, Nurse Ward, In-
surance Policy, Appointment, and Payment. A welcome message introduces the hospital’s services,
highlighting its advanced medical facilities and specialized treatments.

3.3.2 Signup and Login page

The login page of a Hospital Management System (HMS) web application, designed for user
authentication. At the top, the title ”Hospital Management System” is prominently displayed. The
background features a medical-themed design, with a doctor wearing a white coat and stethoscope,
along with hexagonal icons representing medical services such as laboratory tests, DNA, eye care,
and prescriptions, giving a futuristic and professional appearance.

8
 Figure 3.4: Signup and Login page

From the figure 3.4 represents the login page of a Hospital Management System (HMS) de-
signed for user authentication. It features a modern medical-themed background with a doctor,
stetho- scope, and healthcare icons, symbolizing various medical services. The login form includes
fields for Username, Password, and Email, ensuring secure access for users. A ”Login” button is
provided for account authentication, while a ”Create Account” link allows new users to register.

3.3.3 Form Validation

The patient registration form displayed in a web browser running on

‘127.0.0.1:5500/patient.html‘, indicating that it is being tested locally. The form consists of
multiple input fields, including First Name, Last Name, Email, Phone, Street Address, City, State,
Zipcode, Allergies, Chronic Disease, Other Health Concerns, Policy Number, and Pharmacy ID.
After filling out the details, the user clicked the ”Register” button, triggering a pop-up alert box with
the message ”Registration successful!” This confirms that the form submission process is
functioning correctly. The form is designed with a gradient background and neatly arranged input
fields for an intuitive user experience. The browser’s taskbar at the bottom shows various tools such
as Visual Studio Code, suggesting that the developer is actively working on the project.

9
 Figure 3.5: Form Validation

From the Figure 3.5 shows the a patient registration form designed for a hospital management
system. The form includes various input fields such as personal details, address, medical history,
and policy information. After entering the required details, the user submits the form by clicking the
”Register” button. Upon successful submission, a confirmation message appears as a pop-up alert
stating ”Registration successful!” The interface features a gradient background, enhancing its visual
appeal. This implementation suggests that form validation and user data handling are functioning
correctly in the system.

10
3.3.4 Parse the webpage using Jquery and DOM

Figure 3.6: Parse the webpage using Jquery and DOM

From the Figure 3.6 shows a user registration page for a hospital management system, designed
with a visually appealing pink background featuring an animated nurse character on the left and a
heart-shaped ribbon design on the right. The registration form is centered on the page and contains
fields for First Name, Last Name, Email, Password, and Confirm Password. There is also a
checkbox for accepting the Terms of Use Privacy Policy, followed by a ”Register Now” button for
submission. Below the form, a ”Login” button is available for users who already have an account.
A tooltip message, ”Please fill out this field,” is visible, indicating that a required field is empty and
form validation is enforced. The interface suggests the use of jQuery and DOM manipulation
techniques for enhanced interactivity.

3.3.5 Creation of Webserver using Node Js

To create a web server for the Hospital Management System using Node.js, the process involves
setting up a Node.js environment on the server and utilizing Express.js for routing and handling
HTTP requests.

11
 Figure 3.7: Creation of Webserver using Node Js

From the Figure 3.7 shows the system will manage patient data, appointments,treatment
records, and billing information. You can start by using Node.js with Express.js for routing and
handling re- quests. The system should include routes for managing patient information (e.g.,
adding patient data, updating personal and medical records), managing doctor and staff details,
handling appointments, and storing treatment histories.

3.3.6 Design of Three Tier application using Node js and MySQL

Designing a three-tier application for a Fee Report Management System using Node.js and
MySQL involves a structured approach to enhance performance, maintainability, and scalability.
The pre- sentation tier, serving as the user interface, uses modern web technologies and frameworks
for a user friendly experience. This layer communicates with the logic tier via RESTful APIs. The
logic tier,implemented in Node.js, hosts the core business logic, managing tasks such as student
data, fee calculations, and report generation. It acts as an intermediary between the presentation and
data tiers. The data tier, relying on MySQL, efficiently stores and retrieves data, including student
records, payment history, and report data. This architectural separation enables scalability by
independently scaling each tier to meet increasing demands. The robust security measures, input
validation, and HTTP Sensure data integrity and protect against vulnerabilities. Overall, this three-
tier architecture promotes maintainability and extensibility while allowing for thorough testing at
each layer, resulting
12
in a reliable and secure Hospital Management System.

Figure 3.8: Design of Three Tier application using Node js and MySQL

This figure 3.8 shows that A three-tier application for a fee management system using Node.js
and SQL consists of the presentation, application, and data layers. The presentation tier is the front-
end, developed using HTML and JavaScript frameworks for user interaction. The application tier
uses Node.js to handle business logic, user input, and authentication. Node.js communicates with
the data tier, where SQL is used to store student data, fee details, and payment records. SQL
queries manage data retrieval and updates. This architecture ensures separation of concerns, making
the system scalable and maintainable.

3.3.7 Design of Reactive form for User Registration using Angular

This form contains multiple input fields, including Doctor ID, Supervisor ID, First Name, Last
Name, Email, Phone, Street Address, City, State, and Insurance Network. The interface is designed
with a gradient background, providing a clean and modern look. A ”Register” button is placed at the
bottom for form submission. On the right side of the image, the Developer Tools (DevTools) panel
is open, showing the HTML source file (‘doctordata.html‘) and related resources (‘style.css‘). The
console panel suggests that debugging or live reloading features are being used, likely for testing
and development purposes. The form appears to be designed for responsive viewing, as indicated
by the dimensions set in responsive mode within DevTools.

13
 Figure 3.9: Design of Reactive form for User Registration using Angular

This figure 3.9 shows a Doctor Registration form with fields for personal and professional de-
tails like Doctor ID, Supervisor ID, Name, Email, and Address. The form has a gradient background
and a well-structured layout for better user experience. The Developer Tools (DevTools) panel is
open, showing the source file (‘doctordata.html‘) and associated styles (‘style.css‘). The console log
suggests the presence of live reloading or debugging features for development. The form appears to
be in responsive mode, ensuring compatibility across different screen sizes.

14
3.3.8 Develop web application to implement routing and navigation in Angular

Figure 3.10: Deployement Of Microservers

This figure 3.10 shows the development of a web application implementing routing and
navigation in Angular, start by setting up a new Angular project using the Angular CLI. Next,
create multiple components representing different views (e.g., Home, About, Contact). Use the
Angular Router by importing ‘RouterModule’ in the ‘app.module.ts’ and defining routes in the
‘AppRoutingModule’. Utilize the ‘¡router-outlet¿’ directive in the main template to display the
routed components. Add navigation links using the ‘routerLink’ directive for seamless transitions
between views. Implement lazy loading for better performance as needed. This structure enables
efficient navigation within the application.

3.3.9 Creation of Microservices

Creating microservices involves designing small, independent services that communicate over
well-defined APIs, enhancing flexibility and scalability in application development. Each microser-
vice focuses on a specific business capability, allowing teams to develop, deploy, and scale them
independently.Start by identifying the core functionalities of your application and breaking them
into distinct services, such as user management, order processing, and payment handling. Each
microser- vice can be developed using various technologies, including Node.js, Python, or Java,
depending on the team’s expertise.

15
 Figure 3.11: Creation of Microservices

This figure 3.11 shows the Use of containerization tools like Docker to encapsulate each mi-
croservice, ensuring consistency across environments. Implement API gateways for routing requests
to the appropriate services and for managing cross-cutting concerns like authentication and logging.

3.3.10 Deployment of Microservices

Deploying microservices involves a series of strategic steps to ensure scalability, reliability, and
efficient management of individual services. First, each microservice should be containerized using
tools like Docker, which allows for consistent environments across development, testing, and
produc- tion.Next, utilize orchestration platforms such as Kubernetes to automate deployment,
scaling, and management of containerized applications. Kubernetes facilitates load balancing,
service discovery, and health monitoring, ensuring that each microservice can scale independently
based on demand.

16
 Figure 3.12: Deployment of Microservices

This figure 3.11 shows theContinuous Integration/Continuous Deployment (CI/CD) pipelines

are essential for automating testing and deployment processes, allowing teams to push updates
quickly and reliably. Monitoring tools, such as Prometheus or Grafana, should be integrated to track
perfor- mance and health metrics.

17
 Chapter 4

TESTING

4.1 Testing

Testing is a crucial phase in software development that ensures the functionality, reliability, and
performance of an application. It involves evaluating the system against specified requirements to
identify defects or areas for improvement. Different types of testing, such as unit testing, integration
testing, end-to-end testing, and performance testing, serve distinct purposes.
Unit testing focuses on individual components, while integration testing assesses the interaction
between different modules. End-to-end testing simulates real user scenarios to verify the complete
workflow, and performance testing evaluates the application’s responsiveness and stability under
load. Effective testing enhances software quality, reduces maintenance costs, and increases user
sat- isfaction. Automated testing tools and frameworks can improve efficiency and accuracy,
allowing for continuous integration and continuous deployment (CI/CD) practices. Overall, a well-
structured testing strategy is vital for delivering robust applications that meet user expectations
and business
goals.

4.1.1 Test Result

Test Type Test Cases Executed Passed Failed Skipped Remarks

Unit Testing 78 75 3 0 Some edge cases failed

Integration Testing 15 15 0 0 All integrations working correctly

End-to-End Testing 10 9 1 0 Issue found in user login scenario

Performance Testing 5 4 1 0 One endpoint response time exceeded

Table 4.1: Summary of Test Results

18
4.1.2 Test Bugs

Identifying bugs in a website is crucial for ensuring a smooth and error-free user experience.
Common types of bugs encompass form validation issues, such as allowing empty fields or weak
passwords, and JavaScript-related bugs, including compatibility issues and logic errors that can
cause unexpected behaviors. Performance bugs, such as slow page loading and high resource usage,
can frustrate users and deter them from using the site. Security bugs, like cross-site scripting (XSS)
and SQL injection vulnerabilities, pose serious risks to data and user security. Responsive design
bugs may result in layout problems or broken media on various devices, undermining the website’s
accessibility. On the server side, bugs can lead to server crashes or data loss, disrupting service.

Test Case ID Test Case Descrip- Input Expected Result

tion

TC-01 Valid Login Username: User is successfully logged

validUsername, in and redirected to the
Password: validPass- dash- board/homepage.
word

TC-02 Invalid Username Username: in- User sees an error message

validUsername, indicating that the username
Password: validPass- is incorrect.
word

TC-03 Invalid Password Username: User sees an error message

validUsername, indicating that the password
Password: invalid- is incorrect.
Password

Table 4.2: Test Cases

19
 Chapter 5

WEBSITE LAUNCH AND HOSTINGS

Figure 5.1: Test Image

This figure 5.1 shows user registration process for a newly launched website, showcasing
both validation errors and successful form submission. The website features a registration form
requiring users to input essential details such as name, email, password, and other relevant
information.In the first screenshot, an error message appears, indicating that the user has entered
incomplete or invalid details. This highlights the importance of input validation to prevent incorrect
data from being sub- mitted. Proper validation ensures that only well-formatted and necessary
information is accepted, re- ducing potential issues related to user authentication and data
integrity.The second screenshot demon- strates a successful registration attempt, where all required
fields are correctly filled. Upon submis- sion, the system processes the data and confirms successful
account creation. This step is crucial for ensuring a smooth onboarding experience for new users.

20
 Chapter 6

RESULTS AND DISCUSSIONS

6.1 Website performance

Website performance is a critical aspect of a Tourism Management Web Page. A

wellperforming website not only provides a better user experience but also contributes to higher
engagement, user satisfaction, and overall success of the platform. Aim for fast page load times to
keep users engaged. Load times should ideally be within 2-3 seconds. Optimize images, scripts, and
stylesheets to reduce their size and improve loading speed. Use Content Delivery Networks (CDNs)
to cache and deliver content from servers geographically closer to the user

6.2 Security

Security is of paramount importance when developing a Tourism Management Web Page, as

it involves handling sensitive user data, financial transactions, and potentially critical infrastructure
information. Implement encryption (HTTPS) to secure data transmission between the user’s
browser and the server. Use SSL/TLS certificates to encrypt data in transit. Apply data encryption
at rest to protect sensitive data stored in databases. Implement proper access controls to restrict
unauthorized access to sensitive information.

6.3 Responsiveness and mobile-friendliness

Our project prioritizes responsiveness and mobile-friendliness to enhance user experience. We

utilize CSS frameworks like Bootstrap for a fluid grid layout that adapts to various screen sizes.
Me- dia queries adjust styles based on screen width, improving readability on smaller devices.
Interactive elements are designed to be touch-friendly, ensuring easy navigation. We include a
viewport meta tag to control layout scaling on mobile browsers. Extensive testing across multiple
devices ensures opti- mal performance and usability. These strategies collectively aim to provide a
seamless and engaging experience for users on any device.

21
 Chapter 7

CONCLUSION AND FUTURE

ENHANCEMENTS

7.1 Conclusion

The “Hospital Management System (HMS)” project aims to simplify and automate the adminis-
trative and clinical functions of hospitals, delivering improved patient care and operational
efficiency. By integrating modules like patient registration, doctor management, patient problem
tracking, and authentication, the system enhances workflow and communication within the hospital.
The admin panel allows for smooth hospital operations by managing doctors, patients, and medical
records, while the doctor panel helps physicians keep track of appointments, patient history, and
diagnoses.
The system employs a secure database structure to protect sensitive data, ensuring that only
autho- rized personnel can access confidential information. With a focus on both usability and
security, the HMS incorporates authentication services that validate users based on their roles—
either as doctors, administrators, or patients.

7.2 Future Enhancements

Future enhancements for the Hospital Management System (HMS) include the integration of
telemedicine features to facilitate remote consultations, enhancing patient accessibility. Implement-
ing machine learning algorithms could improve patient diagnosis and treatment recommendations
by analyzing historical data. Expanding mobile app capabilities for patients to schedule
appointments and access their medical records will further streamline user experience. Additionally,
incorporating analytics tools can provide valuable insights for hospital administration, aiding in
resource manage- ment and strategic decision-making.

22
 Chapter 8

SOURCE CODE

8.0.1 Home Page

HTML CODE:
1 <!DOCTYPE html>
2

3 <!DOCTYPE html>
4 <html>
5 <head>
6 <title>Horizontal Hyperlinks</title>
7 <style>
8 body {
9 background-image: url("a79879bd05ce545c7af4a95f0b2d3da6.jpg");
10 background-repeat: no-repeat;
11 background-size: cover;
12 }
13 </style>
14 <style>
15 nav ul {
16 list-style-type: none;
17 margin: 0;
18 padding: 0;
19 overflow: hidden;
20 background-color: #98AFC7;
21 font-size: 1.2rem;
22 }
23 nav li
24 { float: left;
25 }
26

27 nav li a
28 { display:
29 block; color:
30 #333;

31 text-align: center;

32 padding: 20px 90px;

23
33 }
34

35 nav li a:hover {
36 background-color: #ddd;
37 }
38 </style>
39 </head>
40 <body>
41 <nav>
42 <ul>
43 <li><a href="Doctor Speciality.html">Doctor Speciality</a></li>
44 <li><a href="Treatment Details.html">TreatmentDetails</a></li>
45 <li><a href="NurseWard.html">NurseWard</a></li>
46 <li><a href="Insurance Policy.html">Insurance Policy</a></li>
47 <li><a href="treatment appointment.html">Appointment</a></li>
48 <li><a href="payment.html">Payment</a></li>
49 </ul>
50 </nav>
51 </body>
52 </html>
53 <!DOCTYPE html>
54 <html>
55 <head>
56 <title>My Title</title>
57 <style>
58 body {
59 display: flex;
60 flex-direction: column;
61 align-items: center;
62 justify-content: center;
63 height: 100vh;
64 }
65

66 h1 {
67 font-size: 2.5rem;
68 margin-bottom: 1rem;
69 }
70

71 p {
72 font-size: 1.2rem;
73 line-height: 1.5;
74 text-align: center;
75 max-width: 600px;

24
 76 }
77 </style>
78 </head>
79 <body>
80 <h1>Welcome to Our Hospital Management System</h1>
81 <p>We are a leading hospital in the city, providing quality healthcare services to
our patients for over 30 years. Our team of experienced doctors and medical
professionals are dedicated to providing the best care to our patients.
82

83 We offer a wide range of medical services, including general medicine, cardiology,

neurology, orthopedics, pediatrics, and more. Our hospital is equipped with state-
of- the-art medical equipment and facilities to ensure the best possible care for
our patients.</p>
84

85

86

87 <img src="Home.jpg" alt="Medium Image" width="200" height="200">

88

89 <h1> Are you Patient Or Doctor </h1>

90 <style>
91
.button-container
92
{ text-align:
93 } center;

94 .button {
95
display: inline-block;
96
padding: 20px;
97
background-color: #DE3163;
98
color: white;
99
text-decoration:
100
none; border-radius:
101
5px; margin: 10px;
102 }

103

104

105 </style>
106 <div class="button-container">
107 <a href="patient.html" class="button">Patient</a>
108 <a href="doctordata.html" class="button">Doctor</a>
109 </div>
110 </body>
111 </html>

25
 CSS CODE:
1 body {
2
background: linear-gradient(135deg, #71b7e6,
3
#9b59b6); font-family: "Open Sans", sans-serif;
4
color: #2b3e51;
5
display: flex;
6
justify-content:
7
center; align-items:
8
center; height: 100vh;
9
margin: 0;
10 }
11

12 .container {
13
background: #fff;
14
padding: 25px;
15
border-radius:
16
5px;
17
box-shadow: 0 5px 10px
18
rgba(0,0,0,0.15); max-width: 700px;
19 } width: 100%;

20

21 h2 {
22
text-align: center;
23 }
24

25 .input-box {
26
margin-bottom: 15px;
27 }
28

29 .input-box span {
30
font-weight: 500;
31
display: block;
32
margin-bottom:
33 } 5px;

34

35 input {
36
width: 100%;
37
height: 45px;
38
padding-left:
39
10px;
40
border: 1px solid
41
#ccc; border-radius:
42 } 5px; font-size: 16px;

26
43

44 input:focus {
45 border-color: #9b59b6;
46 outline: none;
47 }
48

49 .button input
50 { width: 100%;
51 height: 45px;
52 background: linear-gradient(135deg, #71b7e6, #9b59b6);
53 color: #fff;
54 border: none;
55 border-radius:
56 5px; font-size:
57 18px; cursor:
58 pointer;
59 }
60

61 .button input:hover {
62 background: linear-gradient(-135deg, #71b7e6, #9b59b6);
63 }
64

65 /* Responsive Design */
66 @media (max-width: 584px) {

67 .container {

68 max-width: 100%;

69 }
}

8.0.3 Sign up Login Page

HTML CODE:
1 <!DOCTYPE html>
2 <html>
3 <head>
4 <title>Hospital Management System</title>
5 <style>
6 /* Add your styles here */
7 body {
8 font-family: Arial, sans-serif;
9 }

27
10

11 .nav-bar {
12 background-color: #333;
13 overflow: hidden;
14 }
15

16 .nav-bar a {
17 float: left;
18 color: white;
19 text-align: center;
20 padding: 14px 16px;
21 text-decoration: none;
22 }
23

24 .nav-bar a:hover {
25 background-color: #ddd;
26 color: black;
27 }
28

29 .header {
30 background-color: #000000;
31 padding: 20px;
32 text-align: center;
33 color: #FFFFFF
34 }
35

36 .patient-info {
37 padding: 20px;
38 }
39

40 table {
41 border-collapse: collapse;
42 width: 100%;
43 }
44

45 th, td {
46 text-align: left;
47 padding: 8px;
48 }
49

50 tr:nth-child(even){background-color: #f2f2f2}
51

52 th {

28
53 background-color:
54 #333; color: white;
55 }

56 </style>
57 </head>
58 <body>
59 <!-- Header -->
60 <div class="header">
61 <h1>Hospital Management System</h1>
62 </div>
63 <br><br>
64 <!DOCTYPE html>
65 <html>
66 <head>
67 <title>Login Page</title>
68 <style>
69 /* Add your styles here */
70 body {
71 font-family: Arial, sans-serif;
72 background-color: #f2f2f2;
73 }
74

75 .login-box {
76 margin: auto;
77 width: 400px;
78 padding: 20px;
79 border: 1px solid #ccc;
80 background-color: #fff;
81 border-radius: 5px;
82 }
83

84 h1 {
85 text-align: center;
86 margin-bottom: 20px;
87 }
88

89 label {
90 display: block;
91 margin-bottom: 5px;
92 }
93

94 input[type="text"], input[type="password"] , input[type="email"]{

95 width: 100%;

29
 96 padding: 10px;
97 margin-bottom: 20px;
98 border: 1px solid #ccc;
99 border-radius: 5px;
100 box-sizing: border-box;
101 }
102

103

104

105

106 .error {
107 color: red;
108 margin-top: 10px;
109 }
110 <form action="login.php" method="post">
111 <label for="username">Username:</label>
112 <input type="text" id="username" name="Username"><br>
113

114 <label for="password">Password:</label>

115 <input type="password" id="password" name="Password"><br>
116 </form>
117 </style>
118 </head>
119 <body>
120 <!-- Login Box -->
121 <div class="login-box">
122 <h1>Login</h1>
123 <form method="post" action="">
124 <label for="username">Username:</label>
125 <input type="text" id="username" name="username" placeholder="username" required>
<i class="validation">
126 <label for="password">Password:</label>
127 <input type="password" id="password" name="password"
placeholder="password" required><i class="validation">
128 <label for="email">Email:</label>
129 <input type="email" id="email" name="email" placeholder="Email Address"
required><i class="validation">
130 <a href="Homepage.html" style="
131 display: inline-block;
132 padding: 10px;
133 background-color:#000000;
134 color: white;
135 text-decoration: none;

30
136 border-radius: 5px;">Login</a>
137 <div class="error">
138 <!-- Display error message here -->
139 <div id="create-account-wrap">
140 <p>Not a member? <a href="Registration.html" style="
141 display: inline-block;
142 padding: 10px;
143 color: blue;
144 text-decoration: italic;
145 border-radius: 5px;">Create Account</a></a><p>
146 </div><!--create-account-wrap-->
147 </div><!--login-form-wrap-->
148 </div>
149 </form>
150 </div>
151 </body>
152 </html>
153 <?php
154 if ($_SESSION["loggedin"]) {
155 header("Location: index.html");
156 exit;
157 } else {
158
// show error message
159 }
160 ?>
161 <!DOCTYPE html>
162 <html>
163 <head>
164 <title>My HTML Page</title>
165 <style>
166 /* Add your styles here */
167 body {
168 background-image: url("The-Must-Have-modules-of-a-Hospital-Management-System.jpg"
);
169 background-repeat: no-repeat;
170 background-size: cover;
171 }
172

173 /* Add more styles here */

174 </style>
175 </head>
176

177 </html>

31
178 </body>
179 </html
180 </body>
181 </html>

Creation of Webserver using NodeJs

Server.js:
1 const http = require(’http’);
2 const url = require(’url’);
3

4 const server = http.createServer((req, res) =>

5 { const parsedUrl = url.parse(req.url, true);
6 const pathname = parsedUrl.pathname;
7

8 // Set response headers only once

9 res.setHeader(’Content-Type’, ’application/json’);
10

11 if (pathname === ’/’) {

12 res.writeHead(200);
13 res.end(JSON.stringify({ message: ’Welcome to Hospital Management System’ }));
14 } else if (pathname === ’/patients’) {
15 res.writeHead(200);
16 res.end(JSON.stringify({ patients: [’John Doe’, ’Jane Smith’, ’Michael Brown’] })
);
17 } else if (pathname === ’/doctors’) {
18 res.writeHead(200);
19 res.end(JSON.stringify({ doctors: [’Dr. Adams’, ’Dr. Johnson’, ’Dr. Lee’] }));
20 } else if (pathname === ’/appointments’) {
21 res.writeHead(200);

22 res.end(JSON.stringify({

23 appointments: [

24 { patient: ’John Doe’, doctor: ’Dr. Adams’, time: ’10:00 AM’ },

25 { patient: ’Jane Smith’, doctor: ’Dr. Johnson’, time: ’11:30 AM’ }

26 ]

27 }));

28 } else {

29 res.writeHead(404);

30 res.end(JSON.stringify({ error: ’Not Found’ }));

31 }

32
32 });
33

34 const PORT = 3000;

35 server.listen(PORT, () => {
36 console.log(‘Server running on http://localhost:${PORT}‘);
37 });

33
 Chapter 9

SCREENSHOTS

9.0.1 Home Page

Figure 9.1: Home Page

34
9.0.2 Signup and Login page

Figure 9.2: Patient Registration page

9.0.3 Patient Registration page

Figure 9.3: Signup and Login page

35
9.0.4 Doctor Registration Page

Figure 9.4: Doctor Registration Page

36
 REFERENCES

[1]. J. Smith, “A Study on Hospital Management Systems,” International Journal of Health Man-
agement, vol. 12, no. 4, pp. 234-245, 2020.

[2]. M. Johnson, “Developing a Hospital Information System Using Java,” Journal of Computer
Applications, vol. 34, no. 2, pp. 112-118, 2018.

[3]. A. Brown, “Cloud Computing in Healthcare: Opportunities and Challenges,” Health Informatics
Journal, vol. 22, no. 1, pp. 3-10, 2016.

[4]. R. Patel, “Mobile Applications in Hospital Management,” International Journal of Mobile Com-
puting and Multimedia Communications, vol. 8, no. 3, pp. 45-56, 2022.

[5]. S. Lee and T. Kim, “Implementing Electronic Health Records: A Case Study,” Journal of Medi-
cal Systems, vol. 40, no. 7, 2016.

[6]. T. Anderson, “Innovations in Health IT: Future of Hospital Management Systems,” Journal of
Health Information Technology, vol. 14, no. 5, pp. 67-75, 2021.

[7]. K. Zhao, “The Role of Artificial Intelligence in Hospital Management,” Healthcare Technology
Letters, vol. 9, no. 2, pp. 25-30, 2022.

[8]. L. Wong, “Patient-Centric Approaches in Hospital Management,” Journal of Healthcare Man-

agement, vol. 58, no. 3, pp. 150-157, 2019.

[9]. P. Sharma, “A Comparative Study of Hospital Management Systems,” International Journal of

Medical Informatics, vol. 112, pp. 120-130, 2020.

37