BHILAI INSTITUTE OF

TECHNOLOGY

A PROJECT REPORT ON

PATIENT BILLING SOFTWARE

SUBMITTED TO: SUBMITTED BY:

MR. KAULESHWAR PRASAD 1. PRIYA NAIR
2.AMITA PATERIA
3.NISHI PIOUS
4.SHUBHAMGOYAL
 PLANNING PHASE
1.PROBLEM STATEMENT:-
This project is aimed at developing a patient billing software system that is
of importance to a hospital.

a. DESCRIPTION OF PRESENT SITUATION:-

The main idea of making this software is to overcome the problems that
hospitals are facing currently. The problems include maintaining the records
of patients like when they are admitted or discharged, their bed no. ,ward
no., etc. It is difficult to find old records and misplaced records. Also manual
billing is a hectic and time consuming job as well as not reliable.
So, to handle all these problems we are creating this software.

b. PROBLEM CONSTRAINTS:-

MANPOWER- Our group includes 4 members. This software could have

been developed by less members also but since there is a time constraint of
just 2 months , so we decided 4 members as working team.

SOFTWARE- SQL 8.0 for creating the database of the patients and maintain
their records, Netbeans 6.1 for working on java in order to create the software,
MS Acess to provide the database connectivity to the software and Notepad to
use HTML and designing the front page of our software.

HARDWARE- The hard disk space required for the software is around
500 MB – 1GB, to provide faster access to all the information and to have an
efficient software.
c. GOALS :-
The requirement of the system is to maintain the location or bed number of
each patient either it be in the ward or in the ICU. It should maintain the
database which should store all the information about the patient which are
as follows:-
1. Name
2. Address
3. Phone number
4. Ward number
5. Bed number
6. Amount to be paid
7. Treatment

REQUIREMENTS:-
The purpose is to perform some feasibility analysis or use the requirements
for competitive bidding. The developer needs to know the exact format of
the reports, all the queries that can be performed and their structure, total
number of terminals the system has to support, the structure of the major
databases that will exist, etc.

USERS AND THEIR ROLE :-

The users are the hospital staff who would be using this software to
maintain the patient’s database and detailed information about them and
also the facilities availed to them.
The users will provide proper authentication to various departments of the
hospital like accouting, pharmacy,etc.
2. SOLUTION STRATEGY:-
In the present system we have to manage our billing, record of patient manually
needs a huge amount of maintenance of records and it is slow and not secured. In
this PBS this problem is removed by the computer which helps to store data in a
secured environment, avoid maintaining bulky registers, saves processing time
and provides better status to that hospital and performs many more useful
operation. Centralized database is used which provides connectivity between all
the branches of the hospital.
This system helps the users with a very unique and convenient service of bill
generation. At the administrator side, the various bills of various patients are
generated and a history report of paid and unpaid bills is maintained.

3. DEVELOPMENT PROCESS:-
a. Life cycle model for the project:
Waterfall model is used to develop the
project, since all the data are provided at the start only; the basic operation
is fixed using this data the entire system has to deliver at the time only so
waterfall model is used here.

b.Team structure for the project:

PROJECT MANAGER:-PRIYA NAIR

PROGRAMMER:- SHUBHAM GOYAL

TESTER:-AMITA PATERIA

CONFIGURATION CONTROLLER:-NISHI PIOUS

c. Software Configuration Management:-
i. List and brief description of non-changeable objects that would
contribute to the software
Phase wise.
ii. List and brief description of changeable objects that would contribute to
the software
Phase wise.
d. Software Quality assurance :-
i. List and brief description of quality attributed decided for evaluating the
software product
Phase wise.
ii. List and brief description of the validations (are we making the product
right ?) and
Verifications (are we making the right product? ) phase wise.
e. Risk management :-
i. List and brief description of any kind of Risks that may occur phase
wise.
ii. List and brief description of any possible solutions for the above
mentioned risks.