MEDICAL MANAGEMENT SYSTEM

SRIRAM ENGINEERING COLLEGE

PERUMALPATTU

DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING
MINI PRIJECT REPORT

DURING THE YEAR 2010-2011

GUIDED BY : Mr.D.Hemanand M.E.,

 SRIRAM ENGINEERING COLLEGE
PERUMALPATTU

BONAFIDE CERTIFICATE

This is to certify that this is a bonfide certificate record of work

done by

 Rajesh khan
 Ganesh
 Vishwanath
 surya_________________________________ laboratory
during academic year 2010-2011.

SIGNATURE OF GUIDE SIGNATURE OF HOD

 ACKNOWLEDGMENT:
We wish to express our sincere to our principle DR.P.PARTHEEBAN
M.E,PHD., and our beloved head of department of computer science engineering
Ms.S.V.PRIYA,M.E., for having helped us to finish our project work “MEDICAL
MANAGEMENT SYSTEM” successfully by giving as the necessary advices and
required financial help.

We would like to convey our deep sense of gratitude to our guide

Mr.D.Hemanand M.E., LECT/CSE for this mindful guidance and worthy and
timely advice for the development completion of the project.

We also extend our hearty thanks to all staff members and lab
technicians of computer science department, who helped as directly or indirectly
for the successful completion of our project work
.
We are very much grateful to our beloved parents for their moral
supports to do this project.
 CONTENTS:

 SYNOPSIS

 RATIONAL ROSE SOFTWARE

 PROBLEM STATEMENT

 USE CASE DIAGRAM

 CLASS DIAGRAM

 SEQUENCE AND COLLABORATION DIAGRAM

 SYSTEM CONFIGURATION

 SYSTEM DESIGN

 SAMPLE OUTPUT

 CONCLUSION

 BIBILIOGRAPHY
 SYNOPSIS :

This project will automate the daily operations of LIFE LINE

hospital. The project keeps track of the staff and patient (in-patient, out-
patient) details. It also takes care of the ward, medical, invoice and the
doctor’s appointment details. The system generates the daily ward
availability, the status of the operation theatres and ICU. HOSPITAL
MANAGEMENT is an integrated Hospital Information System, which
addresses all the major functional areas of multi-specialty hospitals. The
HOSPITAL MANAGEMENT enables better patient care, patient safety,
patient confidentiality, efficiency, reduced costs and better management
information system. It provides easy access to critical information thus
enabling the management to take better decisions on time. This project deals
with processing of each and every department in the hospital. This project
sincerely aims to reduce the manual processing of each department. The
Scope of the project takes care of the details of each and every department.
These details gives the doctor, staffs, specialists and patient details including
their salary,attendance , doctor’s appointments and the billing system. The
details of Doctor and staff help the hospital to maintain the record of every
person. Their attendance details help them to know about their attentive
presence while salary is calculated. The billing system provides an efficient
way for calculating bill details of the patients.
 RATIONAL ROSE SOFTWARE:

INTRODUCTION:

CASE tools known as computer-aided software engineering tools is a

kind of component-based development which its users to rapidly develop
information systems.tha main goal of case technology is the automation of the
entire information systems development life cycle process using a set of integrated
software tools,such modeling,methodology and automatic code generation. The
main advantages are the availability of high quality,defect free product at low cost
and at a faster time.

CHARACTERISTICS OF CASE:

 It is a graphic oriented tools.

 It support decomposition of process

SOME TYPICAL CASE TOOLS ARE:

 Unified modeling language

 Data modeling tools
 Source code generation tools
 USECASE DESCRIPTION:
Usecases:

1. Admissions
2. Doctor Appointments
3. Tests Appointments
4. Bed Allotment
5. Undergo Operation
6. Login
7. Draw Salary
8. Add Doctor/Staff 9. Delete Doctor/Staff
10. Edit Doctor/Staff
11. Prescribe Tests
12. Ward Wise Bed Status
13. Admission/Discharge Reports
14. Patient Information

Actors:

1. Receptionist
2. Doctors
3. Staff/Nurses
4. Income
5. Expenditure
6. Records System
7. Information System
ADMISSIONS:

This Module helps in registering information about patients and handles

patient’s query. A unique ID is generated for each patient after registration. This
helps in implementing customer relationship management and also maintains
medical history of the patient.

DOCTOR APPOINTMENTS:

This Module Deals with, when the ID is generated the patient receives the
Appointment time & number from the Receptionist and accordingly visit the
doctor.

TESTS APPOINTMENTS:

This Module Deals with, when the ID is generated the patient receives the
Appointment time & number from the Receptionist and accordingly undergoes the
tests.
BED ALLOTMENT:

This Module handles with allotting the Bed to various patients by checking
their ID

UNDERGO OPERATION:

This Module handling with undergoes the various operations by diagnosing

the patients.

LOGIN:

This Module checks whether the person is a Doctor/Staff and handles

various activities such as draw Salary and give Salary.

DRAW SALARY:

This Module checks whether the person is a Doctor/Staff and draws salary
based on the information.
ADD DOCTOR/STAFF:

This Module handles the activities such as adding Doctor/Staff information

into the database.

DELETE DOCTOR/STAFF:

This Module handles the activities such as deleting Doctor/Staff information

into the database.

EDIT DOCTOR/STAFF:

This Module handles the activities such as editing Doctor/Staff information

into the database.

PRESCRIBE TESTS:

This Module handles various activities such as Doctor Diagnoses the patient,
gives treatment & gives suggestions to the patients, & prescribes laboratory tests &
medicines.

WARDWISE BED STATUS:

This Module takes care of medical equipment, doctor visit, vitalsrecording,

patient case sheet, diet ordering, blood requisition, transfer intimation anddischarge
intimation etc. It also deals with the maintenance of the wards, inter- and intra-
ward transfers.

ADMISSION/DISCHARGE REPORTS:

This Module helps in generating patient’s discharge summary,which

includes patient’s health at the time of discharge, medical history, variousdiagnosis
and drug prescriptions, history of present illness and course in hospital.

PATIENT INFORMATION:

This Module helps in generating the patient information which is provided

by doctor.
 USE CASE DIAGRAM:

A use case diagram is quite simple in nature and depicts two types of elements:
one representing the business roles and the other representing the business processes.
Let us take a closer look at use at what elements constitute a use case diagram.

 Actors: 
An actor portrays any entity (or entities) that performs certain roles in a
given system. The different roles the actor represents are the actual business
roles of users in a given system. An actor in a use case diagram interacts with a
use case. For example, for modeling a banking application, a customer entity
represents an actor in the application. Similarly, the person who provides service
at the counter is also an actor. But it is up to you to consider what actors make
an impact on the functionality that you want to model. If an entity does not affect
a certain piece of functionality that you are modeling, it makes no sense to
represent it as an actor. An actor is shown as a stick figure in a use case diagram
depicted "outside" the system boundary, as shown in Figure 3.1.

Figure 3.1: an actor in a use case diagram

To identify an actor, search in the problem statement for business terms that
portray roles in the system. For example, in the statement "patients visit the
doctor in the clinic for medical tests," "doctor" and "patients" are the business
roles and can be easily identified as actors in the system.
 Use case:
 A use case in a use case diagram is a visual representation of a distinct
business functionality in a system. The key term here is "distinct business
functionality." To choose a business process as a likely candidate for modeling
as a use case, you need to ensure that the business process is discrete in
nature. As the first step in identifying use cases, you should list the discrete
business functions in your problem statement. Each of these business
functions can be classified as a potential use case. Remember that identifying
use cases is a discovery rather than a creation. As business functionality
 becomes clearer, the underlying use cases become more easily evident. A use
case is shown as an ellipse in a use case diagram (see Figure 3.2).

Figure 3.2: use cases in a use case diagram

Figure 3.2 shows two uses cases: "Make appointment" and "Perform medical
tests" in the use case diagram of a clinic system. As another example, consider
that a business process such as "manage patient records" can in turn have sub-
processes like "manage patient's personal information" and "manage patient's
medical information." Discovering such implicit use cases is possible only with a
thorough understanding of all the business processes of the system through
discussions with potential users of the system and relevant domain knowledge.
 System boundary: A system boundary defines the scope of what a system
will be. A system cannot have infinite functionality. So, it follows that use cases
also need to have definitive limits defined. A system boundary of a use case
diagram defines the limits of the system. The system boundary is shown as a
rectangle spanning all the use cases in the system.

Figure 3.3: a use case diagram depicting the system boundary of a clinic
application

Figure 3.3 shows the system boundary of the clinic application. The use cases of
this system are enclosed in a rectangle. Note that the actors in the system are
outside the system boundary.
 The system boundary is potentially the entire system as defined in the problem
statement. But this is not always the case. For large and complex systems, each
of the modules may be the system boundary. For example, for an ERP system
for an organization, each of the modules such as personnel, payroll, accounting,
and so forth, can form the system boundary for use cases specific to each of
these business functions. The entire system can span all of these modules
depicting the overall system boundary.

RECEPTION:

LOGIN

ADMISSION

DOCTOR
APPOINTMENT

TESTS APPOINTMENT

BED ALLOTMENT

PATIENT
INFORMATION
 CLASS DIAGRAM:

patient
Int id
Varcharname
Int age Registration
Varcharadd Int rtegister()
Verchar sex Int about bed()
Int create()
Int patient()
Test operation
Int appointment()
Int patient id
Int id
Int flag
Void testapp()

Reports
Void disp()
Void ward status()
Address report()
Void dis()
Appt infor()

SYSTEM CONFIGURATION:

HARDWARE REQUIREMENTS:
PROCESSOR :INTEL PENTIUM 4 (OR)HIGHER
RAM :512 MB & ABOVE
HARD DISK DRIVE : 500 MB FREE SPACE OR ABOVE
PRINTER : INK-JET PRINTER
PEN DRIVE : 512MB.

SOFTWARE REQUIREMENTS :

PROGRAMMING LANGUAGE : VISUAL PROGRAMMING

BACKEND :MS SQL SERVER-2005
FRONT END :VISUAL BASIC.NET
OPERATING SYSTEM : WINDOWS XP & HIGHER VERSION.

SYSTEM DESIGN:

THE SYSTEM DESIGN PROCESS:

System design develops the architectural detail required to build a system or

product.
The system design process encompasses the following activities:
• Partition the analysis model into subsystems.
• Identify concurrency that is dictated by the problem.
• Allocate subsystems to processors and tasks.
• Develop a design for the user interface.
• Choose a basic strategy for implementing data management.
• Identify global resources and the control mechanisms required to access them.
• Design an appropriate control mechanism for the system, including task
management.
• Consider how boundary conditions should be handled.
• Review and consider trade-offs.

Input design:

Input design is a part of overall system design, requires the very careful
analysis of the input data items. The goal of the input design is to make the data
entry easier, logical and free from errors. The user controls input data. The
commonly used input, output devices are mouse, keyboard and the visual display
unit. The well designed, well organized screen formats are used to acquire the
inputs. The data accepted is stored on database file. Our system is classified into
subsystem such as
Admission
Staff Details
Billing
Consultation Details
Ward Details
Ambulance Service
Data Report
Output Design :

Output is the most important and direct source of information the user.
Efficient & intelligent output design improves the system relationships with the
users and helps in decision-making.

SAMPLE CODINGS:

LOGIN FORM:

Public ClassLogin
Dimform1 As Newmainmenu
Private SubOK_Click(ByValsender AsSystem.Object, ByVal
eAs System.EventArgs)Handles OK.Click If PasswordTextBox.Text ="hospital"
Then MsgBox("Login Success", MsgBoxStyle.Information, "Hospital
Management") PasswordTextBox.Text ="" Me.Hide() mainmenu.Show() Else
MsgBox("Login Failed", MsgBoxStyle.Critical, "Hospital Management")
PasswordTextBox.Text ="" Me.Show() End If End Sub Private
SubCancel_Click(ByValsender AsSystem.Object, ByVale AsSystem.EventArgs)
HandlesCancel.Click Me.Close() End Sub Private SubButton1_Click(ByValsender
AsSystem.Object, ByVale AsSystem.EventArgs) HandlesButton1.Click End End
Sub End Class

MAIN MENU:

Inpatient Admission :

ImportsSystem.Data.OleDb Public Classinpatient Private

SubButton2_Click(ByValsender AsSystem.Object, ByVale AsSystem.EventArgs)
HandlesButton2.Click Dimcmd As NewOleDbCommand conn.open() Dimsql As
String= "insert into ipt values('" & TextBox6.Text &"','" & TextBox5.Text &"','" &
TextBox4.Text &"','" & RichTextBox4.Text &"','" & DateTimePicker1.Text & "','"
& ComboBox1.Text & "','" & TextBox2.Text & "','"& TextBox3.Text &"','" &
TextBox7.Text &"','" & TextBox8.Text &"','" & DateTimePicker2.Text &"')"
cmd =New OleDbCommand(sql, conn)
cmd.ExecuteReader()
MsgBox("Record Inserted", MsgBoxStyle.Information,
"Hospital Management") TextBox2.Text =""
TextBox3.Text =""
TextBox4.Text =""
RichTextBox4.Text =""
TextBox5.Text =""
TextBox6.Text =""
TextBox7.Text =""
TextBox8.Text =""
ComboBox1.Text =""
conn.close()
End Sub Private Subinpatient_Load(ByValsender AsSystem.Object, ByVale
AsSystem.EventArgs) Handles MyBase.Load
Me.ComboBox1.Items.Add("Male")
Me.ComboBox1.Items.Add("Female")
End Sub Private SubButton1_Click(ByValsender AsSystem.Object, ByVale
AsSystem.EventArgs) HandlesButton1.Click Me.Hide() mainmenu.Show() End
Sub Private SubButton4_Click(ByValsender AsSystem.Object, ByVale
AsSystem.EventArgs) HandlesButton4.Click iptrecord.Show() End Sub End Clas

Outpatient Admission :

ImportsSystem.Data.OleDb Public Classoutpatient Private

SubButton1_Click(ByValsender AsSystem.Object, ByVale AsSystem.EventArgs)
HandlesButton1.Click Me.Hide() mainmenu.Show() End Sub Private
SubButton2_Click(ByValsender AsSystem.Object, ByVale AsSystem.EventArgs)
HandlesButton2.Click Dimcmd As NewOleDbCommand conn.open() Dimsql As
String= "insert into opt values('" & TextBox6.Text &"','" & TextBox5.Text &"','"
& TextBox4.Text &"','" & RichTextBox4.Text &"','" & DateTimePicker1.Text &
"','" & ComboBox1.Text & "','" & TextBox2.Text & "','"& TextBox3.Text &"','" &
TextBox7.Text &"','" & TextBox8.Text & "')" cmd =New OleDbCommand(sql,
conn)
cmd.ExecuteReader()
MsgBox("Record Inserted", MsgBoxStyle.Information,
"Hospital Management") TextBox2.Text =""
TextBox3.Text =""
TextBox4.Text =""
RichTextBox4.Text =""
TextBox5.Text =""
TextBox6.Text =""
TextBox7.Text =""
TextBox8.Text =""
ComboBox1.Text =""
conn.close()
End Sub Private Suboutpatient_Load(ByValsender AsSystem.Object, ByVale
AsSystem.EventArgs) Handles MyBase.Load
Me.ComboBox1.Items.Add("Male")
Me.ComboBox1.Items.Add("Female")
End Sub End Class Inpatient Bill : ImportsSystem.Data
ImportsSystem.Data.OleDb Public Classinpatbill
Dimadp As NewOleDbDataAdapter
Dimds As NewDataSet
Dimx As New Integer
Dimcmd As NewOleDbCommand
Dimdr AsOleDbDataReader
Private SubButton1_Click(ByValsender AsSystem.Object,
ByVale AsSystem.EventArgs) HandlesButton1.Click Me.Hide()
mainmenu.Show() End Sub Private SubButton2_Click(ByValsender
AsSystem.Object, ByVale AsSystem.EventArgs) HandlesButton2.Click
conn.open() cmd =New OleDbCommand("insert into inbill values('" &
TextBox1.Text &"','" & ComboBox1.Text &"','" & TextBox3.Text
&"','" & DateTimePicker2.Text &"','" & TextBox8.Text &"','"
& TextBox9.Text &"','" & DateTimePicker1.Text &"','" &
DateTimePicker2.Text &"','" & TextBox11.Text &"')", conn)
cmd.ExecuteNonQuery() MsgBox("Bill Saved to Database",
MsgBoxStyle.OkOnly, "Hospital Management") cmd.Dispose()
TextBox1.Text =""
TextBox3.Text =""
TextBox8.Text =""
TextBox9.Text =""
TextBox10.Text =""
TextBox11.Text =""
ComboBox1.Text =""
DateTimePicker1.Value = Now.Date
DateTimePicker2.Value = Now.Date
conn.close()
End Sub Private Subinpatbill_Load(ByValsender AsSystem.Object, ByVale
AsSystem.EventArgs) Handles MyBase.Load ComboBox1.TabIndex = 0
TextBox9.TabIndex = 1
TextBox10.TabIndex = 2
TextBox11.TabIndex = 3
conn.open()
cmd =New OleDbCommand("select * from ipt", conn)
dr = cmd.ExecuteReader
While(dr.Read) ComboBox1.Items.Add(dr(0).ToString) End While cmd.Dispose()
cmd =New OleDbCommand("select max(bno) from inbill", conn) dr =
cmd.ExecuteReader If dr.Read = True Then TextBox1.Text = dr(0) + 1.ToString
Else TextBox1.Text = 1

End If cmd.Dispose() conn.close() End Sub Private

SubComboBox1_SelectedIndexChanged(ByValsender As System.Object,ByVal
eAs System.EventArgs)Handles ComboBox1.SelectedIndexChanged
conn.open()
adp =New OleDbDataAdapter("select * from ipt where
mrdno=' " & ComboBox1.Text & "'", adpx) adp.Fill(ds,"ipt")
TextBox3.Text = ds.Tables(0).Rows(0)(1).ToString
DateTimePicker1.Value = ds.Tables(0).Rows(0)
(10).ToString()
DateTimePicker2.Value = Now.Date
x = DateTimePicker2.Value.Day -
DateTimePicker1.Value.Day
TextBox8.Text = x * 300
conn.close()
End Sub Private SubTextBox11_Enter(ByValsender As Object, ByVal eAs
System.EventArgs)Handles TextBox11.Enter TextBox11.Text ="" Dim x, y, z As
New Integer x = TextBox8.Text
y = TextBox9.Text
z = TextBox10.Text
TextBox11.Text = x + y + z
End Sub Private SubButton4_Click(ByValsender AsSystem.Object, ByVale
AsSystem.EventArgs) HandlesButton4.Click iptbillview.Show() End Sub End
Class Outpatient Bill : ImportsSystem.Data.OleDb ImportsSystem.Data Public
Classoutpatbill
Dimadp As NewOleDbDataAdapter
Dimds As NewDataSet
Dimx As New Integer
Dimcmd As NewOleDbCommand
Dimdr AsOleDbDataReader
Private SubButton1_Click(ByValsender AsSystem.Object,
ByVale AsSystem.EventArgs) HandlesButton1.Click Me.Hide()
mainmenu.Show()

SCREENSHOTS:

MAIN MENU SCREEN:

OUTPATIENT ADMISSION:
INPATIENT REPORT:
BILL COLLECTION REPORT:
OUTPATIENT BILLS COLLECTION REPORT:
BIBILIOGRAPHY:
1.OOP WITH MICROSOFT VISUAL BASIC.NET AND MICROSOFT VISUAL
C#.NET STEP BY STEPBY ROBIN.A.REYNOLDS – HAERTLE – Microsoft
Press 2002

2.THE BOOK OF VISUAL BASIC 2005.by Matthew MacDonald – NO

STARCH PRESS

3.VB.NET Developer’s Guideby Syngress Publishing, Inc.

4.Visual Basic .NET How to Program Second Editionby Deitel & Associates, Inc.,

5. http://www.scribd.com

CONCLUSION:
 The proposed system has been designed to overcome all the drawbacks
found in the existing system. The new system has been proposed to use VISUAL
BASIC.NET as front end and SQL SERVERas backend.The proposed system has
enhanced features, which was not found in the existing system.

The salient features are

•Security for the data is done easily.

•Validation is done to enter correct data.
•Memory consumption is very less and the processing speed is fast
•Data reports are presented in a neat format
•It is apt for this modern world. It is easy to combine the database of other
software and to view the records in the files and also it is easy to get the reports by
giving input data.