CHAPTER-I

INTRODUCTION

1.1 ABOUT THE PROJECT

Hospital are the essential part of our lives, providing best medical facilities to
people suffering from various ailments, which may be due to change in climatic
conditions, increased work-load, emotional trauma stress etc. It is necessary for the
hospitals to keep track of its day-to-day activities & records of its patients, doctors,
nurses, ward boys and other staff personals that keep the hospital running smoothly &
successfully.
But keeping track of all the activities and their records on paper is very
cumbersome and error prone. It also is very inefficient and a time-consuming process
Observing the continuous increase in population and number of people visiting the
hospital. Recording and maintaining all these records is highly unreliable, inefficient and
error-prone. It is also not economically & technically feasible to maintain these records
on paper.
Thus keeping the working of the manual system as the basis of our project. We have
developed an automated version of the manual system, named as “Hospital Management
System”.
The main aim of our project is to provide a paper-less hospital up to 90%. It also aims at
providing low-cost reliable automation of the existing systems. The system also provides
excellent security of data at every level of user-system interaction and also provides
robust & reliable storage and backup facilities.
Objectives of the system:
The project “Medical management system” is aimed to develop to maintain the day –
to-day state of admission/discharge of patients, list of doctors, reports generation, and etc.

It is designed to achieve the following objectives:

1. To computerize all details regarding patient details & hospital details.
2. Scheduling the appointment of patient with doctors to make it convenient for both.
3. Scheduling the services of specialized doctors and emergency properly so that
facilities provided by hospital are fully utilized in effective and efficient manner.

1
 4. If the medical store issues medicines to patients, it should reduce the stock status
of the medical store and vice-versa.
5. It should be able to handle the test reports of patients conducted in the pathology
lab of the hospital.
6. The inventory should be updated automatically whenever a transaction is made.
7. The information of the patients should be kept up to date and there record should
be kept in the system for historical purposes.

1.2. SYSTEM SPECIFICATION

1.2.1 HARDWARE SPECIFICATION

Processor : Intel Core i5 @ 2.40GHz

RAM : 4 GB
System type : 32 bits OS
Hard Disk : 320 GB
Monitor : LCD 15 inches (HCL)
Mouse : USB Optical Mouse
Keyboard : Ps2/USB 104 + Multimedia keys

1.2.2 SOFTWARE SPECIFICATION

Operating System : Windows 7 Ultimate
Front-End : VB.NET 2008
Back-End : SQL SERVER 2005

2
1.2.3 FEATURES OF PROGRAMMING TOOLS

THE .NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies

application development in the highly distributed environment of the Internet.
Visual studio .Net has flexibility, allowing one or more language to interoperate to
provide the solution. This cross language compatibility allows to do project at
faster rate. Visual studio .Net has common runtime, which allows the component
to converge into intermediate format and can interact with visual studio.

.NET FEATURES

Microsoft Visual Studio .Net is used as front end tool. The reason for
selecting visual studio .Net as front end tool is as follows:

 Visual Studio .Net has flexibility, allowing one or more language to

interoperate to provide the solution.
 .Net has to provide excellent security when your application is executed
in the system, allowing us to configure the working environment.
 .Net has intelligence feature that make the coding easy and also
dynamic help provide very less coding time.

OBJECTIVES OF .NET FRAMEWORK

 To provide a consistent object-oriented programming environment

whether object codes is stored and executed locally on Internet-
distributed, or executed remotely.
 To provide a code-execution environment to minimizes software
deployment and guarantees safe execution of code.
 Eliminates the performance problems.

3
 There are different types of application, such as Windows-based
applications and Web-based applications. To make communication on distributed
environment to ensure that code be accessed by the .NET Framework can
integrate with any other code.
COMPONENTS OF .NET FRAMEWORK

VB.NET C# VC++.NET …………

Web xml web Windows

Forms services Forms

asp.net

.NET Framework Class library

Common Language Runtime

Win 32
Fig.4.4.1

The .NET Framework has two components: The .NET Framework

class library and the common language runtime as shown in the figure 4.4.1.
The .NET Framework class library facilitates (CTS) that are common to all .NET
languages. The common language runtime consists of (class loader) that load the
IL code of a program into the runtime, which compiles the IL code into native
code, and executes and manage the code to enforce security and type safety, and
provide threaded support.

The .NET Frame Work Class Library

It is a comprehensive, object-oriented collection of reusable types used

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.

4
 The .NET Framework can be hosted by unmanaged components that
load the common language runtime into their processes and initiate the execution
of managed code, thereby creating a software environment that can exploit both
managed and unmanaged features. The .NET Framework not only provides several
runtime hosts, but also supports the development of third-party runtime hosts.

Internet Explorer is an example of an unmanaged application that hosts

the runtime (in the form of a MIME type extension). Using Internet Explorer to
host the runtime to enables embeds managed components or Windows Forms
controls in HTML documents.

The Common Language Runtime (CLR)

The common language runtime is the foundation of the .NET

Framework. It manages code at execution time, providing important services such
as memory management, thread management, removing and also ensures more
security and robustness.

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.

Data Access with ADO.NET

As you develop applications using ADO.NET, you will have different

requirements for working with data. You might never need to directly edit an
XML file containing data - but it is very useful to understand the data architecture
in ADO.NET. ADO.NET offers several advantages over previous versions of
ADO:

 Interoperability
 Maintainability

5
SQL SERVER 2005

A database system is a computerized information system for the management

of data by means of a general purpose software packages called database management
system.SQL Server2005 is the most widely used database in the world. It runs on
virtually every kind of computer. Including IBM mainframes, UNIX-based
minicomputers, Windows NT, and several proprietary hardware-operating system
platforms; it is clearly the world‟s largest RDBMS vendor.

At the time of this writing, SQL Server2005 is the world‟s leading

supplier of software for information management and the world‟s second (only to
Microsoft) largest software company, with annual revenues of $ 7.5 billion. SQL
Server2005 employs approximately 36,000 professionals worldwide. With SQL
Server2005, SQL Server2000 planted itself firmly in recent years as the premiere
RDBMS vendor in both the government and private arenas, both nationally and
internationally. Initially, SQL Server2005 concentrated on its RDBMS. Lately, it
has launched many successful horizontal and vertical products, such as SQL
Server2005 Application Server. Also, SQL Server2005 has provided many capable
development tools over the years, which is perhaps one of the reasons behind its
steady rise to the top.

Features of SQL-SERVER

Microsoft SQL Server is a relational model database server produced by

Microsoft. Its primary query languages are T-SQL and ANSI SQL. The OLAP
Services feature available in SQL Server version 7.0 is now called SQL Server
2005 Analysis Services. The Repository component available in SQL Server
version 7.0 is now called Microsoft SQL Server 2005 Meta Data Services.
References to the component now use the term Meta Data Services. The term
repository is used only in reference to the repository engine within Meta Data
Services Microsoft® SQL Server 2005 features include:

6
Internet Integration

The SQL Server 2005 database engine includes integrated XML

support. It also has the scalability, availability, and security features required to
operate as the data storage component of the largest Web sites. The SQL Server
2005 programming model is integrated with the Windows DNA architecture for
developing Web applications, and SQL Server 2005 supports features such as
English Query and the Microsoft Search Service to incorporate user-friendly
queries and powerful search capabilities in Web applications.

Scalability and Availability

The same database engine can be used across platforms ranging from
laptop computers running Microsoft Windows98 through large, multiprocessor
servers running Microsoft Windows XP Data Center Edition. SQL Server 2005
enterprise Edition supports features such as federated servers, indexed views, and
large memory support that allow it to scale to the performance levels required by
the largest web sites.

Enterprise-Level Database Features

The SQL Server 2005 relational database engine supports the features
required to support demanding data processing environments. The database engine
protects data integrity while minimizing the overhead of managing thousands of
users concurrently modifying the database.

7
 CHAPTER-II
SYSTEM STUDY

2.1 EXISTING SYSTEM

The project entitled “MEDICAL MANAGEMENT SYSTEM” it tries to

overcome the difficulties that were met during manual operation.

In present systems there is hardly any medical service available in remote

locations. Persons needing medical services often need to travel long distances. Even in
urban areas the service is sometimes not available immediately. Patients and doctors are
hardly to communicate with each others.
And also patients had to wait for long time in order to communicate to the doctor.
2.1.1 DRAWBACKS OF EXISTING SYSTEM

 No Security has been provided to the data.

 As the work is manual it consumes lot of time and energy.
 Records of the customers and supplier are not maintained.
 Finding a specific record required searching of more than half of record.
 Since the system is manual report creation takes lots of time
process.
 As the calculations are done manually there is possibility of incorrect calculation
and tasks like sales receipt, stock and purchase bill generations are manually
carried out.

2.2 PROPOSED SYSTEM

The proposed system is developed to create a simple, user friendly and to use
software that avoids the tedious task done by the existing system. The proposed system is
accessible only to authenticated user of the system wherein all users of the system contain
their valid user id and password. The proposed system handles the various requirements
of the Medical. The main requirement of this project is to make the task of inserting the
employee related details, product related details and maintain them very simple and time
saving. After inserting the details it must be retrieved whenever necessary by search
criteria which will give the actual information needed by the valid patient.

8
 The proposed system is a application which is available all the time. The system
provides details of medical services online and allows users to interact with doctors and
other medical personnel. The patients and doctors are interacting with chatting
applications at their relative places. Initially the doctors had got the patients details in the
online by help of admin people in order to communicate.The Medical Management
System is end user application software. The Medical system we are designing that helps
the Hospital and Management to handle those task that had been handled manually.

2.2.1 FEATURES OF PROPOSED SYSTEM

 Gives and stores details of suppliers.

 Keeping record of medicine stock available.
 Maintaining record of customers.
 Stores record of order placed by the patients.
 Gives details of orders to be processed.
 Generates billing information.
 Displays payment status of patients order like total amount to be paid.

2.3 MODULES
1. Educational Level: At least graduate and should be comfortable with English language.
2. Technical Expertise: Should be a high or middle level employee of the organization
comfortable with using general purpose applications on a computer.
2.4 System Features

 Login module

Description

This module records only user and password of the user.

 Patient module

Description

It keeps track of all details about both in-patient and out-patient. Patient id, patient name,
address, admitted date, doctor name, and room no are entered in a form and stored for

9
future reference. Also particular patient details can be viewed in the table using a separate
form with an attribute patient id.

 Inpatient module

Description

Admission request will be made here. Request for admission is made before patient
admitting the hospital.

 Outpatient module

Description

This module manages activities related to patient who visits the Hospital or Resident
Doctor or Consultant Doctor for Medical Consultations, diagnosis and treatment.

 Pathology module

Description

This module Generates reports which will be done in pathology lab of the Hospital.

 Billing module

Description

This module bills the both inpatient and outpatient who comes to hospital. It also
includes Payment details of patients. Depending on the payments bill report is generated.

3. Logical Database Requirements

The proposed information system contains the following data tables in its database
collection.
i. Patient Details table
ii. Doctor Details Table
iii. Room Details Table
iv. Bill Details table

10
 CHAPTER-III
SYSTEM DESIGN AND DEVELOPMENT
The design of the system is essentially a blue print or plan for solution of the
system to be developed. A part of the system or subsystem of a whole system can itself be
considered a system with its own complements.

3.1 FILE DESIGN

The file design is the last phase that indicates the final system and process of the
final system. In the design phase of „MEDICAL MANAGEMENT SYSTEM‟, the
database tables, input screen design and output design etc. are designed.
 The database tables were designed by using all the necessary fields in compact
manner.
 All the input screens in this system are user-friendly and understandable format.
Also the sizes of all the screens are standardized.
 Icons designed in this system are brief, compact and self-explanatory. The icons
are sharp and the user can invoke the system.
 Reports generated here give the minute information, which helps the manager to
take vital decisions.

The importance of software design can be stated with a single word “QUALITY”.
Design is a place where quality is fostered in software development. Design is the only
way where their requirements are accurately translated into finished software product or
system.

3.2 INPUT DESIGN

Input design is the process of converting user-originated inputs to a computer-
based format. The system takes input from the users, processes it and produces an output.
Input design is link that ties the information system into the world of its users. The system
should be users friendly to gain appropriate information to the user. Forms for input
design in this project are:

11
3.3 OUTPUT DESIGN

Output design generally refers to the results and information that are integrated by
the system for many end users. Output is the main reason for developing the system and
the basis on which they evaluate the usefulness of the application

The objective of a system finds its shape in terms of output; Output of a system
can face various forms. The most command are the reports, screen displays, printed
forms, graphical, drawings etc. The basic requirements of output are that, it should be
accurate, timely and of content, medium and layout for its in tented purpose.

External outputs are those whose destination will be outside the Organization.
Interactive outputs are those, in which user uses in communicating directly with
computer.

3.4 DATABASE DESIGN

The Database Management System (DBMS) consists of a collection of
interrelated data and a set of programs to access that data. The collection of data usually
referred to as database. The primary key goal of DBMS is to provide an environment that
is both convenient and efficient to use in retrieving and storing data information.

The term database design can be used to describe many different parts of the
design of an overall database system. Principally and most correctly, it can be thought of
as the logical design of the base data structures used to store the data. In the relational
model these are the tables and views. In an object database the entities and relationships
map directly to object classes and named relationships. However, the term database
design could also be used to apply to the overall process of designing, not just the base
data structures, but also the forms and queries used as part of the overall database
application within the database management system (DBMS).

The process of doing database design generally consists of a number of steps

which will be carried out by the database designer.

12
3.5 SYSTEM DEVELOPMENT

A system development project encompasses all the activities undertaken from the
time at which a potential requirement is identified until the resulting system is fully
implemented and accepted by the end user. The process can involve many stages over a
long period. The following section highlights some fundamental issues to be considered,
outlines the main stages in development and procuring new systems and indicates when
and how the auditor should be involved.

An information system acquired today must not only satisfy present business
needs; it must also be flexible and capable of being enhanced to meet changing
circumstances well into the future. Thus a pre-requisite to the introduction of a new
system is for management to identify and understand their organization‟s mission and its
related information needs. Writing this down helps to ensure common understanding and
direction, and provides a yardstick against which achievement can be measured.

The first step in which the analyst must undertake is to understand the current
system by gathering all information about it. The required data are collected by several
methods like:

 Study of the current manuals

 Observation of the functioning

 Sampling and Research

13
System Design
The purpose of Design phase is to plan a solution for problem specified by the
requirements. System design aims to identify the modules that should be in the system,
the specification of those modules and how the interact with each other to produce the
results. The goal of the design process is to produce a model that can be used later to
build that system. The produced model is called design of the system.

System design is the process of defining the architecture, components, modules,

interfaces and data for a system to satisfy specified requirements. Normally, the design
proceeds in two stages:

 Physical design
 Database design

Physical Design
The physical design is a graphical representation of a system showing the system‟s
internal and external entities and the flow of data into and out of these entities. An
internal entity is an entity within the system that transforms data.
To represent the physical design of the system, we use diagrams like data flow diagrams,
use case diagrams, etc.

3.6 Data Flow Diagrams

The Data Flow Diagram (DFD) is a graphical representation of the flow of data through
an information system. Data flow diagrams are used by systems analysts to design
information-processing systems but also as a way to model whole organizations. The
main merit of DFD is that it can provide an overview of what data a system would
processes, what transformations of data are done, what data are stored and which stored
data is used, and where the result is flow.

14
Standard Symbols used in DFD:

Symbol Name Function

Data Flow Used to connect processes to each other. The

arrowhead indicates direction of data flow.

Process Performs some transformation to input data

to output data.

Source or A source of system inputs or sink of system

sink.(external outputs.
entity)

Data Store A repository of data. Arrowheads indicate

net inputs or net outputs to the store.

Level 0 DFD
A context diagram is a top level (also known as Level 0) data flow diagram. It only
contains one process node (process 0) that generalizes the function of the entire system in
relationship to external entities. In level 0 DFD system is shown as one process.

The Level 0 DFD shows how the system is divided into 'sub-systems' (processes), each of
which deals with one or more of the data flows to or from an external agent, and which

15
together provide all of the functionality of the system as a whole. It also identifies internal
data stores that must be present in order for the system to do its job, and shows the flow
of data between the various parts of the system.

Level-1 DFD:

16
3.7 E-R Diagram
Entity-Relationship Diagram is a graphical representation of entities and their relationship
to each others. It describes how data is related to each other. An entity is a piece of data-
an object or a concept about which data is stored. A relationship is how the data is shared
between entities. In E-R Diagram, there are 3 main Components:

Symbol Name Description

An entity can be any object, place,

Entity person or anything.

An Attribute Describes a property or

Attribute characteristics of an entity.

A Relationship Describes relation

Relationship between entities.

Data Dictionary

1. Doctor Details
Name-Doctor Details

Name Type Size Description

ID Integer ID of the Doctor

Name Varchar 50 Name of the Doctor

Address Varchar 150 Address of the Doctor

Phone Number Varchar 90 Contact number of the doctor

Qualification Varchar 100 Qualification of the Doctor

17
Gender Varchar 30 Gender of the doctor

Room Details
Name-Room Details

Name Type Size Description

Room_no Integer Id of the Room

Room Type Varchar 50 General or Private Room

patient Details

Name- patient Details

Name Type Size Description

Patient_no Integer 20 ID of the Patient

Name Varchar 60 Name of the patient

Age Integer 20 Age of the Patient

Gender Varchar 30 Gender of the Patient
Address Varchar 90 Address of the Patient

Date Datetime 30 Date of admission

Contact Number Varchar 90 Contact number of the patient

Room No Varchar 50 Admitted patient room no.(in case of

IP)

18
Bill Details

Name-Bill Details
Name Type Size Description
Bill_no Integer 20 Number of the Bill

Date Datetime 20 Date at which bill is generated

Patient Id Varchar 50 Id of the patient

Name Varchar 50 Name of the Patient

Age Varchar 50 Age of the patient

Gender Varchar 50 Gender of the Patient

Date of Varchar 50 Date on which patient is admitted

Admission into Hospital
Date of Varchar 50 Date on which patient is Discharged
Discharge from the Hospital
Room Charges Varchar 50 Charges of the room

Pathology fees Varchar 50 Laboratory report Charges

Doctor Fees Varchar 50 Doctor Checkup Fees

Miscellaneous Varchar 50 Other Charges

Total Amount Varchar 100 Total amount of the bill

19
 CHAPTER-IV
SYSTEM TESTING AND IMPLEMENTATION

4.1 SYSTEM TESTING:

A test plan documents the strategy that will be used to verify and ensure that a
product or system meets its design specifications and other requirements. A test plan is
usually prepared by or with significant input from test engineers.

Depending on the product and the responsibility of the organization to which the
test plan applies, a test plan may include a strategy for one or more of the following:

 Design Verification or Compliance test - to be performed during the development

or approval stages of the product, typically on a small sample of units.
 Manufacturing or Production test - to be performed during preparation or
assembly of the product in an ongoing manner for purposes of performance
verification and quality control.
 Acceptance or Commissioning test - to be performed at the time of delivery or
installation of the product.
 Service and Repair test - to be performed as required over the service life of the
product.
 Regression test - to be performed on an existing operational product, to verify that
existing functionality didn't get broken when other aspects of the environment are
changed (e.g., upgrading the platform on which an existing application runs).

A complex system may have a high level test plan to address the overall requirements
and supporting test plans to address the design details of subsystems and components.
Test plan document formats can be as varied as the products and organizations to which
they apply.

20
TEST CASES
A test case has components that describe an input, action or event and an expected
response, to determine if a feature of an application is working correctly.

There are levels in which each test case will fall in order to avoid duplication efforts.

Level 1: In this level you will write the basic test cases from the available

specification and user documentation.

Level 2: This is the practical stage in which writing test cases depend on actual

functional and system flow of the application.

Level 3: This is the stage in which you will group some test cases and write a test

procedure. Test procedure is nothing but a group of small test cases maximum of 10.

Level 4: Automation of the project. This will minimize human interaction with system

and thus QA can focus on current updated functionalities to test rather than remaining
busy with regression testing.

UNIT TESTING
Unit testing comprises the set of tests performed by an individual programmer
prior to integration of the units a larger system. Unit testing comprises functional test,
Performance test, stress test and structure test.

Performance testing determines the amount of execution time spent in various

parts of the unit, program throughout, and response time and device utilization by the
program unit. In Garments Management System, each execution time, program
throughout and response time should be perfect. Stress test are those test designed to
intentionally break to unit. A great deal can be learned about the strengths and limitations
of a program the coding should be short and output information is large and logic is more.

INTEGRATION TESTING

Bottom up integration is the strategy used to integrate the components of software

into a functioning whole. Bottom up integration sting, followed by testing the entire

21
system. In the system sample date was given to check the integration between
disconnection modules.
VALIDATION TESTING

At the end of the integration testing, software is completely assembled as a

package. Interfacing errors have been uncovered and corrected. validation succeeds when
the software functions in a manner that can be reasonably accepted by the students.

This acceptance by the customer is achieved only when all the data validation is
proper. The appropriate input must be given at the respective input box, like number in
the numeric input and date type of input. Even after storing the data it has been taken care
that the same data is not stored more than once.

USER ACCEPTANCE TESTING

User acceptance testing of the system is the key factor the success of any system.
The system under consideration is tested for user acceptance by constantly keeping in
touch with prospective system at the time of development and making change whenever
required. This is done with regard to the input screen design and output screen design.
The user interface testing is important since the user has to declare that the arrangements
made in the frames are convenient and it is satisfied. When the frames where given for
the test, the end user gave suggestions. Since they were much exposed to do the work
manually. Based on their suggestions the frames where modified and put into practice.

22
4.2 SYSTEM IMPLEMENTATION:

When the initial design was done for the system, the client was consulted for the
acceptance of the design so that further proceedings of the system development can be
carried on. After the development of the system a demonstration was given to them about
the working of the system. The aim of the system illustration was to identify any
malfunction of the system. After the management of the system was approved the system
implemented in the concern, initially the system was run parallel with existing manual
system. The system has been tested with live data and has proved to be error free and user
friendly.

Implementation is the process of converting a new or revised system design into an

operational one when the initial design was done by the system; a demonstration was
given to the end user about the working system. After the approval of the system by both
end user and management the system was implemented. System implementation is made
up of many activities. The six major activities as follows:

CODING

Coding is the process of whereby the physical design specifications created by the
analysis team turned into working computer code by the programming team.

TESTING

Once the coding process is begin and proceed in parallel, as each program module
can be tested.

INSTALLATION

Installation is the process during which the current system is replaced by the new
system. This includes conversion of existing data, software, and documentation and work
procedures to those consistent with the new system.

DOCUMENTATION

It is result from the installation process, user guides provides the information of
how the use the system and its flow.

TRAINING AND SUPPORT

Training plan is a strategy for training user so they quickly learn to the new
system. The development of the training plan probably began earlier in the project.

23
 CHAPTER-V
CONCLUSION AND FUTURE ENHANCEMENT

The proposed system is developed to create a simple, user friendly and to use
software that avoids the tedious task done by the existing system. The proposed system is
accessible only to authenticated user of the system wherein all users of the system contain
their valid user id and password. The proposed system handles the various requirements
of the hospital. The administrator of the system has been assigned to make their settings
of the system. He also has the right to see the login details.

The main requirement of this project is to make the task of inserting the doctor
and patient related details, product related details and maintain them very simple and time
saving. After inserting the details it must be retrieved whenever necessary by search
criteria which will give the actual information needed by the valid user. There are several
reports that are generated based on the employees and room which will show doctor and
employee information, salary records and attendance. It will also show room check in
details and check out details. The Medical Management System is end user application
software. The garments system we are designing that helps the hospital to handle those
task that had been handled manually. The tasks like:

 Keeping record of raw material purchased.

 Gives and stores details of suppliers.
 Keeping record of stock available.
 Maintaining record of customers.
 Generates billing information.

24
FUTURE ENHANCEMENT

This project has very effective useful for handling day activates in Medical
management. All the type of updating can be made through system whenever necessary.
The system has been designed in such a manner the reports are generated at each and
every stage of the transaction process. Implementing this project reduces burden due to
the manual reports. The maintenance of this is easier one. The software obtained the
number of reports within a time.

The software created is attractive and user-friendly. It is highly interactive too.

The software appears more flexible, which is completely menu-driven, it gives advantage,
as it needs less typing by the user. It maintains data consistency. The system reduces
workload and produces adequate and timely information as and when required.

Although this “MEDICAL MANAGEMENT SYSTEM” almost satisfies all the

requirements of the user (admin), there is further development in this system into a better
from in the following areas.

 Further security can be improved.

 The design of this package can be extended.

25
 CHAPTER-VI
BIBLIOGRAPHY

I. BOOK REFERENCES

1. Alistair McMonnies,(2004) “OBJECT-ORIENTED PROGRAMMING IN

VISUAL BASIC.NET”, Pearson Education, and ISBN: 81-297-0649-0, First
Indian Reprint 2004.

2. Elias M.Awad,(1998) “SYSTEM ANALYSIS AND DESIGN”, Galgotia

Publication Second Edition.

3. Jittery R.Shapiro,(2005) "THE COMPLETE REFERENCE VISUAL BASIC

.NET” Edition 2002, Tata McGraw-Hill, Publishing Company Limited, New
Delhi.

4. Leonard Lobel and Andrew Brust “PROGRAMMING MICROSOFT SQL

SERVER” Edition 2012, Pearson Education, ISBN: 0735658226

5. Roger S. Pressman, (2008) “SOFTWARE ENGINEERING PRACTITIONERS

APPROACH” Mc-Graw Hill International Edition, Sixth Edition.

II. URL REFERENCES

1. http://www.w3schools.com
2. http://www.projectideas.co.in
3. http://www.codeproject.com
4. http://www.tutorialpoint.com

26
 APPENDICES
Screenshot and Source Code.

Inpatient Registration Form

27
Outpatient Registration Form

28
Doctor Information form

29
Room Information Form

30
Inpatient Billing Form

31
Outpatient Billing Form

32
Pathology Form

33
Inpatient Search Form

34
Outpatient Search Form

35
REPORTS

Inpatient Registration Form

36
Outpatient Registration Form

37
Doctor Information form

38