Hospital Management System

HOSPITAL MANAGEMENT SYSTEM
A Project work submitted to the

DEPARTMENT O !OMP"TER APPLI!ATIONS
P#$#N# ARTS AND S!IEN!E !OLLEGE
THIR"MANGALAM#
Submitted b%
E#AR"L &EN'AMIN !HANDR" (Re) No * A+,-./012
R#&ALA'I (Re) No * A+,-./032
BCA-IIIrd year
P.K.N. Arts and Science College
Thirumangalam.
Guided b%
Mrs#4#PANDISEL4I M#Sc#5M#Phi6#5
He7d o8 the De97rtme:t
Department O computer Applications
P.K.N. Arts and Science College
Thirumangalam
! Ailiated to "adurai Kamara# $ni%ersity&
Thirumangalam.
THIR"MANGALAM
&ONAIDE !ERTII!ATE
Certiied that the pro#ect 'or( entitled ; HOSPITAL
MANAGEMENT SYSTEM< su)mitted )y E#AR"L &EN'AMIN
!HANDR" ! *eg No + A+,-./01& to the Department o Computer
Applications, P.K.N. Arts and Science College, under the guidance
o Mrs#4#PANDISEL4I5 M#Sc5 M#Phi6#5 He7d o8 the De97rtme:t
in partial ulillment o the re-uirements or the $nder .raduate
degree in Bachelor o Computer Applications.
"rs. /. PANDIS01/I ". Sc, ". Phi l . , "rs. /. PANDIS01/I ". Sc, ". Phi l . ,
PRO'E!T G"IDE HEAD O THE DEPARTMENT
Su)mitted or %i%a %oice e2amination held on 3333333333
INTERNAL E=AMINER E=TERNAL E=AMINER

THIR"MANGALAM
&ONAIDE !ERTII!ATE
Certiied that the pro#ect 'or( entitled ; HOSPITAL
MANAGEMENT SYSTEM< su)mitted )y R#&ALA'I ! *eg no +
A+,-./03& to the Department o Computer Applications, P.K.N.
Arts and Science College, under the guidance o
Mrs#4#PANDISEL4I5 M#Sc5 M#Phi6#5 He7d o8 the De97rtme:t in
partial ulillment o the re-uirements or the $nder .raduate
degree in Bachelor o Computer Applications.
"rs. /. PANDIS01/I ". Sc, ". Phi l . , "rs. /. PANDIS01/I ". Sc, ". Phi l . ,
PRO'E!T G"IDE HEAD O THE DEPARTMENT
Su)mitted or %i%a %oice e2amination held on 3333333333
INTERNAL E=AMINER E=TERNAL E=AMINER

THIR"MANGALAM
DE!LARATION
4e here)y declare that this 'or( 'as carried out )y us under the
guidance and Super%ision o Mrs#4#PANDISEL4I M#Sc#5M#Phi6#5 He7d
o8 the De97rtme:t. The period o pro#ect 'or( is 5rom No%em)er 6778
To April 6797. This pro#ect 'or( is su)mitted to P.K.N. Arts and Science
College, Department o Computer Applications in partial ulillment or
the re-uirement o Degree in Bachelor o Computer Applications.
4e declare that this 'or( has not )een su)mitted any'here else or
the a'ard o any other degree.
E#AR"L &EN'AMIN !HANDR" R#&ALA'I
A!$NO>LEDGEMENT
5irst o all 4e 'ould li(e to e2press our heartul than(s to : The
Almighty .od: or this opportunity, 'hich he rendered to us and gi%es the
physical strength and pleasant mind to complete this pro#ect 'or(.
4e than( our honora)le Principal Dr#'# MAHATMAN RAO5
Ph#D5 or his inspiration. And 'e than( Mrs#4#PANDISEL4I M#Sc#5
M#Phi65 our ;ead o the Department and also my pro#ect guide or the
correct guidance and ad%ice.
4e also than( our department sta
Mr#A#&767ji 5 MS(IT?M25 M#Phi6#5
Ms#D#Muru)7su:d7ri 5 M#Sc(IT?!S2#5
Mr#R#Pr7b7k7r7:5 M!A#5
Mr#$#'7:7k7r7j5 M!A#5
'ho all encourage and satisy our needs to inish this pro#ect 'or(.
4e are %ery happy to than( our la) co-ordinator, la) assistants or
gi%ing a 'ell e-uipped la) or de%eloping this pro#ect 'or(.

4e e2tent our than(s and gratitude to our parents, 5riends and those 'ho
helped us directly and indirectly or the successul completion o this
pro#ect 'or(.
!ONTENTS
S#No !o:te:ts
9. Introduction
Synopsis
Company Proile
6. Pro#ect O)#ecti%e
<. System Speciication
System Coniguration
Sot'are Speciication
=. System Analysis
02isting System
Proposed System

>. System Design
Input Design
Output Design
?. Data)ase Design
@. Datalo' Diagram
A. System Testing
8. Sample Codings
97. Screenshots
99. Bi)iliography
96. 4e)iliography
INTROD"!TION
SYNOPSIS
This pro#ect 'ill automate the daily operations o 1I50 1IN0 hospital.
The pro#ect (eeps trac( o the sta and patient !in-patient, out-patient& details. It
also ta(es care o the 'ard, medical, in%oice and the doctorBs appointment
details. The system generates the daily 'ard a%aila)ility, the status o the
operation theatres and IC$.
;OSPITA1 "ANA.0"0NT is an integrated ;ospital Inormation
System, 'hich addresses all the ma#or unctional areas o multi-specialty
hospitals. The ;OSPITA1 "ANA.0"0NT ena)les )etter patient care, patient
saety, patient conidentiality, eiciency, reduced costs and )etter management
inormation system. It pro%ides easy access to critical inormation thus ena)ling
the management to ta(e )etter decisions on time.
This pro#ect deals 'ith processing o each and e%ery department in the
hospital. This pro#ect sincerely aims to reduce the manual processing o each
department.
The Scope o the pro#ect ta(es care o the details o each and e%ery
department. These details gi%es the doctor, stas, specialists and patient details
including their salary, attendance , doctorBs appointments and the )illing
system. The details o Doctor and sta help the hospital to maintain the record
o e%ery person. Their attendance details help them to (no' a)out their
attenti%e presence 'hile salary is calculated. The )illing system pro%ides an
eicient 'ay or calculating )ill details o the patients.
!OMPANY PROILE
4i:7%7)7m Hos9it76s is a multi-specialty, tertiary care hospital
e2tending -uality health care ser%ice to people in and around "adurai or the
past 96 years. The hospital 'as ounded )y Dr.S.*a#endran 'ho is a leading
1aser and 1aparoscopic surgeon. The hospital is located at Dhanappa "udali
Street 'hich is %ery near to "adurai "eena(shi Amman Temple. Its head
oice is located at *oyapettai, Chennai. Its moti%e is to C*each the
$nreached:.
Histor% o8 the 4i:7%7)7m Hos9it76s*
/inayagam ;ospital 'as irst started at 988A 'ith ten sta and i%e Beds
or inpatients. In the )eginning it started pro%iding ser%ices to the outpatients
and inpatients.
In the year 6777, the hospital e2tends its ser%ices such as D-*ay and Scan
Centre. Ater that, the hospital de%eloped rapidly. In the year 677> 1aser Cancer
Treatment 5acility 'as started )y the amous leading tamil actor Surya 'ho is
the relati%e to Dr.S.*a#endran. 1ast year the hospital is 'ell urnished and it
pro%ides the ollo'ing acilities.
Capsule 0ndoscopy
0ndoscopy !Diagnostic E Therapeutic&
Colonoscopy
Sigmoidoscopy
Bronchoscopy
1aser Surgery !ND,FA.&
1aparoscopy !Key ;ole& Surgery
.eneral Surgeries
$ltra Sound and Color Doppler !Scan E 0C;O&
Dental Care
Psychiatric Treatments
No' the hospital is amous or its laser and laparoscopic surgeries. The
hospital no' consists o 96 specialists , = duty doctors and =7 sta mem)ers. It
also pro%ides am)ulance ser%ices to the patients. The hospital is unctionally
a%aila)le to the pu)lic 6= hours a day.
The hospital also pro%ides star health insurance plan or go%ernment
employees and also (alaignar (appeettu thittam. The hospital is rapidly
de%eloping to'ards the moti%e C Ser%ice to the human is the ser%ice to the
.od C.
I: 8uture5 the hos9it76 h7@e 967:s to im96eme:t the 8o66owi:)
9ro)r7mmes#
Identiying Anemia in rural 4omen and Children
Pre%enti%e health care in rural areas.
PRO'E!T O&'E!TI4E
PRO'E!T O&'E!TI4E
To computeriGe all details regarding patient details E hospital
details.
To automate the process o 'ard entries.
To maintain records eecti%ely.
To manage current status o sta and doctor a%aila)lity.
The pro#ect has inormation regarding the inpatient details,
outpatient details, Billing details and Am)ulance details.
This 9roject i:c6udes modu6es such 7s
9& Admission
Inpatient
Outpatient
6& Sta Details
Payroll
Personnel Details
Attendance
On Duty
Shit
<& Billing
Inpatient
Outpatient

=& Consultation

>& 4ard Details
?& Am)ulance Ser%ice
Dri%er
Am)ulance
MOD"LES REA"IRED
Admission :
This module records )asic patient related inormation, 'hich is collected
'hen the patient %isits the hospital or the irst time. 0ach patient is allocated
a uni-ue patient identiication num)ers also (no'n as ;ospital No.
Patient Details:
It (eeps trac( o all details a)out )oth in-patient and out-patient.
Patient id, patient name, address, admitted date, doctor name, room no are
entered in a orm and stored or uture reerence. Also particular patient details
can )e %ie'ed in the ta)le using a separate orm 'ith a attri)ute patient id.
Outpatient:
This module manages acti%ities related to patient 'ho %isits the ;ospital
*esident Doctor or Consultant Doctor or "edical Consultations, diagnosis and
treatment.
Inpatient:
Admission re-uest 'ill )e made here. *e-uest or admission is made
)eore patient admitting the hospital.
Staff Details:
It (eeps trac( o all details a)out doctors and stas o the hospital. stas,
Doctors, Nurses name, sta id, address, -ualiication, cell no, e-mail are entered
and stored in a separate orm. Indi%idual sta details can )e %ie'ed in the ta)le
using a separate orm 'ith a attri)ute Sta id.
Salary Details:
This module contains the details salary or the doctors and nurse. This
salary calculated )asic salary, P5, ;*A, and year increment or the stas rom
date o #oining automatically calculated.
Consultation Details :
This module contains the details or the inpatient 'hich includes disease
name, type o treatment and medicine gi%en to them.
Billing Details:
This module )ills the )oth inpatient and outpatient 'ho comes to
hospital.
Ward Details:
This module enters and stores the details a)out each 'ard o the hospital
or uture reerence. Indi%idual 'ard detail can )e %ie'ed in the ta)le using
'ard id .The attri)utes used in storing a 'ard detail is 'ard id, 'ard name,
loor no, no o rooms.
Ambulance Services:
Another ser%ice or Am)ulance a%aila)ility, out time, in time, search or
the am)ulance 'ent to place or petrol and uel e2penses.
SYSTEM
SPE!II!ATION
SYSTEM !ONIG"RATION
HARD>ARE REA"IREMENTS
P*OC0SSO* +INT01 P0NTI$" = !O*&;I.;0*
*A" +>96 "B E ABO/0
;A*D DISK D*I/0 + >77 "B 5*00 SPAC0 O* ABO/0
P*INT0* + INK-H0T P*INT0*
P0N D*I/0 + >96"B.
SOT>ARE REA"IREMENTS
P*O.*A""IN. 1AN.$A.0 + /IS$A1 P*O.*A""IN.
BACK0ND +"S SI1 S0*/0*-677>
5*ONT 0ND +/IS$A1 BASIC.N0T
OP0*ATIN. SFST0" + 4INDO4S DP E ;I.;0* /0*SION
SOT>ARE SPE!II!ATION
4IS"AL ST"DIO # NET
/isual Studio .N0T is a complete set o de%elopment tools or )uilding
ASP 4e) applications
D"1 4e) ser%ices
des(top applications
mo)ile applications
/isual Basic .N0T, /isual CJJ .N0T, and /isual CK .N0T all use the
same integrated de%elopment en%ironment !ID0&, 'hich allo's them to share
tools and acilitates in the creation o mi2ed-language solutions.
4isu76 &7sic
/isual Basic has )een updated to include many ne' and impro%ed
language eatures that ma(e it a po'erul o)#ect-oriented programming
language. These eatures include inheritance, interaces, and o%erloading,
among others. /isual Basic also no' supports structured e2ception handling,
and custom attri)utes. In addition, /isual Basic supports multithreading.
"ultithreading is the a)ility to assign indi%idual tas(s to separate processing
threads.
!B
/isual CK, pronounced C sharp, is a ne' o)#ect-oriented programming
language that is an e%olution o C and CJJ, pro%iding a simple and type-sae
language or de%eloping applications.
!CC
"anaged 02tensions or CJJ and attri)uted programming are #ust some
o the enhancements made to the CJJ language. "anaged 02tensions simpliy
the tas( o migrating e2isting CJJ applications to the ne' .N0T 5rame'or(.
Attri)utes, li(e CJJ (ey'ords, are used in your source iles and interpreted )y
the compiler. Attri)utes are designed to pro%ide a -uic( and eicient method to
simpliy CO" programming 'ith /isual CJJ.
'Scri9t
HScript has )een updated to )e a class-)ased, o)#ect-oriented scripting
language that maintains ull )ac('ards compati)ility 'ith pre%ious %ersions o
HScript. HScript no' pro%ides class-)ased o)#ects, typed %aria)les, true compiled
code, and cross-language support through Common 1anguage Speciication
!C1S& compliance. The primary role o HScript is de%elopment o 4e) sites
'ith ASP.N0T and customiGation o applications 'ith Script or the .N0T
5rame'or(.
T%9es o8 8orms used i: #Net
>eb orms
4e) 5orms are an ASP.N0T technology that you use to create
programma)le 4e) pages. 4e) 5orms render themsel%es as )ro'ser-
compati)le ;T"1 and script, 'hich allo's any )ro'ser on any platorm to
%ie' the pages. $sing 4e) 5orms, you create 4e) pages )y dragging and
dropping controls onto the designer and then adding code, similar to the 'ay
that you create /isual Basic orms
>i:dows orms
4indo's 5orms is the ne' platorm or "icrosot 4indo's application
de%elopment, )ased on the .N0T 5rame'or(. This rame'or( pro%ides a clear,
o)#ect-oriented, e2tensi)le set o classes that ena)les you to de%elop rich
4indo's applications. Additionally, 4indo's 5orms can act as the local user
interace in a multi-tier distri)uted solution.
The #NET r7mework
O@er@iew
The .N0T 5rame'or( is a ne' computing platorm that simpliies
application de%elopment in the highly distri)uted en%ironment o the Internet.
The .N0T 5rame'or( is designed to ulill the ollo'ing o)#ecti%es+
To pro%ide a consistent o)#ect-oriented programming en%ironment
'hether o)#ect code is stored and e2ecuted locally, e2ecuted locally )ut
Internet-distri)uted, or e2ecuted remotely.
To pro%ide a code-e2ecution en%ironment that minimiGes sot'are
deployment and %ersioning conlicts.
To pro%ide a code-e2ecution en%ironment that guarantees sae e2ecution
o code, including code created )y an un(no'n or semi-trusted third
party.
To pro%ide a code-e2ecution en%ironment that eliminates the perormance
pro)lems o scripted or interpreted en%ironments.
To ma(e the de%eloper e2perience consistent across 'idely %arying types
o applications, such as 4indo's-)ased applications and 4e)-)ased
applications.
To )uild all communication on industry standards to ensure that code
)ased on the .N0T 5rame'or( can integrate 'ith any other code.
The .N0T 5rame'or( is a multi-language en%ironment or )uilding,
deploying, and running D"1 4e) ser%ices and applications.
!ommo: L7:)u7)e Ru:time Despite its name, the runtime actually
has a role in )oth a componentLs runtime and de%elopment time
e2periences. 4hile the component is running, the runtime is responsi)le
or managing memory allocation, starting up and stopping threads and
processes, and enorcing security policy, as 'ell as satisying any
dependencies that the component might ha%e on other components. At
de%elopment time, the runtimeLs role changes slightlyM )ecause it
automates so much !or e2ample, memory management&, the runtime
ma(es the de%eloperLs e2perience %ery simple, especially 'hen compared
to CO" as it is today. In particular, eatures such as relection
dramatically reduce the amount o code a de%eloper must 'rite in order to
turn )usiness logic into a reusa)le component.
":i8ied 9ro)r7mmi:) c67sses The rame'or( pro%ides de%elopers
'ith a uniied, o)#ect-oriented, hierarchical, and e2tensi)le set o class
li)raries !APIs&. Currently, CJJ de%elopers use the "icrosot 5oundation
Classes and Ha%a de%elopers use the 4indo's 5oundation Classes. The
rame'or( uniies these disparate models and gi%es /isual Basic and
HScript programmerBs access to class li)raries as 'ell. By creating a
common set o APIs across all programming languages, the common
language runtime ena)les cross-language inheritance, error handling, and
de)ugging. All programming languages, rom HScript to CJJ, ha%e
similar access to the rame'or( and de%elopers are ree to choose the
language that they 'ant to use.
ASP#NET ASP.N0T )uilds on the programming classes o the .N0T
5rame'or(, pro%iding a 4e) application model 'ith a set o controls and
inrastructure that ma(e it simple to )uild ASP 4e) applications.
ASP.N0T includes a set o controls that encapsulate common ;T"1 user
interace elements, such as te2t )o2es and drop-do'n menus. These
controls run on the 4e) ser%er, ho'e%er, and push their user interace as
;T"1 to the )ro'ser. On the ser%er, the controls e2pose an o)#ect-
oriented programming model that )rings the richness o o)#ect-oriented
programming to the 4e) de%eloper. ASP.N0T also pro%ides
inrastructure ser%ices, such as session state management and process
recycling that urther reduce the amount o code a de%eloper must 'rite
and increase application relia)ility. In addition, ASP.N0T uses these
same concepts to ena)le de%elopers to deli%er sot'are as a ser%ice.
Debu))i:)
/isual Studio .N0T pro%ides a single integrated de)ugger or all /isual
Studio languages, including /isual Basic and CK. A ne', uniied interace
com)ines eatures o the /isual CJJ and /isual Basic ?.7 de)uggers, as 'ell as
many ne' eatures.
!rossDL7:)u7)e Debu))i:)
$sing the integrated de)ugger, you can de)ug pro#ects that are part o the
same solution )ut are 'ritten in dierent languages. 5or e2ample, you can
de)ug a solution that contains a pro#ect consisting o a /isual Basic or /isual
CK user interace application and a /isual CJJ ser%er application, and you can
step )ac( and orth )et'een these pro#ects, or e2ample rom "anaged
02tensions or CJJ to /isual Basic and )ac( to "anaged 02tensions or CJJ.
Att7chi:) to 7 Ru::i:) Pro)r7m
Fou can attach the de)ugger to a program that is already running and
de)ug the program. Attaching to a running program 'or(s the same 'ay
'hether the program is running on a host machine or a remote machine. The
program does not need to )e launched in the /isual Studio .N0T integrated
de%elopment en%ironment !ID0&.
Remote Debu))i:)
Fou can attach to and de)ug a process that is running on a dierent
computer rom the one on 'hich you are running /isual Studio. 5or e2ample, i
you are de)ugging a 4indo's 5orms client application and an D"1 4e)
ser%ice it uses, you can run /isual Studio on the client and then attach to the
ser%er that is pro%iding the D"1 4e) ser%ice. Fou typically perorm this (ind
o de)ugging or 4e) 5orms pro#ects or ASP.N0T 4e) Ser%ice pro#ects.
Debu))i:) Mu6tithre7ded A996ic7tio:s
Ne' or /isual Basic users is the a)ility to 'rite and de)ug
multithreaded applications. The Threads 'indo' can )e used to %ie' the
threads that are running and to s'itch conte2t.
Debu))i:) Mu6ti96e Pro)r7ms
Fou can de)ug multiple programs )y attaching to running programs or )y
launching multiple programs rom the /isual Studio ID0.
Debu))i:) ASP#NET >eb A996ic7tio:s
Coniguring de)ugging or ASP.N0T 4e) applications has )een
signiicantly impro%ed. In most cases you can simply choose Start rom the
De)ug menu and the de)ugger 'ill automatically attach to the ASP.N0T
'or(er process or de)ugging 4e) 5orms, e%en i the ASP.N0T 'or(er
process is running on a dierent ser%er. Security coniguration has )een made
easier )y the addition o a de)ugger users group.
#NET r7mework !67sses 8or Debu))i:) 7:d !ode Tr7ci:)
Fou can include instrumentation code in your "icrosot .N0T
application. Se%eral .N0T 5rame'or( classes are a%aila)le or use )oth in
de)ugging and in instrumenting your code.
4isu76 &7sic#Net
New i: 4isu76 &7sic
>eb De@e6o9me:t* /isual Basic and CK include support or 4e) 5orms
and D"1 4e) ser%ices. 4e) 5orms allo' you to easily and -uic(ly create the
)ro'ser-)ased interace or ASP.N0T 4e) applications. D"1 4e) ser%ices
allo' you to pac(age a /isual Basic or CK method and ma(e it accessi)le on
the 4e).
New i: D7t7* ADO.N0T pro%ides scala)le, high-perormance data
access or all /isual Studio
Applications )ased on the .N0T 5rame'or(. Fou can access data directly in the
data source or create an in-memory cache N a dataset N or 'or(ing 'ith
disconnected data. Fou can also 'or( directly 'ith D"1 as relational data or
)y creating and editing D"1 iles directly.
>i:dows orms 7:d !o:tro6s* Fou can use 4indo's 5orms and
controls to create the presentation layer o a distri)uted application. 4indo's
5orms pro%ides a clear, o)#ect-oriented, e2tensi)le set o classes that ena)le you
to de%elop rich 4indo's applications.
New i: Projects* Fou can use the Pro#ect templates in this %ersion to
easily create %arious types o 4indo's and ASP.N0T 4e) applications and
controls. Pro#ect templates set necessary reerences or you, import namespaces,
and add deault items to your pro#ects.
!om9o:e:ts 7:d !om9o:e:t Authori:)* Fou can use non%isual
components and associated eatures to incorporate resources such as message
-ueues, e%ent logs, and perormance counters into your applications. This
%ersion also oers *AD support or component creation %ia the Component
Designer and rame'or( classes that help you create controls and components.
New i: Debu))i:)* Fou can no' de)ug pro#ects that are part o the
same solution )ut 'ritten in dierent languages, perorm remote de)ugging,
and implement trace unctionality throughout your code to retrie%e inely tuned
output.
EEte:sibi6it% 7:d Autom7tio:* /isual Studio .N0T includes a
programma)le o)#ect model that pro%ides access to the underlying components
and e%ents o the integrated de%elopment en%ironment !ID0&. This model
allo's you to e2tend the unctionality o the ID0, automate repetiti%e tas(s, and
integrate the ID0 'ith other applications.
ADO (Acti@eE D7t7 Objects2#Net
"ost /isual Basic and /isual CK applications re%ol%e around reading
and updating inormation in data)ases. To allo' data integration in distri)uted,
scala)le applications, /isual Studio .N0T pro%ides support or a ne' generation
o data access technology+ ADO.N0T.
D7t7 Access with ADO#NET
As you de%elop applications using ADO.N0T, you 'ill ha%e dierent
re-uirements or 'or(ing 'ith data. In some cases, you might simply 'ant to
display data on a orm. In other cases, you might need to de%ise a 'ay to share
inormation 'ith another company.
No matter 'hat you do 'ith data, there are certain undamental concepts
that you should understand a)out the data approach in ADO.N0T. Fou might
ne%er need to (no' some o the details o data handling N or e2ample, you
might ne%er need to directly edit an D"1 ile containing data N )ut it is %ery
useul to understand the data architecture in ADO.N0T, 'hat the ma#or data
components are, and ho' the pieces it together.
New i: ADO#Net
ADO#NET Does Not De9e:d O: !o:ti:uous6% Li@e !o::ectio:s
In traditional clientOser%er applications, components esta)lish a connection to
a data)ase and (eep it open 'hile the application is running. 5or a %ariety o
reasons, this approach is impractical in many applications+
Open data)ase connections ta(e up %alua)le system resources. In most
cases, data)ases can maintain only a small num)er o concurrent
connections. The o%erhead o maintaining these connections detracts
rom o%erall application perormance.
Similarly, applications that re-uire an open data)ase connection are
e2tremely diicult to scale up. An application that does not scale up 'ell
might perorm accepta)ly 'ith our users )ut 'ill li(ely not do so 'ith
hundreds. ASP.N0T 4e) applications in particular need to )e easily
scala)le, )ecause traic to a 4e) site can go up )y orders o magnitude
in a %ery short period.
In ASP.N0T 4e) applications, the components are inherently
disconnected rom each other. The )ro'ser re-uests a page rom the
ser%erM 'hen the ser%er has inished processing and sending the page, it
has no urther connection 'ith the )ro'ser until the ne2t re-uest. $nder
these circumstances, maintaining open connections to a data)ase is not
%ia)le, )ecause there is no 'ay to (no' 'hether the data consumer !the
client& re-uires urther data access.
A model )ased on al'ays-connected data can ma(e it diicult and
impractical to e2change data across application and organiGational
)oundaries using a connected architecture. I t'o components need to
share the same data, either ha%e to )e connected, or a 'ay must )e
de%ised or the components to pass data )ac( and orth.
5or all these reasons, data access 'ith ADO.N0T is designed around an
architecture that uses connections sparingly. Applications are connected to the
data)ase only long enough to etch or update the data. Because the data)ase is
not holding on to connections that are largely idle, it can ser%ice many more
users.
&e:e8its o8 ADO#NET
I:tero9er7bi6it%
ADO.N0T applications can ta(e ad%antage o the le2i)ility and )road
acceptance o D"1. Because D"1 is the ormat or transmitting datasets across
the net'or(, any component that can read the D"1 ormat can process data. In
act, the recei%ing component need not )e an ADO.N0T component at all+ The
transmitting component can simply transmit the dataset to its destination
'ithout regard to ho' the recei%ing component is implemented. The destination
component might )e a /isual Studio application or any other application
implemented 'ith any tool 'hatsoe%er. The only re-uirement is that the
recei%ing component )e a)le to read D"1. As an industry standard, D"1 'as
designed 'ith e2actly this (ind o interopera)ility in mind.
M7i:t7i:7bi6it%
In the lie o a deployed system, modest changes are possi)le, )ut
su)stantial, architectural changes are rarely attempted )ecause they are so
diicult. That is unortunate, )ecause in a natural course o e%ents, such
su)stantial changes can )ecome necessary. 5or e2ample, as a deployed
application )ecomes popular 'ith users, the increased perormance load might
re-uire architectural changes. As the perormance load on a deployed
application ser%er gro's, system resources can )ecome scarce and response
time or throughput can suer. 5aced 'ith this pro)lem, sot'are architects can
choose to di%ide the ser%erLs )usiness-logic processing and user-interace
processing onto separate tiers on separate machines. In eect, the application
ser%er tier is replaced 'ith t'o tiers, alle%iating the shortage o system
resources.
Pro)r7mm7bi6it%
ADO.N0T data components in /isual Studio encapsulate data access
unctionality in %arious 'ays that help you program more -uic(ly and 'ith
e'er mista(es. 5or e2ample, data commands a)stract the tas( o )uilding and
e2ecuting SI1 statements or stored procedures.
Per8orm7:ce
5or disconnected applications, ADO.N0T datasets oer perormance
ad%antages o%er ADO disconnected recordsets. 4hen using CO" marshalling
to transmit a disconnected recordset among tiers, a signiicant processing cost
can result rom con%erting the %alues in the recordset to data types recogniGed
)y CO". In ADO.N0T, such data-type con%ersion is not necessary.
Sc767bi6it%
Because the 4e) can %astly increase the demands on your data,
scala)ility has )ecome critical. Internet applications ha%e a limitless supply o
potential users. Although an application might ser%e a doGen users 'ell, it might
not ser%e hundreds Nor hundreds o thousands N e-ually 'ell. An application
that consumes resources such as data)ase loc(s and data)ase connections 'ill
not ser%e high num)ers o users 'ell, )ecause the user demand or those limited
resources 'ill e%entually e2ceed their supply.
!om97riso: o8 ADO#NET 7:d ADO
Fou can understand the eatures o ADO.N0T )y comparing them to
particular eatures o Acti%eD Data O)#ects !ADO&.
I:Dmemor% Re9rese:t7tio:s o8 D7t7
In ADO, the in-memory representation o data is the recordset. In
ADO.N0T, it is the dataset. There are important dierences )et'een them.
Number o8 T7b6es
A recordset loo(s li(e a single ta)le. I a recordset is to contain data rom
multiple data)ase ta)les, it must use a HOIN -uery, 'hich assem)les the data
rom the %arious data)ase ta)les into a single result ta)le.
In contrast, a dataset is a collection o one or more ta)les. The ta)les
'ithin a dataset are called data ta)lesM speciically, they are DataTa)le o)#ects.
I a dataset contains data rom multiple data)ase ta)les, it 'ill typically contain
multiple D7t7T7b6e o)#ects. That is, each D7t7T7b6e o)#ect typically
corresponds to a single data)ase ta)le or %ie'. In this 'ay, a dataset can mimic
the structure o the underlying data)ase.
A dataset usually also contains relationships. A relationship 'ithin a
dataset is analogous to a oreign-(ey relationship in a data)ase Nthat is, it
associates ro's o the ta)les 'ith each other. 5or e2ample, i a dataset contains
a ta)le a)out in%estors and another ta)le a)out each in%estorLs stoc( purchases,
it could also contain a relationship connecting each ro' o the in%estor ta)le
'ith the corresponding ro's o the purchase ta)le.
Because the dataset can hold multiple, separate ta)les and maintain
inormation a)out relationships )et'een them, it can hold much richer data
structures than a recordset, including sel-relating ta)les and ta)les 'ith many-
to-many relationships.
D7t7 N7@i)7tio: 7:d !ursors
In ADO you scan se-uentially through the ro's o the recordset using the
ADO Mo@eNeEt method. In ADO.N0T, ro's are represented as collections, so
you can loop through a ta)le as you 'ould through any collection, or access
particular ro's %ia ordinal or primary (ey inde2. D7t7Re67tio: o)#ects
maintain inormation a)out master and detail records and pro%ide a method that
allo's you to get records related to the one you are 'or(ing 'ith. 5or e2ample,
starting rom the ro' o the In%estor ta)le or PNate Sun,P you can na%igate to the
set o ro's o the Purchase ta)le descri)ing his purchases.
A cursor is a data)ase element that controls record na%igation, the a)ility
to update data, and the %isi)ility o changes made to the data)ase )y other users.
ADO.N0T does not ha%e an inherent cursor o)#ect, )ut instead includes data
classes that pro%ide the unctionality o a traditional cursor. 5or e2ample, the
unctionality o a or'ard-only, read-only cursor is a%aila)le in the ADO.N0T
D7t7Re7der o)#ect. 5or more inormation a)out cursor unctionality, see Data
Access Technologies.
Mi:imiFed O9e: !o::ectio:s
In ADO.N0T you open connections only long enough to perorm a
data)ase operation, such as a Select or $pdate. Fou can read ro's into a dataset
and then 'or( 'ith them 'ithout staying connected to the data source. In ADO
the recordset can pro%ide disconnected access, )ut ADO is designed primarily
or connected access.
There is one signiicant dierence )et'een disconnected processing in
ADO and ADO.N0T. In ADO you communicate 'ith the data)ase )y ma(ing
calls to an O10 DB pro%ider. In ADO.N0T you communicate 'ith the data)ase
through a data adapter !an OleD)DataAdapter or S-lDataAdapter o)#ect&, 'hich
ma(es calls to an O10 DB pro%ider or the APIs pro%ided )y the underlying data
source. The important dierence is that in ADO.N0T the data adapter allo's
you to control ho' the changes to the dataset are transmitted to the data)ase N
)y optimiGing or perormance, perorming data %alidation chec(s, or adding
any other e2tra processing.
Sh7ri:) D7t7 &etwee: A996ic7tio:s
Transmitting an ADO.N0T dataset )et'een applications is much easier
than transmitting an ADO disconnected recordset. To transmit an ADO
disconnected recordset rom one component to another, you use CO"
marshalling. To transmit data in ADO.N0T, you use a dataset, 'hich can
transmit an D"1 stream.
The transmission o D"1 iles oers the ollo'ing ad%antages o%er
CO" marshalling+
Richer d7t7 t%9es
CO" marshalling pro%ides a limited set o data types N those deined )y
the CO" standard. Because the transmission o datasets in ADO.N0T is )ased
on an D"1 ormat, there is no restriction on data types. Thus, the components
sharing the dataset can use 'hate%er rich set o data types they 'ould ordinarily
use.
Per8orm7:ce
Transmitting a large ADO recordset or a large ADO.N0T dataset can
consume net'or( resourcesM as the amount o data gro's, the stress placed on
the net'or( also rises. Both ADO and ADO.N0T let you minimiGe 'hich data
is transmitted. But ADO.N0T oers another perormance ad%antage, in that
ADO.N0T does not re-uire data-type con%ersions. ADO, 'hich re-uires CO"
marshalling to transmit records sets among components, does re-uire that ADO
data types )e con%erted to CO" data types.
Pe:etr7ti:) irew766s
A ire'all can interere 'ith t'o components trying to transmit
disconnected ADO recordsets. *emem)er, ire'alls are typically conigured to
allo' ;T"1 te2t to pass, )ut to pre%ent system-le%el re-uests !such as CO"
marshalling& rom passing.
Because components e2change ADO.N0T datasets using D"1, ire'alls
can allo' datasets to pass.
SAL SER4ER
SAL SER4ER*

SI1 ser%er is a clientOser%er relational data)ase management system
!*DB"S& that uses transact-SI1 to send re-uest )et'een a client and SI1
ser%er.
!6ie:tGser@er Architecture
SI1 ser%er is designed to )e a clientOser%er system. ClientOser%er systems
are constructed so that the data)ase can reside on a central computer, (no' as a
ser%er, and )e shared among se%eral users. 4hen users 'ant to access the date
in SI1 ser%er, they run an application on their local computer, (no' as a client
that connects o%er a net'or( to the ser%er running SI1 ser%er.
SI1 ser%er can 'or( 'ith thousands o client applications
simultaneously. The ser%er has eatures to pre%ent the logical pro)lems that
occur i a user tries to read or modiy data currently )eing used )y others.
4hile SI1 ser%er is designed to 'or( as a ser%er in a clientOser%er
net'or(. It also capa)le o 'or(ing as a stand-alone data)ase directly on the
client. The scala)ility and ease-o-use eatures o SI1 ser%er allo' it to 'or(
eiciently on a client 'ithout consuming too many resources. SI1 ser%er
eiciently allocates the a%aila)le resources, such as memory, net'or(
)and'idth, and dis( IOO, among the multiple users.
Additio:76 87ci6it% Like TIMESTAMP 7:d TIMESTAMP with
TIMEHONE 8or stori:) Time#
6eEibi6it% i: i:ter@76s setti:)
CodeBs 96 rules are satisied. That is,
Data *epresentation
*ule o guaranteed access
Proper treatment o null %alue
Security
/ersioning
Physical Independence
1ogical Independence
Integrity constraint independence
/ie' $pdating
Data Description
Comprehensi%e data su) language
Insert and update rule
Distri)ution
SYSTEM ANALYSIS
S%stem A:76%sis
System analysis is the irst and oremost step perormed in de%eloping the
sot'are to sol%e a particular pro)lem. In the analysis part, a sot'are de%eloper
e2amines the re-uirements. Carrying out preliminary in%estigation identiies
these re-uirements
Analysis consists o t'o su) phases
Planning
*e-uirement deinition
During planning phase, cost estimates and 'or( schedules 'ill )e planned.
*e-uirement deinition is a speciication that descri)es the processing
en%ironment, the re-uired sot'are unctions, perormance constraints !siGe,
speed, machine coniguration& and e2ception handling.
E=ISTING SYSTEM
The e2isting system uses manual transaction processing.
Dr7wb7cks
1arge amount o clerical time is re-uired.
The record maintaina)ility is diicult.
Accessi)ility o accurate inormation rom the past record is diicult.
There is al'ays delay in inormation search and retrie%al. It re-uires
many people to carry out a single pro)lem.
1ot o human resources is re-uired.
Data relia)ility and maintaina)ility is diicult.
1ot amount o records need much place to sa%e.
The paper 'or(s ha%e to )e ta(en care.
The patient entry orm may miss
The doctor appointment cannot )e maintained in properly
The patient i2 the appointment to consulting 'ith doctor such things may
misplaced
The patients records %eriication is too complicated
Compare 'ith the patient and doctor record %eriication and %alidation is
too complicated
Cannot )e maintaining manual record or long time
PROPOSED SYSTEM
The proposed system has )een designed to o%ercome all the dra')ac(s
ound in the e2isting system. The ne' system has )een proposed to use
/IS$A1 BASIC.N0T as ront end and SI1 S0*/0* as )ac(end.

The proposed system has enhanced eatures, 'hich 'as not ound in
the e2isting system. The salient eatures are
Security or the data is done easily.
/alidation is done to enter correct data.
"emory consumption is %ery less and the processing speed
is ast.
Data reports are presented in a neat ormat.
It is apt or this modern 'orld.
It is easy to com)ine the data)ase o other sot'are and to %ie' the
records in the iles and also it is easy to get the reports )y gi%ing input data.

SYSTEM DESIGN
SYSTEM DESIGN
THE SYSTEM DESIGN PRO!ESS*
System design de%elops the architectural detail re-uired to )uild a
system or product.
The s%stem desi): 9rocess e:com97sses the 8o66owi:) 7cti@ities*
Q Partition the analysis model into su)systems.
Q Identiy concurrency that is dictated )y the pro)lem.
Q Allocate su)systems to processors and tas(s.
Q De%elop a design or the user interace.
Q Choose a )asic strategy or implementing data management.
Q Identiy glo)al resources and the control mechanisms re-uired to access them.
Q Design an appropriate control mechanism or the system, including tas(
management.
Q Consider ho' )oundary conditions should )e handled.
Q *e%ie' and consider trade-os.

I:9ut desi):
Input design is a part o o%erall system design, re-uires the %ery
careul analysis o the input data items. The goal o the input design is to ma(e
the data entry easier, logical and ree rom errors. The user controls input data.
The commonly used input, output de%ices are mouse, (ey)oard
and the %isual display unit. The 'ell designed, 'ell organiGed screen ormats
are used to ac-uire the inputs. The data accepted is stored on data)ase ile.
Our system is classiied into su)system such as
Admission
Sta Details
Billing
Consultation Details
4ard Details
Am)ulance Ser%ice
Data *eport
Out9ut Desi):
Output is the most important and direct source o inormation the user.
0icient E intelligent output design impro%es the system relationships
'ith the users and helps in decision-ma(ing. The output is collected in order to
help the user to ma(e a 'ise decision.
DATA&ASE DESIGN
INPAI!N
O" PAI!N

NAME

TYPE !ONSTRAINTS
;no Bigint Primary (ey
Name /archar!977& Not null
Age Int Not null
Addr /archar!967& Not null
Do) Datetime Not null
.ender /archar!67& Not null
State /archar!>=& Not null
District /archar!977& Not null
Concession /archar!977& Not null
*eeral /archar!977& Not null
Date Datetime Not null
NAME

TYPE !ONSTRAINTS
"rdno Bigint Primary (ey
;no Bigint Not null
Age Int Not null
Addr /archar!967& Not null
Do) Datetime Not null
State /archar!>=& Not null
District /archar!977& Not null
Concession /archar!977& Not null
*eeral /archar!977& Not null
Date o admit Datetime Not null
SA##
NAME
T
YPE !ONSTRAINTS
Idno Int Primary (ey
Name /archar!>7& Not null
Department /archar!977& Not null
Do# Datetime Not null
.ender /archar!<7& Not null
Address /archar!9>7& Not null
Salary Int Not null
Dtc Datetime Not null
*eason /archar!677& Not null
Age Int Not null
0mail /archar!977& Not null
Phone /archar!87& Not null
Cell /archar!87& Not null

PA$%O&&

NAME

TYPE !ONSTRAINTS
Idno Bigint Primary (ey
Department /archar!>7& Not null
Do# Datetime Not null
Dt Datetime Not null
Sperday Bigint Not null
Odpay Bigint Not null
Salary Bigint Not null
A&&OWANC!
NAME

TYPE !ONSTRAINTS
Idno Bigint Primary (ey
P Bigint Not null
Da Bigint Not nul
;ra Bigint Not nul
Ta Bigint Not null
.a Bigint Not null
INPAI!N BI&&
NAME

TYPE !ONSTRAINTS
Bno Bigint Primary (ey
;no Int Not null
"rdno Bigint Not null
Pname /archar!977& Not null
Department /archar!>7& Not null
*rent Int Not null
1a) Int Not null
Ad Datetime Not null
Dd Datetime Not null
Amount Bigint Not null
O"PAI!N BI&&
NAME

TYPE !ONSTRAINTS
Bno Int Primary (ey
;no Int Not null
Patientname /archar!>7& Not null
Docname /archar!>7& Not null
Date Datetime Not nul
Amount Int Not null
WA%D
NAME

TYPE !ONSTRAINTS
"rdno Bigint Primary (ey
;no Bigint Not null
Department /archar!977& Not null
4ardno Int Not null
*type /archar!977& Not null
Bno Int Not null
Adt Datetime Not null
Ddt Datetime Not null
A'B"&ANC!
NAME

TYPE !ONSTRAINTS
Amno Int Primary (ey
Type /archar!>7& Not null
Designation /archar!977& Not null
Stime Datetime Not null
*time Datetime Not null
Pde2p Int Not null
Stentry Bigint Not null
*tentry Bigint Not null
Dri%ername Nchar!977& Not null
Dri%erno Bigint Not null
Num Nchar!>7& Not nul
DATA LO> DIAGRAM
DATA LO> DIAGRAM
Data 5lo' Diagram !D5D& is a design tool constructed to sho' ho' data
'ithin the system. It is designed rom the data 'hich is collected during data
collection phase. D5D is other'ise called as CBu))le Chart:.
There are i%e sym)ol used in D5D. They are *ectangle, Open
*ectangle, Circle, arro', small circle. 0ach one has its o'n meaning.

- Source or Destination

- Data lo'

- Process

- Data Storage

- Control 5lo'

(O'!
Check
User
Name
&
Password
Auth.

Faile
d
A
Inpatient
Details
In
Patient
Outpatient
Details
A
ADMISSION
Out
Patient
Sta
Details
B
S!AFF
Inpatient
"ill
In "ill
"I##IN$
In
Patient
"illin%

"ill
Out
Patient

A
CONSU#!A!ION
Consultation
Details
Cons
In
Patient
&A'D
&ard
Details

&ard
AM"U#ANC(
S(')IC(
Shit
Details
Am*ulance
Details
Dri+er
Am*
Sta
PA$%O&&
Pa,roll
Details
Pa,roll
P!%SONA&
D!AI&S
Sta
Details
Sta
A!NDANC!
Attendance
Details
B
ON D"$
On Dut,
Details
Sta
OD
Atten
OD

Shit

S-IF!
Shit
Details
SYSTEM TESTING
S%stem Testi:)
System Testing is an important stage in any system de%elopment lie
cycle. Testing is a process o e2ecuting a program 'ith the intention o inding
errors. The importance o sot'are testing and its implications 'ith respect to
sot'are -uality cannot )e o%eremphasiGed. Sot'are testing is a critical
element o sot'are -uality assurance and represents the ultimate re%ie' o
speciication, design and coding. A good test case is one that has a high
pro)a)ility o inding a yet undisco%ered error.

Testing is the set o acti%ities that can )e planned in ad%ance and
conducted systematically. Dierent test conditions should )e thoroughly
chec(ed and the )ugs detected should )e i2ed. The testing strategies ormed )y
the user are perormed to pro%e that the sot'are is ree and clear rom errors.
To do this, there are many 'ays o testing the systemBs relia)ility, completeness
and maintaina)ility.
":it Testi:)*
In the unit testing the analyst tests the program ma(ing up a system. The
sot'are units in a system are the modules and routines that are assem)led and
integrated to perorm a speciic unction. In a large system, many modules on
dierent le%els are needed.

$nit testing can )e perormed rom the )ottom up starting 'ith the
smallest and lo'est le%el modules and proceeding one at a time. 5or each
module in a )ottom-up testing, a short program e2ecutes the module and
pro%ides the needed data.
I:te)r7tio: Testi:)*
Integration testing is a systematic techni-ue or constructing the program
structure 'hile conducting test to unco%er errors associate 'ith interacing.
O)#ecti%es are used to ta(e unit test modules and )uilt program structure that
has )een directed )y design.

The integration testing is perormed or this ;ospital "anagement
System 'hen all the modules 'here to ma(e it a complete system. Ater
integration the pro#ect 'or(s successully.
476id7tio: Testi:)*
/alidation testing can )e deined in many 'ays, )ut a simple deinition is
that can )e reasona)ly e2pected )y the customer. Ater %alidation test has )een
conducted, one o t'o possi)le conditions e2ists.
The unctions or perormance characteristics conirm
to speciication and are accepted.
A de%iation rom speciication is unco%ered and a
deiciency list is created.
Proposed system under consideration has )een tested )y using %alidation
testing and ound to )e 'or(ing satisactorily.
5or e2ample, in this pro#ect %alidation testing is perormed against
inpatient search module. This module is tested 'ith the ollo'ing %alid and
in%alid inputs or the ield patientname.
>hite &oE Testi:)
4hite )o2 testing, sometimes called glass-)o2 testing is a test case design
method that uses the control structure o the procedural design to deri%e test
cases. $sing 'hite )o2 testing methods, the sot'are engineer can deri%e test
cases that
.uarantee that all independent paths 'ith in a module ha%e )een
e2ercised at least once.
02ercise all logical decisions on their true and alse sides.
02ecute all loops at their )oundaries and 'ith in their operational
)ounds and
02ercise internal data structure to assure their %alidity.
5or e2ample in this pro#ect 'hite )o2 testing is perormed against
inpatient module. 4ithout entering te2t i 'e apply it displays the message
C5irst add record then sa%e it: else it should )e sa%ed.
&67ck &oE Testi:)
This method treats the coded module as a )lac( )o2. The module runs
'ith inputs that are li(ely to cause errors. Then the output is chec(ed to see i
any error occurred. This method cannot )e used to test all errors, )ecause some
errors may depend on the code or algorithm used to implement the module.
S%stem Im96eme:t7tio:
Implementation is the process o ha%ing system personal chec( out and
pro%ides ne' e-uipments into use, train the users to install a ne' application
and construct any iles o data needed to use it. There are three types o
implementation.
Implementation o computer system to replace a manual system.
The pro)lems encountered are co%ering iles, training users,
creating accurate iles and %eriying print outs or integrity.
Implementation o a ne' computer system to replace an e2isting
one. This is usually diicult con%ersion. I not properly planned,
there can )e many pro)lems. So large computer systems may ta(e
as long as a year to con%ert.
Implementation o a modiied application to replace the e2isting
one using the same computer. This type o con%ersion is relati%ely
easy to handle, usually there are no ma#or changes in the ile.
Our pro#ect is yet to )e implemented.
SAMPLE !ODINGS
SAMPLE !ODINGS *
Lo)i: 8orm*
Public Class Login
Dim form1 As New mainmenu
Private Sub OK_Click(!"al sen#er As S!stem$Ob%ect& !"al
e As S!stem$'ventArgs( )an#les OK$Click
*f Passwor#+e,to,$+e,t - ./os0ital. +/en
1sgo,(.Login Success.& 1sgo,St!le$*nformation&
.)os0ital 1anagement.(
Passwor#+e,to,$+e,t - ..
1e$)i#e((
mainmenu$S/ow((
'lse
1sgo,(.Login 2aile#.& 1sgo,St!le$Critical&
Passwor#+e,to,$+e,t - ..
1e$S/ow((
'n# *f
'n# Sub
Private Sub Cancel_Click(!"al sen#er As S!stem$Ob%ect&
!"al e As S!stem$'ventArgs( )an#les Cancel$Click
1e$Close((
'n# Sub
Private Sub utton1_Click(!"al sen#er As S!stem$Ob%ect&
!"al e As S!stem$'ventArgs( )an#les utton1$Click
'n#
'n# Sub
'n# Class
M7i: Me:u*
Public Class mainmenu
Private Sub ',it+oolStri01enu*tem_Click(!"al sen#er As
S!stem$Ob%ect& !"al e As S!stem$'ventArgs(
'n#
'n# Sub
Private Sub *n0atient+oolStri01enu*tem_Click(!"al sen#er
As S!stem$Ob%ect& !"al e As S!stem$'ventArgs( )an#les
*n0atient+oolStri01enu*tem$Click
1e$)i#e((
in0atient$S/ow((
'n# Sub
Private Sub Out0atient+oolStri01enu*tem_Click(!"al sen#er
Out0atient+oolStri01enu*tem$Click
1e$)i#e((
out0atient$S/ow((
'n# Sub
Private Sub Doctor+oolStri01enu*tem_Click(!"al sen#er As
1e$)i#e((
#oct0er$S/ow((
'n# Sub
Private Sub Doctor+oolStri01enu*tem1_Click(!"al sen#er As
1e$)i#e((
#oc0a!$S/ow((
'n# Sub
1e$)i#e((
#octsal$S/ow((
'n# Sub
Private Sub PersonalDetails+oolStri01enu*tem_Click(!"al
sen#er As S!stem$Ob%ect& !"al e As S!stem$'ventArgs( )an#les
PersonalDetails+oolStri01enu*tem$Click
1e$)i#e((
#oct0er$S/ow((
'n# Sub
Private Sub mainmenu_Loa#(!"al sen#er As S!stem$Ob%ect&
!"al e As S!stem$'ventArgs( )an#les 1!ase$Loa#
'n# Sub
1e$)i#e((
#octate$S/ow((
'n# Sub
#octsif$S/ow((
'n# Sub
Private Sub OD2orm+oolStri01enu*tem_Click(!"al sen#er As
S!stem$Ob%ect& !"al e As S!stem$'ventArgs( )an#les
OD2orm+oolStri01enu*tem$Click
1e$)i#e((
#octsal$S/ow((
'n# Sub
Private Sub Pa!rollDetails+oolStri01enu*tem_Click(!"al
Pa!rollDetails+oolStri01enu*tem$Click
1e$)i#e((
#oc0a!$S/ow((
'n# Sub
Private Sub Atten#anceDetails+oolStri01enu*tem_Click(!"al
Atten#anceDetails+oolStri01enu*tem$Click
1e$)i#e((
#octate$S/ow((
'n# Sub
Private Sub S/iftDetails+oolStri01enu*tem_Click(!"al
S/iftDetails+oolStri01enu*tem$Click
1e$)i#e((
#octsif$S/ow((
'n# Sub
Private Sub *n0atient+oolStri01enu*tem1_Click(!"al sen#er
*n0atient+oolStri01enu*tem1$Click
1e$)i#e((
in0atbill$S/ow((
'n# Sub
Private Sub Out0atient+oolStri01enu*tem1_Click(!"al
Out0atient+oolStri01enu*tem1$Click
1e$)i#e((
out0atbill$S/ow((
'n# Sub
Private Sub Consultation+oolStri01enu*tem_Click(!"al
Consultation+oolStri01enu*tem$Click
1e$)i#e((
consul$S/ow((
'n# Sub
Private Sub 6ar#Details+oolStri01enu*tem_Click(!"al
6ar#Details+oolStri01enu*tem$Click
1e$)i#e((
war#$S/ow((
'n# Sub
Private Sub
illingAn#P/armac!+oolStri01enu*tem_Click(!"al sen#er As
illingAn#P/armac!+oolStri01enu*tem$Click
'n# Sub
Private Sub AmbulanceService+oolStri01enu*tem_Click(!"al
AmbulanceService+oolStri01enu*tem$Click
1e$)i#e((
ambul$S/ow((
'n# Sub
Private Sub ',it+oolStri01enu*tem1_Click(!"al sen#er As
1e$)i#e((
Login$S/ow((
'n# Sub
Private Sub ',it+oolStri01enu*tem_Click_1(!"al sen#er As
',it+oolStri01enu*tem$Click
1e$)i#e((
Login$S/ow((
'n# Sub
Private Sub *n0atients+oolStri01enu*tem_Click(!"al sen#er
*n0atients+oolStri01enu*tem$Click
i0tre0ort$S/ow((
'n# Sub
Private Sub P/armac!+oolStri01enu*tem_Click(!"al sen#er
P/armac!+oolStri01enu*tem$Click
i0tbillview$S/ow((
'n# Sub
Private Sub 2eesCollections+oolStri01enu*tem_Click(!"al
2eesCollections+oolStri01enu*tem$Click
outbillview$S/ow((
'n# Sub
'n# Class
I:97tie:t Admissio: *
*m0orts S!stem$Data$OleDb
Public Class in0atient
Dim cm# As New OleDbComman#
conn$o0en((
Dim s7l As String - .insert into i0t values(8. 9
+e,to,:$+e,t 9 .8&8. 9 +e,to,;$+e,t 9 .8&8. 9 +e,to,5$+e,t
9 .8&8. 9 <ic/+e,to,5$+e,t 9 .8&8. 9 Date+imePicker1$+e,t 9
.8&8. 9 Comboo,1$+e,t 9 .8&8. 9 +e,to,3$+e,t 9 .8&8. 9
+e,to,4$+e,t 9 .8&8. 9 +e,to,=$+e,t 9 .8&8. 9 +e,to,>$+e,t
9 .8&8. 9 Date+imePicker3$+e,t 9 .8(.
cm# - New OleDbComman#(s7l& conn(
cm#$',ecute<ea#er((
1sgo,(.<ecor# *nserte#.& 1sgo,St!le$*nformation&
+e,to,3$+e,t - ..
+e,to,4$+e,t - ..
+e,to,5$+e,t - ..
<ic/+e,to,5$+e,t - ..
+e,to,;$+e,t - ..
+e,to,:$+e,t - ..
+e,to,=$+e,t - ..
+e,to,>$+e,t - ..
Comboo,1$+e,t - ..
conn$close((
'n# Sub
Private Sub in0atient_Loa#(!"al sen#er As S!stem$Ob%ect&
1e$Comboo,1$*tems$A##(.1ale.(
1e$Comboo,1$*tems$A##(.2emale.(
'n# Sub
1e$)i#e((
mainmenu$S/ow((
'n# Sub
i0trecor#$S/ow((
'n# Sub
'n# Class
Out97tie:t Admissio: *
Public Class out0atient
1e$)i#e((
mainmenu$S/ow((
'n# Sub
conn$o0en((
Dim s7l As String - .insert into o0t values(8. 9
+e,to,:$+e,t 9 .8&8. 9 +e,to,;$+e,t 9 .8&8. 9 +e,to,5$+e,t
9 .8&8. 9 <ic/+e,to,5$+e,t 9 .8&8. 9 Date+imePicker1$+e,t 9
.8&8. 9 Comboo,1$+e,t 9 .8&8. 9 +e,to,3$+e,t 9 .8&8. 9
+e,to,4$+e,t 9 .8&8. 9 +e,to,=$+e,t 9 .8&8. 9 +e,to,>$+e,t
9 .8(.
cm# - New OleDbComman#(s7l& conn(
cm#$',ecute<ea#er((
1sgo,(.<ecor# *nserte#.& 1sgo,St!le$*nformation&
+e,to,3$+e,t - ..
+e,to,4$+e,t - ..
+e,to,5$+e,t - ..
<ic/+e,to,5$+e,t - ..
+e,to,;$+e,t - ..
+e,to,:$+e,t - ..
+e,to,=$+e,t - ..
+e,to,>$+e,t - ..
Comboo,1$+e,t - ..
conn$close((
'n# Sub
Private Sub out0atient_Loa#(!"al sen#er As S!stem$Ob%ect&
1e$Comboo,1$*tems$A##(.1ale.(
1e$Comboo,1$*tems$A##(.2emale.(
'n# Sub
'n# Class
I:97tie:t &i66 *
*m0orts S!stem$Data
Public Class in0atbill
Dim a#0 As New OleDbDataA#a0ter
Dim #s As New DataSet
Dim , As New *nteger
Dim #r As OleDbData<ea#er
1e$)i#e((
mainmenu$S/ow((
'n# Sub
conn$o0en((
cm# - New OleDbComman#(.insert into inbill values(8. 9
+e,to,1$+e,t 9 .8&8. 9 Comboo,1$+e,t 9 .8&8. 9 +e,to,4$+e,t
9 .8&8. 9 Date+imePicker3$+e,t 9 .8&8. 9 +e,to,>$+e,t 9 .8&8.
9 +e,to,?$+e,t 9 .8&8. 9 Date+imePicker1$+e,t 9 .8&8. 9
Date+imePicker3$+e,t 9 .8&8. 9 +e,to,11$+e,t 9 .8(.& conn(
cm#$',ecuteNon@uer!((
1sgo,(.ill Save# to Database.& 1sgo,St!le$OkOnl!&
cm#$Dis0ose((
+e,to,1$+e,t - . .
+e,to,4$+e,t - . .
+e,to,>$+e,t - . .
+e,to,?$+e,t - . .
+e,to,1A$+e,t - . .
+e,to,11$+e,t - . .
Comboo,1$+e,t - . .
Date+imePicker1$"alue - Now$Date
conn$close((
'n# Sub
Private Sub in0atbill_Loa#(!"al sen#er As S!stem$Ob%ect&
Comboo,1$+ab*n#e, - A
+e,to,?$+ab*n#e, - 1
+e,to,1A$+ab*n#e, - 3
+e,to,11$+ab*n#e, - 4
conn$o0en((
cm# - New OleDbComman#(.select B from i0t.& conn(
#r - cm#$',ecute<ea#er
6/ile (#r$<ea#(
Comboo,1$*tems$A##(#r(A($+oString(
'n# 6/ile
cm#$Dis0ose((
cm# - New OleDbComman#(.select ma,(bno( from inbill.&
conn(
*f #r$<ea# - +rue +/en
+e,to,1$+e,t - #r(A( C 1$+oString
'lse
+e,to,1$+e,t - 1
'n# *f
cm#$Dis0ose((
conn$close((
'n# Sub
Private Sub Comboo,1_Selecte#*n#e,C/ange#(!"al sen#er As
Comboo,1$Selecte#*n#e,C/ange#
conn$o0en((
a#0 - New OleDbDataA#a0ter(.select B from i0t w/ere
mr#no-8 . 9 Comboo,1$+e,t 9 .8.& a#0,(
a#0$2ill(#s& .i0t.(
+e,to,4$+e,t - #s$+ables(A($<ows(A((1($+oString
Date+imePicker1$"alue - #s$+ables(A($<ows(A(
(1A($+oString((
, - Date+imePicker3$"alue$Da! D
Date+imePicker1$"alue$Da!
+e,to,>$+e,t - , B 4AA
conn$close((
'n# Sub
Private Sub +e,to,11_'nter(!"al sen#er As Ob%ect& !"al
e As S!stem$'ventArgs( )an#les +e,to,11$'nter
+e,to,11$+e,t - . .
Dim ,& !& E As New *nteger
, - +e,to,>$+e,t
! - +e,to,?$+e,t
E - +e,to,1A$+e,t
+e,to,11$+e,t - , C ! C E
'n# Sub
i0tbillview$S/ow((
'n# Sub
'n# Class
Out97tie:t &i66 *
*m0orts S!stem$Data
Public Class out0atbill
Dim , As New *nteger
1e$)i#e((
mainmenu$S/ow((
'n# Sub
conn$o0en((
cm# - New OleDbComman#(.insert into bill values(8. 9
+e,to,1$+e,t 9 .8&8. 9 Comboo,1$+e,t 9 .8&8. 9 +e,to,3$+e,t
9 .8&8. 9 +e,to,4$+e,t 9 .8&8. 9 Date+imePicker1$+e,t 9 .8&8.
9 +e,to,=$+e,t 9 .8(.& conn(
1sgo,(.<ecor# inserte# to Database.&
1sgo,St!le$OkOnl!& .)os0ital 1anagement.(
clear#ata((
conn$close((
'n# Sub
Sub clear#ata((
+e,to,1$+e,t - Not/ing
+e,to,=$+e,t - Not/ing
Comboo,1$+e,t - Not/ing
'n# Sub
conn$o0en((
a#0 - New OleDbDataA#a0ter(.select B from o0t w/ere
/no-8 . 9 Comboo,1$+e,t 9 .8.& a#0,(
a#0$2ill(#s& .o0t.(
+e,to,4$+e,t - #s$+ables(A($<ows(A((?($+oString
conn$close((
'n# Sub
Private Sub out0atbill_Loa#(!"al sen#er As S!stem$Ob%ect&
conn$o0en((
cm# - New OleDbComman#(.select B from o0t.& conn(
6/ile (#r$<ea#(
'n# 6/ile
cm#$Dis0ose((
cm# - New OleDbComman#(.select ma,(bno( from bill.&
conn(
*f #r$<ea# - +rue +/en
+e,to,1$+e,t - #r(A( C 1$+oString
'lse
+e,to,1$+e,t - 1
'n# *f
conn$close((
cm#$Dis0ose((
'n# Sub
clear#ata((
'n# Sub
Private Sub utton;_Click(!"al sen#er As S!stem$Ob%ect&
!"al e As S!stem$'ventArgs( )an#les utton;$Click
outbillview$S/ow((
'n# Sub
'n# Class
I:97tie:t Record Se7rch*
*m0orts S!stem$Data
Public Class i0trecor#
conn$o0en((
+r!
Dim s7l As String - .select B from i0t w/ere name
- 8. 9 +e,to,1$+e,t 9 .8.
Dim a#0 As OleDbDataA#a0ter
a#0 - New OleDbDataA#a0ter(s7l& a#0,(
Dim #s As DataSet - New DataSet
a#0$2ill(#s& .i0t.(
DataFri#"iew1$DataSource - #s$+ables(.i0t.(
Catc/
1sgo,(.<ecor# not 2oun#.& & .)os0ital
1anagement.(
'n# +r!
conn$close((
'n# Sub
Private Sub i0trecor#_Loa#(!"al sen#er As S!stem$Ob%ect&
+e,to,1$2ocus((
'n# Sub
'n# Class
!o:su6t7tio:*
*m0orts S!stem$Data
Public Class consul
Private Sub utton;_Click(!"al sen#er As S!stem$Ob%ect&
!"al e As S!stem$'ventArgs( )an#les utton;$Click
1e$)i#e((
mainmenu$S/ow((
'n# Sub
Private Sub consul_Loa#(!"al sen#er As S!stem$Ob%ect&
DataFri#"iew1$)i#e((
conn$o0en((
cm# - New OleDbComman#(.select B from i0t.& conn(
6/ile (#r$<ea#(
'n# 6/ile
cm#$Dis0ose((
'n# Sub
a#0 - New OleDbDataA#a0ter(.select B from i0t w/ere
mr#no-8 . 9 Comboo,1$+e,t 9 .8.& a#0,(
a#0$2ill(#s& .i0t.(
Comboo,3$+e,t - #s$+ables(A($<ows(A((;($+oString
'n# Sub
cm# - New OleDbComman#(.insert into cons values(8. 9
Comboo,1$+e,t 9 .8&8. 9 +e,to,3$+e,t 9 .8&8. 9 +e,to,4$+e,t
9 .8&8. 9 Comboo,3$+e,t 9 .8&8. 9 Date+imePicker1$+e,t 9
.8&8. 9 +e,to,;$+e,t 9 .8&8. 9 +e,to,:$+e,t 9 .8(.& conn(
1sgo,(.<ecor# inserte# to Database.&
1sgo,St!le$OkOnl!& .)os0ital 1anagement.(
clear#ata((
cm#$Dis0ose((
'n# Sub
Sub clear#ata((
Comboo,1$+e,t - . .
+e,to,3$+e,t - . .
+e,to,4$+e,t - . .
+e,to,;$+e,t - . .
+e,to,:$+e,t - . .
Comboo,3$+e,t - . .
'n# Sub
clear#ata((
'n# Sub
DataFri#"iew1$S/ow((
+r!
Dim s7l As String - .select B from cons w/ere
mr#no - 8. 9 Comboo,1$+e,t 9 .8.
Dim a#0 As OleDbDataA#a0ter
a#0 - New OleDbDataA#a0ter(s7l& a#0,(
Dim #s As DataSet - New DataSet
a#0$2ill(#s& .cons.(
DataFri#"iew1$DataSource - #s$+ables(.cons.(
Catc/
1sgo,(.<ecor# not 2oun#.& & .)os0ital
1anagement.(
'n# +r!
conn$close((
'n# Sub
'n# Class
Modu6e *
1o#ule 1o#ule1
Public v As New OleDbConnection
Public a#0, As String - .Provi#er-S@LOL'DGData
Source-A<HLSO2+G*ntegrate# Securit!-SSP*G*nitial
Catalog-/os0ital1.
Public conn - New OleDbConnection(.Provi#er-S@LOL'DGData
Catalog-/os0ital1.(
Public , As *nteger - New *nteger C 1
Public Sub o0en#ata((
v$ConnectionString - .Provi#er-S@LOL'DGData
Catalog-/os0ital1.
v$O0en((
'n# Sub
Public Sub close#ata((
v$Close((
v - Not/ing
'n# Sub
'n# 1o#ule

S!REENSHOTS
Lo)i: Scree:*
M7i: Me:u Scree:*
I:97tie:t Admissio:*
I:97tie:t Records Se7rch*
Out97tie:t Admissio:*
Doctor Perso:76 Det7i6s*
I:97tie:t &i66*
Out97tie:t &i66*
I:97tie:t Re9orts*
&i66s !o66ectio: Re9ort*
Out97tie:t bi66s !o66ectio: Re9ort*

&I&ILIOGRAPHY
&I&ILIOGRAPHY
9. OOP >ITH MI!ROSOT 4IS"AL &ASI!#NET AND
MI!ROSOT 4IS"AL !B#NET STEP &Y STEP BF
RO&IN#A#REYNOLDS I HAERTLE I Microso8t Press 0--0
6. THE &OO$ O 4IS"AL &ASI! 0--3# )y M7tthew M7cDo:76d I
NO STAR!H PRESS
<. 4&#NET De@e6o9erJs Guide )y S%:)ress Pub6ishi:)5 I:c.
=. 4isu76 &7sic #NET How to Pro)r7m Seco:d Editio: )y Deite6 ?
Associ7tes5 I:c#5
>. 4&#Net L7:)u7)e i: 7 Nutshe66 )y Ste@e: Rom7:5 Ro: Petrush7 I
OJRei66% 0--,
/# Microso8t ADO#NET Ste9 &% Ste9 I Microso8t Press 0--3
@. Pro)r7mmi:) Microso8t >i:dows with Microso8t 4isu76 &7sic #NET
)y !h7r6es Petso6d 6776
A. PROGRAMMING MI!ROSOT 4IS"AL &ASI!#NET By
r7:cesco &76e:o I Microso8t Press 0--1
8. Microso8t 4isu76 &7sic #NET Projects 8or the !67ssroom By A68red !
Thom9so: Distri)uted )y M7i:8u:ctio:#com
97. So8tw7re E:)i:eeri:) 5 A PRA!TITIONERJS APPROA!H )y
Ro)er#S#Pressm7:5Ph#D# i8th Editio:
99. So8tw7re E:)i:eeri:) !o:ce9ts5 By Rich7rd E#7ir6e% I T7t7
McGr7w I Hi66 Pub6ishi:) !om97:% Limited
>E&ILIOGRAPHY
>E&ILIOGRAPHY
9. http+OO'''.%)dotnethea%en.comO
6. http+OO'''.connectionstrings.comO

Hospital Management System

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Hospital Management System

Загружено:

Авторское право:

Доступные форматы

HOSPITAL MANAGEMENT SYSTEM

A Project work submitted to the

Mr#A#&767ji 5 MS(IT?M25 M#Phi6#5

Вам также может понравиться