HEALTH CARE MANGEMENT SYSTEM

CASE STUDY

SUBJECT
VISUAL PROGRAMMING USING .NET

Submitted by Submitted To
Ravi Jatava K13214 Garima Tyagi
 CONTENTS

S.no Content Name Page No

1. ABSTRACT 2

2. INTRODUCTION 4

PROBLEM INTRODUCTION 6

SCOPE OF HEALTH CARE MANAGEMENT 7

MODULES 7

3. REQUIRMENT SPECIFICATION 10

DATA COLLECTION 10

SOFTWARE REQUIRMENT 10

HARDWARE REQUIRMENT 11

4. ANALYSIS 13
EXISTING SYSTEM 13
PURPOSED SYSTEM 13
FEASIBILITY STUDY 14

5. SYSTEM DESIGN 15
FLOW CHART 15
UML DIAGRAM 18
UI DIAGRAM 20

6. TESTING 28

7. SOFTWARE IMPLEMENTATION 29

8. CONCLUSION & FUTURE INHANCEMENT 35

SCREENSHOT 36

9. REFRENCE & BIBLOGRAPHY 49

1
 ABSTRACT
The main intention of introducing this system is to reduce the manual work at
Health center counters. Every sort of task is performed by the system, such as
registering different types of persons (i.e. employees, students and others),
enquiries, and complaints etc. reducing much paper work and burden of file
storage. Also, the latest information is right available for the officials and
executives wherever they require. The system also facilitates the pharmacist to
enquire about the drugs and about the stock to be ordered and about the
expiry date.

Where the system must be placed?

There are a lot of benefits to the Health center by placing the system at their
registration and at drug store office. At the same time the patients are also
benefited using this system. They can get the work done within no time.

How to use the system?

Using the system is as simple as using the personal computer. Since end user
computing is developing in our country, it is beneficial to both Health center
and the patients. Every step is clearly defined and help is provided throughout
the application to the user. Even the exceptions are handled well to avoid
confusion.

How is it beneficial to the Health Center?

The heath center can get much out of the system. The system is used to
enter the patient details and to enter the details about the health center and the
details about the in-patient and out-patient in detail and about the reports of the
patients. This system represents the patient by the OP number and this is main
criteria how the patient is provided by the free services. The drug information
and the specifications is also provided in this Health Center Management System.

2
The growing quality demand in the hospital sector makes it necessary to exploit
the whole potential of stored data efficiently, not only the clinical data, in order
to improve diagnoses and treatments, but also on management, in order to
minimize costs and improve the care given to the patients.
In this sense, Data Mining (DM) can contribute with important benefits to
the health sector, as a fundamental tool to analyze the data gathered by hospital
information systems (HIS) and obtain models and patterns which can improve
patient assistance and a better use of resources and pharmaceutical expense.

3
 1.INTRODUCTION

A healthcare center is looking to develop a state of patient portfolio

management system which is able to track their patients medical history. This
system is to facilitate the center to retrieve, update, and report the patient
information efficiently, in turn helping the doctors make timely, effective
diagnoses. At the same time, the center can utilize this system to monitor their
medical and financial management.
Currently, different departments in the healthcare center have their own
separated systems leading to the lack of communications and the inefficient data
sharing. For example, the finance department uses simple EXCEL spreadsheets
to record the paycheck information of the employees which is inconvenient to
retrieve and update employees information; in the clinic department, the
doctors have to write down the prescriptions for the patients and keep paper
documents, and also do not have any information about the patients insurance
plans; the medicine department has to keep the prescription and inventory
records on their own computer system. While each system serves a distinctive
purpose, there is no coordinating, assimilating and representing of data. The
systems may
have duplicate data which is a waste of space. The different systems also may
have different application programs which cause incompatible files. Due to
these disadvantages of the current system, a healthcare management system is
proposed.

BRIEF OVERVIEW OF HEALTH CENTER MANAGEMENT SYSTEM

To develop a Health Center Management system, we take care of patient

registration, drug information and concerns such as drug enquiries and
complaints.

The current manual system is slow laborious and error prone to computerize the
same for quicker efficient results and customer satisfaction.

ADVANTAGES TO BOTH END USERS & DEVELOPERS

The system is useful in various ways as the information about the patients
who are taking the free services from the health center all the details are already

4
stored in the database, so the service is done in no time. All the information about
the drugs are also maintained in the database.

GOAL AND NEED:

GOAL: With every going day the need to be where the inflow of outpatient
request exceeds that which can be handled manually. Hence computerization of
OP receipt request and maintenance of the drugs through the computerization
brings better satisfaction and service oriented ness.

Quicker processing of OPNO receipt would mean better service to the

patients. It would also help in the complexity of maintaining the records
manually and thus less time is wasted on rework. Proper maintenance of the
drug information timely dispatching of the drugs from the main stores to the
pharmacy and also maintenance of daily dispatching of the drugs to the out
patients from the pharmacy to the out patients. Towards this achievement the
computerization of the Health Center will help greatly in maintaining pf proper
information about the out patients who are eligible for the free services and the
patients who are not eligible for the free services, drug information, patients
records, and daily dispatching of the drugs to various patients.

NEED: To develop a Heath Center Management system as from manual system

to computerized system, and to take care of Records of the various departments
in the health center. The current manual system is slow laborious and error prone
to computerize the same for quicker efficient results.

5
Problem Introduction:

Lack of immediate retrievals: -

The information is very difficult to retrieve and to find particular information like-
E.g. - To find out about the patients history, the user has to go through various
registers. This results in in convenience and wastage of time.
Lack of immediate information storage: -
The information generated by various transactions takes time and efforts to be
stored at right place.
Lack of prompt updating: -
Various changes to information like patient details or immunization details of
child are difficult to make as paper work is involved.
Error prone manual calculation: -
Manual calculations are error prone and take a lot of time this may result in
incorrect information. For example, calculation of patients bill based on various
treatments.
Preparation of accurate and prompt reports: -
This becomes a difficult task as information is difficult to collect from various
register.
Objective: -

1) Define hospital
2) Recording information about the Patients that come.
3) Generating bills.
4) Recording information related to diagnosis given to Patients.
5) Keeping record of the Immunization provided to children/patients.
6) Keeping information about various diseases and medicines available to cure
them.

These are the various jobs that need to be done in a Hospital by the
operational staff and Doctors. All these works are done on papers.
6
Scope of the Project: -

1) Information about Patients is done by just writing the Patients name, age
and gender. Whenever the Patient comes up his information is stored
freshly.
2) Bills are generated by recording price for each facility provided to Patient
on a separate sheet and at last they all are summed up.
3) Diagnosis information to patients is generally recorded on the document,
which contains Patient information. It is destroyed after some time period
to decrease the paper load in the office.
4) Immunization records of children are maintained in pre-formatted sheets,
which are kept in a file.
5) Information about various diseases is not kept as any document. Doctors
themselves do this job by remembering various medicines.

All this work is done manually by the receptionist and other operational staff and
lot of papers are needed to be handled and taken care of. Doctors have to
remember various medicines available for diagnosis and sometimes miss better
alternatives as they cant remember them at that time.

MODULES:

The entire project mainly consists of 7 modules, which are

Admin module
User module (patient)
Doctor module
Nurse module
Pharmacist module
Laboratories module
Accountant module

7
Admin module:

manage department of hospitals, user, doctor, nurse, pharmacist,

laboratories accounts.
watch appointment of doctors
watch transaction reports of patient payment
Bed, ward, cabin status
watch blood bank report
watch medicine status of hospital stock
watch operation report
watch birth report
watch diagnosis report
watch death report

User module(patient):

View appointment list and status with doctors

View prescription details
View medication from doctor
View doctor list
View blood bank status
View operation history
View admit history. like bed, ward icu etc
Manage own profile

Doctor module:
Manage patient. account opening and updating
Create, manage appointment with patient
Create prescription for patient
Provide medication for patients
Issue for operation of patients and creates operation report
Manage own profile

Nurse module:

Manage patient. account opening and updating

Allot bed, ward, cabin for patients
Provide medication according to patient prescription
Manage blood bank and update status
8
 Keep record of patient operation, baby born and death of patient
Manage own profile

Pharmacist module:
Maintain medicine
Keep records of hospitals stock medicines and status
Manage medicine categories
Watch prescription of patient
Provide medication to prescriptions

Laboratories module:
Watch prescription list
Upload diagnostic report
Preview of report files. like xray images, ct scan, mri reports
Manage own profile

Accountant module:

Create invoice for payment

Order invoice to patient
Take cash payment
Watch payment history of patients
Manage own profile

9
 2. REQUIREMENT SPECIFICATION

DATA COLLECTION:

Observation of the Existing System:

In the typical Health Center Management System is developed to make all the
sections computerized . The entire process is very time consuming and involves
tones of paper work- mostly manually, which is both error prone and time
consuming.

The new system would have the patients are requesting for the receipts at the
Registration office by showing the ID given to the patients that are given at
there respected departments at the university level , Just by submitting the
opno to the database the person is confirmed that the person is eligible or not .
If the person is eligible the service is provided to the person. In the Drug Store
the maintenance of the drug information that how many drugs are there in the
store and how much is dispatched to the Pharmacy house and how many are in
the main stores and what content of the drugs are to be ordered? All this
information is in the drug store. The information that how many out- patients
that have visited the health center and how many patients are In-patients this
information is stored in the Case Records, and the daily dispatching of the
drugs from the pharmacy to the patients are maintained in the Daily Records.

Software Requirements:

Platform - Windows (2000/XP) /Unix/Solaris

Software - VB.NET

10
 Hardware Requirements:

Processor - Intel Celeron class Processor with 2.0 GHz

RAM - 1 GB

Hard Disk - 40 GB

Keyboard - 101 keys

Mouse - Any pointing device

Design Constraints:

This Health Center Management System require huge resources as Hundreds of

the patients will require the services instantly, quick response time are needed.
The database should also be very large and robust to maintain very huge patients
and drugs data.

LANGAUGE SPECIFICATION

features OF. Net

Microsoft .NET is a set of Microsoft software technologies for rapidly building

and integrating XML Web services, Microsoft Windows-based applications, and
Web solutions. The .NET Framework is a language-neutral platform for writing
programs that can easily and securely interoperate. Theres no language barrier
with .NET: there are numerous languages available to the developer including
Managed C++, C#, Visual Basic and Java Script. The .NET framework
provides the foundation for components to interact seamlessly, whether locally
or remotely on different platforms. It standardizes common data types and
communications protocols so that components created in different languages
can easily interoperate.
.NET is also the collective name given to various software components built
upon the .NET platform. These will be both products (Visual Studio.NET and

11
Windows.NET Server, for instance) and services (like Passport, .NET My
Services, and so on).

THE .NET FRAMEWORK

The .NET Framework has two main parts:

1. The Common Language Runtime (CLR).
2. A hierarchical set of class libraries.
The CLR is described as the execution engine of .NET. It provides the
environment within which programs run. The most important features are
Conversion from a low-level assembler-style language, called Intermediate
Language (IL), into code native to the platform being executed on.
Memory management, notably including garbage collection.
Checking and enforcing security restrictions on the running code.
Loading and executing programs, with version control and other such
features.
The following features of the .NET framework are also worth description:

Managed Code

The code that targets .NET, and which contains certain extra
Information - metadata - to describe itself. Whilst both managed and
unmanaged code can run in the runtime, only managed code contains the
information that allows the CLR to guarantee, for instance, safe execution and
interoperability.

Managed Data

With Managed Code comes Managed Data. CLR provides memory allocation
and Deal location facilities, and garbage collection. Some .NET languages use
Managed Data by default, such as C#, Visual Basic.NET and JScript.NET,
whereas others, namely C++, do not. Targeting CLR can, depending on the
language youre using, impose certain constraints on the features available. As
with managed and unmanaged code, one can have both managed and
unmanaged data in .NET applications - data that doesnt get garbage collected
but instead is looked after by unmanaged code.

12
 3. ANALYSIS
1 EXISTING SYSTEM:
Hospitals currently use a manual system for the management and maintainance
of critical information. The current system requires numerous paper forms, with
data stores spread through out the hospital management infrastructure. Often
information is incomplete or does not follow management standards. Forms are
often lost in transit between departments requiring a comprehensive auditing
process to ensure that no vital information is lost. Multiple copies of the same
information exist in the hospital and may lead to inconsistencies in data in various
data stores.

2 PROPOSED SYSTEM:
The Hospital Management System is designed for any hospital to replace their existing manual
paper based system. The new system is to control the information of patients. Room
availability, staff and operating room schedules and patient invoices. These services are to be
provided in an efficient, cost effective manner, with the goal of reducing the time and resources
currently required for such tasks .

3 FEASIBILITY STUDY

The feasibility of the project is analysed in this phase and business proposal
is put forth with a very general plan for the project and some cost estimates.
During system analysis the feasibility study of the proposed system is to be carried
out. This is to ensure that the proposed system is not a burden to the company.
For feasibility analysis, some understanding of the major requirements for the
system is essential.

Three key considerations involved in the feasibility analysis are:

3.1 Economic Feasibility

This study is carried out to check the economic impact will have on the system
will have on the organization. The amount of fund that the company can pour
into the research and development of the system is limited. The expenditures
must be justified. Thus the developed system as well within the budget and this
was achieved because most of the technologies used are freely available. Only
the customised products have to be purchased.

13
 3.2 Technical Feasibility
This study is carried out to check the technical feasibility, that is,the technical
requirements of the system. Any system developed must not have a high demand
on the available available technical resources. This will lead to high demands being
placed on the client. The developed system must have a modest requirement, as
only minimal or null changes for the implementing this system.

3.3 Operational Feasibility

The aspect of study is to check the level of acceptance of the system by the
user. This includes the process of training the user to use the system
efficiently. The user must not feel threatened by the system, instead must
accept it as a necessity. The level of acceptance by the users solely depends
on the methods that are employed to educate the user about the system
and to make him familiar with it. His level of confidence must be raised so
that he is also able to make some constructive criticism, which is welcomed,
as he is the final user of the system.

14
 4. SYSTEM DESIGN
INTRODUCTION

Design is the first step in the development phase for any techniques and
principles for the purpose of defining a device, a process or system in sufficient
detail to permit its physical realization.

Once the software requirements have been analyzed and specified the software
design involves three technical activities design, coding, generation and testing
that are required to build and verify the software.

The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its
ease of maintenance are made. These decisions have the final bearing upon
reliability and maintainability of the system. Design is the only way to accurately
translate the customers requirements into finished software or a system.

Design is the place where quality is fostered in development. Software design is

a process through which requirements are translated into a representation of
software. Software design is conducted in two steps. Preliminary design is
concerned with the transformation of requirements into data.

FLOW CHARTS

Before solving a problem with the help of a computer, it is essential to plan the
solution in a step-by-step manner. Such a planning is represented symbolically
with the help of flow chart. It is an important tool of system analysts and
Programmers for tracing the information flow and the logical sequence in data
processing Logic is the essence of a flow chart.

15
A flow chart is the symbolic representation of step-by-step solution of a given
problem, and it indicates flow of entire process, the sequence of the data input,
operations, computations, decisions, results and other relevant information.

Pertaining to a particular problem, a flow chart helps us in the complete

understanding of the logical structure of a complicated problem and in
documenting the method used. It would be seen that the flow chart is a very
convenient method of organizing the logical steps and deciding what, when and
how to proceed with various processes. The logic should be depicted in the
flow charts. Computerization of the data without a flow chart is like
constructing the building without a proper design and detailed drawings.

Kinds of the Flow Charts

1. System Flow Chart

The system analyst to describe data flow and operations for the data processing
cycle uses these. A system flow chart defines the broad processing in the
organizations, showing the origin of the data, filling structure, processing to be
performed, output that is to generate and necessity of the offline operation.

2. Program Flow Chart (or) Computer Procedure flow chart

The programmers to describe the sequence of operations and the decision of a

particular problem normally use these. A program flow chart plans the Program
structure and also serves the purpose of documentation for a program, which is

16
to be retained and used at a later date either by the original programmer or
others.

Advantages:

Apart from, the DFDS the flow charts has been helping the programmer to
develop the programming logic and to serve as the documentation for a
Completed program, it has the following advantages

1.They help for the easy understanding of the logic of a Process or a procedure

2. It is a better communicating tool than writing in words.

3. It is easy to find the conditions, which are responsible For the actions.
4. It is an important tool for planning and designing the New system.
5. It clearly indicates the role-played at each level.
6. It provides an overview of the system and also demonstrates the relationship
between the various steps.
7. It facilitates troubleshooting.
8. It promotes logical accuracy.

Disadvantages:

1.Communication lines are not always easy to show.

2.The charts are sometimes complicated.
3.Reproduction is difficult.
4.They are hard to modify.

17
UML DIAGRAMS
TABLES

Drugs Table: -

DrugName Istock Ostock ExDate1 ExDate2 Total

In-Patient Record: -

Opno Name Age Sex DoB DoA DoD

Out-Patient Record: -

Opno Name Age Sex Diagnosis

Registered :-

Opno Name Age Sex Occupation Diagnosis

18
Registration:-

Opno Name Age Sex Occupation Address Family

members

Pharmacy Entries:-

Opno Drug No. of Drug No. of

Name1 Tablets Name2 Tablets
issued issued
DN1 DN2

19
 ER DIAGRAM
SYSTEM ARCHITECTURE

Application Clinic WS Patient WS

Server

Clinicians

Database

Patients

Web
Clinic WS Patient WS
Service

Web Service Patient Web Pharmacist

Service Web Service

Pharmacist Database

Application Patient Web Pharmacist

Server Server Web Server

COMPLETE ARCHITECTURE OF SOA

20
MODULES

CLINIC MODULE

The Clinic module exposes two interfaces, a Web Server and a Web Service, for
the clinic staff, the patients and the medical monitoring devices. The Web Server
interface is intended for users who prefer to use a Web browser to access the
healthcare services. Humans or devices to communicate with the e-healthcare
system can use the Web Service interface. The Web Server uses the Web
Services to access the data. The Clinic module provides support for routine
activities of the physician. It maintains information, such as the physicians
appointments for a specific day/week, the patients that s/he has examined, notes
related to the patients, etc. The Clinic module sends prescriptions from the
physician to the desired pharmacies using the Web Service provided.

Fig 5.2.1 CLINIC MODULE

21
 PATIENTID PASSWORD NAME SEX DOB ADDRESS MOBILE LANDLINE

PAT4654 ASDF MURALI MALE 15/08/87 FGDHJ 984567321 4567221

PAT4655 ABCD MAHESH MALE 13/01/87 GHDFG 9884108999 26562445

Table 5.2.1 PATIENT DETAILS

PHYSICIANID APPOINTMENTDATE TIME PATIENTID STATUS NOON

PHY4655 13/032008 9 PAT4655 OPEN AM

PHY4663 14/03/2008 4 PAT4657 OPEN PM

Table 5.2.2PHYSICIAN APPOINTMENTS

PATIENTID NO SYMPTOMS PREVIOUS MEDICAL PHYSICIAN ID DIAGNOSIS STATUS

MEDICINES DIAGNOSIS DATE

PAT4654 1 FEVER CROCIN ANACIN PHY4655 13/03/2008 CLOSED

PAT4658 2 HEADACHE CROCIN SARIDON PHY4658 14/03/2008 CLOSED

Table 5.2.3 MEDICAL DIAGNOSIS

ID PASSWORD NAME SEX DOB ADDRESS PHONE QUALIFICATON

PHY4655 ASDF MURALI MALE 15/08/1987 GHFGH 76767 JGJHHJG

PHY4656 GFFS MAHESH MALE 13/01/1987 HJKHJK 65675 HGJG

Table 5.2.4 PHYSICIAN DETAILS

22
 PHARMACY MODULE

The Pharmacy module exposes Web Server and Web Service interfaces. The
Web Server interface allows the users to access the e-healthcare system at the
pharmacy using a browser. The Web Service interface provides access for
applications deployed at the pharmacy and can also be used by humans and
devices. The Pharmacy module provides services to the pharmacist, patients
and devices used at the pharmacy. The Pharmacy module keeps a record of the
patients prescriptions for the pharmacists and the patients reference. When
the physician submits a new prescription to the pharmacy, the Clinic module at
the physicians office communicates with the Pharmacy module at the
pharmacy. The pharmacist can view the outstanding prescriptions for the
patients, as they are received from the physicians. The Pharmacy module
updates the status of the prescriptions as the pharmacist fills them. The patient
can determine, via the Web Server or Web Service, whether a prescription has
been filled and is ready for pick up or delivery.

Fig 5.2.2 PHARMACY MODULE

PATIENTID PHYSICIANID PHARMACYNAME MEDICINE DOSAGE TIMESOFDAY DATE

23
PAT4655 PHY4655 ABC CROCIN 6 2 13/03/07

PAT4654 PHY4662 XYZ ANACIN 6 2 24/03/07

Table 5.2.5 PHYSICIAN PRESCRIPTION

ATOM/RSS MODULE

Atom/RSS are syndication technologies, based on XML, that enable the

sharing and communication of information between heterogeneous platforms
by making the information self-describing. They allow a publisher to make
information available to consumers on the Web, which retrieve that information
subsequently. The information is delivered from the publisher to the consumer
as an XML file, called an Atom/RSS feed.

This project develops a Consistent Data Replication (CDR) and Reliable Data
Distribution (RDD) infrastructure that replicates information from one
computer to another using Atom/RSS feeds. It uses this infrastructure to
synchronize information on the physicians desktop or server computer with
that on his/her PDA, allowing the physician to view that information when it is
offline. At the start of the day, our software on the PDA retrieves the necessary
updates from the Clinic Web Service on the desktop or server computer via a
wired or wireless network. Any modifications to the information on the PDA
are stored locally on the PDA. At the end of the day, our software on the PDA
generates an update feed for the Clinic Web Service on the desktop or server
computer to read.

24
SPEECH MODULE

Natural Voices provides a simple and efficient way to produce natural

sounding device-to-human voice interaction. It can accurately and naturally
pronounce words, and speak in sentences that are clear and easy-to
understand, without the feeling that a computer is talking to the human. Natural
Voices supports many languages, male and female voices, and the SAPI, Voice
XML and JSAPI interface standards. Using Natural Voices, created text to-
speech software for the prototype device, which runs in the background and
accepts messages in Voice XML format.

DATA FLOW DIAGRAM

Patient Clinic

Pharmacy

Fig 5.2.1- LEVEL 0:

25
 Patient Patient

Devices Devices

W E B S E R V E R S

Patient Patient

WS WS

Data Base

PharmacyW PharmacyW
S S

W E B S E R V E R S

Pharmacy Pharmacy
Devices Devices

Fig 5.2.2 DATA FLOW DIAGRAM-LEVEL1:

26
 Patient Patient

Devices Devices

W E B S E R V E R S

Patient Patient

WS WS

Data Base

Clinical WS Clinical WS

W E B S E R V E R S

Clinical Clinical
Devices
Devices

Fig 5.2.3 DATA FLOW DIAGRAM-LEVEL 2

27
 5. SYSTEM IMPLEMENTATION

System implementation is the important stage of project when the theoretical

design is tuned into practical system. The main stages in the implementation are
as follows:

Planning
Training
System testing and
Changeover Planning

Planning is the first task in the system implementation. Planning means

deciding on the method and the time scale to be adopted. At the time of
implementation of any system people from different departments and system
analysis involve. They are confirmed to practical problem of controlling various
activities of people outside their own data processing departments. The line
managers controlled through an implementation coordinating committee. The
committee considers ideas, problems and complaints of user department, it must
also consider:

The implication of system environment;

Self selection and allocation for implementation tasks;
Consultation with unions and resources available;
Standby facilities and channels of communication;

28
 6. SYSTEM TESTING

Testing is the process of detecting errors. Testing performs a very critical

role for quality assurance and for ensuring the reliability of software. The results
of testing are used later on during maintenance also.

The aim of testing is often to demonstrate that a program works by

showing that it has no errors. The basic purpose of testing phase is to detect the
errors that may be present in the program. Hence one should not start testing
with the intent of showing that a program works, but the intent should be to
show that a program doesnt work. Testing is the process of executing a program
with the intent of finding errors.

TESTING OBJECTIVES

The main objective of testing is to uncover a host of errors, systematically

and with minimum effort and time. Stating formally, we can say,

Testing is a process of executing a program with the intent of finding an

error.

A good test case is one that has a high probability of finding error, if it
exists.

The tests are inadequate to detect possibly present errors.

PROCESS:
The purpose of testing is to discover errors. Testing is the process of
trying to discover every conceivable fault or weakness in a work product. It
provides a way to check the functionality of components, sub assemblies,
assemblies and/or a finished product It is the process of exercising software with
the intent of ensuring that the Software system meets its requirements and user

29
 expectations and does not fail in an unacceptable manner. There are various
types of test. Each test type addresses a specific testing requirement

LEVELS OF TESTING

In order to uncover the errors present in different phases we have the

concept of levels of testing. The basic levels of testing are as shown below

Acceptance
Client Needs Testing

System Testing
Requirements

Integration Testing

Design
Unit Testing

Code

TESTING STRATERGIES:

UNIT TESTING:

Unit testing involves the design of test cases that validate that the
internal program logic is functioning properly, and that program input produce
valid outputs. All decision branches and internal code flow should be validated.
It is the testing of individual software units of the application .it is done after the
completion of an individual unit before integration. This is a structural testing,

30
 that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at component level and test a specific business process, application,
and/or system configuration. Unit tests ensure that each unique path of a
business process performs accurately to the documented specifications and
contains clearly defined inputs and expected results.

INTEGRATION TESTING:

Integration tests are designed to test integrated software components

to determine if they actually run as one program. Testing is event driven and is
more concerned with the basic outcome of screens or fields. Integration tests
demonstrate that although the components were individually satisfaction, as
shown by successfully unit testing, the combination of components is correct
and consistent. Integration testing is specifically aimed at exposing the
problems that arise from the combination of components.

FUNCTIONAL TESTING:

Functional tests provide a systematic demonstrations that functions

tested are available as specified by the business and technical requirements,
system documentation and user manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

31
 Output :identified classes of application outputs.

Systems/Procedures : interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to
identify

Business process flows; data fields, predefined processes, and successive

processes must be considered for testing. Before functional testing is complete,
additional tests are identified and the effective value of current tests is
determined.

SYSTEM TESTING:

System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results.
An example of system testing is the configuration oriented system integration
test. System testing is based on process descriptions and flows, emphasizing
pre-driven process links and integration points.

WHITE BOX TESTING:

White Box Testing is a testing in which in which the software tester has
knowledge of the inner workings, structure and language of the software, or at
least its purpose. It is purpose. It is used to test areas that cannot be reached
from a black box level .

BLACK BOX TESTING:

Black Box Testing is testing the software without any knowledge of the
inner workings, structure or language of the module being tested . Black box
tests, as most other kinds of tests, must be written from a definitive source
document, such as specification or requirements document, such as

32
 specification or requirements document. It is a testing in which the software
under test is treated, as a black box .you cannot see into it. The test provides
inputs and responds to outputs without considering how the software works.

UNIT TESTING:

Unit testing is usually conducted as part of a combined code and unit test phase
of the software lifecycle, although it is not uncommon for coding and unit testing
to be conducted as two distinct phases.

TEST STRATEGY AND APPROACH

Field testing will be performed manually and functional tests will be written
in detail.

TEST OBJECTIVES

All field entries must work properly.

Pages must be activated from the identified link.
The entry screen, messages and responses must not be delayed.
Features to be tested.
Verify that the entries are of the correct format.
No duplicate entries should be allowed.
All links should take the user to the correct page.

INTEGRATION TESTING: Software integration testing is the incremental

integration testing of two or more integrated software components on a single
platform to produce failures caused by interface defects.
33
 The task of the integration test is to check that components or software
applications, e.g. components in a software system or one step up
software applications at the company level interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

ACCEPTANCE TESTING:

User Acceptance Testing is a critical phase of any project and requires

significant participation by the end user. It also ensures that the system meets
the functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

34
 7. CONCLUSION & FUTURE ENHANCEMENT

Healthcare is a field where information has to be maintained properly. This field

needs to create a user-friendly system, which guides users at all steps they need
to perform in it. The information provided by the users must be kept secured, as
the healthcare information is very much confidential. The prescriptions for a
certain patient are forwarded electronically to the pharmacy. This avoids the
unnecessary time taken by the patient to carry the prescription to the pharmacy.

Thus our healthcare is much secured providing authentication to the

user. Our project guides the user to the action they need to perform. Our project
is user-friendlier than all other e-healthcare systems with voice messages and
blue tooth enhancement.

Our e-healthcare system currently focuses on the relationships between

patients, physicians and pharmacists. We plan to extend the system to other
healthcare facilities and professionals, such as laboratory technicians who
perform and report tests and analyses requested by physicians. We also plan to
investigate whether our Clinic and Pharmacy modules can be interfaced to
applications supplied by pharmaceutical companies that provide information on
medications and dosages and warn of interactions between medications. In
addition, we plan to investigate drug delivery devices, such as e-pillboxes, that
prompt and monitor the regular and timely consumption of medications.

35
SCREENSHOTS
MAIN PAGES FOR HEALTHCARE

Home page

New user Registration page

36
37
Patient Registration

38
Doctor Registration page

Admin page

39
Create new Admin

40
Schedule patients

41
Invite Doctor

42
Validate patient

43
Bill Generation

44
Patient Report page

45
Doctor login page containing patients information

46
Diagnostic report of patient

47
Diagnostic details of patient

48
CONCLUSION
The growing quality demand in the hospital sector makes it necessary to exploit
the whole potential of stored data efficiently, not only the clinical data, in order
to improve diagnoses and treatments, but also on management, in order to
minimize costs and improve the care given to the patients.

In this sense, Data Mining (DM) can contribute with important benefits to the
health sector, as a fundamental tool to analyze the data gathered by hospital
information systems (HIS) and obtain models and patterns which can improve
patient assistance and a better use of resources and pharmaceutical expense.

49
 8. REFRENCE & BIBLOGRAPHY

WWW.GOOGLE.CO.IN

VB PRROJECTS

50