Rural Health Data Analysis Using Web Services

Rural Health Data Analysis Using Web Services

Department of Computer Science and Engineering, GIT Belgaum Page 1

CHAPTER-1

INTRODUCTION

The development of any country is measured by the health and prosperity of its citizens.

So, personal health of every citizen is a matter of great concern for every nation. Every

country makes health plans on regular basis and ensures that these plans are well executed

by analyzing the survey reports.

Our country has been facing health crisis specially, in the rural areas since independence.

So, to overcome this problem, every year lots of money is spent to improve the health of

rural people. To monitor the standard of services provided, the government bodies or

private organizations rely on surveys. Currently, the surveying system is very tedious.

The surveying process requires lot of investment both in terms of money and labour.

Thus, there is tremendous need for improvement in this area.

So, we decided to improve the process of survey data collection and health analysis. In

this project we have created an application for NGOs. This application allows each client

NGOs to collect data and upload it to central database. The uploaded data is used to

generate report which is accessible to the interested government bodies or private

organizations. After analyzing the report the government bodies can enhance the services

and effectively identify gaps in healthcare services.

1.1 Objective

To create an application, that imports survey data from various NGOs and sends it to the

central repository in an encrypted format through Web Services. The data stored in the

central repository can be utilized by Government bodies for generating rural health data

analysis report.

1.2 Benefits

The benefits of using this application are:



NGOs can use any type of databases like DB2, MS Access, Microsoft SQL server,

etc. according to their need.

All survey details will be available at central repository.

Since we have provided website for report analysis, the report will be available

24x7.

1.3 Users

The users of the system will be:

NGOs - Client NGOs will collect health data from specific villages and then

upload those data to the central repository.

Database Admin - Registration of NGOs will be done by the database admin.

End user - Government bodies and private organizations will be the end user.



CHAPTER-2

LITERATURE SURVEY

2.1 Background Information

Healthcare in India features a universal health care system run by the constituent states

and territories of India. The Constitution charges every state with "raising of the level

of nutrition and the standard of living of its people and the improvement of public health

as among its primary duties". The National Health Policy was endorsed by the Parliament

of India in 1983 and updated in 2002.

2.2 Rural Healthcare Issues

Malnutrition

42% of Indias children below the age of three are malnourished, almost twice the

statistics of sub-Saharan African region of 28%. World Bank estimates this figure to be

60 million children out of a global estimated total of 146 million. Although Indias

economy grew 50% from 20012006, its child-malnutrition rate only dropped 1%,

lagging behind countries of similar growth rate. Malnutrition impedes the social and

cognitive development of a child, reducing his educational attainment and income as an

adult. These irreversible damages result in lower productivity.

High infant mortality rate

Approximately 1.72 million children die each year before turning one. The under five

mortality rate and infant mortality rate indicators have been declining, from 202 and 190

deaths per thousand live births respectively in 1970 to 64 and 50 deaths per thousand live

births in 2009. However, this rate of decline is slowing. Reduced funding for

immunization leaves only 43.5% of the young fully immunized. A study conducted by the

Future Health Systems Consortium in Murshidabad, West Bengal, indicates that barriers

to immunization coverage are: adverse geographic location; absent or inadequately

trained health workers; and low perceived need for immunization. Infrastructures like

hospitals, roads, water and sanitation are lacking in rural areas. Shortages of healthcare



providers, poor intra-partum and newborn care, diarrheal diseases and acute respiratory

infections, also contribute to the high infant mortality rate.

Diseases

Diseases such as dengue fever, hepatitis, tuberculosis, malaria and pneumonia continue to

plague India due to increased resistance to drugs. And in 2011, India finally developed a

totally drug-resistant form of tuberculosis. India is ranked 3rd among the countries with

the most number of HIV-infected. Diarrheal diseases are the primary causes of early

childhood mortality. These diseases can be attributed to poor sanitation and inadequate

safe drinking water in India. However in 2012, India was polio free for the first time in its

history. Indians are also at particularly high risk for atherosclerosis and coronary artery

disease. This may be attributed to a genetic predisposition to metabolic syndrome and

changes in coronary artery vasodilatation. NGOs such as the Indian Heart Foundation and

the Medwin Foundation have been created to raise awareness about this public health

issue.

Poor sanitation

As more than 122 million households have no toilets and 33% lack access to latrines, over

50% of the population (638 million) defecates in the open. This is relatively higher than

Bangladesh and Brazil (7%) and China (4%). Although 211 million people gained access

to improved sanitation from 19902008, only 31% uses them. 11% of the Indian rural

families dispose of child stools safely whereas 80% of the population leave their stools in

the open or throw them into the garbage. Open air defecation leads to the spreading of

diseases and malnutrition through parasitic and bacterial infections.

Inadequate safe drinking water

Access to protected sources of drinking water has improved from 68% of the population

in 1990 to 88% in 2008. However, only 26% of the slum population has access to safe

drinking water and 25% of the total population has drinking water on their premises. This

problem is exacerbated by falling levels of groundwater, caused mainly by increasing

extraction for irrigation. Insufficient maintenance of the environment around water



sources, groundwater pollution, excessive arsenic and fluoride in drinking water pose a

major threat to India's health.

Rural health

Rural India contains over 68% of India's total population with half of it living below

poverty line, struggling for better and easy access to health care and services. Health

issues confronted by the rural people are diverse and many - from severe malaria to

uncontrolled diabetes, from a badly infected wound to cancer. Rural medical practitioners

are highly sought after by people living in rural India as they more financially affordable

and geographically accessible than practitioners working in the formal public health care

sector. The National Rural Health Mission (NRHM) was launched in April 2005 by the

Government of India. The goal of the NRHM is to provide effective healthcare to rural

people with a focus on 18 states, which have poor public health indicators and/or weak

infrastructure.

Healthcare infrastructure

The Indian healthcare industry is seen to be growing at a rapid pace and is expected to

become a US$280 billion industry by 2020. Rising income levels and a growing elderly

population are all factors that are driving this growth. In order to meet manpower

shortages and reach world standards India would require investments of up to $20 billion

over the next 5 years.

2.3 Technologies Used

Microsoft Visual Studio 2008

Microsoft SQL server 2005

Web Services

2.4 Reasons for selecting technologies

Microsoft Visual Studio - The most popular and well suited development

framework for our needs .It provides a large number of libraries that help to



create interactive user interfaces ,web application, data access, database

connectivity etc.

Microsoft SQL server - It is the commonly used Relational Database

Management System(RDBMS) that runs as a server, providing multi-user access

to a number of databases.

Web Services - It is a very effective way of communication between two

electronic devices over the web. It is defined by W3C as a software system

designed to support interoperable machine to machine interaction over a network.

The transfer is done using SOAP messages which encapsulate data to be

communicated. Web Services also ensure platform independence as it is XML

based.



CHAPTER-3

SYSTEM REQUIREMENTS

3.1 Hardware Requirements

Processor Pentium III or higher, 600MHz

RAM 256 MB or higher

Available Hard Disk Space 900 MB

3.2 Software Requirements

Visual Studio .Net 2008

SQL Server Database

Windows OS



CHAPTER-4

SYSTEM DESIGN

4.1 System Block Diagram

Fig 4.1 System Block Diagram

Client application

Repository(Webservice)

Webservice-- Methods to insert into DB

DB

Webservice method to fetch data in

platform independent format

Data in platform independent format

User1 User2

User3

NGO 1 NGO 2



The above diagram illustrates the overall working of the application. The client

application perform data collection and upload functions ,then data in the central

repository is utilized by users to make analysis.

4.2Activity flow diagram

4.2.1 Activity diagram for client NGOs

Logging in by username and password.

Adding new survey and collecting survey data.

View details of previously added survey.

Delete an existing survey in the database of NGO.

Uploading the survey data.

Fig 4.2 Activity Diagram for Client NGOs



4.2.2. Activity diagram for End-Users

Logging in using username and password.

Choose view report.

Select communicable disease or non-communicable disease.

Fig 4.3 Activity Diagram for End-Users



4.3 Sequence Diagram

4.3.1 Sequence diagram for the client NGO

Fig 4.4 Sequence Diagram for client NGOs



4.3.2 Sequence diagram for End-User

Fig 4.5 Sequence Diagram for End-Users



4.4 ER Diagram

Fig 4.6 ER Diagram



4.5 Schema Diagram

Fig 4.7 Schema Diagram

Basically there are four tables created in the database namely

Survey , SurveyMaster , SurveyDetail1 , SurveyDetail2 .

The Survey table stores data pertaining to each survey and the fields are

NGOname , SurveyName , SurveyLocation , SurveyYear .

The SurveyMaster table contains the personal information of each individual

surveyed and the fields are

PID, Gender, PName , DOB, DOI, Age, Qualification , Occupation ,

MaritalStatus , BP, SurveyName, Location, SYear.



The SurveyDetail1 table stores information related to survey done for

communicable diseases and the fields are

SerialNumber, PID, CommnicableDisease, MedicLocation, StillExists

The SurveyDetail2 table stores information related to survey done for non-

communicable diseases and the fields are

SerialNumber, PID,NonCommnicableDisease, MedicLocation,

StillExists

4.6 Normalization of the database:

Normalization is done to make the database design simple and effective. In fact, it is the

process of organizing data in a database. There are two goals of normalization process:

eliminating redundant data and ensuring data dependencies make sense. These are very

worthy goals as they reduce the amount of space a database consumes and ensure that

data is logically stored.

How we have achieved normalization:

1NF

1NF sets the very basic rules for an organized database .It states that domain of each

attribute in the table should be atomic and single-valued. In our database each and every

attribute is single valued. For some attributes like Qualification, Occupation, Marital

Status etc. combo box is used so that only single value can be entered.

2NF

A table is in 2NF if and only if, it is in 1NF and every non-prime attribute of the table is

either dependent on the whole of a candidate key or on another non-prime attribute. A

non prime attribute of a table is an attribute that is not a part of any candidate key of the

table

Our Database is having four tables namely Survey , SurveyMaster , SurveyDetail1 ,

SurveyDetail2 .



In Survey table only non prime attribute is NGOName which is functionally independent

of all other candidate key namely Surveyname , Surveylocation , SurveyYear .Hence it is

in 2NF Form.

In SurveyMaster table all other attribute is functionally dependent on pid (Primary Key).

In SurveyDetail1 and SurveyDetail2 table all attributes are functionally dependent on

both Serial_Number and Pid

3NF

3NF is based on the concept of transitive dependency .It states that any nonprime attribute

of the relation should not be transitively dependent on the primary key. A transitive

dependency is a functional dependency in which X Z (X determines Z) indirectly, by

virtue of X Y and Y Z (where it is not the case that Y X).

In another way a table is in 3NF if and only if, for each of its functional

dependencies X A, at least one of the following conditions holds:

X contains A (that is, X A is trivial functional dependency), or

X is a super key, or

A-X, the set difference between A and X is a prime attribute (i.e., A-X is

contained within a candidate key)

In Our Database 3NF holds as follows

In Survey table there is no functional Dependency therefore so its automatically

in 3NF.

In SurveyMaster table other attribute is functionally dependent on pid which is a

super key (or Primery Key) . Hence 3NF holds.

In SurveyDetail1 and SurveyDetail2 table all attributes are functionally

dependent on both Serial_Number and Pid which is a super key. Thus 3NF holds



CHAPTER-5

SOFTWARE DEVELOPMENT

The key objective of developing high quality software is to minimize cost and

development time and at the same time maintain scalability and consistency in the

outcome. Procedures and method in the software development that can scale up for large

system can be used suitably. It was decided to follow the waterfall model of software

development. It is most widely used paradigm for software development.

5.1 Waterfall Model

The explanation of all mentioned stages has been given below:

5.1.1 Requirement Analysis & Definition

All possible requirements of the system to be development were captured in this phase.

Requirements were set of functionalities and constraints that the end user who would be

using the application expected from the application. The requirements were gathered from



the end user by consultation, these requirements were analyzed for their validity and the

possibility of incorporating the requirements in the application to be developed was also

studied.

5.1.2 System & Software Design

Before the actual coding, it was highly important to understand what we are going to

create and what it should look like. The requirement specifications from first phase were

studied in this phase and system design was prepared. System design helped in specifying

hardware and system requirement and also helped us in defining the overall system

architecture. This served as the input for the next phase of the model.

5.1.3 Implementation & Unit Testing

On receiving the system design document, the work was divided in modules or units and

actual coding was started. The system was first developed in small programs called

modules, which were integrated in the next phase. Each unit was developed and tested for

its functionality; this is referred to as unit testing. Unit testing mainly verified if the

modules or units met their specification in the early phase.

5.1.4 Integration & System Testing

As specified above, the system was first divided in units which were developed and tested

for their functionalities. These units were integrated into a complete system during

integration phase and were tested to check if all modules coordinate between each other

and the system as a whole behaves as per the specifications. After successfully testing the

software, it was put online on the internet for further reviews.

5.1.5 Operations & Maintenance

This phase of waterfall Model is virtually never ending phase. Generally, problems with

the application development which were not found during the development life cycle

came up after it went online, so the issues relate to the system ware solved. Not all the

problems come in picture directly but they arise time to time and needs to be solved.

Hence this process is referred as maintenance and is never ending.



CHAPTER-6

IMPLEMENTATION

6.1 Setting the Environment for Development

It is the first step in developing any software. The following steps are carried out in

setting up the developing environment.

1) Install Microsoft Visual studio 2008.

2) Install Microsoft SQL server 2005.

3) Install DB2 Express C for Windows.

6.2 Identified Modules

Now, divide the entire project into different modules. The following modules are there in

this project:

Modules Identified In Designing NGO application

Login Module

Add new survey Module

Add Survey Details Module

View SurveyMaster Details Module

View Communicable Disease Module

View Non-Communicable Disease Module

Delete Survey Module

Upload Survey Module

Web service Module



Modules identified in Website Design

Login Module

Report Module

View Communicable Disease Report Module

View Non-Communicable Disease Report Module

6.3 Implementation Logic of Modules in NGO application

6.3.1 Login Module

This module handles user accounts in client side. If the user is registered then it allows to

login to the client application else new user has to register to the central database admin.

On Click Events:

btnLogin_Click() If the user is registered then it allows the user to login

btnCancel_click() Exits the application.

6.3.2 Add new Survey Module

This module helps to create new survey which require NgoName, SurveyName, Location,

SurveyYear.

User defined functions:

Clearcontrols() This user-function clears the textboxes and comboboxes

Disablecontrols() This user-defined function disables the textboxes comboboxes

and any other components.

Enablecontrols() This user-defined function enables the components which are

set to enabled.

On click Event:



btnSave_Click() Survey is saved in the survey table.

6.3.3 Add Survey Details Module

This module is used for data collection for a particular survey conducted in particular

location by an ngo.

User defined functions:

cal_age() calculates the age of the person based on two dtp_DOB, dtp_DOI.

Fillgrid() fills the dataGridView that is used in the DataCollection form.

Clearcontrols() This user-function clears the textboxes and comboboxes

Disablecontrols() This user-defined function disables the textboxes comboboxes

and any other components.

Enablecontrols() This user-defined function enables the components which are

set to enabled.

Events:

btnSave_Click() This event is used to save the person details in SurveyMaster

table.

btnNewClick() This event clears the dataCollection form and allows to add

survey information of new person.

txtPname_Leave() Validates the txtPname textbox.

txtBP_Leave() Validates the txtBP textbox.

6.3.4 View SurveyMaster Details Module

Events:

dataGridView_SelectionChanged() It stores the fileds of one row selected in the

dataGridView.



btnViewSurvey_Click() It displays the details of SurveyMaster table of that

particular survey selected in dataGridView.

6.3.5 View Communicable Disease Module

This module handles the viewing of communicable disease information that is stored in

surveydetail1 table.

6.3.6 View Non-Communicable Disease Module

This module handles the viewing of non-communicable disease information that is stored

in surveydetail2 table.

6.3.7 Delete survey Module

This module helps to delete a particular survey from survey table which in turn delete the

details from surveymaster, surveydetail1 and surveydetail2 tables.

6.3.8 Upload survey Module

This module handles the uploading of survey information of selected survey in survey,

surveymaster, surveydetail1 and surveydetail2 tables in the central database using web

services.

On click events:

btnUpload_Click() on clicking the upload button the survey details are uploaded

by callin the web services.

6.3.8 Web Service Module

This module is used to upload the data from the database of client NGO to the central

repository.

Web methods:

uploadsurvey() This webmethod inserts the tuples in survey table in central

database.



Uploadsurveymaster() This webmethod inserts the tuples in surveymaster table

in central database.

Uploadsurveydetail1 This webmethod inserts the tuples in surveydetail1 table in

central database.

Uploadsurveydetail2 This webmethod inserts the tuples in surveydetail2 table in

central database.

6.4 Implementation logic of Modules in RHDA website

6.4.1 Login Module

This module handles the user who are visiting the Rural Health data analysis website.

Before viewing the report they have to register themselves to the website so that

administrator can know the users who are visiting the website. If a new users want to visit

the website then they have to register themselves to the website using signup link.

6.4.2 Report Module

This Module gives a link to choose between communicable disease report or non-

communicable disease report

6.4.3 View Communicable Disease Report Module

This module handles the report generation of communicable disease from the data

available in central database.

Events:

Page_Load() On this event respective items are added to dropdownlist .

btnGraphicalReport_Click() On the occurrence of this event both tabular and

graphical reports are generated for communicable diseases between the years

selected by the user.

6.4.4 View Non-Communicable Disease Report Module



This module handles the report generation of non-communicable disease from the data

available in central database.

Events:

Page_Load() On this event respective items are added to dropdownlist .

btnGraphicalReport_Click() On the occurrence of this event both tabular and

graphical reports are generated for non-communicable diseases between the years

selected by the user.



CHAPTER-7

TESTING

7.1 Verification and Validation

Verification and Validation (V & V) is the name given to the checking and

analysis process that ensures that software conforms to its specification and meets the

needs of the customers who are paying for that software.

Validation: Are we building the right product?

Verification: Are we building the product right?

Verification involves checking that the software conforms to its specification. We should

check that the system meets its specified functional and non-functional requirements.

Validation is a more general process. We should ensure that the software meets the

expectations of the customer. Within the V & V process, two techniques of system

checking and analysis may be used:

Software inspections analyze and check system representations such as requirements

document, design diagrams and the program source code.

Software testing involves executing an implementation of the software with test data and

examining the outputs of the software and its operational behavior to check that it is

performing as required. Testing is a dynamic technique of verification and validation

because it works with an executable representation of the system.

The testing phase of our project included the following tests.

7.1.1 Defect testing

The goal of defect testing is to expose latent defects in a software system before the

system is delivered. This contrasts with validation testing which is intended to

demonstrate that system meets its specification. Validation testing requires the system to

perform correctly using given acceptance test cases. A successful defect test is a test



which causes the system to perform incorrectly and hence exposes a defect. This

emphasizes an important fact about testing. It demonstrates the presence, not the absence,

of program faults.

This software has been exhaustively tested for defects and all the defects have been

successfully countered.

7.1.2 Black-box testing

Functional or black-box testing is an approach to testing where the tests are

derived from the program or component specification. The system is a black-box whose

behavior can only be determined by studying its inputs and the related outputs. Another

name for this is functional testing because the tester is only concerned with the

functionality and not the implementation of the software.

This software was tested repeatedly by supplying many inputs and observing the output.

In each case it has performed up to the mark.

7.1.3 Structural testing

Structural testing is an approach to testing where the tests are derived from

knowledge of the softwares structure and implementation. This approach is sometimes

called white-box testing or clear-box testing to distinguish it from black-box testing.

Structural testing is usually applied to relatively small programs units such as sub-

routines or the operations associated with an object. As the name implies, the tester can

analyze the code and use knowledge about the structure of a component to derive test

data. The analysis of the code can be used to find how many test cases needed to

guarantee that all the statements in the program or component are executed to least once

during the testing process.

Each of the small modules in the software was tested independently and satisfactory

results were obtained. The different modules that were tested were login

module,addSurveyDetails, viewSurveyMaster module, viewCommunicableDisease

module, viewNonCommunicableDisease module, DeleteSurveyDetails,

UploadSurveyDetails module, ViewCommunicableDiseaseReport module,

ViewNonCommunicableDiseaseReport module.



7.1.4 Integration testing

Once individual program components have been tested, they must be integrated to

create a partial or complete system. This integration process involves building the system

and testing the resultant system for problems that arise from component interactions.

Integration tests should be developed from the system specification and integration

testing should begin as soon as usable versions of the system components are available.

After all the modules had been tested independently, the whole system was

integrated and tested again. The entire system included different modules that had to be

tested exhaustively to get the desired results.

7.1.5 Interface testing

Interface testing takes place when modules or sub-systems are integrated to create

larger systems. Each module or sub-system has a defined interface which is called by

other program components. The objective of interface testing is to detect faults which

may have been introduced into the system because of interface errors or invalid

assumptions about the interfaces.



CHAPTER-8

SNAPSHOTS

1. NGO Login



2. Login Validation

3. User Interface for registering new Survey



4. User Interface for Collecting survey Data and uploading to central

repository

5. View Survey Details



6. View Communicable Disease Information

7. View Non-Communicable disease Information



8. User Interface to collect Survey Data

9. Field Validation



10. Adding personal details added to database

11. Adding Communicable disease to database



12. Adding Non-communicable disease to database

13. Login Page of Rural Health Data analysis website



14. Sign Up Page of Rural Health Data Analysis Website

15. Interface to Change Password



16. Report Generation Page

17. Communicable disease Report



18. Non-Communicable Disease Report



CHAPTER-9

CONCLUSION

Providing a single stand alone application for simplifying the work of both client

NGOs and governing body in Belgaum district is the main job of our project. This

project of ours apart from providing easy and flexible entire survey solution, can also

be used by the private medical organization to decide which disease is prominent in a

particular area and supply medicines in required amount to the people in affected

location.

We have used waterfall model in the development of our project which has separate and

distinct phases of specification and development. Since the application is extensively

tested, this application can be considered reliable. As we are providing website to access

the report it is available and accessible from anywhere.

This application can also be used by the foreign organizations that want to extend

its service in rural areas. Since, the application designed is user friendly; to operate

this application there is no need of having technical knowledge for the people who

are working in the NGOs. Only knowledge of operating the computer can suffice

the purpose.



CHAPTER-10

FUTURE SCOPE

We have created application that uses DB2 and MS Access. In future we can

create application that will use other Databases like MySQL, Oracle, etc .

The application which we have developed is only specific to Belgaum District.

This can be further extended to other cities and finally to entire country, which

will also require a lot of maintenance work as the data on the application is real

time.

We can work on the reliability and scalability of the central repository.

We can make the web service secure and more efficient.

We can include facility of providing advice from expert medical doctors soon

after generating the report in order to curb the disease found excessively.

The process of data collection by the NGO can also be improved and more

functionality can be added and we can provide facility to customize the

application.



REFERENCES

[1] http://www.w3schools.com/webservices/default.asp

[2] http://en.wikipedia.org/wiki/Web_service

[3] http://www.whoindia.org/EN/Section20.htm

[4] http://www.whoindia.org/EN/Section3.htm

[5] http://forums.asp.net/t/1193643.aspx/1

[6] Fundamentals of Database Systems Elmasri and Navathe, 5th Edition, Addison-

Wesley, 2007 pages[61-81(ER Diagram), 360-366(Normalization),225-235(Schema

diagram),243-289(Query) ]

[7] C#: The Complete Reference Herbert Schildt, Tata McGraw Hill, 2004.

[8] Software Engineering Ian Somerville 8th Edition Pearson Education, 2004

chapter 4.1 Software Process Model , 4.1.1 Waterfall Model; chapter 7.2 Requirement

Analysis, Use case Diagram

Rural Health Data Analysis Using Web Services

Documents

Transcript of Rural Health Data Analysis Using Web Services