A Project Report

On
Online Hospital Appointment System

Submitted in partial fulfilment of the requirements for the award of degree of

Bachelor of Business Administration (Computer Application)

Submitted By:

A91) Utkarsh Umesh Jadhav

A84) Sahil Sanjay Ushinkar

Submitted to:

Shree Chanakya Education Society

Indira College of Commerce and Science, Pune

Vice Principal & (H.O.D) Guided By

Dr. Shivendu Bhushan Prof.Shubhangi Chavan
 Acknowledgement

We would like to express our sincere and heartfelt gratitude to our institution” Indira
College of Commerce and Science” which provided us with excellent opportunity to achieve our
most cherished goal in life to become bachelor’s degree in BBA-CA.

We are extremely grateful to our respected Vice Principal and HOD Dr.Shivendu
Bhushan for providing excellent academic environment which has made this endeavor possible.

We take this opportunity to express our deep sense of gratitude to our guide Prof.
Shubhangi Chavan for their resplendent idea and constant encouragement in making this project
unmitigated success. Their thoughtfulness and understanding were vast and thoroughly helpful in
successful completion of project. Our sincere thanks to all our faculties and non-teaching staff
for them at most co-operation.

Finally, we proudly thank our parents and friends for their constant support and priceless
guidance in throughout this endeavor.

A91 Utkarsh Jadhav

A84 Sahil Ushinkar

 Index

Sr. No Particulars Page No.

1 Abstract 1
2 Introduction 2-8
2.1 Motivation 2
2.2 Problem statement 3
2.3 Purpose/Objectives/goals 3
2.4 Literature survey 4
2.5 Project Scope and Limitations 5
3 System Analysis 6-10
3.1 Existing System 6
3.2 Scope and Limitation of existing system 7
3.3 Project perspective, features, stakeholders 8
3.4 Requirement Analysis 9
3.4.1 Functional Analysis 10
3.4.2 Performance Analysis 10
3.4.3 Security Analysis 10
4 System Design 11
4.1 Design constraints 12
4.2 System Model 13
4.2.1 Data Flow Diagram 13-15
4.2.2 Data Model 16-23
File Design Normalization 24-28
Data Dictionary 29-33
4.3 User Interface 34-50
5 Implementation Details 51
5.1 Software and hardware specifications 51
6 Output and Report Testing 51-53
6.1 Test Plan 51
6.2 Black Box Testing/Data validations Test cases 52

6.3 White Box Testing/functional validations Test 52-54

cases and results
7 Conclusion and Recommendation 54-56
8 Future Scope 57
9 Bibliography and References 57-58
Abstract:
The purpose of Online Hospital Management System is to automate the existing
manual system by the help of computerized equipment and full-fledged computer software,
fulfilling their requirements, so that their valuable data/information can be stored for a longer
period with easy accessing and manipulation of the same. The required software and hardware
are easily available and easy to work with.

Online Hospital Management System, as described above, can lead to error free,
secure, reliable and fast management system. It can assist the user to concentrate on their other
activities rather to concentrate on the record keeping. Thus, it will help organization in better
utilization of resources. The organization can maintain computerized records without redundant
entries. That means that one need not be distracted by information that is not relevant, while
being able to reach the information.

The aim is to automate its existing manual system by the help of computerized
equipment and full-fledged computer software, fulfilling their requirements, so that their
valuable data/information can be stored for a longer period with easy accessing and manipulation
of the same. Basically, the project describes how to manage for good performance and better
services for the clients.

1
2) Introduction:

Online Hospital Management System is developed on PHP, MySQL Server. The main aim for
this project is to simplify the medical workforce planning and facilitate hospital inventory
Management .the 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 database. The data can be
retrieved easily. The interface is very user-friendly,the data are well protected for personal use
and make the data processing very fast.
The application is reduced as much as possible to avoid errors while entering the data. It also
provides error message while entering invalid data. No formal knowledge is needed for the user
to use this system. Thus, by all this it proves it is user-friendly. It can assist the user to
concentrate on their other activities rather to concentrate on the record keeping. This is used to
assist in strategic planning and will help you ensure that it is equipped with the right level of
information. Also. For those busy executive who are always on the go, our systems come with
remote access features, which will allow you to manage your workforce anytime, at all times.
This system will ultimately allow you to better manage resources.
2.1) Motivation:

The real motivation for the hospital management system project is to make easy process of all
The management process like doctor’s appointment, patient registration ,services details, etc.
We always see that to find out the patients history, the user has to go through various
registers.This results in wastage of time. The interface is very user-friendly,the data are well
protected for personal use and make the data processing very fast. The system reduces lot of
paperwork and helps in arranging all the hospital related, patient related details in organized way.

2
2.2 Problem Statement:

2.3 Purpose/Objectives/Goals:

The main objective of the Hospital Management System is to provide the searching Facilities
based on various factors and to increase efficiency of managing the hospital.The Hospital
Management System is useful to improve the management of hospital in the area of clinical
process analysis and activity-based costing and also improve effectiveness and quality of work

The project is built at administrative end and thus only the administrator is guaranteed the
access and modify the database. editing ,adding and updating of records is improved which
results in proper resource management of hospital data.Provide the timely access to requesting
information and to update information is the primary objective of the system.

2.4 Literature Survey:

An organizational structure is defined by the ways in which work can be divided into, and the
coordination of activities performed by the people who work together (Mintzberg et al., 2005).
speed of transformations and demands in contemporary work environments require considerable
adjustments in the dynamics of organizational structures. Thus, the search for continuous
improvement in process management has determined that organizations increasingly employ
process management models to evaluate organizational maturity (Oliveira, 2015). The intention
of this movement is to excel in competitiveness and sustainability, not only in the area of activity,
but also in its way of working, the quality of its products and the efficient provision of services
(Mani et al., 2010).
of maturity models as a way of a differentiated assessment of implementation processes of
hospital management systems. Due to the absence of a specific model for the hospital area,

3
Tarhan(2015) use a generic maturity model, the Business Process Maturity Model (BPMM), to
assess the maturity and quality of hospital services.

Given the above considerations, the present paper aims to analyze previous researches related to
maturity models for management of hospitals, using the analytical dimensions
proposed Morton (1994), adapted to hospitals. As highlighted by Frega et al. (2017), this
found, revealing that 80% of publications regarding maturity models include the field of
information systems, and only 5% covered the hospital management sector.
The current document is structured as follows: the second section presents the methodological
procedures, the third presents the results of the literature research on the theme of maturity
models and hospital management, and finally, the final considerations.

2.5 Project Scope and Limitations:

This website provides an architectural overview of hospital management. This web site is generic.
A web-based tool that enables the user to manage the crime on tasks completed as part of a project
with tasks and sub-tasks. The tool includes interactivity, Functionality, Information will be stored
into a database. Administrative and managerial functions will be provided including configuration
projects/tasks/subtasks.

4
3) System Analysis:

3.1) Existing System:

In the existing 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.Also , from the admin
point of view maintaining data records in the physical file are cumbersome and tedious work the
order report are stored in physical file and also it is full of risk as anyone can access it and
modify the data.

3.2) Scope and Limitations of Existing System

1] Not User Friendly:

The existing system is not user friendly because the retrieval of data is very
slow and data is not maintained efficiently.

2]Difficulty in report generating:

We require more calculations to generate the report so it is generated

at the end of the session.

3]Manual control:

All calculations to generate report is done manually so there is great Chance

error.

5
4]Lots of paperwork:

Existing system requires lot of paper work.

5] Loss of register/record:

Multiple copies of the same information exist in the hospital and may lead

Inconsistencies in data in various data sources.

6] Time consuming:

Every work is done manually so we cannot generate report in the middle

of the session or as per the requirement because it is very time consuming.

6
3.3) Project perspective, features, stakeholders:

Features:

 Patient: -
 Registration
 Login
 Book Appointment
 Medical History
 Admin: -
 Login
 Dashboard
 Doctors Details
 Users/patient Detalis
 Appointment History
 Contact us Queries
 Doctor Session Logs
 User Session Logs
 Reports
 Patient Search
 Docter -
 Login
 Appointment History
 Add/Update Patients
 Search Patients Details

7
Stakeholders:

There are 3 main figures in the Hospital Management System: Patient, Doctor,Admin Patient
book the appointment, Meanwhile Doctor confirms the appointment and admin manages all the
updations in the database also keeps the report of both the patient and doctors details also the
details related to the services and appointments.

3.4) Requirement Analysis:

Requirements Analysis is the process of defining the users’ expectations for an application to be
built or modified. Requirement’s analysis involves all the tasks that are conducted to identify the
needs of different stakeholders. Therefore, requirements analysis means analyzing, documenting,
validating, and managing software or system requirements. As the software system requirements
were predictable, wallowing the classical system development life cycle method is decided. This
process demands a systematic, sequential approach to software development that begins at the
system level and progress through analysis, design, coding, testing and maintenance. The steps
that apply to all software engineering paradigms. The program is followed by SDLC (Software
Development Life Cycle).

3.4.1) Functional Analysis:

Functional analysis: a method for conceptualizing systems [with an application to the ATC
system] Functional analysis is a method for examining a system's purpose and performance
requirements and translating them into distinct activities or tasks that the system must do.

3.4.2) Performance Analysis:

The success or failure of a project is measured using numerous metrics in a performance analysis.
It aids in the development of a positive project management culture that produces exceptional
results. A good program's performance usually necessitates appropriate stakeholder management.

Following is chart that describes our web-based project performance over the available devices:

8
3.4.3) Security Analysis:

In the existing system, storage of all these records should be arranged and security should be
provided for the records. In the proposed system, separate security arrangement is not needed
since the software provides security and maintenance is simply and hardly needs one or two
people to operate the system.

9
4) System Design:

4.1) Design Constraints:

A) cohesion and coupling:

Book
Appointment

10
B) ERD

11
4.2) System Model:

4.2.1) Data Flow Diagram:

0th level DFD:

12
1st level DFD:

2.0

13
3.0

4.0

14
4.2.2) Data Model:

A) Class Diagram:

15
B)Object Diagram:

16
C) Use Case Diagram:

17
D) Sequence Diagram

18
E) Activity Diagram:

19
F) Deployment Diagram:

20
G) Component Diagram:

21
H) State Chart Diagram:

22
File Design /Normalization:

1)Table Name : admin

Sr.no Field Name Datatype Width Constraints

1 id Integer 11 Primary key

2 username Varchar 255 Not null

3 password Varchar 255 Unique key

4 updationDate Varchar 255 Not null

2)Table Name: appointment

Sr.no Field Name Datatype Width Constraints

1 id Integer 11 Primary key

2 specialization Varchar 255 Not null

3 doctorId Integer 11 Unique key

4 userId Integer 11 Unique key

5 consultancyFees Integer 11 Not null

6 appointmentDate Varchar 255 Not null

7 appointment Time Varchar 255 Not null

8 postingState Timestamp - Not null

23
 9 userSatus Integer 11 Not null

10 doctorStatus Integer 11 Not null

11 updationDate Timestamp - Not null

3)Table Name: doctors

Sr.no Field Name Datatype Width Constraints

1 id Integer 11 Primary key

2 specialization Varchar 255 Not null

3 doctorName Varchar 255 Not null

4 address Long text - Not null

5 doctorFees Varchar 255 Not null

6 contactno Integer 11 Not null

7 docEmail Varchar 255 Not null

8 password Varchar 255 Unique key

9 creationDate Timestamp - Not null

10 updationDate Timestamp - Not null

24
 4)Table Name: doctorslog

Sr.no Field Name Datatype Width Constraints

1 id Integer 11 Primary key

2 uid Integer 11 Unique key

3 username Varchar 255 Not null

4 userip Binary 16 Not null

5 loginTime Timestamp - Not null

6 logout Varchar 255 Not null

7 status Varchar 11 Not null

5)Table Name: doctorsspecialization

Sr.no Field Name Datatype Width Constraints

1 id Integer 11 Primary key

2 specialization Varchar 255 Not null

3 creationDate Timestamp - Not null

4 updationDate Timestamp - Not null

25
 6)Table Name:patient

Sr.no Field Name Datatype Width Constraints

1 ID Integer 10 Primary key

2 Docid Integer 10 Not null

3 PatientName Varchar 200 Not null

4 PatientContactno Integer 10 Not null

5 PatientEmail Varchar 200 Not null

6 PatientGender Varchar 50 Not null

7 PatientAdd Mediumtext - Not null

8 PatientAge Integer 10 Not null

9 PatientMedhis Mediumtext - Not null

10 CreationDate Timestamp - Not null

11 UpdationDate Timestamp - Not null

7)Table Name:userlog

Sr.no Field Name Datatype Width Constraints

1 id Integer 11 Primary key

2 uid Integer 11 Not null

3 username Varchar 255 Unique key

26
 4 userip Binary 16 Not null

5 loginTime Timestamp - Not null

6 logout Varchar 255 Not null

7 status Integer 11 Not null

8)Table Name:users

Sr.no Field Name Datatype Width Constraints

1 id Integer 11 Primary key

2 fullname Varchar 255 Not null

3 address Longtext - Not null

4 city Varchar 255 Not null

5 gender Varchar 255 Not null

6 email Varchar 255 Not null

7 password Varchar 255 Unique key

8 regDate Timestamp - Not null

9 updationDate Timestamp - Not null

27
1) Data Dictionary:

Sr.no FieldName Datatype Widt Constraint Table Name Description

h

1 id Integer 11 Primary key admin Admin id

2 usrename Varchar 255 Not null admin Admin

username

3 password Varchar 255 Unique key admin Admin

password

4 UpdationDate Varchar 255 Not null admin Update date

5 id Integer 11 Primary key appointment Appointment

id

6 Specialization Varchar 255 Not null appointment Doctor

specialization

7 doctorId Integer 11 Unique key appointment Doctor id

8 userId Integer 11 Unique key appointment UserId

9 consultancy Integer 11 Not null appointment Doctor fees

Fees

28
10 Appointment Varchar 255 Not null appointment Appointment
Date
date

11 Appointment Varchar 255 Not null appointment Appointment

Time time

12 postingState Timestamp - Not null appointment Status

13 userSatus Integer 11 Not null appointment User status

14 doctorStatus Integer 11 Not null appointment Doctor status

15 updationDate Timestamp - Not null appointment Updation date

16 id Integer 11 Primary key doctors Doctor id

17 specialization Varchar 255 Not null doctors Doctor

specialization

18 doctorName Varchar 255 Not null doctors Doctor name

19 address Longtext - Not null doctors Doctor

address

20 doctorFees Varchar 255 Not null doctors Doctor fees

21 contactno Integer 11 Not null doctors Doctor

contact no

22 docEmail Varchar 255 Not null doctors Doctor email

29
23 password Varchar 255 Unique key doctors Doctor
password

23 creationDate Timestamp - Not null doctors Doctor

creation date

24 updationDate Timestamp - Not null doctors Doctor

updation date

25 id Integer 11 Primary key doctorslogs Doctor login

id

26 uid Integer 11 Unique key doctorslogs User id

27 username Varchar 255 Not null doctorslogs Username

28 userip Binary 16 Not null doctorslogs Userip

29 loginTime Timestamp - Not null doctorslogs Doctor’s login

time

30 logout Varchar 255 Not null doctorslogs Doctor’s

logout time

31 status Varchar 11 Not null doctorslogs Doctor Login

status

32 id Integer 11 Primary doctorspecialization Specialization

id

30
33 specialization Varchar 255 Not null doctorspecialization Doctor

specialization

34 CreationDate Timestamp - Not null doctorspecialization CreationDate

35 UpdationDate Timestamp - Not null doctorspecialization UpdationDate

36 ID Integer 10 Primary key patient Patient id

37 Docid Integer 10 Not null patient Doctor id

38 PatientName Varchar 200 Not null patient Patient name

39 PatientContact Integer 10 Not null patient Patient

no contactno

40 PatientEmail Varchar 200 Not null patient Patient email

41 PatientGender Varchar 50 Not null patient Patient gender

42 PatientAdd Mediumtext - Not null patient Patient

address

43 PatientAge Integer 10 Not null patient Patient age

44 PatientMedhis Mediumtext - Not null patient Patient

Medical
history

31
45 CreationDate Timestamp - Not null patient CreationDate

46 UpdationDate Timestamp - Not null patient CreationDate

47 id Integer 11 Primary key userlog login id

48 uid Integer 11 Not null userlog User login id

49 username Varchar 255 Unique key userlog Username

50 userip Binary 16 Not null userlog User ip

51 loginTime Timestamp - Not null userlog User login

time

52 logout Varchar 255 Not null userlog User time

53 status Integer 11 Not null userlog User login

status

53 id Integer 11 Primary key users User id

54 fullname Varchar 255 Not null users User fullname

55 address Longtext - Not null users User address

56 city Varchar 255 Not null users User city

57 gender Varchar 255 Not null users User gender

58 email Varchar 255 Not null users User email

59 password Varchar 255 Unique key users User

password

32
4.3) User Interface

33
34
35
36
37
38
39
40
Code :

<?php

include_once('include/config.php');

if(isset($_POST['submit']))

$fname=$_POST['full_name'];

$address=$_POST['address'];

$city=$_POST['city'];

$gender=$_POST['gender'];

$email=$_POST['email'];

$password=md5($_POST['password']);

$query=mysql_query("insertintousers(fullname,address,city,gender,email,password)
values('$fname','$address','$city','$gender','$email','$password')");

if($query)

echo "<script>alert('Successfully Registered. You can login now');</script>";

?>

41
<!DOCTYPE html>

<html lang="en">

<head>

<title>User Registration</title>

<link
href="http://fonts.googleapis.com/css?family=Lato:300,400,400italic,600,700|Raleway:300,400,
500,600,700|Crete+Round:400italic"rel="stylesheet" type="text/css" />

<linkrel="stylesheet" href="vendor/bootstrap/css/bootstrap.min.css">

<link rel="stylesheet" href="vendor/fontawesome/css/font-awesome.min.css">

<link rel="stylesheet" href="vendor/themify-icons/themify-icons.min.css">

<linkhref="vendor/animate.css/animate.min.css" rel="stylesheet"
media="screen">

<link href="vendor/perfect-scrollbar/perfect-scrollbar.min.css" rel="stylesheet"

media="screen">

<link href="vendor/switchery/switchery.min.css" rel="stylesheet"

media="screen">

<link rel="stylesheet" href="assets/css/styles.css">

<link rel="stylesheet" href="assets/css/plugins.css">

<link rel="stylesheet" href="assets/css/themes/theme-1.css" id="skin_color" />

42
 </head>

<body class="login">

<!-- start: REGISTRATION -->

<div class="row">

<div class="main-login col-xs-10 col-xs-offset-1 col-sm-8 col-sm-offset-2

col-md-4 col-md-offset-4">

<div class="logo margin-top-30">

<img src="assets/images/logo.png" alt="Clip-Two"/>

</div>

<!-- start: REGISTER BOX -->

<div class="box-register">

<form name="registration" id="registration" method="post">

<fieldset>

<legend>

Sign Up

</legend>

43
 <p>

Enter your personal detail:

</p>

<div class="form-group">

<input type="text" class="form-

control" name="full_name" placeholder="Full Name" required>

</div>

<div class="form-group">

<input type="text" class="form-

control" name="address" placeholder="Address" required>

</div>

<div class="form-group">

<input type="text" class="form-

control" name="city" placeholder="City" required>

</div>

<div class="form-group">

<label class="block">

Gender

</label>

<div class="clip-radio radiprimary">

<input type="radio" id="rg-female" name="gender" value="female" >

<label for="rg-female">

44
 Female

</label>

<input type="radio" id="rg-male" name="gender" value="male">

<label for="rg-male">

Male

</label>

</div>

</div>

<p>

Enter your account details below:

</p>

<div class="form-group">

<span class="input-icon">

<input type="email"
class="form-control" name="email" id="email" onBlur="userAvailability()"
placeholder="Email" required>

<i class="fafa-envelope"></i> </span>

<span id="user-availability-status1" style="font-size:12px;"></span>

</div>

<div class="form-group">

<span class="input-icon">

45
 <input type="password"
class="form-control" id="password" name="password" placeholder="Password" required>

<i class="fa fa-lock"></i>

</span>

</div>

<div class="form-group">

<span class="input-icon">

<input type="password"
class="form-control" name="password_again" placeholder="Password Again" required>

<i class="fa fa-lock"></i>

</span>

</div>

<div class="form-group">

<div class="checkbox clip-check check-primary">

<input type="checkbox" id="agree" value="agree">

<label for="agree">

I agree

</label>

</div>

</div>

<div class="form-actions">

<p>

46
 Already have an account?

<a href="user-login.php">

Log-in

</a>

</p>

<button type="submit" class="btn btn-primary pull-right" id="submit" name="submit">

Submit <i class="fa fa-arrow-circle-right"></i>

</button>

</div>

</fieldset>

</form>

<div class="copyright">

&copy; <span class="current-year"></span><span

class="text-bold text-uppercase"> HMS</span>. <span>All rights reserved</span>

</div>

</div>

</div>

</div>

47
 <script src="vendor/jquery/jquery.min.js"></script>

<script src="vendor/bootstrap/js/bootstrap.min.js"></script>

<script src="vendor/modernizr/modernizr.js"></script>

<script src="vendor/jquery-cookie/jquery.cookie.js"></script>

<script src="vendor/perfect-scrollbar/perfect-scrollbar.min.js"></script>

<script src="vendor/switchery/switchery.min.js"></script>

<script src="vendor/jquery-validation/jquery.validate.min.js"></script>

<script src="assets/js/main.js"></script>

<script src="assets/js/login.js"></script>

<script>

jQuery(document).ready(function() {

Main.init();

Login.init();

});

</script>

<script>

function userAvailability() {

$("#loaderIcon").show();

jQuery.ajax({

url: "check_availability.php",

48
data:'email='+$("#email").val(),

type: "POST",

success:function(data){

$("#user-availability-status1").html(data);

$("#loaderIcon").hide();

},

error:function (){}

});

</script>

</body>

<!-- end: BODY -->

</html>

49
 5) Implementation Details:

5.1) Software and Hardware Specifications:

Software Requirement
Operating System Microsoft windows
Software Technology: -
Front –End Software XAMPP/WAMP Server(anyone) HTML, CSS,
JavaScript,AJAX,JQUERY
Back-End Software PHP, MySQL
Hardware Requirement
Processer: Intel core i5 2GHZ
RAM: 4GB or more
Monitor: LCD monitor
Keyboard: Normal keyboard
Mouse: Compatible mouse

6) Output and Report Testing:

6.1) Test Plan:

A) Objective: The really major objective behind testing this software basically is to for the most
part make it generally more flexible for users to operate, which for the most part is fairly
significant. And to essentially avoid really technical faults in the particularly particular program
in a subtle way. However, the software really is web based and here we for all intents and
purposes consider the software as an internet based and the testing will find out proper working
condition of software, demonstrating that objective: The actually major objective behind testing

50
this software kind of is to basically make it sort of more flexible for users to use, which literally
is fairly significant.

B) Project Overview: The Online Crime Reporting System is an application that covers
complete case management system and this project will help in managing activities of the police
station. It can used to report crimes and manage activities in a police station using computers by
tracking all the details of complaints, etc. Currently, most tasks are done manually, but by
computerizing all the activities inside a police station the working systems can be managed
easily and effectively.

C) Assumptions:

I. while testing this software we assume that expected output will recur
II. there may be a chance of errors while testing functionalities under different environments.

D) Test Execution

Testing of this particular software is divided into two parts:

1. Black Box Testing / Data Validation Test Cases

2. White Box Testing/ Functional Validations Test Cases and Results

6.1.1) Black Box Testing / Data Validation Test Cases:

Black Box Testing is a software testing method in which the functionalities of software
applications are tested without having knowledge of internal code structure, implementation
details and internal paths. Black Box Testing mainly focuses on input and output of software
applications and it is entirely based on software requirements and specifications. It is also known
as Behavioral Testing.

A TEST CASE is a set of actions executed to verify a particular feature or functionality of your
software application. A Test Case contains test steps, test data, precondition, postcondition
developed for specific test scenario to verify any requirement. The test case includes specific

51
 variables or conditions, using which a testing engineer can compare expected and actual results
to determine whether a software product is functioning as per the requirements of the customer.

Following is a performed data validation test cases and its result:

Test Case Type Description Test Step Expected Result Status

Functionality Databases must be Sign in with user ’ s Access should be

fetched and shown as credentials fetching permitted according to
per requirements. from database. whomever user is Pass
logged in.

Security Verify password rules Create a new The user ’ s password

are working password in will be accepted if it
accordance with rules. adheres to the rules. Pass

Usability Ensure all links are Have users click on Links will take users to
working properly. various links on the another web page
page according to the on- Pass
page URL.

6.1.2) White Box Testing/Functional Validity Test Cases and Results:

The White Box Testing is a type of testing technique that mainly examines program structure
and derives test data on the basis of program logic or code. It also referred to names like clear
box testing, open box testing, logic-driven testing or path driven testing or structural testing.

How Does White Box Testing Work?

The steps to perform this Testing mentioned as following in a specific order -

 Firstly, all feature, components, and programs to be tested, identified first.

 Create a flow graph and identify /plot all possible paths in the flow graph.

52
  Identification of all possible paths from the flow graph.
 Write test cases for every single path of the flow path.
 Execute, rinse and repeat test cases.

Benefits of this testing explained in the following manner -

 Required knowledge of the internals of the software under test to be tested.

 It allows a finding of hidden errors, to find internal errors because it checks and
works by internal functionality.
 It helps to find issues and optimize code to adopt different techniques of White Box
Testing to test a developed application or website.
 It requires internal knowledge to do testing that's why it helps in maximum coverage
of the code.

53
test case name :admin login

test case type Functional test case

reqiurement no: 101

module admin module

status active

serverity default

release admin login

version 2

precondition required to login

STEPS DESCRIPTION INPUTS EXCEPTED RESULT ACTUAL RESULT STATUS COMMENTS

1 open browser and enter url localhost:/hospital Landing page shouldbe dispalyed Asexcepted PASS workingproperly

2 selectthe usertype admin admin dashboard should be opened Asexcepted PASS workingproperly

3 click on login button clicked Login form should be displayed from top to bottom Asexcepted PASS workingproperly

4 enter the following values for "email id"

valid([email protected]) [email protected] Accepted Asexcepted PASS workingproperly

invalid 123a# error message-"enter valid email id" error messagecomebutwithspelling FAIL change the spelling mistake
mistake
blank - error message-"email id required" Asexcepted PASS workingproperly

5 enter the following values for "password"

valid(admin12345) admin12345 Accepted Asexcepted PASS workingproperly

invalid 123a# error message-"enter valid email id" error messagecomebutwithspelling FAIL change the spelling mistake
mistake
blank error message-"email id required" Asexcepted PASS workingproperly

entervalidemail idandpasswordandclickon [email protected]

"Login" button

6 admin12345 "name should be dispalyed on dashboard Asexcepted PASS workingproperly

author Utkarsh

date 05-04-2024

reviewed by Sahil

approved by Prof. Shubhangi Chavan

54
7) Conclusion And Recommendations:

The conclusion and recommendations for an online hospital management system can vary
depending on the specific context and goals of the system. However, here are some general
conclusions and recommendations that can be applied to such a system:

Conclusion:

Efficiency and Accuracy: An online hospital management system can significantly improve the
efficiency and accuracy of hospital operations. It streamlines various processes, such as
appointment scheduling, patient record management, billing, and inventory management, leading
to faster and more precise healthcare services.

Data Centralization: The system centralizes patient information, making it easily accessible to
authorized healthcare professionals. This can enhance patient care by providing a complete and up-
to-date medical history.

Improved Communication: Online systems facilitate communication between different

departments and staff members, reducing errors and enhancing collaboration. This is especially
crucial in a hospital setting where timely information sharing is vital.

Patient Convenience: Patients benefit from online scheduling, prescription refills, and access to
their medical records, enhancing their experience and engagement in their own healthcare.

55
Cost Reduction: By automating processes and reducing paperwork, hospitals can reduce
administrative costs and allocate resources more efficiently.

Recommendations:

Security and Data Privacy: Ensure robust security measures to protect sensitive patient data.
Compliance with data privacy regulations, such as HIPAA in the United States, is essential.

User Training: Adequate training for hospital staff is crucial to maximize the system's potential.
Training should cover both the technical aspects of using the system and how it integrates with
existing workflows.

Scalability: Design the system to be scalable, so it can grow with the hospital's needs. This is
important for accommodating an increasing number of patients and expanding services.

Integration: Integrate the hospital management system with other healthcare systems, such as
electronic health records (EHR), laboratory systems, and billing software, to ensure seamless
information flow.

Regular Updates and Maintenance: Continuously update and maintain the system to keep it
current with the latest technology and security standards. This helps prevent system vulnerabilities
and ensures long-term reliability.

User Feedback: Gather feedback from both staff and patients to identify areas for improvement.
Regularly assess the system's performance and make necessary adjustments.

Disaster Recovery and Backup: Implement robust disaster recovery and data backup procedures
to prevent data loss and ensure continuity of care in case of system failures or natural disasters.

Vendor Selection: Choose a reputable vendor with a strong track record in healthcare IT. Evaluate
their experience, support services, and references.

56
Accessibility: Ensure that the system is accessible to all users, including those with disabilities, in
compliance with accessibility standards and regulations.

Cost-Benefit Analysis: Periodically assess the system's cost-effectiveness by comparing the

benefits it provides in terms of improved healthcare delivery and cost savings with the expenses
associated with its implementation and maintenance.

In conclusion, an online hospital management system can greatly enhance hospital operations, but
it must be carefully designed, implemented, and maintained to realize its full potential while
safeguarding patient privacy and data security. Continuous monitoring and improvement are
essential to adapt to changing needs and technology advancements in the healthcare industry.

8) Future Scope:

 The future scope for online hospital management systems is promising, with ongoing
advancements in technology, changing healthcare needs, and a growing emphasis on digital
healthcare solutions. Here are some areas where the future of online hospital management
systems holds significant potential.

 The future scope is closely tied to the evolving healthcare landscape, technological
advancements, and patient-centric care. By adapting to these changes and embracing
innovation, these systems can continue to improve the efficiency, quality, and accessibility
of healthcare services

9) Bibliography and References:

1) https://www.w3schools.com

2) https://www.geeksforgeeks.org

57
 3) https://phpgurukul.com

4) https://research gate.com

5) https://academia.edu.com

6) https://www.irjet.net

7) https://www.slideshare.net/apevp

1)Nambiar, R., & Raman, R. (2017). Hospital management systems: A systematic review.
Journal of Health Informatics in Developing Countries, 11(2).

2)Raza, S., Standing, C., Karim, A., & Karim, A. (2017). An exploratory study of the key
challenges affecting the implementation of hospital information systems. Health Informatics
Journal, 23(2), 105-116.

3)Kuhn, K. A., Giuse, D. A., & Lapuerta, P. (2019). Success of health information technologies:
Evaluation and outcomes. Health Informatics Journal, 25(3), 140-157.

4)Dash, S., Shakyawar, S. K., Sharma, M., & Kaushik, S. (2018). Big data in healthcare:
Management, analysis, and future prospects. Journal of King Saud University-Computer and
Information Sciences.

58
5)Lau, F., Kuziemsky, C., & Price, M. (2016). A review on systematic reviews of health
information system studies. Journal of the American Medical Informatics Association, 14(2),
130-140.

59