OBJECTIVE

Patient can easily look out hospital and doctor with

relevant disease for better cure at one click from home
with out going any where. At present it is very typical to
find out specialist doctor and hospital for relevant
disease. If we provide all the information at single window
which will be very feasible for patient for cure and
appointment.
Slowly -2 as many as possible hospitals not only of India
throughout the world we will add it make more effective
to this project.
It is fully online management system and in todays world
every one knows the feature and advantage of online
system and this system will be the next coupling in this
chain obviously

THE PROPOSED SYSTEM:

The present system has obvious problems, inhibiting
growth and more usage of man power. The present
system which has been proposed is very easy to
work .The computerization detail of the every
department , hospital in the website will reduce the
work that is done manually. The man power is reduced
to the maximum extent. The patients at the registration
doctor are registered within no time, because every
 time there is no need search for the particular
appointment no in the shelfs .The doctor and hospital
information are maintained without any complexity and
all the calculations are made automatically by this
system there is no need for the calculations

Implementation Plan:
The main plan for the system developed is to mimic the existing system as it is in
the proposed system.

Study of the Existing System

The existing system is very complex as every work is done manually. By
using the present system, work is done automatically without any help. So, each
and every work takes much time to complete. Whenever the patient needs the
information it is very difficult for the patient to search for that particular doctor or
hospital details and the drug information to be ordered. Every time we should
search the records at the shelves.

Disadvantages Before System

Introduced

1. The work is done manually so that it takes much time to recognize the
doctor or hospital info.
2. More manual detail required
3. We cant asses the calculations accurately.
4. Amount of time is more needed when the more mining about hospital or
doctor require. It counts time factor.
5. As there are thousands of doctors or hospital records; Searching process is
a difficult task.

Advantages After System Introduced

 1. A fast and more efficient service to all patients . As there are thousands
of hospital and doctor records; Searching process is an easy task.

2. Saving in search time in entering and changing doctor or hospital.

3. Easy input, deletion and manipulation of lot, hospital and doctor details.

4. Simple correction of input errors and we can assess the calculations

accurately.

SCOPE
Easy for patients to search hospitals and doctors
User can check appointment details
User can check hospital facilities
We can upload details throughout the world

FUTURE SCOPE AND ENHACEMENT

Online drug information
Online doctor prescription
Online disease consultation
Online dispatching of drug
Attach testing centers also

MODULES

Administrator module
(To register Doctor,Patient,Department,Appointment
Time)
Patient Detail(Registration)
Patient OPD Confirmation
 Hospitals details
Doctors Details
Admin Log in
User Log in

TOOLS AND TECHNOLOGY

USED
Hardware Requirements:-

Pentium-IV(Processor).
256 MB Ram
512 KB Cache Memory
Hard disk 10 GB
Microsoft Compatible 101 or more Key Board

Software Requirements: -

Operating System : Windows XP

Programming language: .NET
 Web-Technology: ASP.NET 2.0
Front-End: C#.NET
Back-End: Sql Server 2000
Web Server: IIS

PRESCRIBED TABLES AS PRE

ASSUMPTION
Hospital
HID(Hospital ID) Integer(Primary key)
HNAME(Hospital Varchar(20)
Name)
Address Varchar(50)
Department
DID(Department Id) Integer(Primary key)
DNAME(Department Varchar(20)
Name)
HID(Hospital ID) Integer(Foreign key)

Doctor Detail
 ID(Doctor ID) Integer(Primary key)
DOCNAME(Doctor Varchar(20)
Name)
HID(Hospital ID) Integer
DID(Department ID) Integer

PATIENT DETAIL
PID(Patient ID) Integer(Primary key)
ID(Doctor ID) Integer
HID(Hospital ID) Integer
DID(Department ID) Integer
Appointment(Date Date/Time
and Time)
Note-Tables above are just as per pre assumption not so at the
time of implementation it will be modifiable.
OVERVIEW OF TECHNOLOGIES USED

Front End Technology

Microsoft .NET Framework
The .NET Framework is a new computing platform that simplifies application development in the
highly distributed environment of the Internet. The .NET Framework is designed to fulfill the
following objectives:

To provide a consistent object-oriented programming environment whether

object code is stored and executed locally, executed locally but Internet-distributed,
or executed remotely.

To provide a code-execution environment that minimizes software deployment

and versioning conflicts.
 To provide a code-execution environment that guarantees safe execution of
code, including code created by an unknown or semi-trusted third party.

To provide a code-execution environment that eliminates the performance

problems of scripted or interpreted environments.

To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on

the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and the .NET
Framework class library. The common language runtime is the foundation of the .NET Framework.
You can think of the runtime as an agent that manages code at execution time, providing core
services such as memory management, thread management, and remoting , while also enforcing
strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the
concept of code management is a fundamental principle of the runtime. Code that targets the
runtime is known as managed code, while code that does not target the runtime is known as
unmanaged code. The class library, the other main component of the .NET Framework, is a
comprehensive, object-oriented collection of reusable types that you can use to develop
applications ranging from traditional command-line or graphical user interface (GUI) applications
to applications based on the latest innovations provided by ASP.NET, such as Web Forms and
XML Web services.

NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly integrate with the
common language runtime. The class library is object oriented, providing types from which your
own managed code can derive functionality. This not only makes the .NET Framework types easy
to use, but also reduces the time associated with learning new features of the .NET Framework. In
addition, third-party components can integrate seamlessly with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of interfaces that you can
use to develop your own collection classes. Your collection classes will blend seamlessly with the
classes in the .NET Framework.
 As you would expect from an object-oriented class library, the .NET Framework types enable you
to accomplish a range of common programming tasks, including tasks such as string management,
data collection, database connectivity, and file access. In addition to these common tasks, the class
library includes types that support a variety of specialized development scenarios. For example,
you can use the .NET Framework to develop the following types of applications and services:

Console applications.

Scripted or hosted applications.

Windows GUI applications (Windows Forms).

ASP.NET applications.

XML Web services.

Windows services.

For example, the Windows Forms classes are a comprehensive set of reusable types that vastly
simplify Windows GUI development. If you write an ASP.NET Web Form application, you can use
the Web Forms classes.

Client Application Development

Client applications are the closest to a traditional style of application in Windows-based
programming. These are the types of applications that display windows or forms on the desktop,
enabling a user to perform a task. Client applications include applications such as word processors
and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools,
and so on. Client applications usually employ windows, menus, buttons, and other GUI elements,
and they likely access local resources such as the file system and peripherals such as printers.

Another kind of client application is the traditional ActiveX control (now replaced by the managed
Windows Forms control) deployed over the Internet as a Web page. This application is much like
other client applications: it is executed natively, has access to local resources, and includes
graphical elements.
 Server Application Development
Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications host the common language runtime, which allows your custom managed
code to control the behavior of the server. This model provides you with all the features of the
common language runtime and class library while gaining the performance and scalability of the
host server.

The following illustration shows a basic network schema with managed code running in different
server environments. Servers such as IIS and SQL Server can perform standard operations while
your application logic executes through the managed code.

Language Support

The Microsoft .NET Platform currently offers built-in support for three languages: C#,
Visual Basic, and Jscript .

What is ASP.NET Web Forms?

The ASP.NET Web Forms page framework is a scalable common language runtime programming
model that can be used on the server to dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with existing
pages), the ASP.NET Web Forms framework has been specifically designed to address a number of
key deficiencies in the previous model. In particular, it provides:

The ability to create and use reusable UI controls that can encapsulate common
functionality and thus reduce the amount of code that a page developer has to write.

The ability for developers to cleanly structure their page logic in an orderly
fashion (not "spaghetti code").

The ability for development tools to provide strong WYSIWYG design support for
pages (existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name extension. They can be deployed
throughout an IIS virtual root directory tree. When a browser client requests .aspx resources, the
ASP.NET runtime parses and compiles the target file into a .NET Framework class. This class can
then be used to dynamically process incoming requests. (Note that the .aspx file is compiled only
the first time it is accessed; the compiled type instance is then reused across multiple requests).

An ASP.NET page can be created simply by taking an existing HTML file and changing its file
name extension to .aspx (no modification of code is required). For example, the following sample
demonstrates a simple HTML page that collects a user's name and category preference and then
performs a form post back to the originating page when a button is clicked:

ASP.NET provides syntax compatibility with existing ASP pages. This includes support
for <% %> code render blocks that can be intermixed with HTML content within an
.aspx file. These code blocks execute in a top-down manner at page render time.

BACK END TECHNOLOGY:

About Microsoft SQL Server 2000

Microsoft SQL Server is a Structured Query Language (SQL) based, client/server relational
database. Each of these terms describes a fundamental part of the architecture of SQL Server.
Database

A database is similar to a data file in that it is a storage place for data. Like a data
file, a database does not present information directly to a user; the user runs an
 application that accesses data from the database and presents it to the user in an
understandable format.

A database typically has two components: the files holding the physical database and the database
management system (DBMS) software that applications use to access data. The DBMS is
responsible for enforcing the database structure, including:
Maintaining the relationships between data in the database.
Ensuring that data is stored correctly and that the rules defining data
relationships are not violated.
Recovering all data to a point of known consistency in case of system failures.

Relational Database

There are different ways to organize data in a database but relational databases are
one of the most effective. Relational database systems are an application of
mathematical set theory to the problem of effectively organizing data. In a relational
database, data is collected into tables (called relations in relational theory).

When organizing data into tables, you can usually find many different ways to define
tables. Relational database theory defines a process, normalization, which ensures
that the set of tables you define will organize your data effectively.

Client/Server:-

In a client/server system, the server is a relatively large computer in a central

location that manages a resource used by many people. When individuals need to use
the resource, they connect over the network from their computers, or clients, to the
server.

Examples of servers are: In a client/server database architecture, the database files

and DBMS software reside on a server. A communications component is provided so
applications can run on separate clients and communicate to the database server
over a network. The SQL Server communication component also allows
communication between an application running on the server and SQL Server.

Server applications are usually capable of working with several clients at the same time. SQL
Server can work with thousands of client applications simultaneously. The server has features to
prevent the logical problems that occur if a user tries to read or modify data currently being used
by others.

While SQL Server is designed to work as a server in a client/server network, it is also capable of
working as a stand-alone database directly on the client. The scalability and ease-of-use features of
SQL Server allow it to work efficiently on a client without consuming too many resources.
Structured Query Language (SQL)

To work with data in a database, you must use a set of commands and statements
(language) defined by the DBMS software. There are several different languages that
can be used with relational databases; the most common is SQL. Both the American
National Standards Institute (ANSI) and the International Standards Organization (ISO)
have defined standards for SQL. Most modern DBMS products support the Entry Level
of SQL-92, the latest SQL standard (published in 1992).

SQL Server Features

Microsoft SQL Server supports a set of features that result in the following benefits:

Ease of installation, deployment, and use

SQL Server includes a set of administrative and development tools that improve your
ability to install, deploy, manage, and use SQL Server across several sites.

Scalability
The same database engine can be used across platforms ranging from laptop
computers running Microsoft Windows 95/98 to large, multiprocessor servers
running Microsoft Windows NT, Enterprise Edition.

Data warehousing
SQL Server includes tools for extracting and analyzing summary data for online
analytical processing (OLAP). SQL Server also includes tools for visually designing
databases and analyzing data using English-based questions.

System integration with other server software

SQL Server integrates with e-mail, the Internet, and Windows.
BIBLIOGRAPHY
The following books were referred during the analysis and execution phase of
the project

MICROSOFT .NET WITH C#

Microsoft .net series

ASP .NET 2.0 PROFESSIONAL

Wrox Publishers

ASP .NET WITH C# 2005

Apress Publications

C# COOK BOOK
O reilly Publications

PROGRAMMING MICROSOFT ASP .NET 2.0 APPLICATION

Wrox Professional Guide

BEGINNING ASP .NET 2.0 E-COMMERCE IN C# 2005

Novice to Professional