A

Synopsis
ON

THE HOSPITAL PATIENT INFORMATION

SYSTEM
(HPIS)
 CONTENTS

 Title of Project

 Introduction and Objective of Project

 Project Category

 A complete structure which includes:

 Analysis (DFDs, ER Diagrams etc.)
 Number of Modules and their description
 Data structure(Tables)For all the modules
 Process Logic of the Modules
 Report Generation

 Tools/platform, Hardware and Software Requirement

specifications

 Security Mechanism

 Future scope and further enhancement of the project.

 Title of Project:

THE HOSPITAL PATIENT INFORMATION SYSTEM

1.1. INTRODUCTION:
Today hospitals are high-tech public welfare and relation system. At
present days most of them need a speedy and efficient system to finish daily
activity such as new patient enrollment, doctor activity, nursing staff
management etc. till today some of the nursing home and hospital
maintaining their daily activity manually or some are using old computer
based system which are became obsolete as compared to today’s technology
so to over come this problem which are facing by different health center in
around Guwahati city we have proposed to reinvestigate the system to
develop a modernize computer base hospital management system.
We have visited so many private and government hospitals in an around
Guwahati city from where we collect the data about what kind of system they
were using to maintain the whole data about the patient and the doctors and
the rooms and lab service they have. The system they are using not a user
friendly and efficient. Database management system use to handle day to day
data and previous data is not up to date. The existing system is bound to some
particular system of activity only or some of them are not using proper user
interface for output, input and reporting.
So overcome this above problem we have proposed to design a user
friendly hospital management system having modern database at back end.
We have proposed to develop computer base hospital management database
system using Visual basic and MS Access .
 1.2. OBJECTIVE:

“THE HOSPITAL PATIENT INFORMATION SYSTEM” is designed to

achieve the following objectives:
I. The whole system should be menu driven and the main menu should
be displayed automatically as soon as the user logon succeeds.
II. The software must have a user-friendly interface and appealing
appearance to ease the work of the end users.
III. The software should have a data entry interface feature so that firm
could be able to do manage data entry perfectly.
IV. The software must be able to return the actual patient’s status of the
hospital, i.e., it must be able to say how much money is left in the
wallet of the firm and how much it could spend on different business
activities.
V. The new system must be designed to allow the firm to record the
details of its patient’s date of admission, full name, address, phone
no., date of birth, etc. and should be able to generate report of the
system.
VI. The software should be able to record all deals & bills and related
details made by hospital.
VII. The software must be able to return report of every head.

Above all, the software system should be able to

eliminate all the paper work required in implementing the task of data
maintenance, which previously was tedious, time consuming and error prone.
The objective of this system can be summarized as,
“To provide such kind of platform where the hospital can increase their
growth and market strength through the optimization in time and man power
with the help of proposed system. ” Also the hospital can better target to their
goals through the various types of reports and charts generated by the system.
1- It helps the management of finance and gives exact financial position of
hospital according to rules and regulation.
 2- It helps in management of patients and it is very useful for performing
other pathological related operations.
3- It makes patients management very easy for hospital with its patient
management module.
With the above discussion a conclusion is
drawn that all the components which are covered by this software is very
useful for “HOSPITAL PATIENT INFORMATION SYSTEM” and all
medical and surgical related firms for smooth working and helps their
business a lot.

4. PROJECT CATEGORY:
My project falls under the category –

“Relational Database Management System (RDBMS)”

A relational database management system (RDBMS) has the following properties:

 Represents data in the form of tables
 Does not hard-code relationships between tables

 Doesn't require the user to understand its physical implementation (data

abstraction concept
 Provides information about its contents and structure in system tables
 Can be manipulated through SQL commands
 Supports the concept of NULL values

5. Tools/Platform,Hardware and Software Requirement Specification:

 Tools:

Front End: Java Swing

Back End: MySQL Server.

 Platform: Windows NT/XP

 Hardware and Software Requirement specification:

1- Processor: Pentium IV or higher processor

 2- Memory Size: At least 2 GB or more disk storage space.

3- RAM: 512 MB or more.

4- Operating System: Windows Xp

Man Power: A Qualified computer professional with appropriate knowledge of GUI, Visual
Basic and SQL Server is sufficient
TABLE DESIGN:
DB Table for Login:-
Table name - Login.
Table Description – Contains login information.
Primary key-

Field name Data type Length

u_id Varchar 16
u_pwd Varchar 16

DB Table for Admissions: -

Table name – Admissions
Table Description – Contains information relating to admission.
Primary key – pat_code

Field name Data type Length

Pat_code Varchar 15
Phy_code Varchar 8
D_admited Smalldatetime 4
T_admited date time 8
Room_no Varchar 10
Release Bit 1
DB Table for physicians:-
Table name – physicians
Table Description – Contains information relating to physician.
Primary key – phy_code

Field name Data type Length

Phy_code varchar 15
Phy_name varchar 20
Phy_add varchar 50
Status varchar 10
specialization varchar 25

DB Table for Archives:-

Table name – Archives
Table Description – Contains Archives information.
Primary key – pat_code

Field name Data type Length

Pat_code Varchar 15
Pat_name Varchar 50
B_date Varchar 4
Pat_add Varchar 50
Gender Varchar 6
Age Int 4
Tel_no Varchar 20
Status Varchar 25
Nationality Varchar 25
DB Table for Patients:-
Table name – Patients
Table Description – Contains information related to Patients.
Primary key – pat_code

Field name Data type Length

Pat_code Varchar 15
Pat_name Varchar 50
B_date Varchar 4
Pat_add Varchar 50
Gender Varchar 6
Age Int 4
Tel_no Varchar 20
Status Varchar 25
Nationality Varchar 25

DB Table for Rooms:-

Table name – Rooms
Table Description – Contains information related to rooms.
Primary key – Room_no

Field name Data type Length

Room_no Varchar 15
Room_rate Currency 8
Room_type Varchar 15
Ward_no Varchar 4
Bed_no Varchar 8
Room_status Varchar 20
Capacity Int 4
Vacant Int 4
Occupied Int 4

DB Table for Checkout:-

Table name – Checkout
Table Description – Contains information related to checkout.
Primary key – pat_code

Field name Data type Length

Pat_code Varchar 15
Pat_name Varchar 50
D_discharge Smalldatetime 4
T_discharge Date time 8

DB Table for Bill:-

Table name – Bill
Table Description – Contains information related to Billings.
Primary key – bill_id

Field name Data type Length

Pat_code Varchar 15
Pat_name varchar 8
D_admited Smalldatetime 4
T_admited date time 8
Room_no varchar 10
Admission_fees Currency 8
Room_rate Currency 8
Exam_fees Currency 8
D_discharge Smalldatetime 4
Phy_fees Currency 8
Tax Currency 8
Total Currency 8

DB Table for Lab Services: -

Table name – Lab Services.
Table Description – Contains information related to Services.
Primary key – pat_code

Field name Data type Length

Pat_code Varchar 15
Pat_name Varchar 20
Phy_code Varchar 15
Exam_stat Varchar 20
Exam_type Varchar 20
Disease Varchar 20
Exam_date Smalldatetime 4
Exam_fees Currency 8
Exam_result Varchar 50

10.1 SYSTEM SECURITY:

The measures for data protection taken by an organization reflect its awareness and
attitude towards INFORMATION AND Information Technology. If top management treats
computers as a de-humanized, intangible, but integrity would, at best, be lackadaisical. On
the other hand, if the management considers information as an important recourse and
computers as an aid in decision making one would find a positive approach and
involvement by the management towards security of information. This attitude naturally
percolates down to the lower levels and the workers consider the computer correspondingly
as an enemy.
One of the best and first steps in ensuring data security is to create awareness and
develop a culture within the organization towards the ways in which information can be
lost/alter and what would be the consequences, of such an occurrence, to the organization
and individuals.
All other steps that can be taken are:
 IT ‘Planning: The organization must decide on a policy for introduction of IT. This
must be done at the highest level and should address issues such as levels of protection for
various aspects of information relating to the organization.
 Selection of technology, keeping in mind obsolesces due to new innovations and
necessity for keeping in step;
 Identification of points of exposure of weak links to device means to plug them;
 Physical protection of machine and media.
Control and monitoring the access to data, its usage, by persons and its integrity
must be early defined and responsibility for ensuring these must test on persons designed
for these tasks; an audit procedure would go a long way in ensuring adherence to laid down
guidelines.
While the above are relevant for any computer based MIS implementation, in case of
PCs, the rules acquisition and use must be unambiguously stated. Additional points to be
looked into are:
 Information classification;
 Responsibility for security;
 User training to increase security awareness and propagation of do’s and do not’s.
 Guidelines for creation and changes to passwords etc.
There are four time-honored principles for ensuring security and recovery in case
of breaches of security:

10.2 PREVENTION:

The best method is of course stopping all breaches of security before they occur.
‘Need-to knows’ policy is an offshoot of the principle of prevention.

10.3 DETECTION:
 However one may try to ensure it, total security is almost impossible. The next
principle, therefore, is that one must be able to detect breaches to security, whenever they
occur, within the shortest possible time. This helps in damage assessment and, also, in
devising further preventive measures.

10.4 DAMAGE MINIMIZATION:

There must be enough resilience in the system to recoup the losses, damage and
become functional, by reinstating the status, at the earliest.

10.5 PHYSICAL SECURITY:

These measures are for PCs being used by us. The measures available are:
 Physically bolt down the PC to a table so that it can’t be casually lifted and taken
away.
 Locate the PC in such a way that it is conveniently accessible to the user, but hidden
from casual passes-by.
 Have likeable cupboards for floppies and keep them locked at all times, except when
used.
 Keyboard and PC locking devices can be fitted so that the PC can’t be operated unless
these locks are opened.
 Keep a record of all floppies in use; don’t permit alien floppies into the organization.
 Use lockable rooms for PCs, specially those handling sensitive data. Make it a
practice to lock the room when leaving it for even a short time.
 Time above apply to server, gateways and the like.

5. PROJECT MODULES :

Different process module of HPIS:

a) Login Process :
 Administrator or supervisor will enter user id and password.
System will confirm the entry and give permission for login into
the system.

b) Admission Process :
This process is automates the registration of the patient. Here
settings up the entry of various information relating to patients
are recorded. Also a physician is allocated to a patient.

c) Lab services :
Patient lab regarding test will be process and record through
this module and update the database. On the basis of the record it
will report the lab test. It will also give the information about the
cost of lab test to the bill process.

d) Billing process :
This process calculates the total expenditure made on various
information relating to patients through the entire process i.e.
from admission to discharge is produced out in the form of bill to
be paid by the patients.

e) Room maintenance :
This process maintains the rooms and beds whether they are
vacant or occupied along with capacity of the rooms and rates.
 f) Checkout process :
This process is automates the discharge of the patient. Here
settings up the entry of various information relating to patients
like bills paid or not are recorded.

g) Report generation process :

Reports have to generate periodically and should be provided
to the different authorities personals.

10.3 FUTURE SCOPE AND FURTHER ENHANCEMENT OF THE

PROJECT:-
 People can easily find out the information of physician with of
patients through the project. This project will help in further to
develop the web site to browse for various information relating to
patients and physicians.

The users who will remain responsible to use this system

would also become very reluctant while using this system as
because it can be connects with LAN.

A serious accident person/ill person can reserve a bed or a

room from other site before he/she gets admitted.

Any new test or the diseases cured can be inserted or modified

any time with the permission of the authority.