Hospital AVNR

Hospital Management System
A
PROJECT REPORT
ON
“Hospital Management System”
SUBMITTED TO
MAHARAHSTRA STATE BORD OF TECHNICAL EDUCATION, MUMBAI
IN PARTIAL FULFILLMENT OF THE REQUIREMENTS
FOR THE AWARD
DIPLOMA IN
(INFORMATION TECHNOLOGY)
MAHARAHSTRA STATE BOARD OF TECHNICAL EDUCATION, MUMBAI
BY
Ms. Jagadale Akshata Anil (2008480221)

Ms. Tupe Vaishnavi Shambhudas (2008480225)
Ms. Navghane Rohini Rajaram (2008480228)
Ms. Giramkar Nikita Shivaji (2108480395)
Under the guidance of Prof. Prajakta P.Babar
DEPARTMENT OF INFORMATION TECHNOLOGY

ABHINAV EDUCATION SOCIETY’S
COLLEGE OF ENGINEERING & TECHNOLOGY (POLYTECHNIC), WADWADI (2022-23)
1
DEPARTMENT OF INFORMATION TECHNOLOGY

ABHINAV EDUCATION SOCIETY’
COLLEGE OF ENGINEERING& TECHNOLOGY (POLYTECHNIC),
WADWADI
CERTIFICATE
This is to certify that the dissertation report entitled
“HOSPITAL MANAGEMENT SYSTEM”
Submitted by
Ms. Jagadale Akshata Anil (2008480221)
Ms. Tupe Vaishnavi Shambhudas (2008480225)
Ms. Navghane Rohini Rajaram (2008480228)
Ms. Giramkar Nikita Shivaji (2108480395)
under the guidance of Ms.Prajakta P.Babar
Is a certify work carried out by him under the supervision of Prof. Prajakta P.Babar
and it is submitted towards the partial fulfillment of the requirement of Maharashtra
state board of technical education ,Mumbai for the award of the of Engineering
(Information technology)
Internal Guide External Examiner

Department of Information Department of Information
Technology Technology
Prof. A.A. Shivtare R.B.GIRI
2
Head of Information Technology ( PRINCIPAL)
INDEX
Content
ACKNOWLEDGEMENT……………………………..
1. Introduction
1.2 Existing system & need of the system
1.3 Scope of System
1.4 Operational Environment
1.5 Brief Description of Technology Used
2 Feasibility Study……………………………………
2.1 Economical feasibility
2.2 Operational Feasibility
2.3 Schedule Feasibility
2.4 Objectives of Proposed System
3. Users of System………………………………....
3.1 Admin Panel
3.2 Patients Accounts
3.3 Doctor panel
4.System Requirements (Functional and Non-Functional
requirements)…………………………………….
4.1 Functional requirements
4.2 Admin module
4.3 User module (patient)
4.4 Doctor module
3
4.5 Non-functional requirements
4.6 Entity Relationship Diagram (ERD)
4.7 Table Structures
4.8 Use Case Diagrams for (ADMIN, DOCTER, PATIENTS)
4.9 Class Diagram
4.10 Activity Diagram
4.11 Deployment Diagram
5. Sample Input and Output Screens……………………………….
6. Coding………………………………………………….
7. Test Strategy………………………………………………...
7.1 Test case
7.2 Integration testing
7.3 Validation testing
7.4 White box testing
7.5 Black box testing
7.6 System implementation
7.8 Acceptance Test Plan
8. REFERENCE…………………………………………….
9. CONCLUSION…………………………………………...
4
5
ACKNOWLEDGEMENT
We are happy to present this project after completing it successfully. This project
would not have been possible without the guidance, assistance and suggestions of
many individuals. We would like to express our deep sense of gratitude and
indebtedness to each and everyone who has helped us make this project a success.
We heartily Thank our Principal Prof. R B Giri Abhinav Education Society College
of Engineering And Technology for his constant encouragement and inspiration in
taking up this project. We heartly thank for our Head of Department and Project
Guide Prof. Prajakta P Babar, department of Information Technology Abhinav
Education Society College of Engineering And Technology for his constant
encouragement and inspiration in taking up this project And for his constant follow
up the advice throughout the course of the project work. Special thanks to all the
staff members of Information Technology Department for their help and kind co-
operation. The lastly we thanks our parents and friends for their encouragement and
support given to us in order to finish this precious work
Group Members
Jagadale Akshata Anil

Tupe Vaishnavi Shambhudas
Navghane Rohini Rajaram
Giramkar Nikita Shivaji
6
ABSTRACT
“ Hospital Management System”
Hospital Management System is an organized computerized system

designed and programmed to deal with day-to-day operations and
management of hospital activities. The program can look after inpatients,
outpatients, records, database treatments, status illness, billings in the
pharmacy, and labs. It also maintains hospital information such as ward id,
doctors in charge, and department administering. The major problem for
the patient nowadays is to get the report after consultation, many hospitals
managing reports in their system but it's not available to the patient when
he/she is outside. In this project, we are going to provide the extra facility
to store the report in the database and make it available from anywhere in
the world.
7
Introduction of project
 This project will automate the daily operations of LIFE LINE hospital. The
project keeps track of the staff and patient (in-patient, out-patient) details. It
also takes care of the ward, medical, invoice and the doctor’s appointment
details.
 The system generates the daily ward availability, the status of the operation
theatres and ICU.
 HOSPITAL MANAGEMENT is an integrated Hospital Information System,
which addresses all the major functional areas of multi-specialty hospitals. The
HOSPITAL MANAGEMENT enables better patient care, patient safety,
patient confidentiality, efficiency, reduced costs and better management
information system.
 It provides easy access to critical information thus enabling the management to
take better decisions on time.
 This project deals with processing of each and every department in the
hospital. This project sincerely aims to reduce the manual processing of each
department.
 The Scope of the project takes care of the details of each and every
department. These details gives the doctor, staffs, specialists and patient
details including their salary, attendance , doctor’s appointments and the
billing system.
 The details of Doctor and staff help the hospital to maintain the record of
every person.
 Their attendance details help them to know about their attentive presence
while salary is calculated.
8
 The billing system provides an efficient way for calculating bill details of the
patients.
1.3 Existing system & need of the system
 The existing systems provide the basic functionalities needed to be

handled in a hospital management environment. There is no
intelligence of the software in such cases.
 In the existing system all the patient details, doctor availability details
and regarding the tests done to the patients prescribed by the
doctor is maintained manually by the receptionist. If a patient
has to be admitted, we need to check the availability of the bed which
consumes lots of time if done manually. Also there is no proper search
technique to check the patient information.
9
1.4 Scope Of System
Information about Patients is done by just writing the Patients name, age
and gender. Whenever the Patient comes up his information is stored
freshly.
Bills are generated by recording price for each facility provided to
Patient on a separate sheet and at last they all are summed up.
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.
Immunization records of children are maintained in pre-formatted sheets,
which are kept in a file.
Information about various diseases is not kept as any document. Doctors
themselves do this job by remembering various medicines.
10
1.5 Operational Environments:
Hardware Requirements (Server side):
The System program uses the following hardware components.

Processor I3
RAM 4GB and above
Hard Disk 512 GB and above
Hardware Requirements (client side):

The System program uses the following hardware components.
Processor I3
RAM 1 GB and above
Hard Disk 250 GB and above
Software Requirements (Server side):-
Operating System Windows 10,7

Web Server XAMPP
Web Browser Google chrome,Microsoft edge
Software Requirements (client side): -
Operating System Windows 10,7

Web Server XAMPP
Web Browser Google chrome,Microsoft edge
11
1.5Brief Description of Technology Used :-
6.1.1Front End Details:
Front End tool is used for give a Graphical user interface to

system. By this we can make a system user friendly and more
capable. I have chosen PHP as
front-end tool. Because it is an Open-Source Technology, freely
available and more familiar with any type of database.
HTML (Hyper Text Markup Language)
Html is document layout and hyperlink specification language. it
defines the syntax and placement of special embedded directions
that are not displayed by the browser, but tell it to display the
content of the document include text, images and other supported
media. the HTML language also tells you how to make a
document interactive through special hypertext links which
connect your document with other documents on either your
computer or someone else as well as with other Internet
resources.
About PHP: -
PHP: Hypertext Pre-processor is a widely used, general-purpose scripting
language that was originally designed for web development to
produce dynamic web pages. For this purpose, PHP code is embedded
into the HTML source document and interpreted by a web server with a
PHP processor module, which generates the web page document. As a
general- purpose programming language, PHP code is processed by an
interpreter application in command-line mode performing desired
operating system operations and producing program output on its
standard output channel. It may also function as a graphical application.
PHP is available as a processor for most modern web servers and as
12
standalone interpreter on most operating systems
Feasibillity Study
While developing any computerized system it is necessary to examine

whether the developed computerized system is feasible in the point of view
operational, technical and financial.
Requirement analysis take place can be combined into a feasibility
analysis and a business proposal is put forth. With a very general plan for the
project and some cost estimates. For feasibility analysis, some understanding
of the major requirements of the system is essential.
The cases are categorized as follows:
1. Economical Feasibility
2. Technical Feasibility
3. Operational Feasibility
4. Schedule Feasibility
13
1.Economical feasibility
Economical feasibility study is the actual cost and benefit of the system. Actual
cost of the system is calculated in the economic study so as to inform the user
and management that this mush cost will be required to develop the system.
Because system cost is the first cost before starting system designing. The
organization is ready to invest on hardware and software required by the
proposed system. So system is economically feasible.
2.Technical Feasibility
Technical feasibility is the study of cost benefit analysis of the system and study
of the hardware and software requirements i.e. technical requirements of the
system in order to inform management and user for particular system designing
this much technical sources are required, in order to know user and management
view, regarding the technical resources. By studying the technical study the
actual cost the system designing is known. To know the total system cost. It
is essential for any management to know the actual expense of the system.
Organization can provide the minimum required as specified in
operational environment
14
1. Operational Feasibility
Training program will be required to the user. A group of user will

be trained during the training period. It focuses on the willingness and the
ability of the user. PES website does not require special efforts to educate
the staff on new way on conducting ways.
The system incorporates user friendly interface, default processing
and required validations. These all are done keeping in view the
individual with minimum computer knowledge.
2. Schedule Feasibility
The development work of the software was completed within

the specified time period there was no need for extra resources for the
development and hence the system economically feasible.
15
2.2 Objectives of Proposed System

 Define hospital.
 Recording information about the Patients that come.
 Generating bills.
 Recording information related to diagnosis given to Patients.
 Keeping record of the Immunization provided to children/patients.
 Keeping information about various diseases and medicines

available to cure them.
 To develop the system that enables efficient management
 Providing facility to admin to create the multiple patients.
 To add the list of Doctors
 To reduce time consumption.
 To provide more security for data
 To provide more security for login based on their role
 To approve the report of every Doctor and Patient at admin side.
 Providing facility to admin to check every report at any time.
These are the various jobs that need to be done in a Hospital by the
operational staff and Doctors.
16
2.3 Users of System:
 Admin Panel
 Patients Account
 Doctor Panel
Admin Panel
 On the other hand, the admin has full control over the system. He/she can view
all the existing records of the hospital.
 An admin can manage patients, doctors, their departments, treatment types,
and medical records. An admin has the right to register a doctor’s account.
 For this, the admin has to set the doctor’s account under various hospital
departments too. The admin can view all the appointment records too. Also,
the admin has to maintain billing records for each patient’s treatment.
 In order to maintain the payment of each patient, the user has to enter the
discount amount and the reason for it. After the payment, the patient can view
all the reports from their own personal accounts.
17
Patient’s Account
 After making an appointment for the very first time, the user can log in to the
system and check their appointment status. By default, each appointment is set
to pending status.
 Which later, the doctor should approve or reject it in order to start their
treatment process. Also, the patient can remove their appointments anytime.
 From a patient’s panel, he/she can update their profile, view treatment records,
and prescription records.
 Under the treatment section, a patient can view all the records such as
treatment type, doctor’s name, date, and total charge. Similarly, the
prescription section displays the date, name, and quantity of the medicines
with the total bill charge.
18
Doctor’s Panel
 Each doctor will have their own personal account which lets them access the
system. Here, the doctor can view all the pending appointments.
 Each appointment has options that allow the doctor to approve or reject them.
After approving the appointment, the doctor can view the patient’s profile and
appointment record.
 For the rest, the doctor has to maintain each by filling up their treatments. In
order to set a treatment record, the user has to select a treatment type,
description, date, and upload treatment files.
 After the completion of treatment records, the doctor can now proceed towards
the prescription section.
 For the prescription, the doctor has to select available medicine, date, and
enter quantity and dosage.
 After the submission of the prescription record, the system generates the total
bill for the patient.
19
3.1 System Requirements (Functional and Non-Functional

requirements)
3.1.1 Functional requirements

The entire project mainly consists of 3 modules, which are
 Admin module
 User module (patient)
 Doctor module
Admin module:
 Signup their account. Then Login (No approval Required).

 Can register/view/approve/reject/delete doctor (approve those doctor who
applied for job in their hospital).
 Can admit/view/approve/reject/discharge patient (discharge patient when
treatment is done).
 Can Generate/Download Invoice pdf (Generate Invoice according to medicine
cost, room charge, doctor charge and other charge).
 Can view/book/approve Appointment (approve those appointments which is
requested by patient).
User module (patient):

 Create account for admit in hospital. Then Login (Approval required by
hospital admin, Then only patient can login).
20
 Can view assigned doctor's details like ( specialization, mobile, address).

 Can view their booked appointment status (pending/confirmed by admin).
 Can book appointments.(approval required by admin)
 Can view/download Invoice pdf (Only when that patient is discharged by
admin).
Doctor module:
 Apply for job in hospital. Then Login (Approval required by hospital admin,
Then only doctor can login).
 Can only view their patient details (symptoms, name, mobile ) assigned to that
doctor by admin.
 Can view their discharged(by admin) patient list.
 Can view their Appointments, booked by admin.
 Can delete their Appointment, when doctor attended their appointment.
3.1.2 Non functional requirement/s

21
The development of this new system contains all of the above

functional requirements along with following activities:
 Fast Performance and high accuracy.
 Reliability and flexibility.
 The system is Doctor & Patient friendly and self-explanatory.
 The system is available 100% for the Doctors & Patients and is
used 24 hours a day and 365 days a year. The system shall be
operational 24 hours a day and 7 days a week.
22
3.2 Entity Relationship Diagram (ERD)
23
3.3 Table Structures:
TABLE NAME : Admin
Sr. Data type Data

Field Name Constraints
No Size
1. Positive Integer 10
Admin Id Not Null
2. Char Field 40
Admin Name Not Null
3. Char Field 40
Address Not Null
4. Char Field 40
Phone No Not Null
5. Char Field 40
Password Not Null
TABLE NAME : DOCTER
Sr. Data type Data

No Size
1. Positive Integer 10
Doctor Id Not Null
2. Char Field 40
Doctor Name Not Null
3. Char Field 40
Address Not Null
4. Char Field 40
Phone No Not Null
5. Char Field 40
Department Not Null
6. Char Field 40
Education Not Null
7. Char Field 40
Profile Not Null
8. Char Field 40
Experience Not Null
9. Char Field 40
Consultancy Not Null
Charges
10. Char Field 40
Password Not Null
11. Char Field 30
Status Not Null
24
TABLE NAME : PATIENTS
Sr. Data type Data

No Size
1. Patient Id Positive Integer - Not Null
Field
2. Patient Name Char Field 40 Not Null
3. Address Char Field 40 Not Null
4. Mobile No Char Field 20 Not Null
5. Pin Code Char Field 10 Not Null
6. Date Of Birth Date Field 40 Not Null
7. Gender Char Field 40 Not Null
8. Blood Group Char Field 40 Not Null
9. Admit date Date field - Not Null
10. Symptoms Char Field 40 Not Null
11. Status Char Field 40 Not Null
TABLE NAME: APPOINTMENT

Sr. Data type Data
No Size
1. Positive integer - Not Null
Appointment Field
Id
2. Char Field 40 Not Null
Appointment
Type
3. Patient Id Positive integer - Not Null
Field
4. Doctor Id Positive integer - Not Null
Field
5. Department Id Char Field 40 Not Null
6. Appointment Char Field 40 Not Null
Time
7. Appointment Date Field - Not Null
Date
8. Description Text Field 500 Not Null
9. Status Boolean Field - Not Null
TABLE NAME: Laboratory

25
Sr. Data type Data

No Size
1. Lab Id Positive integer - Not Null
Field
2. Category Char Field 40 Not Null
3. Patient Name Char Field 40 Not Null

4. Doctor Name Char Field 40 Not Null
5. Date Date Field - Not Null
6. Report Positive integer 20 Not Null

Field
7. Status Char Field 20 Not Null
8. Hospital_Id Positive integer 20 Not Null
Field
TABLE NAME: Laboratories
Sr. Data type Data

No Size
1. Laboratorist Id Positive integer - Not Null
Field
2. Name Char Field 40 Not Null
3. Email Char Field 40 Not Null

4. Adderss Char Field 40 Not Null
5. Phone No Date Field - Not Null

Field
TABLE NAME: Medicine

26
Sr. Data type Data

No Size
1. Medicine Id Positive integer - Not Null
Field
3. Category Char Field 40 Not Null
4. Price Char Field 40 Not Null
5. Quantity Date Field - Not Null
6. Company Positive integer 20 Not Null

Field
7. Expiry Date Char Field 20 Not Null
TABLE NAME: Department
Sr. Data type Data

No Size
1. Department Id Positive integer - Not Null
Field
3. Description Char Field 40 Not Null

Field
TABLE NAME: Pharmacist
Sr. Data type Data

No Size
1. Pharmacist Id Positive - Not Null
integer
Field
2. Pharmacist Name Char Field 40 Not Null

4. Phone No Char Field 40 Not Null
6. Hospital_Id Positive 20 Not Null
integer
Field
TABLE NAME: Receptionits
27
Sr. Data type Data

No Size
1. Receptionist Id Positive integer - Not Null
Field
2. Receptionist Name Char Field 40 Not Null
4. Phone No Char Field 40 Not Null
Field
3.4 Use Case Diagrams for (ADMIN, DOCTER, PATIENTS)
28
29
3.5 Class Diagram
30
3.6 Activity Diagram
31
3.7 Deployment Diagram
32
3.8 Sample Input and Output Screens

Home Page :-
33
Admin Login :-
Admin Dashboard : -
34
Docter Login :-
Docter Dashboard:-
35
Patients Login :-
Patients Dashboard :-
36
Patients Report panel :-
37
Appointment:-
Appointment Successfully Insert :-
38
Appointment Dashboard :-
39
4.1 CODE SNIPPETS :
<?php include 'header.php';?>


<section class="main-banner">
<div class="tp-banner-container">
<div class="tp-banner">
<ul>


<li data-transition="random" data-slotamount="7" data-masterspeed="300" data-
saveperformance="off" >

<img src="images/hms.jpg" alt="slider" data-bgposition=" center center" data-
bgfit="cover" data-bgrepeat="no-repeat">


<div class="tp-caption sfl tp-resizeme"
data-x="center" data-hoffset="0"
data-y="center" data-voffset="-120"
data-speed="800"
data-start="800"
data-easing="Power3.easeInOut"
data-splitin="chars"
data-splitout="none"
data-elementdelay="0.03"
data-endelementdelay="0.4"
data-endspeed="300"
style="z-index: 5; font-size:50px; font-weight:500; color:black; max-width: auto;
max-height: auto; white-space: nowrap;">Hospital Management System</div>


<div class="tp-caption sfr tp-resizeme"
data-speed="800"
data-start="1000"
40
data-endspeed="300"
style="z-index: 6; font-size:40px; color:gray; font-weight:500; white-space:
nowrap;">We care about your health </div>


<div class="tp-caption sfb tp-resizeme"
data-y="center" data-voffset="0"
data-speed="800"
data-start="1200"
data-splitin="none"
data-endspeed="300"
style="z-index: 7; font-size:22px; color:gray; font-weight:500; max-width: auto;
max-height: auto; white-space: nowrap;">Best Hospitality Services in your town</div>


<div class="tp-caption lfb tp-resizeme scroll"
data-speed="800"
data-start="1300"
data-endspeed="300"
data-scrolloffset="0"
style="z-index: 8;"><a href="#." class="btn">Book Now</a> </div>
</li>



<img src="images/hms2.jpg" alt="slider" data-bgposition="center center" data-


<div class="tp-caption sfl tp-resizeme"
data-x="left" data-hoffset="400"
data-speed="800"
41
data-start="800"
data-endspeed="300"
style="z-index: 5; font-size:40px; font-weight:500; color:#000; max-width: auto;
max-height: auto; white-space: nowrap;">Best Diagnostic Centre </div>


<div class="tp-caption sfr tp-resizeme"
data-speed="800"
data-start="800"
data-endspeed="300"
style="z-index: 5; font-size:55px; font-weight:500; color:#000; max-width: auto;
max-height: auto; white-space: nowrap;">Care And Cure</div>


data-speed="800"
data-start="1400"
data-splitin="none"
data-endspeed="300"
style="z-index: 7; font-size:16px; color:#000; font-weight:500; line-height:26px;
max-width: auto; max-height: auto; white-space: nowrap;">Improved diagnostic
performance and heightened satisfaction of patients <br> and physicians delight.</div>


<div class="tp-caption lfb tp-resizeme scroll"
data-speed="800"
data-start="1600"
42
data-endspeed="300"
style="z-index: 8;"><a href="#." class="btn">CONTACT NOW</a> </div>
</li>



<img src="images/hms3.jpg" alt="slider" data-bgposition="center center" data-


data-speed="800"
data-start="800"
data-endspeed="300"
style="z-index: 6; font-size:40px; color:#000; font-weight:500; white-space:
nowrap;"> Welcome To Our Research Center </div>


<div class="tp-caption sfb tp-resizeme text-center"
data-speed="800"
data-start="1000"
data-endspeed="300"
style="z-index: 7; font-size:20px; font-weight:500; line-height:26px; color:#000;
max-width: auto; max-height: auto; white-space: nowrap;">We work in a friendly and
efficient using the latest <br>
technologies and sharing our expertise.</div>
</li>
</ul>
</div>
43
</div>
</section>


<div id="content">


<section class="p-t-b-150">
<div class="container">
<div class="intro-main">
<div class="row">


<div class="col-md-8">
<div class="text-sec">
<h5>Health Check Ups</h5>
<p>Besides providing world class clinical lab services, Labaid Diagnostic Centre
houses a pool of doctors of different medical specialty to serve the ailing patients as
outpatients. They are all reputed and respected in their medical specialty for outstanding
clinical management</p>
<ul class="row">
<li class="col-sm-6">
<h6> <i class="lnr lnr-checkmark-circle"></i> EMERGENCY CASE</h6>
<p>Excepteur sint occaecat cupidatat non roident,
sunt in culpa qui officia deserunt mollit </p>
</li>
<h6> <i class="lnr lnr-checkmark-circle"></i> QUALIFIED DOCTORS</h6>
</li>
<h6> <i class="lnr lnr-checkmark-circle"></i> ONLINE APPOINTMENT</h6>
</li>
<h6> <i class="lnr lnr-checkmark-circle"></i> FREE MEDICAL
COUNSELING</h6>
</li>
</ul>
</div>
</div>


44
<div class="timing"> <i class="lnr lnr-clock"></i>

<ul>
<li> Monday <span>8.00 - 16.00</span></li>
<li> Tuesday <span>8.00 - 16.00</span></li>
<li> Wednesday <span>8.00 - 16.00</span></li>
<li> Thursday <span>8.00 - 16.00</span></li>
<li> Friday <span>8.00 - 16.00</span></li>
<li> Saturday <span>8.00 - 16.00</span></li>
<li> Sunday <span>8.00 - 16.00</span></li>
</ul>
</div>
</div>
</div>
</div>
</div>
</section>


<section class="p-t-b-150">
<div class="container">


<div class="heading-block">
<h2>Our Services</h2>
<hr>
<span>Duis autem vel eum iriure dolor in hendrerit n vuew lputate velit esse molestie
conseu vel illum dolore eufe ugiat nulla facilisis at vero.</span> </div>


<div class="services">
<div class="row">


<article>
<div class="media-left"> <i class="flaticon-eye-2 icon"></i> </div>
<div class="media-body">
<h6>Eye Specialist</h6>
<p>Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia
deserunt mollit random text.</p>
</div>
</article>
</div>


45
<article>
<div class="media-left"> <i class="flaticon-operating-room icon"></i> </div>
<h6>Operation Theater</h6>
</div>
</article>
</div>


<article>
<div class="media-left"> <i class="flaticon-icu-monitor icon"></i> </div>
<h6>ICU Department</h6>
</div>
</article>
</div>


<article>
<div class="media-left"> <i class="flaticon-doctor icon"></i> </div>
<h6>Qualified Doctors</h6>
</div>
</article>
</div>


<article>
<div class="media-left"> <i class="flaticon-heartbeat icon"></i> </div>
<h6>Heart Problems</h6>
</div>
</article>
</div>


46
<article>
<div class="media-left"> <i class="flaticon-stomach-2 icon"></i> </div>
<h6>Stomach Problems</h6>
</div>
</article>
</div>
</div>
</div>
</div>
</section>
</div>


<?php include 'footer.php';?>
5.1 Test Strategy:

 System Testing is an important stage in any system development life cycle.
47
 Testing is a process of executing a program with the intention of finding

errors.
 The importance of software testing and its implications with respect to

software quality cannot be overemphasized.
 Software testing is a critical element of software quality assurance and

represents the ultimate review of specification, design and coding. A good test
case is one that has a high probability of finding a yet undiscovered error.
 Testing is the set of activities that can be planned in advance and conducted
systematically.
 Different test conditions should be thoroughly checked and the bugs detected
should be fixed. The testing strategies formed by the user are performed to
prove that the software is free and clear from errors.
 To do this, there are many ways of testing the system’s reliability,

completeness
and maintainability.
48
5.2 Unit Test Plan :
 In the unit testing the analyst tests the program making up a system. The
software units in a system are the modules and routines that are assembled
and integrated to perform a specific function.
 In a large system, many modules on different levels are needed. Unit testing
can be performed from the bottom up starting with the smallest and lowest
level modules and proceeding one at a time. For each module in a bottom-up
testing, a short program executes the module and provides the needed data.
Integration Testing:
 Integration testing is a systematic technique for constructing the program

structure while conducting test to uncover errors associate with interfacing.
 Objectives are used to take unit test modules and built program structure that
has been directed by design.
 The integration testing is performed for this Hospital Management System

when all the modules where to make it a complete system. After integration
the project works successfully.
Validation Testing:
 Validation testing can be defined in many ways, but a simple definition is that
can be reasonably expected by the customer. After validation test has been
conducted, one of two possible conditions exists.
49
 The functions or performance characteristics confirm to specification and are

accepted. A deviation from specification is uncovered and a deficiency list is
created.
 Proposed system under consideration has been tested by using validation

testing and found to be working satisfactorily.
 For example, in this project validation testing is performed against inpatient

search module. This module is tested with the following valid and invalid
inputs for the field patient name.
White Box Testing:
 White box testing, sometimes called glass-box testing is a test case design
method that uses the control structure of the procedural design to derive test
cases. Using white box testing methods, the software engineer can derive test
cases that
· Guarantee that all independent paths with in a module have been
exercised at least once.
· Exercise all logical decisions on their true and false sides.
· Execute all loops at their boundaries and with in their operational bounds
and
· Exercise internal data structure to assure their validity.
 For example in this project white box testing is performed against inpatient
module. Without entering text if we apply it displays the message “First add
record then save it” else it should be saved.
Black Box Testing
50
 This method treats the coded module as a black box. The module runs with
inputs that are likely to cause errors. Then the output is checked to see if any
error occurred.
 This method cannot be used to test all errors, because some errors may depend
on the code or algorithm used to implement the module.
System Implementation
 Implementation is the process of having system personal check out and

provides new equipments into use, train the users to install a new application
and construct any files of data needed to use it.
 There are three types of implementation
1. Implementation of computer system to replace a manual system.

The problems encountered are covering files, training users, creating accurate files
and verifying print outs for integrity
2. Implementation of a new computer system to replace an existing one.

This is usually difficult conversion. If not properly planned, there can be many
problems. So large computer systems may take as long as a year to convert.
3. Implementation of a modified application to replace the existing one

using the same
Computer. This type of conversion is relatively easy to handle, usually there are no
major changes in the file.
51
5.3 Acceptance Test Plan :

Once the Hospital system is ready for implementation, it needs to test using
user acceptance testing. The purpose of this test is to confirm that the system is
developed according to the specified user requirements and is ready for operational
use. Alpha and Beta testing types will be used at developer site and customer’s site
respectively.
Acceptance testing is preformatted using real data of the client to demonstrate that
software.
working satisfactory. Testing lane focuses in the external behavior by the system
Intense the fanatical testing is performance at this level.
52
5.4 TEST CASE :
Test Case For Admin Login
Test Test Case Purpose Steps Expected Actual Pass /

Case Id name Result Result Fail
Hms01 Username To validate 1]Enter valid Usernames in Message pops- Message pops- pass
username textbox up up
Field 2] Enter valid Password in ‘Successfully ‘Successfully
textbox
Login’ Login’
3] Click on LOGIN Button
To 1] Enter Username with
Hms02 Username invalidate blank spaces Message Message Fail
username 2]Enter Correct Password pops- up’ pops- up"
field 3]Enter on LOGIN button. Invalid Invalid
Username’ Username"
1] Enter correct Username Message Message pops-

To validate
Hms03 Password 2]Enter correct password pops- up" up" pass
Password 3]Click on OK button Successfully Successfully
field
login" login"
1] Enter correct Username
2] Enter Wrong password Message Message pops-
To
Hms04 Password 3]Click on OK button pops- up’ up’ Invalid Fail
Invalidate
Invalid password’
Password
password’
field
Hms05 Login Form To 2]Enter correct password pops- up" up" pass
validate 3]Click on OK button Successfully Successfully
Login login" login"
form
1] Enter incorrect Username Message Message pops-

Hms06 Login Form To 2]Enter correct password pops- up" up" fail
invalidate 3]Click on OK button Invalid Successfully
Login username" login"
form
Hms07 Login Form To 2]Enter incorrect password pops- up" up" invalid pass
invalidate 3]Click on OK button invalid password"
Login password"
form
1] Enter incorrect Username Message pops- Message pops-
Hms08 Login Form To 2]Enter incorrect password up" invalid up" invalid pass
invalidate 3]Click on OK button username & username and
Login password" password"
form
53
 Only the permanent and registered Admin, Doctor, Patients can access the
system.
 System works in all platforms and its compatible environments.
 Advanced techniques are not used to check the authorization
It is not possible to develop a system that makes all the requirements of the user.
User requirements keep changing as the system is being used. Some of the future
enhancements that can be done to this system are:
 As the technology emerges, it is possible to upgrade the system and can be
adaptable to desired environment.
 Because it is based on object-oriented design, any further changes can be
easily adaptable.
 Based on the future security issues, security can be improved using emerging
technologies.
 Backup Plug in should be added.
 Working on the project was an excellent experience. It helped us to understand
the importance of planning, designing and implementation so far we have
learnt in our theory books. It helped us unleashing our creativity while
working in a team. It also realized the importance of team working,
communication as a part of this project.
 The project was successfully completed after a lot of efforts and work hours.
This project underwent number of compiling, debugging, removing errors,
making it bug free, adding more facilities in Hospital Management System and
interactivity making it more reliable and useful.
54
 This project focused that scheduling a project and adhering to that schedule
creates a hard sense of time- management. It has also let us known that co-
operative teamwork always produce effective results.
 The entire project has been developed and deployed as per the requirements
stated by
the user. It is found to be bug free as per the testing standards that are
implemented.
 There are also few features which can be integrated with this system to make it
more flexible. Below list shows the future points to be consider :
• Getting the current status of patient.
• Including a different module for pharmacy, LAB, Bed Allotment and more
• Including a Frequently Asked Questions Section.
 Finally, we like to conclude that we put all our efforts throughout the
development of our project and tried to fulfill most of the requirements of the
user.
55
This user manual is meant to be used by the all user using the system, with
prior training session from the Development unit, plus he/she has to be skillful
enough in operating the intended system. This manual is used for the benefit of
the intended user to make it more understandable along with functioning of the
system, the processes and the precautions that must be followed during working
with the system. It also tells the user how to use various functionality of the
system as various college are being provided according to the type of user,
whenever user logs into the system. This System is very easy to operate to those
who have the Fundamental knowledge of computer operations & little bit of the
help of this user manual. The appropriate error message & supporting help
makes this online web application easy to handle. Now, in order to get a better
understanding of the system various user interfaces along-with directions are
also provided in the user-interface designs.
User manual for Admin:
 Signup their account. Then Login (No approval Required).

 Can register/view/approve/reject/delete doctor (approve those doctor who
applied for job in their hospital).
 Can admit/view/approve/reject/discharge patient (discharge patient when
treatment is done).
 Can Generate/Download Invoice pdf (Generate Invoice according to medicine
cost, room charge, doctor charge and other charge).
 Can view/book/approve Appointment (approve those appointments which is
requested by patient).
56
User manual for User:
 Create account for admit in hospital. Then Login (Approval required by

hospital admin, Then only patient can login).
 Can view assigned doctor's details like (specialization, mobile, address).
 Can view their booked appointment status (pending/confirmed by admin).
 Can book appointments.(approval required by admin)
 Can view/download Invoice pdf (Only when that patient is discharged by
admin).
User manual for Doctor:
 Apply for job in hospital. Then Login (Approval required by hospital admin,
Then only doctor can login).
 Can only view their patient details (symptoms, name, mobile) assigned to that
doctor by admin.
 Can view their discharged (by admin) patient list.
 Can view their Appointments, booked by admin.
 Can delete their Appointment, when doctor attended their appointment.
57
Click Here
ClickFor Log
In
58
Admin Log In
Patient LogIn
Doctor Log In
Type Admin
Username and
Password
Admin Dashboard
59
REFERENCES:

 https://www.geeksforgeeks.org/top-6-best-books-to-learn-
php/
 https://www.guru99.com/best-php-books.html
 https://www.tutorialspoint.com/php/index.html
 https://www.tutorialspoint.com/sql/index.html
BOOKS:-
 PHP & MySQL Novice to ninja - by Kevin Yank
 PHP : A beginner’s Guide – by vikram vaswani
60
CONCLUSION:
Hospital management system is all about the modernizing a hospital through use of
technology. Computers helps in it and take over the manual system for quick and
easy functioning. This hospital management system is a quite the reliable and is
proven on many stages. All the basic requirements of the hospital are provided in the
hospital in order to manage it perfectly and large amount of data can also be stored.
It gives many facilities like searching for the detail of patient. Billing facilities as
well as the creation of test reports. So it is important system for modern days.
61

Hospital AVNR

Uploaded by

Copyright:

Available Formats

Hospital AVNR

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hospital AVNR

Uploaded by

Copyright:

Available Formats

Hospital Management System

“Hospital Management System”

Ms. Jagadale Akshata Anil (2008480221)

Under the guidance of Prof. Prajakta P.Babar

DEPARTMENT OF INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

Internal Guide External Examiner

Prof. A.A. Shivtare R.B.GIRI

Head of Information Technology ( PRINCIPAL)

4.1 Functional requirements

4.2 Admin module

4.3 User module (patient)

4.4 Doctor module

4.5 Non-functional requirements

4.6 Entity Relationship Diagram (ERD)

4.7 Table Structures

4.8 Use Case Diagrams for (ADMIN, DOCTER, PATIENTS)

4.9 Class Diagram

4.10 Activity Diagram

4.11 Deployment Diagram

5. Sample Input and Output Screens……………………………….

7.2 Integration testing

7.3 Validation testing

7.4 White box testing

7.5 Black box testing

7.6 System implementation

7.8 Acceptance Test Plan

Jagadale Akshata Anil

“ Hospital Management System”

Hospital Management System is an organized computerized system

1.3 Existing system & need of the system

 The existing systems provide the basic functionalities needed to be

1.4 Scope Of System

1.5 Operational Environments:

Hardware Requirements (Server side):

The System program uses the following hardware components.

Hardware Requirements (client side):

Software Requirements (Server side):-

Operating System Windows 10,7

Software Requirements (client side): -

Operating System Windows 10,7

1.5Brief Description of Technology Used :-

6.1.1Front End Details:

Front End tool is used for give a Graphical user interface to

standalone interpreter on most operating systems

While developing any computerized system it is necessary to examine

Training program will be required to the user. A group of user will

The development work of the software was completed within

2.2 Objectives of Proposed System

 Recording information about the Patients that come.

 Recording information related to diagnosis given to Patients.

 Keeping record of the Immunization provided to children/patients.

 Keeping information about various diseases and medicines

 Providing facility to admin to create the multiple patients.

 To add the list of Doctors

 To reduce time consumption.

 To provide more security for data

 To provide more security for login based on their role

 To approve the report of every Doctor and Patient at admin side.