CS – 76 PROJECT

INTRODUCTION TO SYSTEM DESIGN

System design is a process of preparing input process and the result
detail procedure.

After gathering the facts through various techniques such as

questionnaires, interviews, analysis of documents and observation into
all existing system and recording these collected information in the
proper format using DFD’s decision table, flowcharts etc. The next step
is to define the system in terms of user requirements. This is referred
to as logical design and then converted into physical design.

 LOGICAL DESIGN
When the system analyst prepares the logical design of system which
contains the details of the users requirements. The information flowing
in and out of the system and the required data resources. The logical
design contains the following information.

1. Specification about input data. The source of input data the

document from which it will be derived and the process of
data preparation from the documents.
2. Specification about output reports the data contained in the
reports, its formats and frequency of generation of report.
3. Specification about data to be stored permanently in the
system and its format.
4. Specification about edit correction, backup procedures and
data security arrangement. Specification about

52
 CS – 76 PROJECT

implementation plans brief information about current logical

and physical system.
5. Brief information about the benefit of the new system, its
constraints and required resources to implement it.

 PHYSICAL DESIGN OF SYSTEM

Once the agreements are reached between the user and about the
logical design of the system, the system analysts can start with the
physical design of the system.
Physical design of the system means the designing the computer part
of the information system. The physical design of the computer system
involves the following aspects.

52
 CS – 76 PROJECT

INTRODUCTION AND OBJECTIVES

Hospital Management System includes all transactions such as

storing patient information such as name, address, phone no,
all information about test, relative related information, receipt
transactions for general and inward, calculation of daily and
monthly reports, ward , deposit and total billing process.

52
 CS – 76 PROJECT

TOOLS/PLATFORM, HARDWARE & SOFTWARE

REQUIRMENTS

SOFTWARE REQUIREMENTS

 OS : WIN 98 or higher version

 VISUAL BASIC 6.0

 ORACLE 8i

ADDITIONAL INFORMATION

FEASIBILITY STUDY ABOUT THE SYSTEM

One of the main meanings of the feasibility study is possibility.

Checking of different criteria for successful system is included in this
feasibility study section. These criteria’s are cost, time, efficiency etc.
all these factors play important role in achieving objective of system.

52
 CS – 76 PROJECT

That means the system should be such that it gives optimum

performance at minimum cost, time and requirements.

The six types of feasibility study are,

 Operational feasibility: The system should be easy to operate
by the system user. The user should be given operating manual
about the system.
 Technical feasibility: Technically the systems configuration
should be less complex. Here, for software system technical
feasibility system means technically it should be comfortable for
further maintenance.
 Economical feasibility: According to the concept of economical
study the system should be completed with minimum cost. This is
the most important factors for any system.
 Time feasibility: Time feasibility study is a determination of
whether a proposed project will be completed within given time;
we have achieved this thing in our system.
 Management feasibility: It is a determination whether the
hospital management system will be acceptable to the
management.
 Social feasibility: Social feasibility is a determination of
whether the new system will be acceptable to the people or not.

52
 CS – 76 PROJECT

ANALYSIS

DATA FLOW DIAGRAM (DFD’s)

Data Flow Diagram is a pictorial representation which shows how the

data passes from various stages one by one during the processing.

DFD has some in defined symbols using which we can denote input,
output, data flow and storing database files. Like, rectangle for input

52
 CS – 76 PROJECT

and output, circle for processing, arrow for data flow and one sided
opened rectangle for storing files. And to continue flow small circle is
used. Thus, after understanding data flow diagram we can create
general overview about the current system processing.

 SYMBOLS USED IN DATA FLOW DIAGRAM.

Input and output

Processing

Flow of data
Data storage

CONTEXT DIAGRAM

52
 CS – 76 PROJECT

The context diagram for the hospital management system is shown

above. By seeing the context diagram we can get general overview on
dependence of different section. It describes the reference for various
stages within overall structure of the entire system. In hospital
management system the billing section is at the centered position. And
all other sections are referenced with each other.

1’st LEVEL DIAGRAM

52
 CS – 76 PROJECT

Patient Room

Patient Info Case Paper

3.0
1.0 Allocate
Create Room
case New Case
file
Updated
Case File Room Ward
Provided

2.0 Update Room File

Case
Fee

Ward Request
Indoor Section
Payment
Payment Details

6.0
Discharg
e Case No

Receipt Dept

Update Bill
5.0
Treat
ment
Bill File

Bill request 4.0 Test Details

Creat Bill Info
Perform Test
e Bill
Test Request
Bill
LAB

52
 CS – 76 PROJECT

Description about 1’st level data flow diagram

According to these diagram in this system first from all stages of

processing patient enters in the hospital then he/she has given case file
and patient pay case fee at the case counter section. Then all the data
about the patient is stored in the patient database.

Then, the patient is suggested for further tests and regarding to those
reports patient is determined to discharge or to admit. If the patient is
discharged then receipt for general patient is given. Patient pay for
general receipt to the billing section and all those data of payment and
receipt are stored in the general receipt database.

If the patient is suggested as an indoor patient then he/she has given

ward name and time. Patient is admitted in the indoor section. After all
recovery of the patient receipt of payment is given and according to it

52
 CS – 76 PROJECT

patient has to pay money at the billing section. Billing section keeps all
the records for day and month and gives these all reports to the
account section. 1’st level data flow diagram gives more understanding
than 0’s level data flow diagram.

ENTITY RELATIONSHIP DIAGRAM (ER Diagram)

52
 CS – 76 PROJECT

Description of Entity-Relationship Diagram:-

52
 CS – 76 PROJECT

Any business systems description must start with their entities –people,
places and things. These entities interact with each other in various ways
and those interactions are called entity relationship. In system analysis
entity relationship analysis is one of the conceptual modeling methods.

The e-r data model uses a few basic concepts in producing e-r diagram.
They are,

[1] Entity: - An entity is a person, place or thing in an enterprise e.g. a

customer, an employee, a project, an order etc. Similar objects or things
are grouped in to entity sets.
[2] Relation: - A relationship is a meaningful association or linkage or
connection between entities.
[3] Attributes: - An attribute is any aspect, quality and characteristic,
descriptor of either an entity or a relationship. An attribute tells what an
entity is, entity has, entity contains or the entity does.

Description of E-R model for Hospital Management System

Entity Relationship Entity
Patient Relate many(1:n) Ward, doctor, receipt
Test Examine many Patient
Receipt Generate General/Indoor
Report Generate Daily/Monthly

Steps of implementation

52
 CS – 76 PROJECT

Implementation of system includes all those activities that take palce to

convert the old system into a new one from the old system to the new.
Mainly the implementation phase of system consists of

(i) Training of personnel

(ii) Conversion
(iii) Documentation

TRAINING: Training may be for systems operators and users.

This is done with a view to providing hands-on experience with the
new system with interactive systems; users can try out software
directly.

In fact training should include

(a) Overview of how the system functions.
(b) How it will affect their jobs
(c) How it will relate to current manual procedures.

In any system training should be given to the user for efficient use of
the system. There are mainly four steps which should specifically take
care of: User involvement in the equipment use, instruction to
individuals in troubleshooting the systems and coming out unscathed
from troubles, data maintenance.
Each and every system is implemented after passing many
stages like system analysis, design, testing, documentation etc.
successfully. All the instructions which are prepared for the system
implementation are arranged in specific order in systems

52
 CS – 76 PROJECT

documentation and then according to it and requirement the main

stage of system, implementation is taking placed by the system
designer.

CONVERSION: It is the process of changing from the old system to

the new one. There are four methods of handling a system conversion.
Which are the parallel-systems method, the dual system method or
phase-method, the direct cutover method and last is the pilot approach.
Here, for this hospital management system we have used the
direct cutover method. Because in this method the conversion takes
place abruptly. The drawback of this method is that it requires careful
planning and training sessions must be scheduled and maintained.

DOCUMENTATION
Anything that is written about how a system is designed or functions is
documentation. In documentation there are many types such as system
documentation, programming documentation, operations
documentation, training documentation, implementation documentation
and appendix. From those types of documentation system
documentation describes the overall system design and includes
flowchart, i/o formats, file descriptions, control requirements and report
specification. Programming documentation includes programming
specifications, descriptions of program logic including graphic aids such
as flowcharts. Operating documentation is deal with operating schemes
and problems created in the system.

52
 CS – 76 PROJECT

Training documentation includes the user training manuals and

materials to be used in the conversion and installation of new system.
Implementation plans and the results of implementation must be
documented. Appendix contains all other documentation. i.e feasibility
study report, problem definition report, study plan, list of controls etc.

DATABASE DESIGN

52
 CS – 76 PROJECT

Each database file is described below:

PATIENT_MST: [Database file that stores information about

patients of general category] Maintenance of patient record is the
major aspect of management that does not mean transaction is less
important. For keeping patient record here we are considering the
database file called patient. Various fields within this database file will
care for saving required information.
Fields and its description of this database file are as under:
1. Case_no : It store identification number as case number. And it
must be unique to all the patient.So it is taken as primary key.
2. E_date: It stores the date of entry of patient in hospital.
3. Name: The field stores full name of patient.
4. Age: It stores age of patient.
5. Gender: It stores gender of patient whether the patient is male
or female.
6. Address: This field stores the address of patient without
city/village.
7. City: This field saves the name of city of patient.
8. Phone_off: It stores the phone number of office.
9. Phone_res: It stores the phone number of resident.
10. Ref_doc: This field stores name of concern doctor, by whom the
patient is treated.

INWARD_PAT: [It stores inward patient information]

52
 CS – 76 PROJECT

The database file that includes the record of indoor patient named
inward_pat. The fields are same as of patient. Additional is only the
indoor number and admit information. i. e. admit date and time as well
as ward transfer and incharge doctor should be included some more
fields have to added because indoor patient should be care well case
number is also with primary concept here.

Fields of this database file are as under

1. Case_no: The field stores case number of patient who is
suggested to admit in the hospital.
2. Indoor_no: It stores unique indoor number for each inward
patient, so it is a primary key.
3. Name: Field stores name of patient.
4. Age: It stores age of patient.
5. Gender: This field stores gender of patient.
6. Address: It stores address of patient.
7. Occupation: Patient’s occupation is stored in this field.
8. Village: Field stores name of village.
9. Taluka: It stores name of taluka of patient.
10. District: The field stores name of district of patient.
11. Phone_no: It stores the phone number of patient.
12. Rel_name: This field stores the name of relative of patient.
13. Rel_address: It stores the address of relative.
14. Ward_name: It stores name of ward in which the patient is
admitted.
15. Deposit: The field store payment of patient at admits time. That
payment is given back to the patient at discharge time.

52
 CS – 76 PROJECT

16. Admit_date: It stores the date on which patient is admitted.

17. Admit_time: At which time patient is admitted is stored by the
field.
18. Ward_trans_date: It stores date of transferring the ward.
19. Ward_trans_time: Field stores time at which ward is
transferred.
20. Disch_date: Discharge date will be stored in these fields.
21. Disch_time: Discharge time will be stored in it.
22. Doctor_incharge: It stores name of concern doctor.

TESTS:

52
 CS – 76 PROJECT

[DATABASE FILE THAT STORES VARIOUS TEST INFORMATION]

 Laboratory tests
 Sonography tests
 X-ray tests
 Cardiology tests

These four database file maintains the above tests and their charges.
Four type of test are descripted above. They include their subtests.
Test id, name and charge are fields for each test database. From the
master we can change or add the tests. Test is derived directly from
the receipt. So, entering the data become easy.

Fields of all these four database files are as under:

1. Test_name: The field stores name of test.
2. Test_id: It stores the unique identification number of test.
3. Test_charge: Charge of the test will be stored in this field.

RECEIPT:

52
 CS – 76 PROJECT

[GENERAL/INWARD]

[1].Receipt general:
Receipt is a part of transaction, when patient leaves, receipt is
generated. It includes the case no, date, total and particulars. Test
name and charges are included in particulars .Indexing of receipt are
also necessary because total account depends upon receipts. Receipt
general is for the general patients.

Fields of receipt general is as under:

1. Case_no: It stores the case no. of the patient which is given at
the entry of the patient.
2. Receipt_no: This field stores the receipt number.
3. Date: It is used to storing date on which the receipt is delivered
to patient.
4. Total: Amount of rupees to be paid by patient is stored in this
field.

[2]. Receipt_discharge:
Inward receipt is same as general receipt but it is used for indoor
patient at discharge time, so the discharge receipt maintains the
discharge account.

Fields of receipt for inward receipt listed below.

52
 CS – 76 PROJECT

1. Case_no: This field is same as case number field for general

patient.
2. Indoor_no: This is used to store the indoor number for indoor
patient who is given at the admission in hospital.
3. Date: This is used to store the date at which the patient is
discharged.
4. Total: Amount of rupees to be paid is stores in this field.

REPORT:
[Daily Income Report/Monthly Income Report]

Two types of reports are considered for calculation purpose.

52
 CS – 76 PROJECT

[1] Daily Income Report: Total income during a day will include in
daily report with help of starting and ending receipt no and amount.
Fields and datatype are same as monthly report.

Fields for daily income report is as under:

1. Date: this field stores the date for the daily income report.
2. Startreceiptno: This field stores starting receipt number for the
day of given date.
3. Endreceiptno: This field stores ending receipt number for the day
of given date.
4. Total_receipt: For storing total no. of receipt for the day.
5. Total_amount: It stores total income for the day of the hospital.

[2] Monthly Income Report: Collection of daily receipts is base for

monthly report provides the total income that is summation of total of
receipts. Month starting receipt no, ending receipt no, total amount are
fields.

Fields for the Monthly income report is given as below:

1. Month: This field stores month of report for the any month given
by the user.
2. Startreceiptno: Stores the starting receipt no for the whole month.
3. Endreceiptno. Stores ending receipt no for the whole month.
4. Total receipts: It stores the number of receipts for the given
month.
5. Total_amount: It stores the total income for the given month.

52
 CS – 76 PROJECT

DOCTOR INFORMATION:
[IT STORES THE INFORMATION ABOUT DOCTORS]
In hospital, patients are cured by doctors. So doctors are more important for
the patient. It is necessary to know that which doctors are available and

52
 CS – 76 PROJECT

what are the qualifications, contact time and address, phone no, etc. So all
these details are store in one database file called Doctor_info. So the patient
can get the proper information of doctor easily.

Fields for the Doctor_info is as under:

1. Doctor_id: It stores the unique id for the doctors who are
serving in hospital.so it is taken as primary key.
2. Joining_date: Date on which the doctor has started the service
is stored into this field.
3. Name: It stores the name of the doctor.
4. Age: It stores the age of the doctor.
5. Gender: It stores the gender of the patient.
6. Address: It stores the full address of the doctor.
7. City: Stores city in which the doctor is lives is stored in this field.
8. Phone_off: phone no. of office of doctor is stored in this field.
9. Phone_res: phone no for resident of doctor is stores in this
field.
10. Mobile_no: It stores the mobile no of the doctor.
11. Qualification: It contains the information about
degree/qualification of the doctor.
12. Specification: It stores specification weather it is visiting or
permanent doctor.

COMPLETE STRUCTURE

Number of Modules:

52
 CS – 76 PROJECT

1. Title Form
2. Homepage (Main Menu)

Input Forms:
1. Entry form for general patient
2. Entry form for inward patient
3. Entry form for Doctor’s
4. Entry form for the Test

Output Forms:
1. General Receipt
2. Discharge Receipt
3. Daily Report
4. Monthly Report
5. List of Patient / Doctor’s / Test

DESCRIPTION OF FORMS

[1]. TITLE FORM: - It is the starting form which is displayed first in

the system. It shows some specific information about system such as
hospital name, address, symbol, platform of the system in which entire

52
 CS – 76 PROJECT

system is made, license specification and information about developers

such as name, address etc. It displayed on the screen according to
provided time interval for the timer control in the system. After then
the homepage (main menu) will be displayed. In any system starting
page should be attractive and it should include general overview about
the system. By using some additional images and backgrounds we can
make the title page attractive.
In our hospital management system we have used labels, timer control,
picture box, images, frames etc. in designing the title form. The layout
of form makes the concept of the designing more clear. Title form
doesn’t contain any type of programming except timer event
programming. As execution of timer event is occur, actual navigation
window-main menu will be displayed. And then transaction processing
will be started.

[2]. MAIN MENU: After displaying the title form, a form will be
displayed which displays options of various operations handled by the
hospital management system. Name of this form itself indicates its
importance and according to it we can assume the utility of this form.
This is so due to before performing any sort of operation we have to
pass from this form. This form provides options for further transactions
for patient, receipt, reports, and master records for entry, change,
delete etc. and exit option to come out from the system.
In this form by using patient option the user enter data and
information for general or discharge patient. The second option is
receipt which generates invoices for general or inward patient. Third
option is report which includes option for daily income report and

52
 CS – 76 PROJECT

monthly income report. Hence, the management can observe records

for finance for each day and month. Fourth option is master which
provides many options especially for entry, modification and deletion.
And the last option is exit to quit from the system. All these operation
can also be performed by using menu options which are located on the
top position of the form. The user can go directly from these menu
options to required destinations. In designing we have used labels,
command buttons, menus etc. This page also displays current time and
date.

[3]. DESCRIPTION OF INPUT FORMS.

[1] Entry Form for General Patient: The entry form for
general patient is used to enter and store the patient information
at arrival time. This form has fields like patient case no, date,
name, age, address, city, phone no and concerned doctor. All
these information are entered in given text boxes and it stored in
the patient general database file. Here, the case no must be
unique because it is considered as a primary key in database file.
Access of particular stored records becomes possible by the primary
key. Hence, no patient is entered for same case no. In this form we
have provided one command button named ‘save’. By clicking this
command button the user can store all the patient information in
related database file. In this form we have taken combo box for gender
field and through it the user can directly select option. For other fields
we have used text boxes for entry purpose.
Labels and frames are also used in the form designing. One command
button save which is used to store particular information in the

52
 CS – 76 PROJECT

database file. The user can retrieve any type of information at any time
through the database file. Whatever changes the user has made in the
master form it affect the data which are stored in database file from
this form.

[2]. Inward patient: After entry of patient is being made by

the entry clerk, patient will in the O.P.D (observation patient
department) for the treatment of diseases where doctor will check
patient and if necessary then doctor will advice for admitting patient so
the new entry of patient is necessary in indoor section for maintaining
his account or further administrative process.
This form is used to store the all information about patient who will be
admitted in the hospital. All the information of patient collected at the
case counter is again entered in inward database file and in addition to
this information there so many information required in this section
because responsibility of hospital increased after admitting the patient.
Now, each patient is given one unique indoor no, which is used to
maintain account until the discharge of patient, case no is also stored
for O.P.D department’s flexibility. Another important data to be stored
is deposit of patient which must be pay by all inward patient .Ward
name also stored during the admission process of patient from the
general, special, special A.C, or deluxe and on the basis of this ward
name all the calculation of payment is done using the ward name and
its charge with this field admit date and time also entered. After
selecting ward, if patient want to change the ward then one another
field is provided to store ward transfer date and time and also ward
name is again entered. Along with all this information another

52
 CS – 76 PROJECT

important fields are the real’s name and real’s address to stored the
information about detail of relatives. All this data is stored in one
database file called inward_pat.

[3]. Entry form for doctor: For the best administration of

patient, it is necessary to keep the records of doctor who are currently
serving in the hospital and it will be useful for the inquiry dept of the
hospital when any patient want to see information about the doctor like
what specialists are available in the hospital, what is his name and
what’s their qualification and also his mobile or phone no for the
emergency contact of the doctor. So this form is responsible for
entering the information about doctor when they join the hospital.
Personal information about doctor like name, age, city, address phone
no and mobile no. is stored when they join the hospital. In addition to
this information, most important information is qualification and
specification which shows doctor is which type of specialist and
whether it is permanent or visiting mobile no and phone no field is
used for emergency contact of the doctor when patient passing
through the very serious pain.

[4]. Test entry form: Each general hospital provides modern

test laboratory facility for its patient. This hospital provides four type of
test lab like cardiology test, laboratory test, x-ray test, sonography test.
Entry of each type of test is required for the receipt and it should be
stored in one database file. When new test is Introduce then it is enter
into the database file so using this form new entry of test is being
made.

52
 CS – 76 PROJECT

This form include the one test id for identifying the test uniquely so it is
taken as the primary key and can not be live null. Along with the name
of the test it’s charge also entered because the flexibility of the
operator when he enter the test name in the receipt, the charge of the
test is automatically display in the charge list box.

[4]. OUTPUT FORMS

[1] Receipt for General Patient: After the treatment of
patient at the discharge time, he has given the invoice for the total
charge that he has to pay. The receipt for general patient includes case
no, receipt no., name, date, place, particular tests, quantity, referenced
doctor and charges. Total of all type of charges is calculated and
shown in total field. For entering the test name in the receipt four
combo boxes are placed. From these combo boxes user can select
different tests. As the user select test, that particular test directly
comes in the particular field of receipt.
The database file of the receipt for general patient includes four fields
like case no, receipt no, total and date. These four types of information
of each receipt are stored in this database file. We can update the
stored records of receipts if mistake founds in it. We are not storing
information except above mentioned. Here one interesting point is that
the user is not bothered about entry of all fields. Because the
arrangement is done by the coding in such away that as the user click
on combo box of case number, all the case number of already entered
patient is displayed. Now the selection of one case number directly
results in entry of most fields like name, reference doctor, case fee,

52
 CS – 76 PROJECT

place, and date. From two buttons first is save which will store the data
in database file and another is print which will print the receipt.

[2]. Receipt for Inward Patient: If the patient is inward then

he/she has given inward receipt. Inward receipt is almost same as
receipt general. The difference is that the inward receipt includes
indoor number. In inward receipt the combo box of indoor no. taken
from which the indoor no. can be selected and related information can
be access easily in other fields. This form also has another combo
boxes for tests like laboratory, sonography, cardiology and x-ray, from
these combo boxes the user can directly select tests from test options
according to requirement.
In this form as the user enters indoor no. , all the related information
can be retrieved from text boxes directly. Here, we have one
interesting feature is that regarding to the patient’s deposit what the
charges for patient should be taken those are subtracted automatically
from the deposit. This receipt has fields like indoor no, place, date, sr.
no, particular test’s name, referred doctor, charges for that particular
test, amount and total. One another feature of this receipt is that in it
receipt number is incremented automatically. There are some another
options for ward. Which includes ward transfer date, time and types of
ward. And also according to indoor no case no is directly taken from
storage or database file.

[3]. Daily income report: Motto of any administration system

is to calculate the income for the hospital to achieve goal of top
management .It is necessary to calculate profit or loss of the hospital

52
 CS – 76 PROJECT

for the best, efficient management of the hospital and to accomplish

this task it is necessary to generate daily and monthly income sheet. So
this form is used as output of the system and will be send to the
management of hospital. This output screen contains the most
important field date and on the basis of date the income for the day is
calculated. It will also shows starting receipt no and ending receipt no
for whole the day .It also shows total no of receipts sold during the day
and form that total amount in rupees is calculated.

[4]. Monthly Income report: This is same as the daily report

but the only difference Is it calculate the income on the basis of given
month and remaining all the things are same as the daily report.

[5]. List [patient general/inward, doctor, tests]: After

entering information about the patient, test, doctor, it is necessary to
view it in the form of list. On the inquiry dept., if any body wants to
see the information about any patient, doctor and test then inquiry
clerk has to refer the all list of above mentioned item to give accurate
information speedy. This output form used for listing the above
mentioned items in the form of table and for this list we have used one
data grid control of VB which shows the all the records of the database file.

DATA STRUCTURE AS PER THE PROJECT REQUIREMENT

[1]. Patient_mst:

Sr.no Field Name Data type Size Constraints

1. Case_no Varchar2 7 Primary key

2. E_date Date - -

52
 CS – 76 PROJECT

3. Name Varchar2 40 Not null

4. Age Number 3 -
5. Gender Varchar2 1 -
6. Address Varchar2 40 -
7. City Varchar2 20 -
8. Phone_off Number 7 -
9. Phone_res Number 7 -
10. Ref_doctor Varchar2 20 -

[2]. Lab_test/Cardio_test/Xray_test/Sonography_test
Sr.no. Field name Data type Size Constraints
1. Test_id Varchar2 7 Primary key
2. Test_name Varchar2 35 -
3. Charge Number 6,2 -

[3]. Inward_pat:

Sr. no Field name Data type size Constraints

1. Case_no Varchar2 7 Primary key}
2. Indoor_no Varchar2 7 Primary key} Composite
key
3. Name Varchar2 40 Not null
4. Age Number2 3 -
5. Gender Varchar2 1 -
6. Address Varchar2 40 -

52
 CS – 76 PROJECT

7. Occupation Varchar2 15 -
8. Village Varchar2 20 -
9. Taluka Varchar2 20 -
10. District Varchar2 20 -
11. Phone_no Number 7 -
12. Rel_name Varchar2 40 -
13. Rel_address Varchar2 40 -
14. Ward_name Varchar2 15 -
15. Deposit Number 5 -
16. Admit_date Date - -
17. Admit_time Varchar2 10 -
18. Ward_trans_date Varchar2 Date -
19. Ward_trans_time Varchar2 10 -
20. Disch_date Date - -
21. Disch_time Varchar2 10 -
22. Doctor_incharge Varchar2 15 -

[4]. Doctor_info:

Sr.no. Field name Data type Size Constraints

1. Doctor_id Varchar2 7 Primary key
2. Joining_date Date - -
3. Name Varchar2 40 Not null
4. Age Number 3 -
5. Gender Varchar2 1 -
6. Address Varchar2 40 -
7. City Varchar2 20 -

52
 CS – 76 PROJECT

8. Phone_off Number 7 -
9. Phone_res Number 7 -
10. Mobile_no Number 10 -
11. Qualification Varchar2 30 -
12. Specification Varcahr2 15 -
[5]. Receipt_general:
Sr.no Field name Data type Size Constraint
1. Receipt_no Varchar2 7 Primary key
2. Case_no Varchar2 8 Foreign key
3. Date Date - -
4. Total Number 8 -

[6].Receipt_discharge:
Sr.no Field name Data type Size Constraints
1. Case_no Varchar2 7 FK
2. Receipt_no Varchar2 8 FK
3. Indoor_no Varchar2 7 -
4. Date Date - -
5. Total Number 8 -

[7]. Daily_report:
Sr.no Field name Data type Size Constraints

52
 CS – 76 PROJECT

1. Date Date - -
2. Start_receiptno Varchar2 8 -
3. End_receiptno Varchar2 8 -
4. Total_receipt Number 8 -
5. Total_amount Number 10 -

[8].Monthly_report:
Sr.no Field name Data type Size Constraints
1. Month Varchar2 15 -

2. Start_receiptno Varchar2 8 -

3. End_receiptno Varchar2 8 -
4. Total_receipt Number 8 -
5. Total_amount Number 10 -

SYSTEM TESTING & DEBUGGING

ABOUT TESTING AND DEBUGGING

The phase of system development life cycle tests system design.

Testing of system decides whether the newly designed system works
properly or not. After the development of documentation manually
about the system this stage is checked. And if the system working
properly then it will be considered for implementation and if isn’t then
system analyst is informed to find out generated errors or problems
and to find out its solutions. This process is known as debugging.

52
 CS – 76 PROJECT

For any software system testing means to check out its coding. If there
is not any problem in the coding then that code is proper and efficient
to design. If we are not getting proper or required output then we have
to debug the system coding. So, the debugging is also a subpart of the
testing section. If the system runs correctly during testing then there is
no need to debug.

During the testing of our project we have to face different types of

errors. Especially, database errors annoyed us but at last we solved it,
successfully. Some of the errors are listed below with their cause and
solution.

ERROR SCREENS AND SOLUTIONS

[1] Table or view does not exist

52
 CS – 76 PROJECT

 Cause: If we use the database table or view in our form for the
purpose of storing and retrieving the data, but there is no
existence of such table.
 Solution: This error basically arises due to absent of database
table or view solution.

[2] Invalid use of null

 Cause: Because of absent values in input control box or input

data field, hence front end cannot access data from database
file which are allocated as backend.
 Solution: Discarding the null values by giving some proper
values to the input box. And so we have to define some
values for blank space.

[3] Inserted value too large for column.

52
 CS – 76 PROJECT

 Cause: This error occurs because of the large value inserted

which is out of predefined size in the database file during the
creation of table. i.e. If you have defined size for field
‘case_no’ varchar (4), and if you enter value like “b00009”,
then this error occurs.
 Solution: To solve this error we have to insert proper value
according to specified field size at run time.

[4] Object required.

 Cause: If we use any VB control in our coding but there is no

existence of such control in our form.
 Solution: Error message give the solution itself that add the
particular at the particular control which is used in the coding
otherwise omit the coding of that part.

52
 CS – 76 PROJECT

[5] Object variable or with block variable not set.

 Cause: If we not create the reference variable of particular

variable when it is required. i.e. If we declare variable dim rs
as adodb.recordset but do not create its reference variable like
rs as new adodb.recordset.
 Solution: We have to set the reference variable in the coding
described as above.

INPUT & OUTPUT SCREENS

 HOME PAGE (MAIN MENU)

52
 CS – 76 PROJECT

LAYOUT OF EACH INPUT FORM IS SHOWN BELOW

[1] ENTRY FORM FOR GENERAL PATIENT

52
 CS – 76 PROJECT

[2] ENTRY FORM FOR INWARD PATIENT

52
 CS – 76 PROJECT

[3] ENTRY FORM FOR DOCTOR

52
 CS – 76 PROJECT

[4] ENTRY FORM FOR TEST

52
CS – 76 PROJECT

52
 CS – 76 PROJECT
LAYOUT OF OUTPUT FORMS SHOWN BELOW

[1] GENERAL RECEIPT

52
 CS – 76 PROJECT
[2] DISCHARGE RECEIPT

52
 CS – 76 PROJECT
[3] DAILY REPORT

52
 CS – 76 PROJECT

[4] MONTHLY REPORT

52
 CS – 76 PROJECT

[5] LIST OF PATIENT / TEST / DOCTOR

52
 CS – 76 PROJECT

FUTURE APPLICATION OF THE PROJECT

 Reducing Process time

 Reports can be generated according to the requirements.
 Object oriented design
 Reducing manual efforts for maintaining the system.
 Its stored large amount of data on database file, for future
references.

The whole project covers all important information of hospital;

therefore in future it will help to gather such information about the
hospital management.

52
 CS – 76 PROJECT

BIBLIOGRAPHY

Oracle and Visual Basic Handbook

- SSI publication

Internet sites
- www.altavista.com
- www.google.com
- www.bing.com

52