Patient care system

PATIENT CARE SYSTEM

A mini project report submitted in partial fulfillment of the requirement for the degree of

BACHELOR OF COMPUTER APPLICATION

By

G.MANIKANDAN [Reg.No: 2879052 ]

S.MUGILAN [ Reg.No:2879060 ]
G.SATHISH KUMAR [ Reg.No:2879088 ]

Under the guidance of

Mr. O.VISHWANATHAN, M.Sc., M.E.,
(Head of the Department of Computer Application)
Sri Aravindar Arts and Science College
Vanur Tk – 605 111.

Department of Computer Science and Applications,

Sri Aravindar Arts and Science College,
Akasampet, Vanur Tk – 605 111.
March 2011.

1
 Patient care system

CERTIFICATE
This is to certify that this project work entitled

PATIENT CARE SYSTEM

Being submitted to the Thiruvalluvar University, Vellore.

By
G.MANIKANDAN [Reg.No: 2879052 ]
S.MUGILAN [ Reg.NO:2879060 ]
G.SATHISH KUMAR [ Reg.NO:2879088 ]

for the partial fulfillment for the award of degree of

B.C.A. (COMPUTER APPLICATION)

is a bonafide record of work carried out by his,

Under the guidance and supervision.

HEAD OF THE DEPARTMENT INTERNAL GUIDE

Submitted for the viva-voce examination on _______________

Examiners:

1.

2.

2
 Patient care system

ACKNOWLEDGEMENT
The successful completion of any task would be incomplete without
mentioning the people who made it possible and whose constant guidance and
encouragement secured my success take this privilege to express a few words of
gratitude and respect to all these who helped me in completion of this project.

First of all express my deep sense of gratitude to our respected Honorable

Principal Dr. R. RAMALINGAM M.sc, M.Phil, B.Ed ,PhD then to our Vice
Principal Mr. J. AROKIANATHAN M.sc, M.Phil for their cheerful encouragement
throughout the course.

I would like to extend and record my deep sense of gratitude of my to

Mr. O. VISHWANATHAN M.Sc, ME., Head of the Department, for Granting me
the opportunity to do my project work successfully.

With immense of pleasure I express my deepest gratitude to my guide Mr.

O.VISHWANATHAN M.Sc,ME for the enthusiastic and valuable suggestion
throughout my project.

I would like to thank all my friends who involved in there development of the
project. Finally my special thanks to my parents for their continued support and
encouragement.
G,MANIKANDAN
S.MUGILAN
G.SATHISH KUMAR

3
 Patient care system

TABLE OF CONTENTS

PAGE NO.

SYNOPSIS 6

1.INTRODUCTION

1.1 ABOUT THE PROJECT 7

2. SYSTEM CONFIGURATION

2.1 HARDWARE CONFIGURATION 10

2.2 SOFTWARE CONFIGURATION 11

3. SOFTWARE ENVIRONMENT

3.1 FEATURES OF FRONT END 11

3.2 FEATURES OF BACK END

4. SYSTEM ANALYSIS

4.1 INTIAL INVESTIGATION 16

4.2 DETAILED STUDY AND ANALYSIS 16
4.3 FEASIBILITY STUDY 17
4.4 EXISTENCE SYSTEM 17
4.5 PROPOSED SYSTEM 18

4
 Patient care system

5. SYSTEM DESIGN

5.1 DATA FLOW DIAGRAM 20

5.2 DATABASE DESIGN 22

5.3 DATA TABLE STRUCTURE 23

6.SYSTEM IMPLEMENTATION 26

7.SYSTEM TESTING 28

8.CODING 31

9.SCREEN SHOTS 41

10.CONCLUSION 49

11.BIBILIOGRAPHY 50

5
 Patient care system

SYNOPSIS

Patient Care System is a computer-based "patient record system" which facilitates an

electronic patient encounter, helping automate the entire clinical workflow. This allows
capture of medical data in a standard format, making its collection, comparison and use
across the health care spectrum quick and efficient. This package has been developed at SRI
ARAVINDAR ARTS AND SCIENCE COLLEGE for the SEIGNEUR TECHNOLOGY.
The SEIGNEUR TECHNOLOGY maintains the work manually; request to develop the
system in automation.

This project is developed in Visual Basic Dot Net as Front End and MS Access as
Back End. This project is mainly concentrated on liven modules namely patient master
index, Treatment Tracking System, Visit Tracking System, Medical Record Data
Management, Investigation View / Reports, Discharge Card, Patient Queue Management,
Appointment Scheduling, Admit Module, Bed Management, Administrative Data
Management.

6
 Patient care system

1.INTRODUCTION

1.1 ABOUT THE PROJECT

Patient Care System is a computer-based "patient record system" which facilitates an

electronic patient encounter, helping automate the entire clinical workflow. This allows
capture of medical data in a standard format, making its collection, comparison and use
across the health care spectrum quick and efficient. This package has been developed at SRI
ARAVINDAR ARTS AND SCIENCE COLLEGE for the SEIGNEUR TECHNOLOGY.
The SEIGNEUR TECHNOLOGY maintains the work manually; request to develop the
system in automation.

PATIENT MASTER INDEX MODULE:

In computing, a Patient Master Index (PMI) is a form of Data Integration (DI) specific to the
healthcare industry. Healthcare organizations or groups of them will implement PMI to
identify, match, merge, de-duplicate, and cleanse patient records to create a master index that
may be used to obtain a complete and single view of a patient. The PMI will create a unique
identifier for each patient and maintain a mapping to the identifiers used in each record’s
respective system. A PMI may additionally work with or include Application
Integration (AI) capabilities to update the originating source systems of the patient records
with the cleansed and authoritative data.

Organizations that would use an EMPI include hospitals, medical centers, outpatient clinics,
physician offices, rehabilitation facilities, etc
This screen enables users to choose a registered patient from a database.

TREATMENT TRACKING SYSTEM

A computerized, prototype patient tracking system, designed for a forward medical

treatment facility (MTF), was developed and tested. The system, named MEDTRAK, was

7
 Patient care system
tested in a side-by-side comparative evaluation with the current manual method of patient
tracking. Results of the evaluation showed that the MEDTRAK system admitted, identified,
and tracked patients within the MTF significantly more accurately than did the current
manual system. Furthermore, the types of tracking errors produced by the manual system
were found to be more detrimental to both the effective operation of the MTF and to the
discharge of theater evacuation policy than were those produced by the MEDTRAK system.
In addition to improved patient accountability, the MEDTRAK system reduced the
administrative burden that patient tracking placed on medical personnel, thereby allowing
them to perform clinical duties
Here, user can view the details of various treatments carried out on a patient for all
encounters.

VISIT TRACKING SYSTEM

This module shows the numbers of visits made by a patient for a given encounter.
This module contains a visitor number, checkup date, Remarks, etc.

MEDICAL RECORD DATA

Static data: This module assists in capturing information on patients (like patient
personal information, patient past history, patient family history, etc)

INVESTIGATION VIEW
This module is used to provide various reports based on all the information stored in it
up to the time of generation of reports, this system contains history report\, discharge card
reported.

DISCHARGE CARD

This module includes information on inpatients. The information ranges from various
follow-up reading by doctors and nurses while the patients is in the hospital, prognosis and
long term care, do’s and don’ts, recommendation etc.

8
 Patient care system

PATIENT QUEUE MANAGEMENT

This module is used to manage the track of patients having an appointment with the
doctors. The doctors too can use this module to view their patients as well as review the list
of patients currently waiting in queue.

APPOINTMENT SCHEDULING

The module helps in scheduling patient’s appointment with doctors. This module
contains doctor name, medical record number, patient name, type, and eye.

ADMIT MODULE
In this module can be used to allow user the facility to fill the admission details of
patients.

BED MANAGEMENT
This module helps in keeping track of the status of bed availability of the status of bed
availability for inpatients. In hospitals there may be different classes like general, luxury,
etc.Thus the system categorizes the availability of beds according to classes. The system also
shows the status/reading of various facilities like oxygen, glucose, blood, etc, for each bed,
Doctors/Nurses can enter various readings like pulse, respiration, BP, temperature, etc.of
patients while going about their daily rounds ups.This helps keep track of the progress of
patients.

ADMINISTRATIVE DATA MANAGEMENT

This module allow user to add the administrative details such as fee structure, creation of
hospital master, doctor/nurse master, emergency telephones etc.
9
 Patient care system

2. SYSTEM CONFIGURATION

As a Result of careful analysis of the requirements of developing this project and as

per the needs of the project, the system requirements are determined to the company. The
Requirements are being classified as Hardware and Software Requirements respectively.
They are summarized in the form of tables as follows.

2.1 HARDWARE CONFIGURATION:

PROCESSOR : Pentium IV –2.24GHz

HARD DISK : 40GB

RAM : 512 MB

MONITOR : 15”SVGA Digital Color Monitor

PEN DRIVE : 512 MB

DVD-ROM DRIVE : 16X

MODEM : D Link 56Kbps

KEY BOARD : 104 keys

MOUSE : Optical Mouse

PRINTER : HP DeskJet 640C

10
 Patient care system

2.2 SOFTWARE CONFIGURATION:

Front-End Design : VB.NET

Back-End Database : MS Access

Operating System : Windows XP

3. SYSTEM ENVIRONMENT
3.1 FEATURES OF FRONT END
Visual basic is very popular for it’s friendly working (graphical)
environment Visual basic .net is an extension of visual basics programming
language with many new features in it .The changes from VB to VB.NET are huge ,ranging
from the change in syntax of the language to the types of projects we can create now and the
way we design application .Visual Basic.Net frame work base classes and runtime
environment .it comes with power packed features such as Exception handling,
multithreading that simplifies application development .
VB.NET now supports all the key OOP features like
 Inheritance
 Abstraction
 Encapsulation

INHERITANCE
Inheritance is the concept that a new class can be based on an existing class, inheriting its
interface and functionality from the original class. This is done by inheriting these behaviors
from the existing class through a process know as sub classing .VB.NET is the first version of
VB that supports inheritance .with the introduction of full inheritance ,VB is now a fully
OBJECT –ORIENTED language by any reasonable definition

11
 Patient care system
An inheritance relationship is one in which one type (the derived type) derives from
another (the base type), such that the derived type’s declaration space implicitly contains all
of the accessible non constructor type members of the base type.

The term polymorphism means having or passing through many different forms .In the
.NET Framework, polymorphism is tied directly to inheritance. Polymorphism provides the
ability to vary a veritable method’s implementation with polymorphism; the same base
method can perform different actions depending on the run-time type of the instances that
invokes the methods implementation.

ABSTRACTION
An abstract class is one that is not used to create objects .An abstract class is designed
only to act as base class .IT is a design concept in program development and provides a base
upon which other classes may be built

ENCAPULATION
The wrapping up of data functions into a single unit known as Encapsulation is the most
striking features of the class .the data is not accessible to the outside word, and only those
functions, which are wrapped in the class, can access it.

VISUAL BASIC .NET REFLECTS THE FOLLOWING DESIGN PRINCIPLE:

 It is responsible the descendant of visual basic .An existing visual basic programmer
will feel immediately familiar with the language.
 Its syntax and semantics are simple, straightforward, and easy to understand. The
language avoids unintuitive features.
 It gives developers the major features of the .NET framework and is consistent with
the framework convention
 Its is reasonably upgradeable from Visual Basic
 It is as compatible with previous version of visual Basics as possible .whenever
practical ,Visual Basic .NET has the same syntax ,the same semantics ,and the same
run time behavior as its predecessor

12
 Patient care system
UPGRADING TO VISUAL BASICS.NET
Visual basics.NET enables a fundamental shift from traditional windows
development to building next-generation web and n-tier applications. For this reason, your
code will need to be upgraded to take advantages of visual basics .NET.
This happen automatically when the you open a visual basics .NET: the upgrade
Wizard steps you through the upgrade process and create a new visual basic .NET project
.This is a one way process ;the new visual basic .NET project cannot be opened in visual
basic 6.0

When the project is upgraded, the language is modified for any syntax changes and your
visual basic 6.0 forms are converted to windows forms .In most cases you will have to make
changes to your code after it is upgraded.

EXTRA FEATURES OF VB.NET

NAMESPACES
A namespaces is a collection of different classes .all VB application are developed
using classes from the .NET system namespaces .The namespaces with all the built-in VB
functionality is the system namespaces .all other namespaces .all other namespaces are based
on this system namespaces.
System. Data includes classes which lets us handle data from data sources
System. Drawing: access to drawing
System .IO: Includes classes for data access with files
System .NET: provides interface to protocols used on the internet

ASSEMBLIES
An assembly is the building block of a VB.NET application .An Assembly is a
complied and versioned collection of code and Meta data that forms an atomic function unit

3.2 FEATURES OF BACK END

MS ACCESS
Microsoft Office Access, previously known as Microsoft Access, is a relational database
management system from Microsoft that combines the relational Microsoft Jet Database
Engine with a graphical user interface and software-development tools. It is a member of
13
 Patient care system
the Microsoft Office suite of applications, included in the Professional and higher editions or
sold separately. In mid-May 2010, the current version of Microsoft Access 2010 was released
by Microsoft in Office 2010; Microsoft Office Access 2007 was the prior version.
USES

When reviewing Microsoft Access in the real world, it should be understood how it
is used with other products. An all-Access solution may have Microsoft Access Forms and
Reports managing Microsoft Access tables. However, Microsoft Access may be used only as
the 'front-end', using another product for the 'back-end' tables, such as Microsoft SQL
Server and non-Microsoft products such as Oracle and Sybase. Similarly, some applications
will only use the Microsoft Access tables and use another product as a front-end, such
as Visual Basic orASP.NET. Microsoft Access may be only part of the solution in more
complex applications, where it may be integrated with other technologies such as Microsoft
Excel, Microsoft Outlook or ActiveX Data Objects.
Access tables support a variety of standard field types, indices, and referential integrity.
Access also includes a query interface, forms to display and enter data, and reports for
printing. The underlying Jet database, which contains these objects, is multiuser-aware and
handles record-locking and referential integrity including cascading, updates and deletes

FEATURES

The original concept of Access was for end users to be able to "access" data from
any source. Other uses include: the import and export of data to many formats
including Excel, Outlook, ASCII, dBase, Paradox, FoxPro, SQL Server, Oracle, ODBC, etc.
It also has the ability to link to data in its existing location and use it for viewing, querying,
editing, and reporting. This allows the existing data to change and the Access platform to
always use the latest data. It can perform heterogeneous joins between data sets stored across
different platforms. Access is often used by people downloading data from enterprise level
databases for manipulation, analysis, and reporting locally.

Access Services and Web database

VB.NET web forms can query an MS Access database, retrieve records and display them on
the browser,

SharePoint Server 2010 via Access Services allows for Access 2010 databases to be
published to SharePoint, which enables multiple users to interact with the database
application from any standards-compliant Web browser. Access Web databases published to

14
 Patient care system

SharePoint Server can use standard objects such as tables, queries, forms, macros, and
reports. Access Services stores those objects in SharePoint.

Benefits of MS Access

 Get better results faster with the Office Fluent user interface.

 Create tables quickly without worrying about database complexity.

 Create multiple reports with different views of the same information.

 Track Windows SharePoint Services lists with the rich client capabilities of
Office Access 2007.

 Access and use information from multiple sources.

 Share your information with Microsoft Windows SharePoint Services.

 Move data to Windows SharePoint Services for better manageability.

 . Collect and update your information directly from the source.

15
 Patient care system
4. SYSTEM ANALYSIS

System Analysis is for finding out what happens in the existing system, deciding on
what changes and new features are required and defining exactly what the proposed system
must be. The process of system analysis is largely concerned with determining, developing
and agreeing to the user’s requirements. It provides prime opportunity to communicate well
with the user and conceive a joint understanding of what a system should be doing, together
with a view of the relative importance of the system facilities using interactive techniques.

4.1 INITIAL INVESTIGATION

Initial investigation is the activity that determines whether the user’s requisition is
valid and feasible. The first step in initial investigation is the problem definition. It includes
the identification of the problem to be solved for the task to be accomplished and the system
goals to be achieved. Since the existing system is manual the data processing and certain
report generation may is time consuming. Computerizing the system is an interactive; user-
friendly layout can solve this problem. The security of data in the manual system is less and
providing a system that holds administrative power via computerization it is the best remedial
measure.

4.2 DETAILED STUDY AND ANALYSIS

Detailed system study is a very critical activity while developing application software.
This phase involves detailed study of the existing system and interacting with users to
determine their requirements and specifications using certain techniques. After the feasibility
study, a detailed analysis of the existing system and the new system is to be done. It involves
deep investigation into the existing system for collecting all data carriers that are at present
used in the organization. The formulae that are used for the data carriers, forms, and records
are thoroughly studied and limitations and insufficiencies are stated. For overcoming these
limitations and insufficiencies a new system is proposed so that nature of the existing data
manipulation may increase.

16
 Patient care system
These features are in corporate into a candidate system to produce the necessary
improvement. The improvement must include faster information retrieval and processing,
elimination of human errors; provide better friendly services with the operator etc.

4.3. FEASIBILITY STUDY

During system analysis, a feasibility study of the proposed system is carried out to see
whether it is beneficial to the organization.
The integration unit is currently manual. To get the detailed information on production,
bagging etc large bundles of files have to be looked into. It is very time consuming affair. An
operator has to keep in mind or search a file for the details of department for the data. So
working with the existing system is quite tedious. Whereas considering the merits of the new
system it is very beneficial. The results of the feasibility study are given below:

4.3.1 TECHNICAL FEASIBILITY STUDY

It is a study of resource availability that may affect the availability to achieve an

acceptable system. It is essential that the process of analysis and definition be conducted in
parallel with an assessment of technical feasibility.
It centers on the existing computer system and to what extent it can support the
proposed system. Though information in manual system is enormous, it is easily handled by
the Access (which is RDBMS software). It is easy to find and buy a system, which support
this software. So it is technically feasible.

4.3.2ECONOMIC FEASIBILITY STUDY

Tremendous is the range of changes that accompanies the new technology. Introduction
of a computerized system has some merits and demerits can lead to monetary gains. The cost
to buy a computer system for running this software is quite cheap. We get benefit because we
serve more borrowers quickly and easily. So this system is economically feasible.

17
 Patient care system
4.4 EXISTING SYSTEM

At present all the activities in transaction are handled manually. Manual data
processing system, whole providing economy, flexibility and adaptability at low data
volumes become more complex when the volume of data becomes large. As an organization
expands in size and function, a stage is reached when manual procedures become inadequate
and inefficient. No matter how many clerks are employed a stage is reached then it becomes
impossible to systemize such a large amount of information. What is required then is an
upgrading in the class of information processing technology.
The present system is not sufficient to hold all the information that is necessary for the
processing. So the library is in need of new computerized system, which is very flexible,
user-friendly and capable of holding the system in a robust manner.

LIMITATIONS OF EXISTING SYSTEM

There were a lot of reasons for the introduction of the new system. They are mainly due
to the drawbacks and efficiency of the existing system.

 Physical volume of the data is very large.

 The delay in information search and retrieval.

 Problems in updating and backup.

 Damage of papers containing the information.

 Considerable time taken for report generation.

 Accuracy of data is very lower in manual system.

4.5 PROPOSED SYSTEM

The system study phase studies the problem, identifies alternate solution, evaluates
these solutions and finally recommends best solution. The system gives the structure and
function of the system. A detailed system study is essential for developing an efficient
system. The proposed system provides a better user interface. The system is a menu driven
program.

18
 Patient care system
ADVANTAGES OF PROPOSED SYSTEM

 The proposed system can be utilized for easy documenting and accessing
various data carriers such as forms, reports, records etc.

 Automation makes the system to be user-friendly and hastily in manipulation

and generation of valuable reports providing menu driven facilities.

 Accuracy and security of data will be more comfortable for the organization.

 Computerization will avoids human errors due to inexperience in data entry,

manipulation etc.

 The paper work occurred in the manual system can be completely avoided.

19
 Patient care system
5. SYSTEM DESIGN

5.1 DATA FLOW DIAGRAM

Data flow diagram is a structured analysis tool for showing the movement of data

through the different transformation or processes in the system. Named bubbles show the

processes and data named arrows, entering or leaving the bubbles, represent flows. A

rectangle represents a source or sinks and is a net originator or consumer of data. A source or

sink is typically outside the main system study. DFD can be hierarchically organized which

helps in partitioning and analyzing the large system, such system are called leveled DFD’s.

For the hierarchy to be consistence it is important that net input or output of a DFD for a

process are the same input and output of the process in the higher level DFD. The refinement

stops until each bubble is atomic.

The data flow diagram may be used to represent a system or software at any level of

abstraction. In fact, DFD may be partitioned into levels that represent increasing information

flow and functional detail. A level 0 DFD is called a Context Level DFD.

Appointment

Appointment id

USER
Appointment date

date
ACCOUNT APPOINTMENT

Pat date database

phycode

Appoint desc

Appoint time 20
 Patient care system

PATIENTS

Patient code

USER
Patient name

ACCOUNT PATIENTS Date of discharge

database
Time of discharge

LOGIN

Login id
USER ACCOUNT Databas
e

Password

21
 Patient care system

ROOM

Room no

USER
Room rate

Room type
ACCOUNT ROOM

Status Databas
e

Capacity

Vacant

Occupied

5.2 DATA DESIGN

Data design creates a model of data and information that is represented at a high level of
abstraction. The structure of data has always been an important part of software design. Data
design plays a vital role at the program component level, application level and business level.
In program component level, the design of data structures and algorithms are manipulated. At
the application level, the data model is translated into a database and at the business level,

22
 Patient care system

MODULES:

PATIENT CARE
adddssSYSTEM

PATIENT MASTER
INDEX
VISIT TRACKING

QUEUEING TREATMENT TRACKING PREVIOUS

SYSTEM TREATMENT
SELECTION
APPOINTMENT MEDICAL RECORD
SCHEDULING DATA

ADMIT INVESTIGATION
MODULE REPORTS

DISCHARGE CARD DOCTOR

BED
TRACKING
MANAGEMENT
AAASSYSTEMSYST
EM

ADMINISTRATIVE
DATA

23
 Patient care system
5.3 DATA TABLE STRUCTURE

ACCOUNT

ADMISSION

APPOINTMENT

DRUG ISSUED

EMPLOYEE

24
 Patient care system

LOGIN

OUTBILL

25
 Patient care system

PATIENT

6.SYSTEM IMPLEMENTATION
Implementation includes all those activities that take place to convert from the old
system to the new. The old system consists of manual operations, which is operated in a very
different manner from the proposed new system. A proper implementation is essential to
provide a reliable system to meet the requirements of the organizations. An improper
installation may affect the success of the computerized system.

IMPLEMENTATION METHODS:

There are several methods for handling the implementation and the consequent
conversion from the old to the new computerized system.
The most secure method for conversion from the old system to the new system is to run
the old and new system in parallel. In this approach, a person may operate in the manual
older processing system as well as start operating the new computerized system. This method
offers high security, because even if there is a flaw in the computerized system, we can
depend upon the manual system. However, the cost for maintaining two systems in parallel is
very high. This outweighs its benefits.

Another commonly method is a direct cut over from the existing manual system to the
computerized system. The change may be with in a week or with in a day. There are no

26
 Patient care system
parallel activities. However, there is no remedy in case of a problem. This strategy requires
careful planning.

A working version of the system can also be implemented in one part of the
organization and the personnel will be piloting the system and changes can be made as and
when required. But this method is less preferable due to the loss of entirety of the system.

IMPLEMENTATION PLAN:

The implementation plan includes a description of all the activities that must occur to
implement the new system and to put it into operation. It identifies the personnel responsible
for the activities and prepares a time chart for implementing the system. The implementation
plan consists of the following steps.
 List all files required for implementation.
 Identify all data required to build new files during the implementation.
 List all new documents and procedures that go into the new system.

The implementation plan should anticipate possible problems and must be able to deal
with them. The usual problems may be missing documents; mixed data formats between
current and files, errors in data translation, missing data etc.

POST IMPLEMENTATION REVIEW:

After the system is implemented, a review should be conducted to determine whether

the system is meeting expectations and where improvements are needed. System quality, user
confidence and operating systems statistics are accessed through such technique event
logging, impact evaluation and attitude surveys. The review not only assesses how well the
proposed system is designed and implemented, but also is a valuable source of information
that can be applied to a critical evaluation of the system.

The reviews are conducted by the operating personals as well as the software
developers in order to determine how well the system is working, how it has been accepted
and whether adjustments are needed. The review of the system is highly essential to

27
 Patient care system
determine the future enhancements required by the system. The system can be considered
successful only if information system has met it objectives. The review analyses the opinion
of the employees and identifies the attitudes towards the new computerized system. Only
when the merits and demerits of the implemented system are known, one can determine what
all additional features it requires are. The following are the issues to be considered in the
evaluation of the system.

 The change in the cost of operation after the installation of the

computerized system.

 The basic change that has been effected after the introduction of the
system.

 The improvement in the accuracy of the computations.

 The acceptance of the new system by the staff and the convenience it
brought to them.

 The change in the effectiveness caused by the implementation of the new

system.

A study of the system has revealed that the employees due to the user friendliness have
accepted the system, reduced the number of errors, increased accuracy and decreased cost of
operations. The system also pays for efficient and speedy execution of operations compared
to the earlier system.

7. SYSTEM TESTING
The system testing is the stage of implementation, which is aimed at ensuring that

the system works efficiently and accurately before live operation commences. System testing

requires a test plan that consists of several key activities and steps for program, system and

user acceptance testing. Testing is vital to the success of the system. Inadequate testing or

28
 Patient care system
non-testing leads to errors that may not appear until months later. A small system error can

explode into a much larger problem.

WHITE BOX TESTING

In this approach, tests are made with the internal working of the product. All the

independent paths within a module have been exercised once, executing all the logical

decisions, executing all the loops within their bounds. This approach takes long time for

testing.

BLACK BOX TESTING

Black box testing is not an alternative approach to white box testing. It is rather a

complementary approach. The main focus of this approach is on the information domain

rather than on the logical testing. This test ensures that the input is properly accepted and the

desired output is been produced. This approach has a very little regards for the internal

logical structure of the software. This approach saves the time and energy.

LEVELS OF TESTING

The details of the software functionality tests are given below:

1. UNIT TESTING

2. INTEGRATION TESTING

3. VALIDATION TESTING

4. SYSTEM TESTING

UNIT TESTING

Unit testing is carried out to verify and uncover errors within the

29
 Patient care system
Boundary of the smallest unit or modules. In this testing step, each module was found to be

working Satisfactory as per the expected output of the module. Unit testing exercise specific

paths in the Modules control structure to ensure complete coverage and maximum error

detection.

Initially low volumes of data, often refereed to as modules were evaluated using the

test data. This constitutes the unit testing. This focuses on individual modules independently,

to locate for the errors.

INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure while

contacting test to uncover errors associated with interfacing the objective is to take unit tested

modules and build a program structure that has been dictated by design.

Then the volume was increased gradually, i.e., the individual modules were linked

together, and until the maximum level for each transaction type was reached. This constitutes

the integration testing.

VALIDATION TESTING

It is a final series of software testing. Validation succeeds when software functions in

a manner that can be reasonably expected by the customer. It is achieved through a series of

Black box test that demonstrate conformity with requirements.

The test plan and test procedure are designed to ensure that all the functional

Requirements are satisfied, all performance requirements are achieved, and documentation is

Correct and other requirements are met.

30
 Patient care system
8. CODINGS:

Code
Imports System.DateTime
Imports System.Data.OleDb
Imports System.IO
Imports System.Math
Public Class frm_patinfo
Inherits System.Windows.Forms.Form
Dim MyConnection As New
OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\PIS.mdb")
Dim MyCommand
Dim e As Exception
Dim MyCommand2
Dim MyReader As OleDbDataReader
Dim MyReader2 As OleDbDataReader
Dim dbset As New DataSet
Dim dataA
Dim time As Date
Dim formref
Dim ref2
Dim ref3
Dim ref4
Private Sub frm_patinfo_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
dbset.Clear()
MyConnection.Open()
MyCommand = New OleDbCommand("Select patcode,patname,address,blood
FROM Patients", MyConnection)
dataA = New OleDbDataAdapter(MyCommand)
dataA.Fill(dbset, "Patients")
'DataGrid1.ReadOnly = True
'DataGrid1.DataSource = dbset.Tables("Patients")
MyConnection.Close()
MyCommand.Dispose()
dataA.Dispose()
dbset.Dispose()
disablefields()
getward()
getphy()
End Sub
Function getid()
MyConnection.Open()
MyCommand = New OleDbCommand("SELECT * FROM Patients",
MyConnection)
MyReader = MyCommand.ExecuteReader()
While MyReader.Read
TextBox13.Text = MyReader("patcode")
End While
MyConnection.Close()
MyReader.Close()
MyCommand.dispose()
End Function
Function saveclinicothers()
Dim filename As String = "C:\patinfo\" + TextBox4.Text + ".txt"
Try
Dim oFile As FileStream = New FileStream(filename,
FileMode.OpenOrCreate, FileAccess.Write)
Dim oStream As StreamWriter = New StreamWriter(oFile)
oStream.Write(TextBox12.Text)

31
 Patient care system
oStream.Flush()
oStream.Close()
oFile.Close()
Catch e As Exception
MsgBox(e.ToString)
End Try
End Function
Function getpatcode()
Dim some = TextBox13.Text
Dim another As Integer
Dim newslip2 As String = "pat-0"
Dim number As String
another = CInt(some.TrimStart("p", "a", "t", "-"))
another += 1
number = another.ToString()
Return newslip2 + number
End Function
Function getphy()
MyConnection.Open()
MyCommand = New OleDbCommand("SELECT * FROM physicians",
MyConnection)
MyReader = MyCommand.ExecuteReader()
While MyReader.Read
ComboBox5.Items.Add(MyReader("phycode"))
End While
MyConnection.Close()
MyReader.Close()
MyCommand.dispose()
End Function

If check() = True Then

MsgBox("Please fill in the particular field",
MsgBoxStyle.OkOnly, "Patient Care System")
Button1.Visible = False
Button4.Visible = True
Button2.Enabled = False
Button3.Enabled = False
Button5.Visible = True
Else
MyConnection.Open()
MyCommand = New OleDbCommand(iCmd, MyConnection)
Try
MyCommand.ExecuteNonQuery()
Catch c As Exception
MsgBox(c.ToString)
End Try
'DataGrid1.Refresh()
MyCommand.dispose()
MyCommand = New OleDbCommand(iCmd2, MyConnection)
Try
MyCommand.ExecuteNonQuery()
Catch c As Exception
MsgBox(c.ToString)
End Try
MyConnection.Close()
MyCommand.Dispose()
MsgBox("New Patient Has been Added", MsgBoxStyle.OkOnly,
"Patient Care System")
clear()
disablefields()
saveclinicothers()

32
 Patient care system
End If
End Sub

Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button5.Click
clear()
Button5.Visible = False
Button3.Enabled = True
Button1.Visible = True
Button1.Enabled = True
Button2.Enabled = True
Button4.Visible = False
Button11.Visible = False
Button11.Enabled = False
disablefields()
End Sub
Private Sub Button6_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button6.Click
ref2 = New frm_app
ref2.mdiparent = Me.MdiParent
ref2.show()
End Sub
Private Sub Button9_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button9.Click
ref3 = New frm_alert
ref3.mdiparent = Me.MdiParent
ref3.show()
End Sub
Private Sub Timer1_Tick(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Timer1.Tick
Label16.Text = time.Now.ToLongTimeString
End Sub
Private Sub Button8_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button8.Click
ref4 = New frm_ad
Try
ref4.show()
Catch c As Exception
MsgBox(c.ToString)
End Try
End Sub
Private Sub Button10_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button10.Click
Me.Close()
End Sub
Private Sub Button11_Click(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Button11.Click
updatepatient()
disablefields()
clear()
updatemsg()
fresh()
Button2.Visible = True
Button11.Visible = False
Button11.Enabled = False
End Sub
Private Sub Button12_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button12.Click
If fieldcodecheck() = True Then
MsgBox("Please Enter the Patient code if you would like to
Delete an patient", MsgBoxStyle.Information, "Patient Care System")

33
 Patient care system
Else
buttondis()
fillform()
Button13.Enabled = True
Button12.Enabled = False
End If
End Sub
Private Sub Button13_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button13.Click
deletefield()
buttonena()
'MsgBox("Would you like to delete this patient record?",
MsgBoxStyle.Question.YesNo, "Patient Care System")
Button13.Enabled = False
Button12.Enabled = True
clear()
deletemsg()
End Sub
Private Sub Button14_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button14.Click
If idcheck() = True Then
MsgBox("Please Enter the Patient ID", MsgBoxStyle.Information,
"Patient Care System")
Else
'clear()
disablefields()
fillform()
End If
End Sub
Private Sub Button15_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button15.Click
clear()
End Sub
End Class

SECOND LEVEL OF CODINGS

Imports System.DateTime
Imports System.Data.OleDb
Imports System.IO
Imports System.Math
Public Class frm_outpat
Inherits System.Windows.Forms.Form

#Region " Windows Form Designer generated code "

Public Sub New()

MyBase.New()

'This call is required by the Windows Form Designer.

InitializeComponent()

'Add any initialization after the InitializeComponent() call

End Sub

'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)
If disposing Then
If Not (components Is Nothing) Then
components.Dispose()
End If

34
 Patient care system
End If
MyBase.Dispose(disposing)
End Sub

'Required by the Windows Form Designer

Private components As System.ComponentModel.IContainer

'NOTE: The following procedure is required by the Windows Form Designer

'It can be modified using the Windows Form Designer.
'Do not modify it using the code editor.
Friend WithEvents Label1 As System.Windows.Forms.Label
Friend WithEvents PictureBox1 As System.Windows.Forms.PictureBox
Friend WithEvents Label2 As System.Windows.Forms.Label
Friend WithEvents Timer1 As System.Windows.Forms.Timer
Friend WithEvents Label3 As System.Windows.Forms.Label
Friend WithEvents GroupBox1 As System.Windows.Forms.GroupBox
Friend WithEvents GroupBox2 As System.Windows.Forms.GroupBox
Friend WithEvents Button2 As System.Windows.Forms.Button
Friend WithEvents Button3 As System.Windows.Forms.Button
Friend WithEvents Button4 As System.Windows.Forms.Button
Friend WithEvents TextBox1 As System.Windows.Forms.TextBox
Friend WithEvents TextBox2 As System.Windows.Forms.TextBox
Friend WithEvents Label4 As System.Windows.Forms.Label
Friend WithEvents TextBox3 As System.Windows.Forms.TextBox
Friend WithEvents Label5 As System.Windows.Forms.Label
Friend WithEvents TextBox4 As System.Windows.Forms.TextBox
Friend WithEvents Label6 As System.Windows.Forms.Label
Friend WithEvents TextBox5 As System.Windows.Forms.TextBox
Friend WithEvents Label7 As System.Windows.Forms.Label
Friend WithEvents ComboBox1 As System.Windows.Forms.ComboBox
Friend WithEvents Label8 As System.Windows.Forms.Label
Friend WithEvents Label9 As System.Windows.Forms.Label
Friend WithEvents TextBox6 As System.Windows.Forms.TextBox
Friend WithEvents ComboBox2 As System.Windows.Forms.ComboBox
Friend WithEvents Label10 As System.Windows.Forms.Label
Friend WithEvents ComboBox3 As System.Windows.Forms.ComboBox
Friend WithEvents Label11 As System.Windows.Forms.Label
Friend WithEvents TextBox7 As System.Windows.Forms.TextBox
Friend WithEvents Label12 As System.Windows.Forms.Label
Friend WithEvents ComboBox4 As System.Windows.Forms.ComboBox
Friend WithEvents TextBox8 As System.Windows.Forms.TextBox
Friend WithEvents Label13 As System.Windows.Forms.Label
Friend WithEvents Label14 As System.Windows.Forms.Label
Friend WithEvents Label15 As System.Windows.Forms.Label
Friend WithEvents TextBox9 As System.Windows.Forms.TextBox
Friend WithEvents TextBox10 As System.Windows.Forms.TextBox
Friend WithEvents Label16 As System.Windows.Forms.Label
Friend WithEvents TextBox11 As System.Windows.Forms.TextBox
Friend WithEvents Label17 As System.Windows.Forms.Label
Friend WithEvents TextBox12 As System.Windows.Forms.TextBox
Friend WithEvents Label18 As System.Windows.Forms.Label
Friend WithEvents TextBox13 As System.Windows.Forms.TextBox
Friend WithEvents GroupBox3 As System.Windows.Forms.GroupBox
Friend WithEvents GroupBox4 As System.Windows.Forms.GroupBox
Friend WithEvents RadioButton1 As System.Windows.Forms.RadioButton
Friend WithEvents RadioButton2 As System.Windows.Forms.RadioButton
Friend WithEvents Label19 As System.Windows.Forms.Label
Friend WithEvents Label20 As System.Windows.Forms.Label
Friend WithEvents ComboBox5 As System.Windows.Forms.ComboBox
Friend WithEvents TextBox14 As System.Windows.Forms.TextBox
Friend WithEvents GroupBox5 As System.Windows.Forms.GroupBox

35
 Patient care system
Friend WithEvents RadioButton3 As System.Windows.Forms.RadioButton
Friend WithEvents RadioButton4 As System.Windows.Forms.RadioButton
Friend WithEvents Label22 As System.Windows.Forms.Label
Friend WithEvents Label23 As System.Windows.Forms.Label
Friend WithEvents Label24 As System.Windows.Forms.Label
Friend WithEvents Label25 As System.Windows.Forms.Label
Friend WithEvents Button11 As System.Windows.Forms.Button
Friend WithEvents GroupBox8 As System.Windows.Forms.GroupBox
Friend WithEvents TextBox15 As System.Windows.Forms.TextBox
Friend WithEvents TextBox26 As System.Windows.Forms.TextBox
Friend WithEvents Button10 As System.Windows.Forms.Button
Friend WithEvents Button12 As System.Windows.Forms.Button
Friend WithEvents Button13 As System.Windows.Forms.Button
<System.Diagnostics.DebuggerStepThrough()> Private Sub
InitializeComponent()
Me.components = New System.ComponentModel.Container
Dim resources As System.ComponentModel.ComponentResourceManager =
New System.ComponentModel.ComponentResourceManager(GetType(frm_outpat))
Me.Label1 = New System.Windows.Forms.Label
Me.PictureBox1 = New System.Windows.Forms.PictureBox
Me.Label2 = New System.Windows.Forms.Label
Me.Timer1 = New System.Windows.Forms.Timer(Me.components)
Me.Label3 = New System.Windows.Forms.Label
Me.GroupBox1 = New System.Windows.Forms.GroupBox
Me.TextBox10 = New System.Windows.Forms.TextBox
Me.TextBox9 = New System.Windows.Forms.TextBox
Me.Label15 = New System.Windows.Forms.Label
Me.Label14 = New System.Windows.Forms.Label
Me.Label13 = New System.Windows.Forms.Label
Me.TextBox8 = New System.Windows.Forms.TextBox
Me.TextBox7 = New System.Windows.Forms.TextBox
Me.Label11 = New System.Windows.Forms.Label
Me.ComboBox3 = New System.Windows.Forms.ComboBox
Me.Label10 = New System.Windows.Forms.Label
Me.ComboBox1 = New System.Windows.Forms.ComboBox
Me.Label7 = New System.Windows.Forms.Label
Me.TextBox5 = New System.Windows.Forms.TextBox
Me.Label6 = New System.Windows.Forms.Label
Me.TextBox4 = New System.Windows.Forms.TextBox
Me.Label5 = New System.Windows.Forms.Label
Me.TextBox3 = New System.Windows.Forms.TextBox
Me.Label4 = New System.Windows.Forms.Label
Me.TextBox2 = New System.Windows.Forms.TextBox
Me.TextBox1 = New System.Windows.Forms.Textbox

Me.Button11 = New System.Windows.Forms.Button

Me.Button8 = New System.Windows.Forms.Button
Me.Button7 = New System.Windows.Forms.Button
Me.Button6 = New System.Windows.Forms.Button
Me.Button5 = New System.Windows.Forms.Button
Me.GroupBox7 = New System.Windows.Forms.GroupBox
Me.TextBox24 = New System.Windows.Forms.TextBox
Me.RadioButton5 = New System.Windows.Forms.RadioButton
Me.GroupBox6 = New System.Windows.Forms.GroupBox
Me.TextBox23 = New System.Windows.Forms.TextBox
Me.Label29 = New System.Windows.Forms.Label
Me.TextBox22 = New System.Windows.Forms.TextBox
Me.Label28 = New System.Windows.Forms.Label
Me.TextBox21 = New System.Windows.Forms.TextBox
Me.Label27 = New System.Windows.Forms.Label
Me.GroupBox5 = New System.Windows.Forms.GroupBox

36
 Patient care system
Me.Label18 = New System.Windows.Forms.Label
Me.Label17 = New System.Windows.Forms.Label
Me.TextBox12 = New System.Windows.Forms.TextBox
Me.TextBox13 = New System.Windows.Forms.TextBox
Me.RadioButton2 = New System.Windows.Forms.RadioButton
Me.RadioButton1 = New System.Windows.Forms.RadioButton
Me.GroupBox4 = New System.Windows.Forms.GroupBox
Me.TextBox25 = New System.Windows.Forms.TextBox
Me.Label30 = New System.Windows.Forms.Label
Me.TextBox14 = New System.Windows.Forms.TextBox
Me.ComboBox5 = New System.Windows.Forms.ComboBox
Me.Label20 = New System.Windows.Forms.Label
Me.Label19 = New System.Windows.Forms.Label
Me.GroupBox3 = New System.Windows.Forms.GroupBox
Me.TextBox20 = New System.Windows.Forms.TextBox
Me.Label26 = New System.Windows.Forms.Label
Me.TextBox19 = New System.Windows.Forms.TextBox
Me.TextBox18 = New System.Windows.Forms.TextBox
Me.TextBox17 = New System.Windows.Forms.TextBox
Me.TextBox16 = New System.Windows.Forms.TextBox
Me.Label25 = New System.Windows.Forms.Label
Me.Label24 = New System.Windows.Forms.Label
Me.Label23 = New System.Windows.Forms.Label
Me.Label22 = New System.Windows.Forms.Label
Me.TextBox11 = New System.Windows.Forms.TextBox
Me.Label16 = New System.Windows.Forms.Label
Me.Button9 = New System.Windows.Forms.Button
Me.Button2 = New System.Windows.Forms.Button
Me.Button3 = New System.Windows.Forms.Button
Me.Button4 = New System.Windows.Forms.Button
Me.Label8 = New System.Windows.Forms.Label
Me.TextBox6 = New System.Windows.Forms.TextBox
Me.ToolTip1 = New System.Windows.Forms.ToolTip(Me.components)
Me.TextBox15 = New System.Windows.Forms.TextBox
Me.TextBox26 = New System.Windows.Forms.TextBox
CType(Me.PictureBox1,
Me.TextBox10.BackColor = System.Drawing.SystemColors.Info
Me.TextBox10.Location = New System.Drawing.Point(288, 128)
Me.TextBox10.Name = "TextBox10"
Me.TextBox10.Size = New System.Drawing.Size(104, 20)
Me.TextBox10.TabIndex = 23
'
'TextBox9
'
Me.TextBox9.BackColor = System.Drawing.SystemColors.Info
Me.TextBox9.Location = New System.Drawing.Point(80, 160)
Me.TextBox9.Name = "TextBox9"
Me.TextBox9.Size = New System.Drawing.Size(88, 20)
Me.TextBox9.TabIndex = 22
'
'Label15
'
Me.Label15.Location = New System.Drawing.Point(224, 136)
Me.Label15.Name = "Label15"
Me.Label15.Size = New System.Drawing.Size(56, 16)
Me.Label15.TabIndex = 21
Me.Label15.Text = "Religon"
'
'Label14
'
Me.Label14.Location = New System.Drawing.Point(16, 168)

37
 Patient care system
Me.Label14.Name = "Label14"
Me.Label14.Size = New System.Drawing.Size(64, 16)
Me.Label14.TabIndex = 20
Me.Label14.Text = "Nationality"
'
'Label13
'
Me.Label13.Location = New System.Drawing.Point(480, 88)
Me.Label13.Name = "Label13"
Me.Label13.Size = New System.Drawing.Size(56, 16)
Me.Label13.TabIndex = 19
Me.Label13.Text = "Symptons"
'
'TextBox8
'
Me.TextBox8.BackColor = System.Drawing.SystemColors.Info
Me.TextBox8.Location = New System.Drawing.Point(496, 112)
Me.TextBox8.Multiline = True
Me.TextBox8.Name = "TextBox8"
Me.TextBox8.Size = New System.Drawing.Size(120, 72)
Me.TextBox8.TabIndex = 18
Me.ToolTip1.SetToolTip(Me.TextBox8, "Enter the patients symptons
here")
'
'TextBox7
'
Me.TextBox7.BackColor = System.Drawing.SystemColors.Info
Me.TextBox7.Location = New System.Drawing.Point(320, 96)
Me.TextBox7.Name = "TextBox7"
Me.TextBox7.Size = New System.Drawing.Size(32, 20)
Me.TextBox7.TabIndex = 17
'
'Label11
'
Me.Label11.Location = New System.Drawing.Point(288, 104)
Me.Label11.Name = "Label11"
Me.Label11.Size = New System.Drawing.Size(40, 16)
Me.Label11.TabIndex = 16
Me.Label11.Text = "Age"
'
'ComboBox3
'
Me.ComboBox3.BackColor = System.Drawing.SystemColors.Info
Me.ComboBox3.Items.AddRange(New Object() {"Single", "Married",
"Widowed", "Divorced"})
Me.ComboBox3.Location = New System.Drawing.Point(520, 56)
Me.ComboBox3.Name = "ComboBox3"
Me.ComboBox3.Size = New System.Drawing.Size(88, 21)
Me.ComboBox3.TabIndex = 15
'
'Label10
'
Me.Label10.Location = New System.Drawing.Point(472, 64)
Me.Label10.Name = "Label10"
Me.Label10.Size = New System.Drawing.Size(40, 16)
Me.Label10.TabIndex = 14
Me.Label10.Text = "Status"
'
'ComboBox1
'
Me.ComboBox1.BackColor = System.Drawing.SystemColors.Info

38
 Patient care system
Me.ComboBox1.Items.AddRange(New Object() {"Male", "Female"})
Me.ComboBox1.Location = New System.Drawing.Point(520, 24)
Me.ComboBox1.Name = "ComboBox1"
Me.ComboBox1.Size = New System.Drawing.Size(88, 21)
Me.ComboBox1.TabIndex = 13
'
'Label7
'
Me.Label7.Location = New System.Drawing.Point(472, 32)
Me.Label7.Name = "Label7"
Me.Label7.Size = New System.Drawing.Size(48, 16)
Me.Label7.TabIndex = 12
Me.Label7.Text = "Gender"
'
'TextBox5
'
Me.TextBox5.BackColor = System.Drawing.SystemColors.Info
Me.TextBox5.Location = New System.Drawing.Point(120, 128)
Me.TextBox5.Name = "TextBox5"
Me.TextBox5.Size = New System.Drawing.Size(100, 20)
Me.TextBox5.TabIndex = 11
'
'Label6
'
Me.Label6.Location = New System.Drawing.Point(8, 136)
Me.Label6.Name = "Label6"
Me.Label6.Size = New System.Drawing.Size(112, 16)
Me.Label6.TabIndex = 10
Me.Label6.Text = "BirthDate(mm/dd/yy)"
'
'TextBox4
'
Me.TextBox4.BackColor = System.Drawing.SystemColors.Info
Me.TextBox4.Location = New System.Drawing.Point(104, 96)
Me.TextBox4.Name = "TextBox4"
Me.TextBox4.Size = New System.Drawing.Size(176, 20)
Me.TextBox4.TabIndex = 9
'
'Label5
'
Me.Label5.Location = New System.Drawing.Point(8, 104)
Me.Label5.Name = "Label5"
Me.Label5.Size = New System.Drawing.Size(104, 16)
Me.Label5.TabIndex = 8
Me.Label5.Text = "Phone(Home/Cell)"
'
'TextBox3
'
Me.TextBox3.BackColor = System.Drawing.SystemColors.Info
Me.TextBox3.Location = New System.Drawing.Point(64, 64)
Me.TextBox3.Name = "TextBox3"
Me.TextBox3.Size = New System.Drawing.Size(384, 20)
Me.TextBox3.TabIndex = 7
'
'Label4
'
Me.Label4.Location = New System.Drawing.Point(8, 72)
Me.Label4.Name = "Label4"
Me.Label4.Size = New System.Drawing.Size(48, 16)
Me.Label4.TabIndex = 6
Me.Label4.Text = "Address"

39
 Patient care system
'

'Button13
'
Me.Button13.BackColor = System.Drawing.SystemColors.ControlLight
Me.Button13.Location = New System.Drawing.Point(512, 224)
Me.Button13.Name = "Button13"
Me.Button13.Size = New System.Drawing.Size(96, 23)
Me.Button13.TabIndex = 26
Me.Button13.Text = "Delete Now"
Me.Button13.UseVisualStyleBackColor = False
'
'Button12
'
Me.Button12.BackColor = System.Drawing.SystemColors.ControlLight
Me.Button12.Location = New System.Drawing.Point(512, 192)
Me.Button12.Name = "Button12"
Me.Button12.Size = New System.Drawing.Size(96, 23)
Me.Button12.TabIndex = 25
Me.Button12.Text = "Edit Now"
Me.Button12.UseVisualStyleBackColor = False
'
'Button10
'
Me.Button10.BackColor = System.Drawing.SystemColors.ControlLight
Me.Button10.Location = New System.Drawing.Point(512, 160)
Me.Button10.Name = "Button10"
Me.Button10.Size = New System.Drawing.Size(96, 24)
Me.Button10.TabIndex = 24
Me.Button10.Text = "Add Now"
Me.Button10.UseVisualStyleBackColor = False
'
'GroupBox8
'
Me.GroupBox8.Controls.Add(Me.RadioButton4)
Me.GroupBox8.Controls.Add(Me.RadioButton3)
Me.GroupBox8.Location = New System.Drawing.Point(208, 0)
Me.GroupBox8.Name = "GroupBox8"
Me.GroupBox8.Size = New System.Drawing.Size(152, 40)
Me.GroupBox8.TabIndex = 23
Me.GroupBox8.TabStop = False
'

'Button11
'
Me.Button11.BackColor = System.Drawing.SystemColors.ControlLight
Me.Button11.Location = New System.Drawing.Point(512, 272)
Me.Button11.Name = "Button11"
Me.Button11.Size = New System.Drawing.Size(72, 23)
Me.Button11.TabIndex = 22
Me.Button11.Text = "Get Patient"
Me.Button11.UseVisualStyleBackColor = False
'
'Button8
'
Me.Button8.BackColor = System.Drawing.SystemColors.ControlLight
Me.Button8.Location = New System.Drawing.Point(400, 192)
Me.Button8.Name = "Button8"
Me.Button8.Size = New System.Drawing.Size(96, 23)

9. SCREENSHOTS

40
 Patient care system
PATIENT MASTER

ADMINISTRATIVE DATA

41
 Patient care system

PATIENT QUEUE

42
 Patient care system

VISIT TRACKING SYSTEM

43
 Patient care system

TREATMENT TRACKING SYSTEM

INVESTIGATION VIEW/REPORT

44
 Patient care system

ADMIT MODULE

45
 Patient care system
DISCHARGE CARD

MEDICAL RECORD

46
 Patient care system

BED MANAGEMENT

47
 Patient care system

FUTURE ENHANCEMENT

Any system has a scope for enhancement even though it is an efficient and effective one.
Likewise, the Information system is however efficient, but it includes some enhancements as
follows:

 This Patient Care System can be modified as account based one. Thus the
users/Patient can access the project even from their home itself.
 Security may be stepped up with more level of authentication and authorization
features.

The overall concept used in this software is good and further addition and
modification can easily be accomplished to it. Right from the beginning of the project,
provisions can be made to upgrade the software to meet further overall concept used in
software enhancement.

Software in VB.NET is very flexible and all application was tested with live data and
has proved to respond successfully. The “PATIENTS CARE SYSTEM” can be further
enabled by adding additional features. Therefore it can be considered as an efficient means of
control.

48
 Patient care system

10. CONCLUSION

The PATIENT CARE SYSTEM has been completed successfully. The proposed
system overcomes all the drawbacks of the existing system and also it is user friendly. The
administrator maintains details of the Patient master index, admit module, etc. And also
blocks the access of the unauthorized users.

The development phase of this system is very essential. The various experienced people
prior to its actual development analyzed the system. The system analysis phase mainly
concentrates on disadvantages of the existing system and how to overcome from that demerit.
Because of the structured analysis, this new system came over the drawbacks of the existing
system
.

The application has been fully developed, fulfilling the necessary requirements, as
identified in the requirements analysis phase.

Finally to conclude, this software is completed successfully to cater the needs of all
users and management. It is also highly interactive and user friendly.

49
 Patient care system

11. BIBLIOGRAPHY

Books:

 Kelly Help Anaya Hettibewa-Teach Tour self VB.NET in 14 Days-Macmillan

Publications-2005 Edition

 Al Williams, Kim Barber, Paul Newkirk- VB.NET Black Book –

The Corollas Group 2000 Edition.

 Ruth Marin-Introduction to VB.NET -John Wiley & Sons Publications-2000

 How to Do Everything with Microsoft Office Access 2007 by Virginia Andersen.

 Roger S.Pressman “Software Engineering” Chill Publicity

Websites:

 www.info.com
 www.functionx.com
 www.utteraccess.com
 www.vbdotnetheavean.com
 www.startvbdotnet.com

50