A PROJECT REPORT ON

HOSPITAL MANAGEMENT SYSTEM

Project Report Submitted to Bengaluru City
University in Partial
Fulfillment Of Requirements for The Award of The Degree In

BACHELOR OF COMPUTER APPLICATIONS

2023-2024
SUBMITTED BY
HARSHITHA.M
(U18EX21S0013)
AND
SHREYA.P.G
(U18EX21S0036)
Under The Guidance Of
Asst. Prof. BHASKAR REDDY SIR

DEPARTMENT OF COMPUTER APPLICATIONS

NAGARJUNA DEGREE COLLEGE
Ramagondanahalli, Yelahanaka – 560 064.
 DEPARTMENT OF COMPUTER APPLICATIONS

NAGARJUNA DEGREECOLLEGE
Ramagondanahalli, Yelahanka – 560 064.

CERTIFICATE
This is to certify that project entitled “HOSPITAL MANAGEMENT SYSTEM”
is a bonafiedwork carried out by HARSHITHA.M and SHREYA.P.G, in partial
fulfillment of the requirement for the award of degree in “Bachelor of Computer
Applications “of the Bangalore City University during the academic year 2023- 2024

Signature of the Internal Guide Signature of the HOD

Ast.Prof.Bhaskar Reddy Asst.Prof.Uma.S

Signature of the principal

Dr. Harish Babu S

Signature of External Examiners:

1.
2.
 DECARATION

I, Harshitha.M[U18EX21S0013]Shreya.P.G[U18EX21S0036], here by
declares thar the project entitled “Hospital Management System” is a
bonafied work carried out by us under the guidance of Asst.Prof. Bhaskar
Reddy sir, Department of Computer Science, Nagarjuna Degree College.
This project has been submitted as Partial fulfillment of the requirement for
the requirement for the course of the Degree in Bachelor of Computer
Applications of Bangalore City University.

SUBMITTED BY

Harshitha.M

And

Shreya.P.G
 ACKNOWLEDGEMENT

In the accomplishment of this project successfully, many people have best owned upon me
their blessings and the heart pledge support, this time I am utilizing to thank all the people
who have been concerned with this project.

I am highly indebted to Prof. Bhaskar for their guidance and constant supervision as well
as for providing necessary information regarding the project & also for their support in
completing the project. I am extremely thankful to him for providing such a nice support
and guidance, although he had busy schedule managing the corporate affairs.

I would like to express my gratitude towards my parents & member of Nagarjuna Degree
College for their kind co-operation and encouragement which help me in completion of
this project.

I am thankful to and fortunate enough to get constant encouragement, support and guidance
from all Teaching staffs of Bachelor of Computer Application which helped us in
successfully completing our project work.

SUBMITTED BY

Harshitha.M
And
Shreya.P.G
 INDEX

1. INTRODUCTION

1.1 Introduction

1.2 Problem introduction

1.3 Modules in the project

2. REQUIREMENTS SPECIFICATION

2.1 Introduction

2.2 Hardware requirements

2.3 Software requirements

3. ANALYSIS

3.1 Existing System

3.2 Proposed System

3.3 Feasibility study

3.4 Software specification

4. DESIGN

4.1 System Design

4.1.1 Introduction to UML

4.1.2 UML Diagrams of our project

5. SYSTEM IMPLEMENTATION
5.1 Introduction

5.2 Sample code

6. TESTING

6.1 Introduction

6.2 testing methods

7. SAMPLE SCREENSHOTS

8.CONCLUSION

9. BIBLOGRAPHY
 ABSTRACT

The purpose of the project entitled as “HOSPITAL MANAGEMENTSYSTEM” is to

computerize the Front Office Management of Hospital to develop software whichis user
friendlysimple, fast, and cost – effective. It deals with the collection of patient’s
information, diagnosis details, etc. Traditionally, it was done manually. The main function
of the system is register and store patient details and doctor details and retrieves these
details as and when required, and also to manipulate these details meaningfully System
input contains patient details, diagnosis details, while system output is to get these details
on to the screen. The Hospital Management System can be entered using a username and
password. It is accessible either by an administrator or receptionist. Only they can add data
into the database. The data can be retrieved easily. The data are well protected for personal
use and makes the data processing very fast.
 CHAPTER 1
INTRODUCTION

The project Hospital Management system includes registration of patients, storing their
details into the system. The software has the facility to give a unique id for every patient
and stores the details of every patient .

The Hospital Management System can be entered using a username and password. It is
accessible either by an administrator .Only they can add data into the database. The data
can be retrieved easily. The interface is very user-friendly. The data are well protected for
personal use and makes the data processing very fast.

Hospital Management System is powerful, flexible, and easy to use and is designed and
developed to deliver real conceivable benefits to hospitals.

Hospital Management System is designed for multispecialty hospitals, to cover a wide

range of hospital administration and management processes. It is an integrated end-to-end
Hospital Management System that provides relevant information across the hospital to
support effective decision making for patient care, hospital administration and critical
financial accounting, in a seamless flow.

Hospital Management System is a software product suite designed to improve the quality
and management of hospital management in the areas of clinical process analysis and
activity-based costing. Hospital Management System enables you to develop your
organization and improve its effectiveness and quality of work. Managing the key
processes efficiently is critical to the success of the hospital helps you manage your
processes
1.2 Problem Introduction:

Lack of immediate retrievals: -

The information is very difficult to retrieve and to find particular information like- E.g. -
To find out about the patient’s history, the user has to go through various registers. This
results in inconvenience and wastage of time.

Lack of immediate information storage: -

The information generated by various transactions takes time and efforts to be stored at
right place.

Lack of prompt updating: -

Various changes to information like patient details or immunization details of child are
difficult to make as paper work is involved.

Error prone manual calculation: -

Manual calculations are error prone and take a lot of time this may result in incorrect
information. For example calculation of patient’s bill based on various treatments.

Preparation of accurate and prompt reports: -

This becomes a difficult task as information is difficult to collect from various register.

Objective:-

1) Define hospital
2) Recording information about the Patients that come.
3) Generating bills.
4) Recording information related to diagnosis given to Patients.
5) Keeping record of the Immunization provided to children/patients.
 6) Keeping information about various diseases and medicines available to cure them.

These are the various jobs that need to be done in a Hospital by the operational staff
andDoctors. All these works are done on papers.

Scope of the Project:-

1) Information about Patients is done by just writing the Patients name, age and gender.
Whenever the Patient comes up his information is stored freshly.
2) Bills are generated by recording price for each facility provided to Patient on a
separate sheet and at last they all are summed up.
3) Diagnosis information to patients is generally recorded on the document, which
contains Patient information. It is destroyed after some time period to decrease the
paper load in the office.
4) Immunization records of children are maintained in pre-formatted sheets, which are
kept in a file.
5) Information about various diseases is not kept as any document. Doctors themselves
do this job by remembering various medicines.

1.3 MODULES:

Hospital Management System is web application for hospital which manages doctors and
patients. In this project, we use PHP and MySQL database.

The entire project mainly consists of 3 modules, which are

 Admin module
 User module (patient)
 Doctor module
1.3.1 Admin module:

1. Dashboard: In this section, admin can view the Patients, Doctors, Appointments
and New queries.
2. Doctors: In this section, admin can add doctor’s specialization and mange doctors
(Add/Update).
3. Users: In this section, admin can view users detail (who take online appointment)
and also have right to delete irrelevant user.
4. Patients: In this section, admin can view patient’s details.
5. Appointment History: In this section, admin can view appointment history.
6. Contact us Queries: In this section, admin can view queries which are send by
users.
7. Doctor Session Logs: In this section, admin can see login and logout time of doctor.
8. User Session Logs: In this section, admin can see login and logout time of user.
9. Reports: In this section, admin can view reports of patients in particular periods.
10.Pages: In this section, admin can update the about us and contact us page details.
11.Patient Search: In this section, admin can search patient with the help of patient
name and mobile number.

Admin can also change his/her own password.

1.3.2 Usermodule (patient):

1. Dashboard: In this section, patients can view the his/her profile, Appointments and
Book Appointment.
2. Book Appointment: In this section, Patient can book his/her appointment.
3. Appointment History: In this section, Patients can see his/her own appointment
history.
4. Medical History: In this section, Patients can see his/her own appointment history.

User can update his/her profile, change the password and recover the password.

1.3.3 Doctor module:

1. Dashboard: In this section, doctor can view his/her own profile and online
appointments.
2. Appointment History: In this section, Doctor can see patient’s appointment history.
3. Patients: In this section, doctor can manage patients (Add/Update).
4. Search: In this section, doctor can search patient with the help of patient name and
mobile number.

Doctor can also update his profile, change the password and recover the password.
 CHAPTER 2
REQUIREMENTSPECIFICATION
2.1 INTRODUCTION:

To be used efficiently, all computer software needs certain hardware components or the
other software resources to be present on a computer. These pre-requisites are known
as(computer) system requirements and are often used as a guideline as opposed to an
absolute rule. Most software defines two sets of system requirements: minimum and
recommended. With increasing demand for higher processing power and resources in
newer versions of software, system requirements tend to increase over time. Industry
analysts suggest that this trend plays a biggerpart in driving upgrades to existing computer
systems than technological advancements.

2.2 HARDWARE REQUIREMENTS:

The most common set of requirements defined by any operating system or software
application is the physical computer resources, also known as hardware. A hardware
requirements list is often accompanied by a hardware compatibility list (HCL), especially
in case of operating systems. An HCL lists tested, compatibility and sometimes
incompatible hardware devices for a particular operating system or application. The
following sub-sections discuss the various aspects of hardware requirements.
HARDWARE REQUIREMENTS FOR PRESENT PROJECT:

PROCESSOR Intel dual core,i3

RAM 1 GB
HARD DISK 80 GB

2.3 SOFTWARE REQUIREMENTS:

Software Requirements deal with defining software resource requirements and pre-
requisites that need to be installed on a computer to provide optimal functioning of an
application. These requirements or pre-requisites are generally not included in the software
installation package and need to be installed separately before the software is installed.

SOFTWARE REQUIREMENTS FOR PRESENT PROJECT:

OPERATING SYSTEM Windows 7/XP/8

FRONT END HTML,CSS,JavaScriptquery
SERVER SIDE SCRIPT PHP
DATABASE MySQL
 CHAPTER-3
ANALYSIS

3.1EXISTING SYSTEM:

Hospitals currently use a manual system for the management and maintenance of critical
information. The current system requires numerous paper forms, with data stores spread
throughout the hospital management infrastructure. Often information is incomplete or
does not follow management standards. Forms are often lost in transit between departments
requiring a comprehensive auditing process to ensure that no vital information is lost.
Multiple copies of the same information exist in the hospital and may lead to
inconsistencies in data in various data stores.

3.2 PROPOSED SYSTEM:

The Hospital Management System is designed for any hospital to replace their existing
manual paper based system. The new system is to control the information of patients.
Roomavailability,staff and operating room schedules and patient invoices. These services
are to be provided in an efficient, cost effective manner, with the goal of reducing the time
and resources currently required for such tasks .

3.3 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates.
Three key considerations involved in the feasibility analysis are:

3.3.1 Economic Feasibility

This study is carried out to check the economic impact will have on the system
will have on the organization. The amount of fund that the company can pour
into the research and development of the system is limited. The expenditures
must be justified. Thus the developed system as well within the budget and
this was achieved because most of the technologies used are freely available.
Only the customized products have to be purchased.

3.3.2 Technical Feasibility

This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high
demand on the available technical resources. This will lead to high demands
being placed on the client. The developed system must have a modest
requirement, as only minimal or null changes for the implementing this
system.

3.3.3 Operational Feasibility

The aspect of study is to check the level of acceptance of the system by

the user. This includes the process of training the user to use the system
efficiently. The user must not feel threatened by the system, instead must
accept it as a necessity.
3.4 SOFTWARE SPECIFICATION

HTML:

HTML or Hypertext Markup Language is the standard markup language used to

create web pages.

 HTML is written in the form of HTML elements consisting of tags enclosed

in angle brackets (like <html>).

 HTML tags most commonly come in pairs like <h1> and </h1>, although some
tags represent empty elements and so are unpaired,

 The purpose of a web browser is to read HTML documents and compose them into
visible or audible web pages.

 The browser does not display the HTML tags, but uses the tags to interpret the
content of the page. HTML describes the structure of a website semantically along
with cues for presentation, making it a markup language rather than
a programming language.

CASCADING STYLE SHEETS (CSS):

 It is a style sheet language used for describing the look and formatting of a
document written in a markup language.

 CSS is a cornerstone specification of the web and almost all web pages use CSS
style sheets to describe their presentation.

 CSS is designed primarily to enable the separation of document content from

document presentation, including elements such as the layout, colors, and fonts.
  This separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable multiple pages to
share formatting, and reduce complexity and repetition in the structural content .

MySQL:

 MySQL is developed, distributed, and supported by Oracle Corporation. MySQL is

a database system used on the web it runs on a server.
 MySQL is ideal for both small and large applications.
 It is very fast, reliable, and easy to use. It supports standard SQL. MySQL can be
compiled on a number of platforms.
 The data in MySQL is stored in tables. A table is a collection of related data, and it
consists of columns and rows.

JAVASCRIPT:

 JavaScript is the scripting language of the Web. All modern HTML pages are
using JavaScript.
 A scripting language is a lightweight programming language.JavaScript code can
be inserted into any HTML page, and it can be executed by all types of web
browsers. JavaScript is easy to learn.

 The purpose of the statements is to tell the browser what to do.

 This JavaScript statement tells the browser to write "Hello Dolly" inside an HTML
element with id="demo":
PHP:

 PHP is an acronym for "PHP Hypertext Preprocessor"

 PHP is a widely-used, open source scripting language
 PHP scripts are executed on the server
 PHP costs nothing, it is free to download and use

 PHP code are executed on the server, and the result is returned to the browser as
plain HTML
 PHP files have extension ".php"
 CHAPTER 4
DESIGN

4.1.1INTRODUCTION TO UML:

UML Design

The Unified Modeling Language (UML) is a standard language for specifying,

visualizing, constructing, and documenting the software system and its components.
It is a graphical language, which provides a vocabulary and set of semantics and
rules. The UML focuses on the conceptual and physical representation of the system.
It captures the decisions and understandings about systems that must be constructed.
It is used to understand, design, configure, maintain, and control information about
the systems.
The UML is a language for:

 Visualizing
 Specifying
 Constructing
 Documenting

Visualizing

Through UML we see or visualize an existing system and ultimately we visualize

how the system is going to be after implementation. Unless we think, we cannot
implement. UML helps to visualize, how the components of the system
communicate and interact with each other.

Specifying

Specifying means building, models that are precise, unambiguous and complete
UML addresses the specification of all the important analysis design,
implementation decisions that must be made in developing and deploying a software
system.

Constructing

UML models can be directly connected to a variety of programming language

through mapping a model from UML to a programming language like JAVA or C++
or VB. Forward Engineering and Reverse Engineering is possible through UML.

Documenting

The Deliverables of a project apart from coding are some Artifacts, which are
critical in controlling, measuring and communicating about a system during its
developing requirements, architecture, desire, source code, project plans, tests,
prototypes releasers, etc...
4.2 UML Approach

UML Diagram

A diagram is the graphical presentation of a set of elements, most often rendered

as a connected graph of vertices and arcs .you draw diagram to visualize a system
from different perspective, so a diagram is a projection into a system. For all but
most trivial systems, a diagram represents an elided view of the elements that
make up a system. The same element may appear in all diagrams, only a few
diagrams , or in no diagrams at all. In theory, a diagram may contain any
combination of things and relationships. In practice, however, a small number of
common combinations arise, which are consistent with the five most useful
views that comprise the architecture of a software-intensive system. For this
reason, the UML includes nine such diagrams:

1. Class diagram

2. Object diagram

3. Use case diagram

4. Sequence diagram

5. Collaboration diagram

6. State chart diagram

 7. Activity diagram

8. Component diagram

9. Deployment diagram

USE CASE DIAGRAM:

A use case diagram in the Unified Modeling Language(UML) is type of behavioral diagram
defined by and created from a use-case analysis. its purpose is to present a graphical
overview of the functionality provided by a system in terms of actors, their
goals(represented as use cases),and any dependencies between those use cases.

Use case diagrams are formally included in two modeling languages defined by
the OMG:theunfied modeling language(UML) and the systems modeling
language(sysML)
Use case diagram of our project:
Sign in
Use Case Diagram Admin

Dashboard

Manage Doctor
Specialization /
Doctors

View Users

View Patients

View Appointment
History

View Appointment
History

Manage Queries

Doctors /Users
Session Logs

Generate Reports

Doctors /Users
Session Logs

Patient Search
Doctor Use Case Diagram
Sign in

Dashboard

Manage
Appointment History

Manage Patient

(Add / Update)

Add patient
History

Search Patient

Update Own
Profile

Change Password

Password Recovery
Patient Use Case Diagram

Signup

Sign in

Dashboard

Book Appointment

Appointment History

View Medical
History

Update Own
Profile

Change Password

Password
Recovery
DATA FLOW DIAGRAMS

The DFD takes an input-process-output view of a system i.e. data objects flow into the
software, are transformed by processing elements, and resultant data objects flow out of
the software.

Data objects represented by labeled arrows and transformation are represented by circles
also called as bubbles. DFD is presented in a hierarchical fashion i.e., the first data flow
model represents the system as a whole. Subsequent DFD refine the context diagram
(level 0 DFD), providing increasing details with each subsequent level.

The DFD enables the software engineer to develop models of the information domain &
functional domain at the same time.

A context-level DFD for the system the primary external entities produce information for
use by the system and consume information generated by the system. The labeled arrow
represents data objects or object hierarchy.

RULES FOR DFD:

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions
 Reads left to right and top to bottom.
 Identify all inputs and outputs.
 Identify and label each process internal to the system with Rounded circles.
 A process is required for all the data transformation and Transfers. Therefore,
never connect a data store to a data Source or the destinations or another data
store with just a Data flow arrow.
 Do not indicate hardware and ignore control information.
 Make sure the names of the processes accurately convey everything the process
is done.
 There must not be unnamed process.
 Indicate external sources and destinations of the data, with Squares.
 Number each occurrence of repeated external entities.
 Identify all data flows for each process step, except simple Record retrievals.
 Label data flow on each arrow.
 Use details flow on each arrow.
 Use the details flow arrow to indicate data movements.
Class Diagram:

A Class is a category or group of things that has similar attributes and common behavior.

A Rectangle is the icon that represents the class it is divided into three areas. The upper

most area contains the name, the middle; area contains the attributes and the lowest areas
show the operations. Class diagrams provides the representation that developers work

from. Class diagrams help on the analysis side, too.

 ER Diagram

Deployment diagram:

A Deployment Diagram shows the configuration of run-time processing nodes and the
components that live on them. Deployment diagrams address the static deployment view
of architecture. They are related to component diagrams in that a node typically encloses
one or more components.

desktop Client
Printer

Hospital Local Server

Database Server

Statechart Diagrams:
The state diagram shows the states of an object and represents activities as arrows
connecting the states. The Activity Diagram highlights the activities. Each activity is
represented by a rounded rectangle-narrower and more oval-shaped than the state icon. An
arrow represents the transition from the one activity to the next. The activity diagram has
a starting point represented by filled-in circle, and an end point represented by bulls eye.
 Enter Hospital

Takes Appointment

Undergo Diagnosis

not cured
Takes Treatment

undergo labtests and buy medicines

gets cured
 DATABASE DESIGN

The data in the system has to be stored and retrieved from database. Designing the database
is part of system design. Data elements and data structures to be stored have been identified
at analysis stage. They are structured and put together to design the data storage and
retrieval system.

A database is a collection of interrelated data stored with minimum redundancy to serve

many users quickly and efficiently. The general objective is to make database access easy,
quick, inexpensive and flexible for the user. Relationships are established between the data
items and unnecessary data items are removed. Normalization is done to get an internal
consistency of data and to have minimum redundancy and maximum stability. This ensures
minimizing data storage required, minimizing chances of data inconsistencies and
optimizing for updates. The MySQL database has been chosen for developing the relevant
databases.

Hospital Management System (hms) contains 10 MySQL tables :

admin table Structure : This table store the login details of admin.

doctorspecilizationtable Structure : This table store the specializations of doctors.

doctorstable Structure : This table store the logins and personal details of doctors.

doctorslogtable Structure : This table store the doctor login and logout details.

userstable Structure : This table store the users login and personal details.
userlogtable Structure : This table store the users login and personal details.

appointmenttable Structure : This table store the users appointment details.

tblpatienttable Structure : This table store the patient details.

tblmedicalhistorytable Structure : This table store the patient medical history .

tblcontactustable Structure : This table store the contact us query details .

tblpage table Structure : This table store the about us and contact us details .
 CHAPTER 5
TESTING
5.1 INTRODUCTION TO SYSTEM TESTING:

The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub-assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the

Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.

TYPES OF TESTING:

Unit testing:
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches
and internal code flow should be validated. It is the testing of individual software units of
the application .it is done after the completion of an individual unit before integration. This
is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests
perform basic tests at component level and test a specific business process, application,
and/or system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined inputs
and expected results.
Integration testing:

Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the basic
outcome of screens or fields. Integration tests demonstrate that although the components
were individually satisfaction, as shown by successfully unit testing, the combination of
components is correct and consistent. Integration testing is specifically aimed at exposing
the problems that arise from the combination of components.

Functional test: Functional tests provide systematic demonstrations that functions tested
are available as specified by the business and technical requirements, system
documentation, and user manuals.
Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key functions,

or special test cases. In addition, systematic coverage pertaining to identify Business
process flows; data fields, predefined processes, and successive processes must be
considered for testing. Before functional testing is complete, additional tests are identified
and the effective value of current tests is determined.

System Test:
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing
is the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.

White Box Testing:

White Box Testing is a testing in which in which the software tester has knowledge of the
inner workings, structure and language of the software, or at least its purpose. It is purpose.
It is used to test areas that cannot be reached from a black box level.

Black Box Testing:

Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of
tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing in
which the software under test is treated, as a black box .you cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.
Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted
as two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.

Test objectives

 All field entries must work properly.

 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested

 Verify that the entries are of the correct format

 No duplicate entries should be allowed
 All links should take the user to the correct page.
Integration Testing:
Software integration testing is the incremental integration testing of two or more integrated
software components on a single platform to produce failures caused by interface defects.

The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company
level – interact without error.
Test Results:

All the test cases mentioned above passed successfully. No defects encountered.

Acceptance Testing:
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results:

All the test cases mentioned above passed successfully. No defects encountered.
 CHAPTER 6
SAMPLE SCREENSHOTS
Home Page
 Patient Panel

Signup Page

Login Page
Forgot Password

Reset Password
Dashboard

Profile
Change Password

Book Appointment
Appointment History

Doctor Panel

Login Page
Forgot Password

Reset Password
Dashboard

Profile
Change Password

Appointment History
Add Patient

Manage Patient
Update Patient Details

View Patient Details

Search Patient

Admin Panel

Login Page
Dashboard

Profile
Doctor Specializations

Update Specialization
Add Doctor

Manage Doctor
Update Doctor Details

Manage Users
Manage Patient

View Patient Details

Patient Appointment History

Manage Read Queries

View Queries Details

Doctor Session Log

User Session Log

Between Dates Report

Between Dates Report Details

About Us
Contact Us Page

Patient Search
 Chapter 8. CONCLUSION

Since we are entering details of the patients electronically in the” Hospital Management
System”, data will be secured. Using this application we can retrieve patient’s history with
a single click. Thus processing information will be faster. It guarantees accurate
maintenance of Patient details. It easily reduces the book keeping task and thus reduces the
human effort and increases accuracy speed.
 Chapter 9. BIBLOGRAPHY

1. PHP MySQL Website Programming: Problem - Design – Solution byChris

Lea, Mike Buzzard, DilipThomas ,Jessey White-Cinis
2. Beginning PHP5, Apache, and MySQL Web Development (Programmer to
Programmer) by Elizabeth Naramore
3. MySQL/PHP Database Applications, 2nd Edition by Brad Bulger
4. How to Do Everything with PHP and MySQL by VikramVaswani