PROJECT REPORT OF HOSPITAL

MANAGEMENT SYSTEM

Page No - 1

INTRODUCTION

Before moving on to the details, I would like to introduce my project in few

words. The topic of my project is “Hospital Management System”. It is a useful

system that can be used in any hospital to manage its working methods and various

activities. It is proposed to be designed for the automation of various activities of the

hospital and the integration of the information so that the proper tacking of a patient

profile and case history can be done.

The software seamlessly integrates various activities and functions of various

entities involved in a typical healthcare environment like patients, doctors,

pathological laboratory, OPD, radiology, IPD, ward management, operation theatre

etc. The software in broadly classified into the following modules: -

1) Reception/Registration.

2) OPD.

3) IPD.

4) Operation Theatre.

5) Pathology.

6) USG.

7) Doctors/ Consultants Management.

8) Certificate Management.

Thus, it can be seen that the software includes all the modules that can

manage various activities of a hospital, in an integrated way. The software has very

dynamic, pleasant and user-friendly interface and is very easy to use.

Page No - 2

OBJECTIVE

Every software has a goal or aim behind which it is developed. The objective

and scope of my software is to record the details of the patient maintaining the

diagnosis details, certificate management, discharge management etc. There are

various limitations and drawback in existing system: -

1) The existing system only provides text-based interface, which is not as user-

friendly as Graphical user Interface.

2) Since the system is implemented in Manual, so the response is very slow.

3) The transactions are executed in off-line mode, hence on-line data capture and

modification is not possible.

4) On-line reports cannot be generated due to batch mode execution.

Hence, there is a need of reformation of the system with more advantages and

flexibility. My software eliminates most of the limitations of the existing software.

It has the following objectives: -

1) Enhancement - The main objective of my software is to enhance and

upgrade the existing system by increasing its efficiency and effectiveness. The

software improves the working methods by replacing the existing manual

system with the computer-based system.

2) Automation - The software automates each and every activity of the manual

system and increases its throughput. Thus the response time of the system is

very less and it works very fast.

3) Accuracy - The software provides the uses a quick response with very

accurate information regarding the patient, doctors etc. Any details or system in

an accurate manner, as and when required.

Page No - 3

4) User-Friendly - The software has a very user-friendly interface. Thus the

users will feel very easy to work on it. The software provides accuracy along

with a pleasant interface.

5) Availability - The transaction reports of the system can be retried as and

when required. Thus, there is no delay in the availability of any information,

whatever needed, can be captured very quickly and easily.

Thus my software of Hospital management can be run on Windows

XP/2000 /2003. It gives a pleasant and user-friendly interface to my project. On

the basis of the functional requirement of the system, VB.6.0 seem to be an

appropriate tool for the front end and SQL-server for the back end.

TOOLS AND TECHNOLOGY

About Technology

Page No - 4

ABOUT VB:

Microsoft Visual Basic is new evolution in current era, whenever we need to develop any window-based application than we use VB. There have a lot of versions in VB like VB.6, VB.7 etc & we use VB.6 version to make this Project. The basic idea of introducing visual Basic to the

world was to provide a Rapid Application Development Environment to the developers. Visual Basic provides the first example of successful component object Model programming in which third Party available components could be added to provide additional functionality. It provides support for ODBS and RDO data access methods, which has brought Visual Basic into a realm of serious development tools. Through this Language Web Browser based application can be written with the help of Microsoft DHTML, Page designer .

Database- Microsoft SQL Server Microsoft SQL Server is a full-featured relational database

management system (RDBMS) that offers a variety of administrative tools to ease the burdens of database development, maintenance and administration. SQL Server2000 has six of the more frequently used tools: Enterprise Manager, Query Analyzer, SQL Profiler, Service Manager, Data Transformation Services and Books. Let's take a brief look at each:

Enterprise Manager is the main administrative console for SQL Server installations. It provides us with a graphical "birds-eye" view of all of the SQL Server installations on our network. We can perform high-level administrative functions that affect one or more servers, schedule common maintenance tasks or create and modify the structure of individual databases.

Query Analyzer offers a quick and dirty method for performing queries against any of our SQL Server databases. It's a great way to quickly pull information out of a database in response to a user request, test queries before implementing them in other applications, create/modify stored procedures and execute administrative tasks.

5. Hardware and Software requirement specification

Hardware Requirements

Intel Celeron Processor and above 128 MB RAM

25 MB free Hard Disk Space

Page No - 5

Software Requirements

1) Operating System: Windows 2000/ 2003 or above.

2) Language Visual Basic 6.0

3) Back End SQL Server 2000 or above

ANALYSIS

Systems analysis is about understanding situations, not solving problems. Effective analysts therefore emphasize investigation and questioning to learn how system

currently operates and to identify the requirements that the users have for a new system, the current system can be analyzed and the recommendations for system design can be assembled.

Requirement Determination: - It involves studying the current system to find out how it works and where improvements are to be made. This study results in an evaluation of how current methods are working and whether adjustments are necessary or possible.

Page No - 6

Requirement is a feature that must be included in a new system. It may include a way of capturing or processing data, producing information, controlling activities and supporting management. The determination of requirements thus entails studying the existing system and collecting details about it to find out what these requirements are.

Before beginning the designing process of my software, I analyzed the current Hospital Management System, to determine the requirements of new system. I analyzed various departments of system. I analyzed various departments in hospital – OPD, IPD, Pathology, Ultrasound, X-Ray, etc. I also reviewed the reports generated in these departments, to improve the accuracy and decrease the complexity.

Activities in Requirement Determination: - Requirement determination process consists of following activities: -

1) Requirement Anticipation : - In this activity, the analyst foresees the likelihood of certain problems or features and requirements for a new system. It causes the analyst to investigate the areas and issues that could otherwise be overlooked.

2) Requirement Investigation : - This activity is at the heart of system analysis. Using a variety of tools and skills, the analyst studies the current system and documents its features for further analysis. It relies o fact- finding techniques and includes methods for describing system features.

3) Requirement Specification : -The data produced during the fact-finding investigation are analyzed to determine requirements specifications. The description of features for a new system.

Data Collection: - The main activity in requirement determination is the collection of data about the current system. So that, the performance of system can be improved. The specific methods that are used for collecting data about requirements are called fact-finding techniques. They may include interviews, questionnaires, record inspections, and observation etc. one or more techniques among these can be employed for data collection to help ensure an accurate and comprehensive investigation.

Hospital Management System”. is a useful system that can be used in any hospital to manage its working methods and various activities. It is proposed to be designed for the automation of various activities of the hospital and the integration of the information so that the proper tacking of a patient profile and case history can be done.

The software seamlessly integrates various activities and functions of various entities involved in a typical healthcare environment like patients, doctors, pathological laboratory, OPD, radiology, IPD, ward management, operation theatre etc. The software in broadly classified into the following modules: -

9) Reception/Registration.10) OPD.

Page No - 7

11) IPD.12) Operation Theatre.13) Pathology.14) USG.15) Doctors/ Consultants Management.16) Certificate Management.

Thus, it can be seen that the software includes all the modules that can Manage various activities of a hospital, in an integrated way. The software has very dynamic, pleasant and user-friendly interface and is very easy to use.

Thus, it can be seen that the software includes all the modules that can manage various activities of a hospital, in an integrated way. The software has very dynamic, pleasant and user-friendly interface and is very easy to use.

Every software has a goal or aim behind which it is developed. The objective and

scope of my software is to record the details of the patient maintaining the diagnosis details, certificate management, discharge management etc. There are various limitations and drawback in existing system: -

5) The existing system only provides text-based interface, which is not as user-friendly as Graphical user Interface.

6) Since the system is implemented in Manual, so the response is very slow.7) The transactions are executed in off-line mode, hence on-line data capture and

modification is not possible.8) On-line reports cannot be generated due to batch mode execution.

SRS Software requirement specification

Software requirement specification contains details of the proposed software system.

In the view of Online Job Portal System, SRS gives all details of its introduction,

overall description, specific requirements and basic processing etc. A simple and

introductory SRS is as follows:--

INTRODUCTION

Purpose: SRS provides details of the proposed software project. Thus SRS is

a means of communicating the findings of the analysis stage to the design stage.

Scope: The scope of SRS includes:-

Page No - 8

Proposed software description

Users of the proposed software

Constraints

Overview :

OVERALL DESCRIPTION

Product description: The candidate should be able to register itself through

the registration form and the he can upload his resume which will be saved into the

Database. A company also can register itself and upload its requirement of the

candidate. These new data are checked by the admin.

Product functioning: The raw data from clients is put into the database that is

candidates and companies can upload their profiles this will then saved in the

database that can be searched by the admin later .

When user login to the website, first he should be authenticated and then

authorization should take place whether he is admin or user, after that on can work

further online.

Users of the Project: Since the project Online Job Portal Management System

is a job portal system so users of this project are students at various levels such as

graduate level, PG level, or working professionals and companies will also visit the

site for their recruitment process.

SPECIFIC REQUIREMENTS:

Interface Requirements:

Easy to follow Interface

Very less graphics

No hidden buttons

User Requirements: After the carefully study of requirements of the users,

some basic requirements of users are

A candidate can register itself easily and find job lists according to his

eligibility

He can find proper tips for making effective resume and for facing

interviews

He can easily update his resume time to time

Page No - 9

He can find proper job alerts time to time through e-mails

A company can find eligible candidate for their working criteria

Admin can see the current status of jobs and candidates

Hardware and Software Requirements: There are three environments that

have been created for the project, viz,

Development environment

Quality Control environment

Production environment

The hardware requirements for all the platforms are:

Since the project is based on the .Net framework, so it can run all platforms and

basic hardware requirements are—

1. 256 MB RAM

2. 4 GB HDD (normally)

3. Pentium family processor

Logical Database Requirements: The following information is to be stored in

the database:

The Clients Raw data

The Clients Validated data

Username and Password

Companies profiles

Detailed job list

BASIC PROCESSING ACTIONS OF THE SYSTEM:

The basic processing actions of the system are:

Verification of the User: A registered user can login with his user-id and

password and system will verify that user login is valid or not.

Upload Data: After the login, candidate can upload his resume which will

save in the database.

Search Data: A candidate can also search data such as job, resume sample,

tips etc. through various options, once user send his query system will match it with

data store in database and give response.

INPUT / OUTPUT FORMATS:

The input format: The input formats for the system plays an important role, so

its format should be attractive, easy and less complex. The basic input format for the

system contains the following screens:

Page No - 10

Square box is used for user input

Rounded Square box is used for system display

Login screen: The following screen that inputs the Username and Password

from the User for authentication of User to the system is:

Output format: The outputs from the system should be in form of list such as

list of job details, list of candidates etc. and admin can find information in the form of

reports.

These are some requirement specifications of the system. Few more specifications

can also be added.

DFD (DATA FLOW DIAGRAM)

Data Flow Diagram

Context Diagram: -

Patient Details Reg. No.

Test Basics Pathology Of Report Patient X-Ray

Report X-Ray Details Surgery

Report

Page No - 11

Login Id

Password

Hospital

Management

System

New Patient

Pathology Department

X-Ray Department

User

Medicine Managemen

Certificate Managemen Final Bill

Surgery

X-Ray

Pathology

Patient Card

Close Login

Parts To be Examined Final Discharge

& CashSurgery Type Medicine

Issued

Receive Order Bill

SlipPrescription

Registration Issued All Certificate Certificate

TransactionNotice

Level 1 DFD: -

Patient

Record Patient FilePatient Details

Case details Case Sheet

History

Updated Patient History Patient Slip

Case Details

Page No - 12

Discharge Management

Billing

Surgery Management

Discharge

Certificate

Medicine Issued / Sell

1 Patient Management

New Patient

2 OPD Management

Prescription

Referred To Patient FileDoctor

OPD Reports

Details Report Patient File

Details

Pathology File

X-Ray File U.S.G. File C.T. Scan File

Page No - 13

Diagnosis Details

3 Diagnosis Management

Pathology Department

X-Ray Department

U.S.G. Department

C.T. Scan Department

To be Patient FileAdmitted

IPD File

IPD File

Report

Surgery File

IPD File

Medicine File

IPD File

Surgery File

Page No - 14

4 IPD Management

Ward Manager

IPD Registration

5 Surgery Management

OT Management

Surgical Details

6 Medicine Management

Medicine Department

7 Billing Management

Find Bill Sanction

Medicine File

Test File

Patient File

IPD File

Pay SlipPatient File

OPD File

IPD File Surgery File Billing File

Page No - 15

8 Certificate Management

Death Certificate

Fitness Certificate

Birth Certificate

9 Final Slip or

Report Prescription

Surgery Department

Discharge Card

ERD (E-R DIAGRAM)

E-R Diagram

Page No - 16

Doctor

Patient

Treats

Ward

Visits

Final Bill

Receives

Pathology

Tests

X-Ray

Are Referred

AreReffered

Id Address

Phone Name

Issues Test

Test Value

Test-Id

Normal Value

Clinician In charge

Examined By

Details

Test Result

Position

Test -Id

Test-Result

Examined By

Details

No. Of Beds

Ward- No.

In charge

ChargesBill No.

OPD No

Name

Sex

Age

DESIGN DOCUMENTATION

Modularization

NUMBER OF MODULES

There are various modules used in my software “Hospital Management System” each

having a different purpose. They are as follows: -

1) Reception / Registration Counter - This module manages the reception where different types of inquiry can be handled and the registration for new patient takes place. As the patient enters, the hospital there can be two options; one is that he can be there for the first time; other option is that he has already visited the Hospital. If he is a first time patient, then he will be issued an OPD Card, if he has already visited the hospital, the card will be renewed. Various validation checks and conditions are been provided for some controlling purpose.

2) O.P.D. – This module manages the detail about the outpatient department. Any new patient generally comes to the OPD. In the reception modules the new patient is filled the registration form. This module is managing the details provided in the form. (For any future reference).

Page No - 17

Ultra SoundTest -Id

3) I.P.D. - If the patient has to be admitted then this module is been used to record various information about the patient like, his bed status, his OT schedule, medicine given, treatment chart and then such information till the patient is been discharged.

4) Operation Theatre - In this module, the schedule of operation theatre is prepared like on which date and time at which patient has to be operated. It also manages that in which OT room which table, how man doctors are going to do the surgery. The surgery type and many other such details related to the operations are been recorded and managed.

5) Pathology - It plays a major role in the software, as there are a lot of test that a doctor suggests a patient and they are done through pathology. Every hospital has its own premises, so it is convenience to have a module for managing the pathology unit of hospital. This module manages the various test details and reports for the patient. The tests can be categorized into Chemistry, Hematology/ Herpetology, General or routine test, Hormone etc. The software checks the date-wise rest reports and test details to ensure accuracy and correctness.

6) USG - This module manages the ultrasound details. The major categories of ultrasound are chemistry, Abdomen liver, Gall bladder etc. The software can check the date wise reports and test details.

7) Doctors/ Consultant Management - This module manages all the details regarding the doctors like their personal details, emergency phone no., the day and time they visit hospital, their chamber no. their consultation fee etc. It provides various facilities for editing and searching the records.

Page No - 18

8) Certificate Management - This module manages the various certificated to be issued by the hospital like discharge certificates, fitness certificate, illness certificate, birth certificate etc.

DATA INTEGRITY

Data Integrity –

Data integrity refers to the validity of data, meaning data is consistent and correct. In the data warehousing field, we frequently hear the term, "Garbage In, Garbage Out." If there is no data integrity in the data warehouse, any resulting report and analysis will not be useful.

In a data warehouse or a data mart, there are three areas of where data integrity needs to be enforced:

Database level

We can enforce data integrity at the database level. Common ways of enforcing data integrity include:

Referential integrity

The relationship between the primary key of one table and the foreign key of another table must always be maintained. For example, a primary key cannot be deleted if there is still a foreign key that refers to this primary key.

Primary key / Unique constraint

Primary keys and the UNIQUE constraint are used to make sure every row in a table can be uniquely identified.

Not NULL vs NULL-able

For columns identified as NOT NULL, they may not have a NULL value.

Valid Values

Only allowed values are permitted in the database. For example, if a column can only have positive integers, a value of '-1' cannot be allowed.

Page No - 19

Types of Data Integrity

This section describes the rules that can be applied to table columns to enforce different types of data integrity.

Null Rule

A null rule is a rule defined on a single column that allows or disallows inserts or updates of rows containing a null (the absence of a value) in that column.

Unique Column Values

A unique value rule defined on a column (or set of columns) allows the insert or update of a row only if it contains a unique value in that column (or set of columns).

Primary Key Values

A primary key value rule defined on a key (a column or set of columns) specifies that each row in the table can be uniquely identified by the values in the key.

Referential Integrity Rules

A referential integrity rule is a rule defined on a key (a column or set of columns) in one table that guarantees that the values in that key match the values in a key in a related table (the referenced value).

Referential integrity also includes the rules that dictate what types of data manipulation are allowed on referenced values and how these actions affect dependent values. The rules associated with referential integrity are:

Restrict: Disallows the update or deletion of referenced data. Set to Null: When referenced data is updated or deleted, all

associated dependent data is set to NULL.

Set to Default: When referenced data is updated or deleted, all associated dependent data is set to a default value.

Cascade: When referenced data is updated, all associated dependent data is correspondingly updated. When a referenced row is deleted, all associated dependent rows are deleted.

Page No - 20

No Action: Disallows the update or deletion of referenced data. This differs from RESTRICT in that it is checked at the end of the statement, or at the end of the transaction if the constraint is deferred. (Oracle uses No Action as its default action.)

Complex Integrity Checking

Complex integrity checking is a user-defined rule for a column (or set of columns) that allows or disallows inserts, updates, or deletes of a row based on the value it contains for the column (or set of columns).

DATA STRUCTURE

There are tables created in the software as data structures, used to store and maintain information related to various entities and the other relative information. Some of the major tables used in the software are as follows: -

Table Name: Patient

This table contains the detail information for the patient been registered.

Field NameType

PatientId Auto Number

Name Varchar (30)

Address Varchar (60)

DateOfBirth DateTime

Phone Varchar (15)

DateOfRegistration DateTime

Sex Varchar (8)

Primary Key – PatientId

Table Name: Doctor

It is a table, where the list of all available doctors in the hospital is maintained.

Page No - 21

Field NameType

DoctorId Auto Number

Name Varchar (30)

Address Varchar (60)

Specialization Varchar (30)

Qualification Varchar (50)

Sex Varchar (8)

E-mail Varchar (30)

Primary Key – DoctorId

Table Name: Bed

It is a master table, where the list of all beds in the hospital is maintained. Before a bed is assigned to a patient, this table is checked for the availability.

Field NameType

BedId Auto Number

BedName Varchar (30)

RatePerDay Number

BedType Varchar (30)

Primary Key – BedId

Table Name: Visit

This is a detail table where the record for each visit of each patient is created and maintained.

Field NameType

Id Auto Number

PatientType Number

Page No - 22

DoctorID Number

BedId Number

DateOfVisit DateTime

DateOfDischarge DateTime

Symptoms Varchar (1000)

Disease Varchar (100)

Treatment Varchar (1000)

Primary Key – Id

Table Name: X-Ray

This table includes the record for X-Ray details for patient (whom X-Ray is referred) .

Field NameType

TestId Auto Number

PatientName Varchar (30)

ReferredBy Varchar (30)

ExaminedBy Varchar (30)

Region Varchar (20)

Position Varchar (20)

TestResult Varchar (50)

Primary Key – TestId

Table Name: Histopathology

This is a table that contains records for histopathology requisition and report.

Page No - 23

Field NameType

TestId Number

Date DateTime

ClinicianDiagnosis Varchar (50)

RecieptNo. Varchar (10)

NatureOfMaterial Varchar (50)

ClinicianIncharge Varchar (30)

Microscopic Varchar (50)

Primary Key – TestId

Table Name: CultureTest

This table contains information related to the pathology culture tests.

Field NameType

TestId Auto Number

Amoxiycillin Number

Ampicillin Number

Bacitracin Number

Pencillin Number

Septran Number

Doxycycline Number

Erthromycin Number

Gentamycin Number

Primary Key – TestId

Table Name: SemenAnalysis

This table contains record related the semen analysis in pathology.

Page No - 24

Field NameType

TestId Auto Number

Color Varchar (15)

Volume Number

Count Number

Motility Number

NormalType Number

AbnormalType Number

NonMotility Number

Primary Key – TestId

Table Name: LabTest

This is a table where all the details for each laboratory test for the patient (to which the test is referred), is created and maintained.

Field NameType

TestId Auto Number

Cholesterol Number

Tryglycerides Number

Sodium Number

Potassium Number

CPK Number

BloodSugar Number

BloodUrea Number

RAFactor Number

Primary Key – TestId

Page No - 25

Table Name: Ward

This detail table contains the details related to the wards in the hospital.

Field NameType

WardId Auto Number

Type Number

Name Number

Location DateTime

TotalBeds DateTime

Primary Key – WardI

USER INTERFACE

Abbreviated GUI (pronounced GOO-ee). A program interface that takes advantage of

the computer's graphics capabilities to make the program easier to use. Well-designed

graphical user interfaces can free the user from learning complex command languages.

On the other hand, many users find that they work

more effectively with a command-driven interface, especially if they already know the command language.

Graphical user interfaces, such as Microsoft Windows and the one used by the Apple Macintosh, feature the following basic components:

pointer : A symbol that appears on the display screen and that you move to select objects and commands. Usually, the pointer appears as a small angled arrow. Text -processing applications, however, use an I-beam pointer that is shaped like a capital I. pointing device : A device, such as a mouse or trackball, that enables you to select objects on the display screen. icons : Small pictures that represent commands, files, or windows. By moving the pointer to the icon and pressing a mouse button, you can execute a command or convert the icon into a window. You can also move the icons around the display screen as if they were real objects on your desk.

Page No - 26

desktop : The area on the display screen where icons are grouped is often referred to as the desktop because the icons are intended to represent real objects on a real desktop. windows: You can divide the screen into different areas. In each window, you can run a different program or display a different file. You can move windows around the display screen, and change their shape and size at will. menus : Most graphical user interfaces let you execute commands by selecting a choice from a menu.

The first graphical user interface was designed by Xerox Corporation's Palo Alto Research Center in the 1970s, but it was not until the 1980s and the emergence of the Apple Macintosh that graphical user interfaces became popular. One reason for their slow acceptance was the fact that they require considerable CPU power and a high-quality monitor, which until recently were prohibitively expensive.

In addition to their visual components, graphical user interfaces also make it easier to move data from one application to another. A true GUI includes standard formats for representing text and graphics. Because the formats are well-defined, different programs that run under a common GUI can share data. This makes it possible, for example, to copy a graph created by a spreadsheet program into a document created by a word processor.

Many DOS programs include some features of GUIs, such as menus, but are not graphics based. Such interfaces are sometimes called graphical character-based user interfaces to distinguish them from true GUIs.

Page No - 27

Procedural Design

1) Patient registration: - When a new patient arrives to the hospital, he has to be

registered. After

registration he receives an OPD card, if he is an OPD patient.

The registration table is been updated with the record of new patient.

2) Taking General Details: - After being registered the new patient goes to a junior

doctor. The

Junior doctor takes his general health details and refers

him to a senior doctor. These details help in maintaining the patient case sheet.

3) IPD Patient moving to ward: - The IPD Patient is moved to a ward, as he is to be

admitted.

There are two cases of the patient to be admitted.

The OPD patient can be moved to IPD or a new patient can be admitted as an

emergency.

4) Treatment given: - As, referred by the junior doctor, patient is been treated by a

senior doctor.

The doctor gives him the prescription, medicines and

suggestions.

Page No - 28

5) Patient referred for pathology test: - The patient is been referred for some pathology

test by

Senior doctor, if required. The pathology table

is been maintained and updated with the new record patient.

6) Issuing Test ID: - If the patient is referred for some pathology test, he is been issued

a

Test id, by the pathology department. Only after, a test id is

provided to the patient, he can be tested.

7) Pathology Test: - The patients who are provided a test id, are been tested for the

pathology

test, been referred.

8) Patient referred for Ultrasound: - The senior doctor may refer Patients for

Ultrasound,

generally, if they are to be operated or in the case

of pregnancy.

9) Taking Ultrasound: -The ultrasound of patient is been done, especially in case, if

they are to

be operated or in the case of pregnancy. The ultrasound is

been taken of some specific regions like pelvis, abdomen, transvaginal etc.

10) Patient referred for operation: - The patient may also be referred for operation.

When a

patient is been operated; the surgery table is been

updated with the patient details, details of junior doctor, consultant doctor, O.T. In

charge and nurses to be involved in the operation.

Page No - 29

11) Patient operated: - The patient, referred for operation, is been operated. In the

surgery,

Senior doctors, junior doctor, consultant doctors and nurses are

been involved. The surgery table is been maintained with these details.

12) Patient referred for X-Ray: - The senior doctor may refer patient for X-Ray of

some region.

The X-Ray table is been maintained with the details

of X-Ray.

13) Taking X-Ray: - The X-Ray of patient is been taken as, referred by the senior

doctor. The X-

Ray table is been maintained by its details.

14) Patient discharged: - The patient is been discharged after having treatment in

hospital. When the patient is been discharged, the patient is been issued the discharge

certificate and the discharge table is maintained with etc.

Page No - 30

FORM DESIGN AND SOURCE CODE

FORM 1- LOGIN FORM

Page No - 31

FORM 2 - MDI FORM

Page No - 32

FORM3 –PATIENT FORM

Page No - 33

FORM4 -DOCTOR FORM

Page No - 34

FORM5 -VISIT FORM

Page No - 35

FORM6 -TEST FORM

SOURCE CODE

FORM1Private Sub Command3_Click()form2.Sho

Page No - 36

FORM2-MDI FORMPrivate Sub MDIForm_Load()MDIForm1.Visible = FalseForm1.ShowEnd Sub

Private Sub O1_Click()form3.Visible = Falseform4.Visible = Falseform5.Visible = Falseform2.ShowEnd Sub

Private Sub O2_Click()form2.Visible = Falseform4.Visible = Falseform5.Visible = Falseform3.ShowEnd Sub

Private Sub O3_Click()form3.Visible = Falseform2.Visible = Falseform5.Visible = Falseform4.ShowEnd Sub

Private Sub O4_Click()form3.Visible = Falseform4.Visible = Falseform2.Visible = Falseform5.ShowEnd Sub

Private Sub O5_Click()Unload MeEnd Sub

FORM 3

Page No - 37

Private Sub Command1_Click()Frame1.Visible = FalseIf Text1.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text2.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text3.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text4.Text = "" Then MsgBox "ENTER THE DATA"Exit SubElseIf Text5.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text6.Text = "" Then MsgBox "ENTER THE DATA" Exit Sub End If msg = MsgBox("ARE YOU SURE YOU WANT TO ADD THE RECORD?", vbYesNo)If msg = vbYes ThenText1.SetFocusData1.Recordset.MoveNextData1.Recordset.AddNewElseIf msg = vbNo ThenText1.SetFocusEnd IfEnd Sub

Private Sub Command2_Click()Frame1.Visible = TrueEnd Sub

Private Sub Command3_Click()Frame1.Visible = FalseData1.RefreshMsgBox "DATA IS SAVED"Text1.SetFocusEnd Sub

Page No - 38

Private Sub Command4_Click()Dim book As StringDim F As IntegerF = 0book = InputBox("ENTER THE BOOK NAME WHICH YOU WANT TO DELETE")Data1.Recordset.MoveFirstDo While (Data1.Recordset.EOF <> True)If (Data1.Recordset.Fields(0) = book) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenData1.Recordset.DeleteData1.RefreshMsgBox ("RECORD IS DELETED")ElseMsgBox ("SORRY!RECORD IS NOT DELETED")End IfEnd Sub

Private Sub Command5_Click()Unload MeEnd Sub

Private Sub Command6_Click()Dim str As Stringstr = InputBox("PLEASE ENTER THE BOOK FOR SEARCHING")Data1.Recordset.MoveFirstF = 0Do While (Data1.Recordset.EOF <> True)If (Trim(Data1.Recordset.Fields(0)) = Trim(str)) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenMsgBox ("FOUND")ElseMsgBox ("NOT FOUND")

Page No - 39

End IfEnd Sub

Private Sub Command7_Click()Dim str As StringDim F As Integerstr = InputBox("ENTER THE BOOK NO WHICH YOU WANT TO UPDATE")Data1.Recordset.MoveFirstF = 0Do While (Data1.Recordset.EOF <> True)If (Trim(Data1.Recordset.Fields(0)) = Trim(str)) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenText1.Locked = FalseText2.Locked = FalseText3.Locked = FalseText4.Locked = FalseText5.Locked = FalseText6.Locked = False Text1.SetFocusData1.Recordset.EditElseMsgBox ("RECORD IS NOT FOUND SO DON'T UPDATES")End IfEnd Sub

Private Sub Form_Click()Frame1.Visible = FalseEnd Sub

Private Sub Form_Load()Frame1.Visible = FalseEnd Sub

Private Sub Command1_Click()Frame1.Visible = False

Page No - 40

If Text1.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text2.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text3.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text4.Text = "" Then MsgBox "ENTER THE DATA"Exit SubElseIf Text5.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text6.Text = "" Then MsgBox "ENTER THE DATA" Exit Sub End If msg = MsgBox("ARE YOU SURE YOU WANT TO ADD THE RECORD?", vbYesNo)If msg = vbYes ThenText1.SetFocusData1.Recordset.MoveNextData1.Recordset.AddNewElseIf msg = vbNo ThenText1.SetFocusEnd IfEnd Sub

Private Sub Command2_Click()Frame1.Visible = TrueEnd Sub

Private Sub Command3_Click()Frame1.Visible = FalseData1.RefreshMsgBox "DATA IS SAVED"Text1.SetFocusEnd Sub

Private Sub Command4_Click()Dim book As String

Page No - 41

Dim F As IntegerF = 0book = InputBox("ENTER THE BOOK NAME WHICH YOU WANT TO DELETE")Data1.Recordset.MoveFirstDo While (Data1.Recordset.EOF <> True)If (Data1.Recordset.Fields(0) = book) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenData1.Recordset.DeleteData1.RefreshMsgBox ("RECORD IS DELETED")ElseMsgBox ("SORRY!RECORD IS NOT DELETED")End IfEnd Sub

Private Sub Command5_Click()Unload MeEnd Sub

Private Sub Command6_Click()Dim str As Stringstr = InputBox("PLEASE ENTER THE BOOK FOR SEARCHING")Data1.Recordset.MoveFirstF = 0Do While (Data1.Recordset.EOF <> True)If (Trim(Data1.Recordset.Fields(0)) = Trim(str)) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenMsgBox ("FOUND")ElseMsgBox ("NOT FOUND")End IfEnd Sub

Page No - 42

Private Sub Command7_Click()Dim str As StringDim F As Integerstr = InputBox("ENTER THE BOOK NO WHICH YOU WANT TO UPDATE")Data1.Recordset.MoveFirstF = 0Do While (Data1.Recordset.EOF <> True)If (Trim(Data1.Recordset.Fields(0)) = Trim(str)) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenText1.Locked = FalseText2.Locked = FalseText3.Locked = FalseText4.Locked = FalseText5.Locked = FalseText6.Locked = False Text1.SetFocusData1.Recordset.EditElseMsgBox ("RECORD IS NOT FOUND SO DON'T UPDATES")End IfEnd Sub

Private Sub Form_Click()Frame1.Visible = FalseEnd Sub

Private Sub Form_Load()Frame1.Visible = FalseEnd Sub

FORM5

Page No - 43

Private Sub Command1_Click()Frame1.Visible = FalseIf Text1.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text2.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text3.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text4.Text = "" Then MsgBox "ENTER THE DATA"Exit SubElseIf Text5.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text6.Text = "" Then MsgBox "ENTER THE DATA" Exit Sub End If msg = MsgBox("ARE YOU SURE YOU WANT TO ADD THE RECORD?", vbYesNo)If msg = vbYes ThenText1.SetFocusData1.Recordset.MoveNextData1.Recordset.AddNewElseIf msg = vbNo ThenText1.SetFocusEnd IfEnd Sub

Private Sub Command2_Click()Frame1.Visible = TrueEnd Sub

Private Sub Command3_Click()Frame1.Visible = FalseData1.RefreshMsgBox "DATA IS SAVED"Text1.SetFocusEnd Sub

Page No - 44

Private Sub Command4_Click()Dim book As StringDim F As IntegerF = 0book = InputBox("ENTER THE BOOK NAME WHICH YOU WANT TO DELETE")Data1.Recordset.MoveFirstDo While (Data1.Recordset.EOF <> True)If (Data1.Recordset.Fields(0) = book) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenData1.Recordset.DeleteData1.RefreshMsgBox ("RECORD IS DELETED")ElseMsgBox ("SORRY!RECORD IS NOT DELETED")End IfEnd Sub

Private Sub Command5_Click()Unload MeEnd Sub

Private Sub Command6_Click()Dim str As Stringstr = InputBox("PLEASE ENTER THE BOOK FOR SEARCHING")Data1.Recordset.MoveFirstF = 0Do While (Data1.Recordset.EOF <> True)If (Trim(Data1.Recordset.Fields(0)) = Trim(str)) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenMsgBox ("FOUND")ElseMsgBox ("NOT FOUND")

Page No - 45

End IfEnd Sub

Private Sub Command7_Click()Dim str As StringDim F As Integerstr = InputBox("ENTER THE BOOK NO WHICH YOU WANT TO UPDATE")Data1.Recordset.MoveFirstF = 0Do While (Data1.Recordset.EOF <> True)If (Trim(Data1.Recordset.Fields(0)) = Trim(str)) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenText1.Locked = FalseText2.Locked = FalseText3.Locked = FalseText4.Locked = FalseText5.Locked = FalseText6.Locked = False Text1.SetFocusData1.Recordset.EditElseMsgBox ("RECORD IS NOT FOUND SO DON'T UPDATES")End IfEnd Sub

Private Sub Form_Click()Frame1.Visible = FalseEnd Sub

Private Sub Form_Load()Frame1.Visible = FalseEnd Sub

Page No - 46

Page No - 47

FORM6

Page No - 48

Private Sub Command1_Click()Frame1.Visible = FalseIf Text1.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text2.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text3.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text4.Text = "" Then MsgBox "ENTER THE DATA"Exit SubElseIf Text5.Text = "" Then MsgBox "ENTER THE DATA" Exit SubElseIf Text6.Text = "" Then MsgBox "ENTER THE DATA" Exit Sub End If msg = MsgBox("ARE YOU SURE YOU WANT TO ADD THE RECORD?", vbYesNo)If msg = vbYes ThenText1.SetFocusData1.Recordset.MoveNextData1.Recordset.AddNewElseIf msg = vbNo Then

Page No - 49

Text1.SetFocusEnd IfEnd Sub

Private Sub Command2_Click()Frame1.Visible = TrueEnd Sub

Private Sub Command3_Click()Frame1.Visible = FalseData1.RefreshMsgBox "DATA IS SAVED"Text1.SetFocusEnd Sub

Private Sub Command4_Click()Dim book As StringDim F As IntegerF = 0book = InputBox("ENTER THE BOOK NAME WHICH YOU WANT TO DELETE")Data1.Recordset.MoveFirstDo While (Data1.Recordset.EOF <> True)If (Data1.Recordset.Fields(0) = book) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenData1.Recordset.DeleteData1.RefreshMsgBox ("RECORD IS DELETED")ElseMsgBox ("SORRY!RECORD IS NOT DELETED")End IfEnd Sub

Private Sub Command5_Click()Unload MeEnd Sub

Private Sub Command6_Click()

Page No - 50

Dim str As Stringstr = InputBox("PLEASE ENTER THE BOOK FOR SEARCHING")Data1.Recordset.MoveFirstF = 0Do While (Data1.Recordset.EOF <> True)If (Trim(Data1.Recordset.Fields(0)) = Trim(str)) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenMsgBox ("FOUND")ElseMsgBox ("NOT FOUND")End IfEnd Sub

Private Sub Command7_Click()Dim str As StringDim F As Integerstr = InputBox("ENTER THE BOOK NO WHICH YOU WANT TO UPDATE")Data1.Recordset.MoveFirstF = 0Do While (Data1.Recordset.EOF <> True)If (Trim(Data1.Recordset.Fields(0)) = Trim(str)) ThenF = 1Exit DoEnd IfData1.Recordset.MoveNextLoopIf (F = 1) ThenText1.Locked = FalseText2.Locked = FalseText3.Locked = FalseText4.Locked = FalseText5.Locked = FalseText6.Locked = False Text1.SetFocusData1.Recordset.EditElseMsgBox ("RECORD IS NOT FOUND SO DON'T UPDATES")

Page No - 51

End IfEnd Sub

Private Sub Form_Click()Frame1.Visible = FalseEnd Sub

Private Sub Form_Load()Frame1.Visible = FalseEnd Sub

TESTING

Testing Practice And Plans:

It should be clear in mind that the philosophy behind testing is to find errors. Test cases are

devised with this purpose in mind. A test case is a set of data that the system will process as

normal input. However, the data are created with the express intent of determining whether

the system will process them correctly.

Testing Objectives: The objective of the testing is:-

Verify integration between objects.

Verify integration of all components of the software

To identify the defects prior t deployment of software

There are two general strategies for testing software: Code Testing and Specification

Testing. In case testing, the analyst develops that case to execute every instructions and path

in a program. Under specification testing, the analyst examines the program specifications

and then writes test data to determine how the program operates under specific conditions.

Regardless of which strategy the analyst follows, there are preferred practices to ensure that

the testing is useful. The levels of tests and types of test data, combined with testing libraries,

are important aspects of the actual test process.

Page No - 52

Levels Of Tests:

Systems are not designed as entire systems nor are they tested as single systems. The

analyst must perform both unit and system testing.

Unit Testing:

In unit testing the analyst tests the programs making up a system. For this reason, unit

testing is sometimes called program testing. Unit testing gives stress on the modules

independently of one another, to find errors. This helps the tester in detecting errors in coding

and logic that are contained within that module alone. The errors resulting form the

interaction between modules are initially avoided. For each, it provides that ability to enter,

modify or retrieve data and respond to different types of inquiries or print reports. The test

cases needed for unit testing should exercise each condition and option.

System Testing:

The important and essential part of the system development phase, after designing and

developing the software is system testing. It cannot say that every program or system design

is perfect and because of lack of communication between the user and the designer, some

error is there in the software development. The number and nature of error in a newly

designed system depend on some usual factors like communication between the user and the

designer the programmer’s ability to generate a code that reflects exactly the system

specifications and the time frame for the design.

Testing is an important function to the success of the system. System testing makes a

logical assumption that if all the parts of the system are correct, the goal will be successfully

activated. Another reason for system testing is its utility as a user-oriented vehicle before

implementation.

System testing consists of the following five steps:

Program Testing

Page No - 53

String Testing

System Testing

System Documentation

User Acceptance Testing

Program Testing:

A program represents the logical elements of a system. For a program to run

satisfactorily, it must compile and test data correctly and tie in properly with other programs.

It is the responsibility of programmer to have an error free program. At the time of testing the

system, there exists two types of errors that should be checked. These errors are syntax and

logic. A syntax error is a program statement that violates one or more rules of the language in

which it is written. An improperly defined field dimension or omitted key words are common

syntax errors. These errors are shown through error messages generated by the computer. A

logic error on the other hand, deals with incorrect data fields out of range items, and invalid

combinations. Since compiler does not detect the logical errors, the programmer must

examine the output carefully to detect them.

When a program is tested, the actual output is compared with the expected output.

When there is a discrepancy, the sequence of the instructions, must he traced to determine the

problem. Breaking the program down into self-contained portions, each of which can be

checked at certain key points, facilitates the process.

String Testing:

Programs are invariably related to one another and interact in a total system. Each

program is tested to see whether it conforms to related programs in the system. Each part of

the system is tested against the entire module with both test and live data before the whole

system is ready to be tested.

System Testing:

System testing is designed to uncover weaknesses that were not found in earlier tests.

This includes forced system failure and validation of total system as it will be implemented

by its user in the operational environment. Under this testing, generally we take low volumes

of transaction based on live data. This volume is increased until the maximum level for each

Page No - 54

transaction type is reached. The total system is also tested for recovery and fallback after

various major failures to ensure that no data are lost during the emergency. All this is done

with the old system still in operation. When we see that the proposed system is successful in

the test, the old system is discontinued.

User Acceptance Testing:

An acceptance test has the objective of selling the user on the validity and reliability

of the system. It verifies that the system’s procedures operate to system specifications and

that the integrity of important data is maintained. Performance of an acceptance test is

actually the user’s show. User motivation is very important for the successful performance of

the system. After that a comprehensive test report is prepared. This report shows the system’s

tolerance, performance range, error rate and accuracy.

Designing Test Data:

The proper designing of test data is as important as the test itself. If test data as input

are not valid or representation of the data to be provided by the user, Then the reliability of

the output is doubtful. Test data may be live or artificial. The live data is that which is

actually extracted from the user’s files. After a system is partially constructed, the

programmers or analysts ask the users to key in a set of data from their normal activities. It is

difficult to obtain live data in sufficient amount to conduct extensive testing.

Need For Documentation:

Preparation of documentation is quite important as it depicts what the system is

supposed to be and how to be and how it should perform its functions. It illustrates both

technically and economically how a system would better serve the objectives and goals of the

company. Documentation improves overall operation in addition to management and audit

control. It also serves the following purposes:

i. Reviews the progress or development of application software.

ii. Communicates facts about system to users.

Page No - 55

iii. Communicates between personnel working on a development

project.Provides necessary guidelines to allow correction or revision of a

system or its computer programs.

Maintainence

System Maintainence

The last part of the system development life cycle is system maintenance, which is actually

the implementation of the post-implementation review plan. When systems are installed, they

are generally used for long periods. The average life of a system is 4 to 6 years, with oldest

application often in use for over 10 years. However, this period of use brings with it the need

to continually maintain the system. Programmers/ analyst spend sufficient time for

maintaining programs. The study on the maintenance requirement for the information system

revealed that are:

a. 60-90 per cent of the overall cost of software during the life of a system is

spent on maintenance.

b. In documented cases, the cost of maintenance, when measured on the basis of

writing each instruction in coding form, is more than 50 times the cost of

developing a system.

c. The software demand is increasing at faster rate than supply. Many

programmer are devoting more time on systems maintenance than on new

software development. There is a backlog of new development work.

The maintenance can be classified as corrective, adoption or perceptive.

Page No - 56

Corrective maintenance means repairing, processing or performance failures or

making alterations because of previously ill-defined problems.

Adoption maintenance means changing the program functions. Enhancing the

performance or modifying the programs according to user’s additional or changing needs are

included in perceptive maintenance. The greatest amount of maintenance work is for user

enhancement and improved documentation of the system for better efficiency. More time and

money are spent on perceptive than on corrective and adaptive maintenance together

Maintenance covers a wide range of activities including correcting coding and design

errors, updating documentation and test data and upgrading user support. Many activities

classified as maintenance actually fall under enhancements. Maintenance means restoring

something to its original position. Unlike hardware, software does not wear out, it is

corrected. In contrast, enhancement means adding, modifying or re-developing the code to

support changes in the specifications. It is to keep with changing user needs and the

operational environment.

The key to reduce the need for maintenance while making it possible to carry on with

essential tasks more efficiently are as follows:

a. More accurately defining the user’s requirement during systems development.

b. Preparation of system documentation in a better way.

c. Using more effective ways for designing processing logic and communicating

it to project team members.

d. Making better use of existing tools and techniques.

e. Managing the systems engineering process effectively.

An addition factor in the success of the maintenance programmer is the environment. A

maintenance programmer has generally been paid fewer amounts and receives less

recognition than other programmers. Lighted attention has been paid to their training and

career plans within the MIS function. Maintenance demands more orientation and training

then any other programming activities, especially for entry-level programmers. The

environment must recognize the needs of the maintenance programmer for tools, methods

and training.

Page No - 57

Implementation of SecurityLimitation of Project

LIMITATION OF THE PROJECT

The project is not online so any area so it can be access only with the signle

computers

Project is not Networking Based

The Complete needs and requirement cannot be fulfilled at this level

Future Scope

The future scope of the project should be determined so that the quality of Software project in terms of flexibility and enhancement can be measured and specified. If the project has no future scope, we would be unable to make any further changes and further enhancement. The future scope of my software can be specified as follows: -

Page No - 58

1) This project is very flexible because if any changes occur in future then it can

be easily accomplished in it. Thus the future extensibility is easily possible.

2) This project can be converted to the multi user system in future if required.

3) If the organization grows upper level then this software can easily handle small

modification.

Bibliography

REFERENCES:

SOFTWARE ENGINEERING BY ROGER S. PRESSMAN SYSTEM ANALYSIS BY JALOTE IGNOU BOOKLET OF SYSTEM ANALYSIS AND DESIGNING Black Book of Visual Basic 6.0 h ttp://www.msdn.com h ttp://www.google.com Master Visual Basic 6.0 Visual Basic Unleashed

Page No - 59

Page No - 60