CHAPTER I

A HEALTH CARE SYSTEM

OBJECTIVE OF THE PROJECT

A Health Care System is powerful, flexible, and easy to use and is designed and
developed to deliver real conceivable benefits to hospitals and clinics. And more importantly
it is backed by reliable and dependable support. Health care 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. Health care System will
be an integrated, modular client server based system working around a common database.
The Solution will be developed across Health care System using the computing technologies.
Health Care Project Following Modules Are Used Such that Patients, Pharmacy, Inpatient,
Outpatient, Administrator The system shall be user friendly and will have code based
selection facility. The user shall not have to remember complex codes for operating the
system. The Main aim of Hospital Management System project is to develop a Hospital
application that can be used to keep track of the in patients registering in a hospital. Also, this
system should support features such as maintain the Tablets details.
MODULES
ADMIN
 Authentication
 Add Inpatient details
 View Outpatient details
 Add Doctors
 View Doctors
 Allotment doctor
DOCTOR
 Login
 View Patient
 Sent Patient Disease details sent to patient
 Sent Patient Tablet details sent to pharmacy

1
IN PATIENT/OUT PATIENT
 Authentication
 View Allotment
 View Disease Details
 View Tablet Details
 Outpatient View and Accept Tablets
 Payment

PHARMACY
 Login
 View tablet details (paid Outpatients)
 Check Payment Details
 Provide Tablets

MODULE DESCRIPTION:
AUTHENTICATION:-
This module contains all the information about the authenticated Person. Admin
without his username and password can’t enter into the login if he is only the authenticated
Person then he can enter to his login. Authentication is the process of verifying the identity
of a Person by obtaining some sort of credentials and using those credentials to verify the
user's identity. If the credentials are valid, the authorization process starts. Authentication
process always proceeds to Authorization process.

IN PATIENT AND OUT PATIENT:

The Hospital can maintain all the patient entry information like in Patient and Out
Patient because how many patient entry in hospital and they maintain accounts details of the
hospital and we can finally store the information in database. Inpatient details add permission
only for admin. Outpatient registers his details himself.

2
ADD DOCTORS:
In Doctors Entry Module Admin Add the New Doctors details. It Contains
Information about Doctors ID, type, Name, Gender, Experience, Specialist, Contact No, Mail
ID, Address. Administrator only maintains details of the Doctors and Admin can finally store
the information in database Doctors Table.

VIEW PAINT DETAILS:

In view Doctors module every patient and admin will be view the information of
Doctors details, without authentication patient unable to view the Doctors details. The
Doctors details are Contains Information about the Doctors ID, type, Name, Gender,
Experience, Specialist, Contact No, Mail ID, Address.

DOCTOR SCHEDULING:
The Health care system maintain all the Physicians information because any
emergency of patient side we can easily find out the Physicians information so doctors can
fix appointment to particular patient in case of emergency. Admin allocate the schedule
information to doctor. Doctor can view his allotted patient details.

SENT PATIENT DISEASE:

In this patient disease module doctor send the patient disease details to particular
patient. This disease details keep safe from external users. Patient view his personal details
and disease details also.

SENT PATIENT TABLET:

In this patient Tablet module doctor send the patient Tablet details to particular
patient. This Tablet details keep safe from external users. Patient view his Tablet details and
disease details also. This Tablet details also send to pharmacy administrator.

OUTPATIENT ACCEPT TABLETS AND PAYMENT:

Out Patient view his Tablet details and disease details also. This Tablet details also
send to pharmacy administrator. Out Patient check his tablet details and amount details if it is
accepted then go to payment option. Then collect the tablet from pharmacy.

3
PHARMACY:
Doctor sends the patient Tablet details to particular patient and also sends to
pharmacy administrator. Out Patient check his tablet details and amount details if it is
accepted then go to payment option. Then collect the tablet from pharmacy.

4
 CHAPTER II
SYSTEM STUDY AND SPECIFICATION

EXISTING SYSTEM
Generally all the Patient details and party details are maintained manually by the
Health care System. But it leads a more time to maintain these records and very difficult to
find the details for various particulars.

DISADVANTAGES
 Everything is done by manually, so it is very difficult to maintain the records.
 It’s also very difficult to find the particular details.
 Long time process

5
PROPOSED SYSTEM
The proposed system is developed to overcome the disadvantages of the existing
specified earlier. This system is being created using.NET and SQLSERVER. Since.Net is our
Front-End it looks more look and feels for the web application is very Effective & Security.
This look and feel of it is more users friendly and easy to operate on. System can maintain
the list of doctors in the hospital. Health care System Contains Doctor Sent the Patient
Disease Details to Patient and Pharmacy. Pharmacy View and Provide the Tablets to
Particular Patient.

ADVANTAGES
 This project is reliable, flexible. So it is Easy to store and retrieve the huge amount of
data.
 Any time you have to view a particular customer status.
 Takes less time to do the process.
 Speed and accuracy is increased

6
SYSTEM REQUIREMENT

HARDWARE SPECIFICATION
PROCESSOR : Dual Core
HARD DISK : 256 GB
RAM : 1 GB
MONITOR : 15” Color Monitor
KEYBOARD : 104 keys Standard Keyboard
MOUSE : Standard 3 Button Mouse

SOFTWARE SPECIFICATION
OPERATING SYSTEM : Windows XP/7/8
FROND END : ASP.NET
BACK END : SQL SERVER

7
 CHAPTER III
DESIGN AND DEVELOPMENT

INPUT FORM DESIGNS

8
9
Level-0

Admin
Homepage

Doctor
Health care Homepage
Login

Patient
Homepage

Pharmacy
Homepage
Level-1

Home

Health care

Doctor, Patient
Registration

valid
Admin Login Main page
Invalid

Pharmacy

10
Level – 2

Authentication

In patient Entry
Database

View Out patient

Admin

Add Doctor

Allotment Doctor

Level – 2

View Allotment

Doctor Send Disease Database

Details

Send Tablet Details

11
Level – 2

View Tablet Detail

Doctor Check Payment Database

Provide Tablet
Level – 2

Authentication

View Allotment
Database

View Disease
Agent

View Tablet

Accept Tablet

Payment

12
 ER- DIAGRAM

Customer
Name password
id

New Patient
Admin

Allot
Login

Doctor
Patient id
ID
ID

Doctor Send Disease

Name

Name
Disease
send Delivery

Specialist

Tablet Provi
de Pharmacy

Dosage
Patient ID
TabletName Patient Tablet
Payment
ID

13
TABLE DESIGN:

Doctor:
Doctor ID varchar(50) Not Null
UserName varchar(50) Not Null
Password varchar(50) Not Null
Gender varchar(50) Not Null
PhoneNo varchar(50) Not Null
MailID varchar(50) Not Null
City varchar(50) Not Null
Address varchar(MAX) Not Null
Specialist varchar(50) Not Null
Join Date varchar(50) Not Null

Patient:
Patient ID int Not Null
Name varchar(50) Not Null
Password varchar(50) Not Null
Gender varchar(50) Not Null
PhoneNo varchar(50) Not Null
MailID varchar(50) Not Null
City varchar(50) Not Null
Address varchar(MAX) Not Null
Type varchar(20) Not Null

DISEASE:
Patient ID int Not Null
Name varchar(50) Not Null
Date varchar(50) Not Null
Disease varchar(50) Not Null
Discription varchar(50) Not Null

14
TABLET:
SNo int Not Null
Patient ID int Not Null
Name varchar(50) Not Null
Date varchar(50) Not Null
Tablet varchar(50) Not Null
Discription varchar(50) Not Null
Dosage varchar(MAX) Not Null
Amount varchar(50) Not Null
Payment varchar(50) Not Null

Allocate
SNo int Not Null
Patient ID varchar(50) Not Null
Doctor ID varchar(50) Not Null
Date varchar(50) Not Null
Time varchar(MAX) Not Null

15
FINAL TEST CASE REPORT OF ALL MODULES

Test ID Test Description Test steps Excepted Actual Status

output output
TC-01 Enter registration 1.Enter The user is Same as EO Success
details to sign up registration registered and as
details shown
successfully
2.click on sign
registered
up

TC-02 Enter registration 1.Enter Alert is shown Same as EO Success

details to sign up registration to type the
details details in correct
incorrect format
format

2.click on sign
up

TC-03 Enter valid 1.enter valid Successful login Same as EO Success

username and username
password
2.enter valid
password

3.click on
login button

16
TC-04 Enter username 1.Enter A popup Same as EO Unsuccessful
and / or password username and message box to
invalid password shown invalid
invalid or username or
enter password
username or
password
invalid

2. click on
login button

TC-05 update Doctor Enter Doctor Doctor details is Same as EO Success

details details successfully
updated..

TC-05 Admin pharmacy Enter pharmacy Same as EO Success

pharmacy details
Click to Uploaded.
upload
TC-06 Admin pharmacy Enter a An alert Same as EO Success
pharmacy pharmacy not
Click to Uploaded
upload
TC-07 Enter a outpaient Click on The outpaient Same as EO Success
outpaient are Shown

TC-08 Detect a outpaient Click to The outpaient is Same as EO Success

Submit the Post
outpatient
details
TC-09 Phishing Click to An alert Test is Same as EO Unsuccessful

17
 Inpaients Submit the not valid
pages
TC-10 View a Inpaients Click to view The Test is Same as EO Success
Phishing show a Inpaients
details
TC-11 DoctorDescription 1.Enter the Doctor Same as EO Success
Doctor submitted

2.Click to
Submit
Doctor

TC-12 Time out Click to Time Displayed the Same as EO Success

out view paient details to
registered
Phishing
Websites

18
 CHAPTER IV
CODING AND DEPLOYMENT

DOCTOR DETAILS:

if(isset($_REQUEST['ok']))
{
$sql="INSERT INTO usertable
VALUES('$_POST[tid]','$_POST[password]','User','$_POST[tid2]')";

if ($conn->query($sql) === TRUE)

{
$sql1="INSERT INTO usertbl
VALUES('$_POST[tid2]','$_POST[tid3]','$_POST[tid4]','$_POST[tid5]','$_POST[ct1]','$_P
OST[tid6]','$_POST[tid7]','$_POST[tid]')";

if ($conn->query($sql1) === TRUE)

{
echo $sql1;
echo '<script>alert("Users Registered Successfully");</script>';
$URL="index.php";
echo '<META HTTP-EQUIV="refresh" content="0;URL=' . $URL . '">';
echo "<script type='text/javascript'>document.location.href='{$URL}';</script>";
}
// echo "success";
}
else
{
echo "Error: " . $sql . "<br>" . $conn->error;
}
}
?>
MENU CREATION:

19
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Profile</title>
<link id="nav" rel="stylesheet" type="text/css" href="style.css">

<link rel="stylesheet" href="dates/jquery.ui.all.css">

<script src="dates/jquery-1.9.0.js"></script>
<script src="dates/jquery.ui.core.js"></script>
<script src="dates/jquery.ui.widget.js"></script>
<script src="dates/jquery.ui.datepicker.js"></script>
<link rel="stylesheet" href="dates/demos.css">
<script>

$(function() {
$( "#datepicker" ).datepicker();
});
</script>

</head>

<body>
<center>
<div id="container">
<div id="nav" align="left">
<div class="lft">
<div class="rit">
<ul>
<li><a href="index.php">Home</a></li>
<li><a href="aboutus.php">About Us</a></li>
20
<li><a href="Features.php">Features</a></li>
<li><a href="Registration.php">Register</a></li>
<li><a href="home.php?b" id="a">User Login</a></li>
<li><a href="home.php?a">Admin Login</a></li> </ul>
</div>
</div>
</div>
<img src="images/123.jpg" width="950" height="150" />
</div>
<div id="container">
<form name="profile" id="profile" method="post" bgcolor="#E6E6FA"
enctype="multipart/form-data" style="
padding-bottom: 16px; ">
<div id="topone">
<?php /*?><?php echo "Welcome,". $_SESSION['name']." Enroll the student Profile"; ?>
<?php */?>

PHARMACHY DETAILS:
<?php echo "Welcome,". $_SESSION['name']; ?>
</div>
<p></p>
<h4 style="color:#400">User Enrollment Process</h4>
<fieldset style="background-color:#77AAC9; width:80%; margin:10px;" align="Left">
<table width="765" height="343">
<tbody>
<tr>
<td valign="top">&nbsp;</td>
<td valign="top">User Id </td>
<td valign="middle"><input name="tid2" required="required" type="text" id="tid2" /></td>
<td valign="middle">&nbsp;</td>
<td valign="middle">Age</td>
<td valign="middle"><input name="tid5" required="required" type="text" id="tid5" /></td>
</tr>
<tr>
21
<td valign="top">&nbsp;</td>
<td valign="top">User Name </td>
<td valign="middle"><input name="tid3" required="required" type="text" id="tid3" /></td>
<td valign="middle">&nbsp;</td>
<td valign="middle">Gender</td>
<td valign="middle"><input type="radio" name="ct1" value="Male" >Male <input
type="radio" name="ct1" value="Female" >Female</td>
</tr>
<tr>
<td valign="top">&nbsp;</td>
<td valign="top">Phone Number </td>
<td valign="middle"><input name="tid4" required="required" type="text" id="tid4" /></td>
<td valign="middle">&nbsp;</td>
<td valign="middle">Area</td>
<td valign="middle"><input name="tid7" required="required" type="text" id="tid7" /></td>
</tr>
<td valign="top">&nbsp;</td>
<td width="115" valign="middle">Password</td>
<td width="280" valign="middle"><input type="password" name="password"
class="login_text" id="password" /></td>
<br>
</tr><tr>
<td></td>
<td></td>
<td valign="middle"><input type="submit" name="ok" value="Submit"/>
<input type="submit" name="ok3" value="Reset"/></td>
<td valign="middle">&nbsp;</td>
<td valign="middle">&nbsp;</td>
<td valign="middle"><img src="images/download (1).jpg" alt="reg" width="110"
height="59" /></td>
</tr>
<tr>
<td height="92"></td>
<td colspan="5"></td>
22
</tr>
<tr>
<td height="2">
</tbody>
</table>
</fieldset>
</form>
</div>
</center>
</body>
</html>

PAIENT REGISTRATION:
<?php
session_start();
$con = mysql_connect("localhost","root","");
$exe = mysql_select_db('Phishing',$con);
$uri = $_SERVER["QUERY_STRING"];
//echo $uri;

if(isset($_REQUEST['submit']))
{

if($uri=="s")
{

$sel ="select * from usertable where loginid = '".$_REQUEST['name']."' and password =

'".$_REQUEST['password']."' and role='Authority' ";
}
elseif($uri=="b")
{

23
$sel ="select * from usertable where loginid = '".$_REQUEST['name']."' and password =
'".$_REQUEST['password']."' and role='User'";
}
else
{
$sel ="select * from usertable where loginid = '".$_REQUEST['name']."' and password =
'".$_REQUEST['password']."' and role='admin'";
}

$run = mysql_query($sel);
$getNo = mysql_num_rows($run);

if($getNo!='')
{
@$_SESSION['name'] = $_REQUEST['name'];

$getRecords = mysql_fetch_array($run);
if($uri=="b")
{
echo '<script>alert("Login successful");</script>';

$URL="Userhome.php";
echo '<META HTTP-EQUIV="refresh" content="0;URL=' . $URL . '">';
echo "<script type='text/javascript'>document.location.href='{$URL}';</script>";

}
else if($uri=="s")
{
$URL="authority_home.php";
echo '<META HTTP-EQUIV="refresh" content="0;URL=' . $URL . '">';
echo "<script type='text/javascript'>document.location.href='{$URL}';</script>";
}

else if($uri=="a")
24
{
$URL="adminhome.php";
echo '<META HTTP-EQUIV="refresh" content="0;URL=' . $URL . '">';
echo "<script type='text/javascript'>document.location.href='{$URL}';</script>";
}
else
{
//$_SESSION['name'] = $_REQUEST['name'];
header('location:adminhome.php');

IN PAIENT PAGE:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Home Page</title>
<link id="nav" rel="stylesheet" type="text/css" href="style.css">
<link rel="stylesheet" type="text/css" href="login_layout.css">

<script language="javascript" type="text/javascript">

function validate()
{
if (document.forms["login"]["name"].value=="" )
{
alert("Enter Username");
document.getElementById('name').focus();
return false;
}
else if (document.forms["login"]["password"].value=="")
{
alert("password must be filled out");
document.getElementById('password').focus();
25
return false;
}
}
</script>
</head>
<body bgcolor="#77AAC9" onLoad="document.forms.login.name.focus()">
<center>
<div id="container">
<div id="nav" align="left">
<div class="lft">
<div class="rit">
<ul>

<li><a href="index.php">Home</a></li>
<li><a href="aboutus.php">About Us</a></li>
<li><a href="Features.php">Features</a></li>
<li><a href="Registration.php">User Enrollment</a></li>
<li><a href="home.php?b" id="a">User Login</a></li>
<li><a href="home.php?a">Admin Login</a></li> </ul>
</div>
</div>
</div>
<img src="images/123.jpg" width="100%" height="150" /> </div>
<div id="container">
<form id="login" name="login" method="post" bgcolor="#77AAC9" onsubmit="return
validate()">
</form>
</div>
</center>
</body>
</html>

26
 CHAPTER V
TESTING AND IMPLEMENTATION

TESTING
It is the process of exercising software with the intent of finding and ultimately
correcting errors. This fundamental philosophy does not change for web applications,
because web based system and applications reside on network and inter-operate with many
different operating systems, browsers, hardware platforms and communication protocols.
Thus searching for errors is significant challenge for web applications.

TESTING ISSUES:
 Client GUI should be considered.
 Target environment and platform considerations
 Distributed database considerations
 Distributed processing consideration

TESTING AND METHODOLOGIES

System testing is the state of implementation, which is aimed at ensuring that the
system works accurately and efficiently as expect before live operation, commences. It
certifies that the whole set of programs hang together System testing requires a test plan, that
consists of several key activities and steps for run program, string, system and user
acceptance testing. The implementation of newly design package is important in adopting a
successful new system
Testing is important stage in software development. System test is implementation
should be a confirmation that all is correct and an opportunity to show the users that the
system works as they expected It accounts the largest percentage of technical effort in
software development process.
Testing phase is the development phase that validates the code against the functional
specifications. Testing is a vital to the achievement of the system goals. The objective of
testing is to discover errors. To fulfill this objective a series of test step such as the unit test,
integration test, validation and system test where planned and executed.

27
UNIT TESTING
Here each program is tested individually so any error apply unit is debugged.
The sample data are given for the unit testing. The unit test results are recorded for further
references. During unit testing the functions of the program unit validation and the limitations
are tested.
Unit testing is testing changes made in a existing or new program this test is
carried out during the programming and each module is found to be working satisfactorily.
For example in the registration form after entering all the fields we click the submit button.
When submit button is clicked ,all the data in form are validated. Only after validation entries
will be added to the database.
Unit testing comprises the set of tests performed by an individual prior to
integration of the unit into large system. The situation is illustrated in as follows
Coding-> Debugging ->Unit testing -> Integration testing
The four categories of test that a programmer will typically perform on a program unit
 Functional test
 Performance test
 Stress Test
 Structure test
Functional test involve exercising the code with nominal input values for which
the expected results are known as well as boundary values and special values.
Performance testing determines the amount of execution time spent in various
parts of unit program through put and response time and device utilization by the program.
A variation of stress testing called sensitivity testing in same situations a very
small range of data contained in a bound of valid data may cause extreme and even erroneous
processing or profound performance degradation.

28
 Structured testing is concerned with a exercising the internal logic of a program
and traversing paths. Functional testing, stress testing performance testing are referred as
“black box” testing and structure testing is referred as “white box” testing

VALIDATION TESTING
Software validation is achieved through a serious of testes that demonstrate
conformity with requirements. Thus the proposed system under consideration has been tested
by validation & found to be working satisfactory.
OUTPUT TESTING

Asking the user about the format required by them tests the output generated by
the system under consideration .It can be done in two ways, One on screen and other on
printer format. The output format on the screen is found to be correct as the format designed
n system test.

SYSTEM TESTING
In the system testing the whole system is tested for interface between
each modules and program units are tested and recorded. This testing is done
with sample data . The securities, communication between interfaces are tested
System testing is actually a series of different tests whose primary
purpose is to fully exercise the computer based system although each test
has a different purpose all work to verify that all system elements properly
integrated and perform allocate function.
It involves two kinds of activities namely
1. Integrated testing
2. Acceptance testing

INTEGRATED TESTING
Integrated testing is a systematic technique for constructing tests to uncover
errors associated with interface.
Objective is to take unit tested modules and build a program structure that has
been dictated by design

29
ACCEPTANCE TESTING
Acceptance testing involves planning an execution of a functional test,
performance test and stress test to verify that the implemented system satisfies the
requirement.
The acceptance testing is the final stage of the user the various possibilities of
the data are entered and the results are tested.
VALIDATION TESTING
Software validation is achieved through a series of test that demonstrates the
conformity and requirements. Thus the proposed system under consideration has to be tested
by validation and found to be working satisfactorily. For example in customer enters phone
number field should contain number otherwise it produces an error message similarly in all
the forms the fields are validated

TESTING RESULTS
All the tests should be traceable to customer requirements the focus of testing will
shift progressively from programs Exhaustive testing is not possible To be more effective
testing should be which has probability of finding errors

The following are the attributes of good test

1. A good test has a probability of finding a errors
2. A good test should be “best of breeds ”
3. A good test to neither simple nor too complex

30
 CHAPTER VI
SYSTEM MAINTENANCE

Maintenance is actually implementation of the review plan as important as it is

programmers and analyst is to perform or identify with him or herself with the maintenance.
There are psychologically personality, and professional reasons for this. Analyst and
programmers spend fair more time maintaining programmer then they do writing them
Maintenances account for 50-80% of total system development. Maintenance is expensive
.One way to reduce the maintenance costs are through maintenance mgt and software
modification audits Types of maintenance are
1. Perfective maintenance
2. Preventive maintenance

PERFECTIVE MAINTENANCE:
Changes made to the system to add features or to improve the performance.
In future any more features can be added in this project and it can easily adopt the changes.

PREVENTIVE MAINTENANCE:
Changes made to the system to avoid future problems. Any changes can be made
in the future and our project can adopt the changes.

31
 CHAPTER VII
CONCLUSION

The “A HEALTH CARE SYSTEM” has been developed to satisfy all proposed
requirements. The process is maintained more simple and easy. The system is highly scalable
and user friendly. Almost all the system objectives have been met. The system has been
tested under all criteria. The system minimizes the problem arising in the existing manual
system and it eliminates the human errors to zero level. The design of the database is flexible
ensuring that the system can be implemented. It is implemented and gone through all
validation. All phases of development were conceived using methodologies. User with little
training can get the required report. The software executes successfully by fulfilling the
objectives of the project. Further extensions to this system can be made required with minor
modifications.

32
 BIBLIOGRAPHY
BOOKS REFERENCES:
1. Professional ASP.NET 1.0, Special Edition
Author(s): Alex Homer, Brian Francis, David Sussman, Karli Watson, Richard
Anderson and Robert Howard
Released: February 2002
Publisher: Wrox Press
2. Extreme .NET: Introducing Extreme Programming Techniques to .NET Developers
Author(s): Dr. Neil Roodyn
Released: November 2004
Publisher: Addison-Wesley
3. Student's Essential Guide to .NET, 1st Edition
Author(s): Tony Grimer
Released: October 2004
Publisher: Butterworth-Heinemann
4. Professional DotNetNuke ASP.NET Portals
Author(s): Shaun Walker, Patrick J. Santry, Joe Brinkman, Dan Caron, Scott
McCulloch, Scott Willhite, Bruce Hopkins
Released: June 2005
Publisher: wrox press.

WEBSITES REFERENCES

http://www.asp.net.com
http://www.dotnetspider.com/
http://www.almaden.ibm.com/software/quest/Resources/
http://www.computer.org/publications/dlib
http://www.developerfusion.com/

33
 APPENDIX 2
9.2 SCREENSHOTS:

A.2.1 MAIN PAGE FOR HEALTHCARE

34
A.2.3 PATIENT REGISTRATION

35
A.2.5 PATIENT LOGIN

36
A.2.8 UPDATING PATIENT DETAILS TO PHYSICIAN

37
A.2.10 TO GET AN APPOINTMENT

38
A.2.12 PHYSICIAN LOGIN

39
A.2.18 TO OBTAIN DETAILS OF PATIENTS

40
A.2.19 OBTAINING DETAILS OF PATIENTS

41
A.2.20 TO FILL MEDICAL PRESCRIPTIONS

42
A.2.25 UPDATING DIAGONOSIS

43
A.2.26 PHARMACY WEBPAGE

44
A.2.28 OBTAINING TODAY’S DETAILS

45
A.2.30 PHARMACIES WEEKLY DETAILS

46
A.2.31 TO VIEW ALL RECORD LIST

47
A.2.32 FULL RECORD LIST OF PHARMACY

48