phr based health care and emergency aid system using ... · phr based health care and emergency aid...

PHR Based Health Care And EmergencyAid System Using Google Cloud

MessagingProject Report

Submitted in partial fulfillment of the requirements for the degree of

Bachelor of Engineering

by

Kazi Ravish Adil Rashida

Roll No 11CO17

Supervisor

Prof Kalpana Bodke

Co-Supervisor

Prof Tabrez Khan

Department of Computer EngineeringSchool of Engineering and Technology

Anjuman-I-Islamrsquos Kalsekar Technical CampusPlot No 2 3 Sector -16 Near Thana Naka Khanda Gaon

New Panvel Navi Mumbai 410206

Academic Year 2014-2015

CERTIFICATE


Anjuman-I-Islamrsquos Kalsekar Technical CampusKhanda GaonNew Panvel Navi Mumbai 410206

This is to certify that the project entitled ldquoPHR Based Health Care And Emergency AidSystem Using Google Cloud Messagingrdquo is a bonafide work of Kazi Ravish Adil Rashida(11CO17) submitted to the University of Mumbai in partial fulfillment of the requirement forthe award of the degree of ldquoBachelor of Engineeringrdquo in Department of Computer Engi-neering

Prof Kalpana Bodke Prof Tabrez Khan

SupervisorGuide Co-SupervisorGuide

Prof Tabrez Khan Dr Abdul Razak Honnutagi

Head of Department Director

Project Approval for Bachelor of Engineering

This project entitled PHR Based Health Care And Emergency Aid System Using GoogleCloud Messaging by Kazi Ravish Adil Rashida is approved for the degree of Bachelor ofEngineering in Department of Computer Engineering

Examiners

1 2

Supervisors1 2

Chairman

Declaration

I declare that this written submission represents my ideas in my own words and where othersideas or words have been included I have adequately cited and referenced the original sourcesI also declare that I have adhered to all principles of academic honesty and integrity and havenot misrepresented or fabricated or falsified any ideadatafactsource in my submission I un-derstand that any violation of the above will be cause for disciplinary action by the Institute andcan also evoke penal action from the sources which have thus not been properly cited or fromwhom proper permission has not been taken when needed

Kazi Ravish Adil Rashida11CO17

Abstract

Title PHR Based Health Care And Emergency Aid System Using Google CloudMessaging

There are two parts of the project-1PHR Based Health Care System2Emergency Aid System using PHR

PHR stands for Personal Health Record PHR is a tool that a person can use to col-lect track and share past and current information about his health or the health of someoneunder his care This concept of PHR Based Health Care System can act as a bridge betweenpatient and doctor with no restriction of time and place In this System the patient has his ownPHR record and can update his PHR record and can also links his family doctor to his PHRrecordWhen a patient updates his PHR record the doctor who is linked with his PHR recordwill get an automatic notification regarding the updation of PHR record by the patientThusdoctor receives updates about the current condition of a patient and can also give suggestion tothe patient as required

Emergency Aid System abbreviated as EAS is a system that provides emergency med-ical care Once it is activated by an incident that causes serious illness or injury the focus ofEAS is emergency medical care of the patient(s)The Concept of Emergency Aid System usingPHR is- Suppose if a person having a PHR record meets with an accident he can immediatelynotify through his digital device about his accident to the nearest registered hospital from thelocation where he met with the accident The corresponding hospital will get notification aboutthe accident which contains personrsquos user id for his PHR record using which the hospital staffcan get the past and present health record of the concerned person and location information orGeo co-ordinates where the accident has taken place Thus the hospital staff can get the personrsquoshealth related information and location where accident has taken place in advance and thus cando emergency treatment appropriately

The project is implemented on android platform

Kazi Ravish Adil Rashida11CO17University of Mumbai

iv

Contents

Project Approval for Bachelor of Engineering iiDeclaration iiiAbstract ivTable of Contents viiList of Figures ixlist of Tables xKeywords And Glossary xi

1 Project Overview 111 Introduction 1

111 Motivation 1112 Advantages Over Current System 2

12 Proposed System Architecture 2121 Formulation of Problem With using Technology 4

13 Organization of the Project 5

2 Review Of Literature 621 An Android-Enabled Mobile Framework for Accessing Holistic Emergency

Medical Services on the Cloud 6211 Description 6212 Pros 7213 Cons 7214 How we overcome Those problem in Project 7

22 Mobile Healthcare Information Management utilizing Cloud Computing andAndroid OS 7221 Description 7222 Pros 10223 Cons 10224 How we overcome Those problem in Project 10

23 An Android Enabled Mobile Cloud Framework for Development of ElectronicHealthcare Monitoring System using VPN Connection 10231 Description 10232 Pros 12

v

233 Cons 12234 How we overcome Those problem in Project 13

24 From Cloud Computing to Mobile Internet From User Focus to Culture andHedonism The Crucible of Mobile Health Care and Wellness Applications 13241 Description 13242 Pros 13243 Cons 14244 How we overcome Those problem in Project 14

25 A Prototype Of Cloud Mobile Health Monitoring System 14251 Description 14252 Pros 15253 Cons 16254 How we overcome Those problem in Project 16

26 Technological Review 16

3 Requirement Analysis 1831 Platform Requirement 18

311 Supportive Operating Systems 1832 Software Requirement 18

321 Front End Software Requirement 18322 Back End Software Requirement 19

33 Hardware Requirement 19331 Basic Hardware Required for Development 19332 Hardware Required For Project Development 19

4 Project Design 2041 Design Approach 20

411 Front End Designs 2142 Software Architectural Designs 24

421 Sequence Diagram 25422 Collaboration Diagram 26423 Activity Diagram 27424 State Diagram 28

43 Database Design 29431 E-R Diagram 29

44 Work-flow Design 30441 Flow Graph 30

5 Implementation Details 3151 Assumptions And Dependencies 3152 Implementation Methodologies 31

521 Modular Description of Project 32

vi

53 Detailed Analysis and Description of Project 32531 Usecase Report 35

6 Results and Discussion 3661 Test Cases 3662 Results Discussion 37

7 Project Time Line 3971 Project Time Line Matrix 3972 Project Time Line Chart 40

8 Task Distribution 4181 Distribution of Workload 41

811 Scheduled Working Activities 41812 Members actvities or task 42

9 Conclusion and Future Scope 4591 Conclusion 4592 Future Scope 45

References 46

References 47

Appendix I 48

Acknowledgment 52

vii

List of Figures

11 System Architecture 312 Hospital Emergency System[5] 413 Hospital Emergency System[6] 4

21 System architecture of Mobile Healthcare Information Management utilizingCloud Computing and Android OS 8

22 System architecture of An Android Enabled Mobile Cloud Framework for De-velopment of Electronic Healthcare Monitoring System using VPN Connection 11

23 System architecture of A Prototype Of Cloud Mobile Health Monitoring System 1524 Hospital Emergency System 1725 Android operating system preference among user 17

41 Home Page 2142 Doctorrsquos Home Page 2143 Patientrsquos Home Page 2244 Patientrsquos personal Detail form 2245 Doctorrsquos personal Detail Form 2346 Pop up in doctorrsquos home page to enter patientrsquos name 2347 Optionrsquos for doctor to create or view Patientrsquos PHR record 2448 Software architecture Design 2449 sequence Diagram Scenario 1 25410 sequence Diagram Scenario 2 25411 Collaboration Diagram Scenario 1 26412 Collaboration Diagram Scenario 2 26413 Activity Diagram Scenario 1 27414 Activity Diagram Scenario 2 27415 State Diagram Scenario 1 28416 State Diagram Scenario 2 28417 ER Diagram 29418 Data Flow Diagram 1 30419 Data Flow Diagram 1 30

51 Use Case Report 35

viii

61 List of PHR record represented as dates on which they are created 3762 Form to create PHR record of Patient 3863 Confirmation for patient whether send emergency notification or not 3864 PHR report in form of pdf 38

71 Time Line Matrix 3972 Time Line Chart 4073 Time Line Chart 40

91 Installation Of App 4892 Home Page 4993 Doctorrsquos Home Page 4994 Optionrsquos for doctor to create or view Patientrsquos PHR record 5095 Patientrsquos Home Page 51

ix

List of Tables

81 Scheduled Working Activities 4182 Member Activities and Task 44

x

Keywords And Glossary

Keywords Google Cloud Messaging Push Notification Database system Client Server Ar-chitecture

Glossary AAndroid is mobile operating system

EEmergency Medical Service is a system that provides emergency medical care

GGCM is Google Cloud Meassaging which is service provided by Google

HHTTP is HyperText Transfer Protocol is a protocol used to transfer hypertext document throughweb

FFrame Work a real or conceptual structure intended to serve as a support or guide for the build-ing of something that expands the structure into something useful

PPersonal Health Record is a tool that a person can use to collect track and share past and currentinformation about hisher health or the health of someone in hisher care

RReal Time a narrative technique whereby events are depicted as occurring entirely within thespan of and at the same rate as the depiction

SSmart Phone is device which is cell phone cum computing device

TTablets are Smart Phone with larger screen

xi

Chapter 1

Project Overview

11 Introduction

111 Motivation

Currently there are many tools available to maintain PHR such as Web based service tools

viz iHealthRecordorg Careplancom Software based tools like Personal Portable Electronic

Medical Records and ID CladeHealth Tracker and Paper based tools such as MyPRO Medical-

Health Records Organizer Jakoter Health Organizer etc But none of them implements concept

of using PHR as a bridge between patient and doctor with no restriction of time and place That

is Patient can share his health information with his doctor due to which doctor can get regular

update about pateintrsquos health which can contribute to better Health care procedure

There also many Emergency Aid Systems in Web based service or Software form such

as Ambutrax AdvanceDispatch Ambulance Dispatch Software AmbuPad etc But none of

them implements concept of using PHR in Emergency Aid System which can provide sufficient

past and present health information about the person and also provide exact location where ac-

cident has taken place to Emergency team Thus Emergency team can use this information to

provide better emergency medical service to the person[9]

1

12 Proposed System Architecture

112 Advantages Over Current System

There are many tools available to maintain PHR such as Web based service tools viz iHealthRecordorg

Careplancom Software based tools like Personal Portable Electronic Medical Records and ID

CladeHealth Tracker and Paper based tools such as MyPRO Medical-Health Records Orga-

nizer Jakoter Health Organizer etc

But none of them implements concept of using PHR as a bridge between patient and

doctor with no restriction of time and place That is Patient can share his health information

with his doctor due to which doctor can get regular update about pateintrsquos health which can

contribute to better Health care procedure








As the project will be implemented on android platform the medium for user of system to inter-

act with the system will be digital devices with android platform such as smartphones tablets

etc Android is chosen as platform as it is popular and it is best suited as client device for this

system architecture The server will be web server to which Android clients connect through

HTTP in order to send request and receive responses along with data contents A database will

be present behind web server which stores all system-relevant user information such as patientrsquos

identity health details doctorrsquos identity etc[7]

Web server will provide data to clients where the data will be the data stored in database

A client can also send data to other client in form of notification The notification will be sent

through web server using Google Cloud Messaging

Below is the Proposed System Architecture

2

Chapter 1 Project Overview

Figure 11 System Architecture

The explanation of the System Architecture is as follows -

Step 1 - A user uses android client to query data from serverEx - Patient select option in

his application to view hisher PHR record and thus request server for required data

Step 2 - Server accepts Android Clientrsquos request and search for the required data in

databaseEx - Server search for patientrsquos PHR record in database

Step 3 - Database gives the required information to server after server searches in database

for dataEx - Server retrieves data from database about patientrsquos PHR record

Step 4 - Server sends the retrieved information to the android clientEx - Patient get the

PHR database on hisher android device

Now Consider the scenario where a patientrsquos PHR record updation is notified to Doctor or

A personrsquos accident is notified to emergency teamIn this scenarios explanation is as follows

Step 123 are same which are mentioned above the difference in the scenario will be -

Instead of following step 4 where data is send to requesting android client in this scenario Step

5 will be followed where data is send to Google Cloud Messaging server from our web server as

the android client (say Patient)is now sending data to another android client instead of asking

data for itself

Now in Step 6 Google Cloud Messaging server now send data to required android client (say

Doctor)

3


121 Formulation of Problem With using Technology

Below Figure represents increasing emergency incidents over years It could be clearly seen

that from the year 1994 there is a tremendous increase in the emergency incidents till now

The below figure represents the use of android operating system among users in the year 2014

Figure 12 Hospital Emergency System[5]

The number of android users are more as compared to other platform users Thus it is clear


that increasing emergency medical system require a platform which should be popular among

most of the usersSo use of android smart phones as a platform to serve for emergency medical

system is quite feasible and will help improve emergency medical service

4


13 Organization of the Project

The organization of the project is as follows

In Chapter 1 we have described about our project which includes the motivation in section

111 and the advantage of our project over the current system in section 112 Section 12

contains the system architecture of our project followed by the formulation of problems of the

technology being used in our project in section 121

In chapter 2 we discuss about the various papers that we have referred for our project This sec-

tion includes the title of the papers along with their description and the pros and cons of those

projects Here we also mention the ways by which we are overcoming all the disadvantages of

the projects that have been described in the paper This chapter also includes the technological

review of our project

In chapter 3 the requirement analysis of our project have been discussed This includes the

operating system that we are working on the hardware software front end and the back end

requirement of our project so as to execute successfully

Chapter 4 is based on project design This includes all the design approaches that include the

front end design component diagram deployment diagram E-R diagram and the flow graph of

our project

Chapter 5 is related to the implementation details of our project This includes the assumptions

that we have taken into consideration while designing our project and also the dependencies

Section 52 describes the modular description of project The use-case report and the classdia-

gram report have been explained in sections 531 and 541 respectively

In chapter 6 we have the results and discussion section which consists of the test cases and the

result discussion

In chapter 7 Project Time Line we have two sections Project time line matrix and chart where

we have explained the steps that were undergone for the completion of our project along with

the time required for completing each part

Chapter 8 is about task distribution where we have discussed about how we have distributed

the project among ourselves This includes the amount of work done by each one of us The

last chapter ie Chapter 9 is about conclusion and future scope

5

Chapter 2

Review Of Literature

21 An Android-Enabled Mobile Framework for Accessing

Holistic Emergency Medical Services on the Cloud

211 Description

Emergency medical services (EMS) have been one of the most important gateways into the

health care system They constitute cross-organizational services involving ambulance agen-

cies and hospital emergency departments (ED) performing a wide range of pre- and in-hospital

emergency care activities[1] A holistic approach to emergency care requires coupling among

multiple health and social care organizations which presents the need for documentation and the

distribution of integrated information for coordinated work driven by organizational properties

and sociocultural constraints Furthermore it requires blending emergency and social care ac-

tivities to address all aspects of patient care needs

Conceptually these activities can be interconnected to form socially enhanced emergency

healthcare processes within and between the participating organizations (ie ambulance agen-

cies and hospitals) thus comprising a virtual holistic emergency healthcare enterprise Thus

in developing an information system that supports EMS processes it is essential to place par-

ticular emphasis on supporting individual process activities as well as on the collaboration and

coordination needs among them

6

Chapter 2 Review Of Literature

The development of an EMS system as a cloud computing application which interfaces with

a PHR and can be accessed by almost any device enables immediate access to critical medical

information concerning an emergency case either by authorized ambulance center personnel on

site of incident and during patient transfer to a hospital or by emergency department personnel

allowing them to check patient medical histories patient medication history patient allergies

and much more to ensure that the treatment provided is the safest and most effective choice for

the patient This paper is concerned with the development of an EMS system and focuses on

providing ubiquitous access to integrated patient information stored and exchanged during an

EMS workflow execution through familiar environments such as GoogleacircTMs Android

212 Pros

bull Deals effectively with emergency cases ubiquitous access to integrated patient informa-

tion

213 Cons

bull It is not a cost-effective solution

214 How we overcome Those problem in Project

We can overcome the problem by implementing a cost-effective solution

22 Mobile Healthcare Information Management utilizing Cloud

Computing and Android OS

221 Description

Cloud Computing provides functionality for managing information data in a distributed ubiq-

uitous and pervasive manner supporting several platforms systems and applications This work

7

22 Mobile Healthcare Information Management utilizing Cloud Computing and Android OS

presents the implementation of a mobile system that enables electronic healthcare data stor-

age update and retrieval using Cloud Computing The mobile application is developed using

GoogleacircTMs Android operating system and provides management of patient health records and

medical images (supporting DICOM format and JPEG2000 coding) The developed system has

been evaluated using the AmazonacircTMs S3 cloud service This article summarizes the imple-

mentation details and presents initial results of the system in practice

Figure below illustrates the proposed system architecture for developing and deploying the

mobile healthcare applications that utilize Cloud Computing The main components of a Cloud

Computing Service usually are [2] the platform front end interface that communicates directly

with users and allows the management of the storage content The interface can be a web client

or a standalone application The Cloud Storage Facilities manages the physical infrastructure

(eg storage elements) and is also responsible for performing maintaining operations (eg

backing up data etc)

Figure 21 System architecture of Mobile Healthcare Information Management utilizingCloud Computing and Android OS

The Cloud Platform interface is also connected to the Cloud Service module which han-

dles and queues user requests Finally the Cloud Infrastructure module manages user account

accessibility and billing issues

Authors has demonstrated the applicability of mobile devices into retrieving medical image

8


data from remote repositories wirelessly utilizing proper content coding (ie wavelet compres-

sion with region of interest support) This work has been now extended to include the function-

ality of communicating with Cloud Computing platforms and support communication through

Web Services Android is a mobile operating system running on the Linux kernel Several mo-

bile device vendors already support it The platform is adaptable to larger and traditional smart

phone layouts and supports a variety of connectivity technologies (CDMA EV-DO UMTS

Bluetooth and Wi-Fi) It supports a great variety of audio video and still image format mak-

ing it suitable for displaying medical content

Finally it supports native multi-touch technology which allows better manipulation of

medical images and generally increases the applicationacircTMs usability

The Cloud Service client running on Android OS consists of several modules The Pa-

tient Health Record application acquires and displays patient records stored into the cloud The

Medical Imaging module is responsible for displaying medical images on the device It decodes

images in DICOM format displaying both image and heard information data When JEPG2000

compression is used the appropriate sub-module decodes the image The communication with

the Cloud is performed through an implementation of Web Services REST API that is supported

natively by Android

The inherent interoperability that comes with using vendor platform and language inde-

pendent XML technologies and the ubiquitous HTTP as a transport mean that any application

can communicate with any other application using Web services

Data in Cloud are seamlessly stored and presented to the user as if they reside locally This

means that the Cloud repository is presented as a virtual folder and does not provide the fea-

tures of a database scheme

SQLite is the database platform supported by Android The file resides into a specific

location at the Cloud and is retrieved on the device every time user needs to query data The

query is performed locally and the actual location of the data in the cloud is revealed to the

applications The database file is updated and uploaded into the Cloud every time user modifies

data respectively

9

23 An Android Enabled Mobile Cloud Framework for Development of ElectronicHealthcare Monitoring System using VPN Connection

222 Pros

bull Efficient storage retrieval and updation of patient information

223 Cons




23 An Android Enabled Mobile Cloud Framework for De-

velopment of Electronic Healthcare Monitoring System

using VPN Connection

231 Description

Cloud computing is on-demand computing that does not reside at the usersacircTM premise In-

stead the computing resources are owned and managed by a service provider and the users

access the resources via the internet Conventional healthcare systems based on patient records

are being considered as electronic format empowering patients to access their records via inter-

net Remote patient monitoring is becoming more feasible as specialized using Virtual Private

Network (VPN) A mobile VPN is described in service provider networks co-operate to dynam-

ically extend a virtual routing area of a local service provider network to the edge of all visited

service provider network and thereby enables IP address continuity for a roaming wireless de-

vice

This paper presents the implementation of electronic healthcare monitoring system which pro-

vides data storage processing and accessing information through mobile cloud using the Virtual

Private Network which improves the privacy and security of the data An android open-source

10


Figure 22 System architecture of An Android Enabled Mobile Cloud Framework forDevelopment of Electronic Healthcare Monitoring System using VPN Connection

cloud computing technologies as the mechanism to build an affordable secure and scalable plat-

form that supports billing as well as Electronic Health Record operations

The client applications are mobile apps run from GoogleacircTMs Android enabled devices

that offers easy networking procedures and low design complexity The developed system has

been proposed to present systemacircTMs client which operates on a mobile device and acquires

data from the EHR and E- billing system connecting to a cloud server within the Virtual Private

Network offered by the Hospital or clinic

Figure below illustrate the proposed system architecture for developing and deploying the

electronic Healthcare monitoring system application that utilize Cloud Computing and the VPN

connection of the public network The main mechanisms of a Cloud Computing Service pro-

vide the platform front-end interface that communicates directly with patientsacircTM and allows

the management of the storage content The PatientsacircTM details are available anytime any-

where whenever required and these data is highly secured because of VPN connection The

interface can be a web client or a standalone application The Cloud Server which manages the

physical infrastructure (eg storage elements) and is also responsible for performing maintain-

ing operations (eg backing up data etc) The Cloud Platform interface is also connected to

the Cloud Service module using Public Network which handles the user requests

11


The Cloud Infrastructure module manages user account accessibility and billing issues

The existing paper [2] has demonstrated the Patient Health Record application obtains and dis-

plays patient records stored into the cloud Data in Cloud are seamlessly stored and presented

to the user as if they reside locally This means that the Cloud repository is presented as a vir-

tual folder and does not provide the features of a database scheme This work has been now

extended to provide all the patients related information to flow more securely using VPN in

the public network and to include the functionality of communicating with Cloud Computing

platforms and support communication through Web Services In this context electronic Health-

care monitoring system has been developed based on GoogleacircTMs Android mobile Operating

System (OS) using the appropriate software development kit (SDK) [3] Android is a mobile

operating system running on the Linux kernel

Several mobile device vendors already support it The platform is adaptable to larger and

traditional smart phone layouts and supports a variety of connectivity technologies (CDMA

EV-DO UMTS Bluetooth and Wi-Fi) It supports a great variety of audio video and still im-

age format making it suitable for displaying medical content Finally it supports native multi-

touch technology which allows better manipulation of medical images and generally increases

the applicationacircTMs usability In order to provide the user with data querying functionality

medical records and related data (images and bio signals) are stored into a SQLite file




applications

232 Pros

bull Provides support for billing as well as electronic healthcare record operations

233 Cons

bull Remote Monitoring may be difficult

12



We can improve the remote monitoring process

24 From Cloud Computing to Mobile Internet From User

Focus to Culture and Hedonism The Crucible of Mobile

Health Care and Wellness Applications

241 Description

With the rise of mobile Internet and cloud computing new ubiquitous medical services will

emerge coinciding with changes in demographics and social structures Mobile e-health and

wellness applications can help relieving the burden of accelerating health care costs due to ag-

ing societies In order to leverage these new innovations a holistic approach must be considered

Facilitating user centered design acceptance models for user diversity and cultural as well

as hedonic aspects can lead to development of services that improve therapy compliance and

can even change the youthacircTMs lifestyle An overview of such applications is presented and put

into a cultural context

242 Pros

Portable devices like mobile phones can be used for effective healthcare system

Cloud provides ease of access of data among users of healthcare system

13

25 A Prototype Of Cloud Mobile Health Monitoring System

243 Cons

Portable devices are not much reliable for critical applications like heatlhcare system


We should all data regarding healthcare system so that if the portable devices crash the system

will still be reliable for for the user of the healthcare system


251 Description

Wireless Body Area Sensor Networks (WBASN) is an emerging technology which uses wire-

less sensors to implement real-time wearable health monitoring of patients to enhance indepen-

dent living In this paper we propose a prototype of cloud mobile health monitoring system

The system uses WBASN and Smartphone application that uses cloud computing location data

and a neural network to determine the state of patients

Figure 23 System architecture of A Prototype Of Cloud Mobile Health Monitoring System

14


The wireless body area sensor network for ubiquitous health monitoring contains three com-

ponents (Tier 1 2 3) Typically a WBASN will form the lowest tier (Tier 1) of a multitiered

medical information system for health monitoring Above figure illustrates general system ar-

chitecture of a medical monitoring information system that includes a personal server at Tier

2 and a series of medical servers in the cloud at Tier 3 The exact system architecture and the

number of system tiers depend predominantly on target applications available infrastructure

and type and number of users The WBASN can include heart sensor motion sensorsacirc

For example similar system can be used for monitoring of cardiac patients during a re-

habilitation period at home The heart sensor can operate in multiple modes reporting either a

raw ECG signal (from one or multiple channels) time-stamped heart beats or averaged heart

rate over a certain period of time The motion sensors each equipped with a 3D accelerometer

can also operate in several modes reporting either (1) raw acceleration signals for x- y- and

z-axes (2) extracted features (eg times tamped steps or phases of a step) or (3) an estimated

level of activity The sensor nodes (together with a network coordinator) attached to a personal

server compose the WBASN Upon configuration the WBASN continually performs sensing

sampling and signal processing Sensors wait for command and control messages from the

WBASN coordinator and report continual sensor readings or events of interest as they occur

Tier 2 encompasses the personal server which is responsible for a number of tasks provid-

ing a transparent interface to the wireless sensor nodes an interface to the user and an interface

to the medical server The interface to the WBASN includes network configuration and manage-

ment Network configuration encompasses the following tasks sensor node registration (type

and number of sensors) initialization (eg specifying sampling frequency and mode of oper-

ation) customization (eg running user-specific calibration or user-specific signal processing

procedure upload) and setup of a

252 Pros

Health monitoring is easy

15

26 Technological Review

253 Cons

It is a very costly solution as it involves wearbles


We can implement the concept in a much more cost-effective manner


Currently there are many tools available to maintain PHR such as Web based service tools like

iHealthRecordorg Careplanco Software based tools like Personal Portable Electronic Medical

Records and ID CladeHealth Tracker and Paper based tools such as MyPRO Medical-Health

Records Organizer Jakoter Health Organizer etcBut none of them implements concept of us-

ing PHR as connecting bridge between patient and doctor with no restriction of time and place

That is Patient can share his health information with his doctor due to which doctor can get

regular update about pateints health which can contribute to better Health care procedure[3]

There also many Emergency Aid System in Web based service or Software form such as

Ambutrax AdvanceDispatch Ambulance Dispatch Software AmbuPad But none of them im-

plements concept of using PHR in Emergency Aid System which can provide sufficient past

and present health information about the person and also provide exact location where accident

has taken place to Emergency team Thus Emergency team can use this information to provide

better emergency medical service to the person[4]

Thus there are no online tool which can provide an efficient medium to communicate with

the doctor to provide each and every current information about patientThus this model provide

an efficient way for communication of health information between patient and doctor Also

there no online tool for better emergency aid service for the person This model provide an

effective way for emergency aid system using PHR

16


Figure 24 Hospital Emergency System

Figure 25 Android operating system preference among user

17

Chapter 3

Requirement Analysis

31 Platform Requirement

311 Supportive Operating Systems

The supported Operating Systems For server include Linux Linux is used as server operating

system For web server we are using apache 20

supported Operating System for client is android

32 Software Requirement

321 Front End Software Requirement

1) Android development tool

2) Java development kit

Android application is built using android adt bundle(application development tool) which

consist of eclipse ide (integrated development environment) and adt plugins

Java development kit is used to support to execute on Android development tool

18

Chapter 3 Requirement Analysis

322 Back End Software Requirement

1) Apache server

2) Mysql database

Apache server will be used to implement web server which contains PHP code

Mysql database will be implemented as database

33 Hardware Requirement

331 Basic Hardware Required for Development

1) Server with 500 GB Hard Disk and 1 GB Ram

332 Hardware Required For Project Development

1) Android Smartphone


19

Chapter 4

Project Design

41 Design Approach

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 real-

ization Once the software requirements have been analyzed and specified the software design

involves three technical activities design coding implementation 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 deci-

sions ultimately affecting the success of the software implementation and its ease of mainte-

nance are made These decisions have the final bearing upon reliability and maintainability of

the system Design is the only way to accurately translate the customeracirc˜s 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

20

Chapter 4 Project Design

411 Front End Designs

Figure 41 Home Page

Figure 42 Doctorrsquos Home Page

21

41 Design Approach

Figure 43 Patientrsquos Home Page

Figure 44 Patientrsquos personal Detail form

22


Figure 45 Doctorrsquos personal Detail Form

Figure 46 Pop up in doctorrsquos home page to enter patientrsquos name

23

42 Software Architectural Designs

Figure 47 Optionrsquos for doctor to create or view Patientrsquos PHR record


Figure 48 Software architecture Design

Our system is follow the three tier architecture First tier consist of GUI Comparision tier and

the Database

1 GUI The GUI(Graphical User Interface) in our project deals with the interface for pa-

tient and doctor Using the GUI patient and doctor can access the system

24


2 Database Database tier is the tier used for the storage of data This tier contains all the

data that is need for the processing of the whole project

421 Sequence Diagram

Figure 49 sequence Diagram Scenario 1


25


422 Collaboration Diagram

Figure 411 Collaboration Diagram Scenario 1


26


423 Activity Diagram

Figure 413 Activity Diagram Scenario 1


27


424 State Diagram

Figure 415 State Diagram Scenario 1


28


43 Database Design

431 E-R Diagram

Figure 417 ER Diagram

29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph

Figure 418 Data Flow Diagram 1


30

Chapter 5

Implementation Details

51 Assumptions And Dependencies

Assumption of project is

1 User should have a google account registered in his android smartphone

2 User should have google play service installed in his android smartphone

3 User should have internet connection in his android smartphone

4 User should have smartphone with Android os platform greater than 23 (Gingerbread)

Dependencies of project is

1 Requires Google Cloud Messaging to transfer data from one Android smartphone to an-

other Android smartphone which is provided by google

2 Requires Google play services to support Google cloud messaging in Android smartphone

52 Implementation Methodologies

Different Modules that will be created are android application web server database


consists of eclipse ide (integrated development environment) and adt plugins The android ap-

plication acts as client which provides an interface to user to interact with system It will provide

the patient an interface to update PHR record link or unlink a doctor to PHR record and notify

31

53 Detailed Analysis and Description of Project

about an emergency situation It provides an interface for doctor to get the updates about PHR

record update list of patient and give suggestion to any patient It provides an interface to emer-

gency team to get notification about any emergency situation view the location of accident and

view the PHR record of the patient who has sent emergency notification Android application

sends data to web server using HTTP or JSON

Web server consists of PHP code which accepts the request from client and gives responses

to client as required The server receives the request from android application and respond to

the particular client who has sent request by HTTP or JSON But if client asks to notify or in

other words sends data to other device then web server uses GOOGLE CLOUD MESSAGING

to send data to the required client Web server is apache 20

Database is mysql and it performs createreadupdate or delete operation as web server

requires

521 Modular Description of Project


There are two parts of the project-

1PHR Based Health Care System

2Emergency Aid System using PHR

PHR stands for Personal Health Record PHR is a tool that a person can use to collect

track and share past and current information about his health or the health of someone under his

care This concept of PHR Based Health Care System can act as a bridge between patient and

doctor with no restriction of time and place In this System the patient has his own PHR record

and can update his PHR record and can also links his family doctor to his PHR recordWhen a

patient updates his PHR record the doctor who is linked with his PHR record will get an au-

tomatic notification regarding the updation of PHR record by the patientThus doctor receives

32

Chapter 5 Implementation Details

updates about the current condition of a patient and can also give suggestion to the patient as

required

Emergency Aid System abbreviated as EAS is a system that provides emergency med-

ical care Once it is activated by an incident that causes serious illness or injury the focus of

EAS is emergency medical care of the patient(s)The Concept of Emergency Aid System using

PHR is- Suppose if a person having a PHR record meets with an accident he can immediately

notify through his digital device about his accident to the nearest registered hospital from the

location where he met with the accident The corresponding hospital will get notification about

the accident which contains personrsquos user id for his PHR record using which the hospital staff

can get the past and present health record of the concerned person and location information or

Geo co-ordinates where the accident has taken place in advance and thus can do emergency

treatment appropriately

The user of this system can be broadly classified as

1 Patient

2 Doctor

3 Emergency medical service team

The Patient accesses the system to create or update his PHR record and registers or update

his family doctorrsquos name As soon ss patient updates his PHR record the updated fields of PHR

is notified to device of patientrsquos family doctor Thus PHR will become an effective medium for

communication between patient and doctor The patient can also press an emergency button

to send emergency medical service team a notification regarding accident of patient Thus a

timely notification is sent to emergency team and emergency team can then perform the emer-

gency medical service efficiently

The Doctor receives notification about the updated PHR record which is updated by patient

through the system The Doctor thus can get the current as well as past information of the pa-

tient and also receive updates about any current information about patientrsquos health Doctor can

also send any suggestion about any health related issue to patientrsquos to which he is registered as

family doctor

33


The Emergency medical service team will get notification about any accident of patient

which is notified by the patient itself The ems team receives the location of accident and the

patientrsquos PHR record in notificationThus ems team will get prior knowledge about the patientrsquos

current and past health record and thus can reach the location where accident has occurred and

can perform emergency treatment more effectively

34


531 Usecase Report

Figure 51 Use Case Report

35

Chapter 6

Results and Discussion

61 Test Cases

Input Patient enters his personal details

Expected Output Personal details of patient are saved in database

Assumption Patientrsquos personal is successfully stored

Error Patient details may not be saved in database due to server crash

Input Doctor enters his personal details

Expected Output Personal details of doctor are saved in database

Assumption Doctorrsquos personal is successfully stored

Error Doctor details may not be saved in database due to server crash

Input Doctor creates patientrsquos PHR record

Expected Output Patientrsquos PHR record will be saved in serverrsquos database

Assumption Patientrsquos PHR record will be successfully stored

Error Patientrsquos PHR record may not be saved in database due to server crash

Input Patientdoctor views PHR record

Expected Output PHR record will be displayed

Assumption PHR record will be successfully retrieved from server and displayed to user

Error PHR record may not be successfully retrieved from the server due to system failure

Input Patient will send an emergency notification

Expected Output Notification will be delivered to doctor

Assumption Emergency notification will be successfully notified to doctor

36

Chapter 6 Results and Discussion

Error Notification may not reach to the doctor due to undesirable circumstances

62 Results Discussion

Thus this project provides a tool to a person to keep track collect and share their present and

past Health information by means of PHR (Personal Health Record) Also it minimizes the

communication gap between Patient and Doctor by means of PHR regardless of their place or

time and thus contributing to overall enhancement of health care service for patient Further-

more it enhances Emergency Medical service by giving person a medium to notify nearest

emergency center immediately in case of an accident or emergency Moreover it helps emer-

gency team in providing emergency medical treatment by providing them with the PHR record

of the person who has to be given emergency treatment

Figure 61 List of PHR record represented as dates on which they are created

37


Figure 62 Form to create PHR record of Patient

Figure 63 Confirmation for patient whether send emergency notification or not

Figure 64 PHR report in form of pdf

38

Chapter 7

Project Time Line

71 Project Time Line Matrix

Figure 71 Time Line Matrix

39

72 Project Time Line Chart


Figure 72 Time Line Chart


40

Chapter 8

Task Distribution

81 Distribution of Workload

811 Scheduled Working Activities

Activity TimePeriod

Comment

Requirement Gathering 08 Days Requirement gathering tookplace through searching oninternet and taking the ideas

Planning 04 Days Planing has done by Reviewingof literature of IEEE papers andby taking the walkthrough

Design 04 Days Designing has done by creat-ing UML diagram By creatingCharts

Implementation 90 Days Implementation has done Firstcreating the backend and thenfront end module by module

Testing 10 Days Testing has done by perfomingunit testing alpha amp Beta Test-ing integrated testing and sys-tem testing

Deployment 05 Days Deployment has done by in-stalling project on the server

Table 81 Scheduled Working Activities

41


812 Members actvities or task

Member Activity TimePeriod

StartDate

EndDate

Comment

M1 RequirementGather-ing

4 Days 010115 040115 M1 has performed thesearching for project re-quirement on the internetby reviewing the relatedliterature and by analyzingthe related project whichis already available in themarket Regularly informto the other member ofteam

M1 Analyzingof therequire-ment

3 Days 050115 070115 M1 has done the require-ment analyzing of projectby sharing the ideas M1has also created the list ofrequirement

M1 Finalisingthe re-quire-ment

1 Day 080115 080115 M1 finalised the require-ment M1 also createda list of finalised require-ment

M1 Planning 4 Days 090115 120115 Planning has done bywalkthrough and byanalysing the availableproduct M1 created alist of function which willbe implemented in theproject Each and everymodule were discussed inevery group meeting andM1 created a blue print forproject

42

Chapter 8 Task Distribution

M1 FrontEnddesign

4 Days 130115 160115 M1 created the UMLdiagram for front endof the system and dataflow diagrams

M1 BackEnddesign

4 Days 130115 160115 M1 created the UMLdiagram for back endof the system and dataflow diagrams

M1 Installationof toolsandtech-nologyfor frontend

1 Days 170115 170115 M1 installed all the re-quired tools which isused for front end de-sign

M1 Installationof toolsandtechnol-ogy forback end

2 Days 170115 190115 M1 installed all the re-quire tools which isused for back end de-sign

M1 Implementationof GUI

4 Days 200115 240115 M1 creates the GUI ofthe project

M1 ImplementationofDatabase

20 Days 200115 100215 M1 implementedthe PHPMYADMINDatabase

ImplementationofServer

12 Days 200115 020215 implemented the PHPserver

M1 Databaseconnec-tivitywithAndroidApplica-tion

4 Days 020215 060215 M1 and makes theconnection amongDatabase and AndroidApplication

43


M1 Databaseconnec-tivity

4 Days 060215 100215 M1 and created thedatabase connectivity

GUIConnec-tivity

4 Days 110215 140215 and created the con-nectivity GUI withdatabase

M1 Integrationof allmodules

10 Days 160315 250315 M1 integrated all themodule Implementedwhole system properly

M1 Unittesting

2 Days 260315 280315 M1 performed the unittesting and noted downresults

M1 Integratedtesting

5 Days 260315 300315 M1 performed the inte-grated testing and noteddown results

M1 Deploymentacirc 30032015 acirc acirc

Table 82 Member Activities and Task

44

Chapter 9

Conclusion and Future Scope

91 Conclusion

Thus this project provides-

1 Provide a tool to a person to keep trackcollect and share their present and past Health infor-

mation by means of PHR (Personal Health Record)

2 Minimizing the communication gap between Patient and Doctor by means of PHR regardless

of their place or time and thus contributing to overall enhancement of health care service for

patient

3 Enhancing Emergency Medical service by giving person a medium to notify nearest emer-

gency center immediately in case of an accident or emergency

4 Helping Emergency team in providing emergency medical treatment by providing them with

the PHR record of the person who has to be given emergency treatment

92 Future Scope

In the future the actual implementation of the project will be done where all the modules will

be coded tested and deployed Further Additional functionality as per requirements will be

added

45

References

[1] Koufi V An Android-Enabled Mobile Framework for Ubiquitous Access to Cloud Emer-

gency Medical Services 95-101 2012 Dept of Digital Syst Univ of Piraeus Piraeus Greece

[2] Doukas C Mobile healthcare information management utilizing Cloud Computing and An-

droid OS 1037 - 1040 2010 Univ of the Aegean Samos Greece

[3] httpwwwmyphrcomStartaPHRwhatisaphraspx

[4] httpwwwemsgovwhatisemshtml

[5] NIDA Foundation httparchivesdrugabusegovNIDA-NotesNNVol16N5Conferencehtml

[6] Katherine Leonard httplonelybrandcomblogmobile-finance-users-a-demographic-breakdown-

for-insurance-and-banking-services

[7] Paul C Tang(MD MS) Joan S Ash(PhD) David WBates (MD) J Marc Overhage(MD

PhD) and Daniel ZSands (MD MPH) Personal Health RecordsDefinitions Benefits and

Strategies for Overcoming Barriers to Adoption Journal of the American Medical Informatics

Association JAMIA

[8] California Office of Privacy Protection (COPP) PHR fact sheet Is a Personal Health Record

Right for You httpwwwprivacycagovconsumerscis13englishpdf

[9] httpenwikipediaorgwikiPersonalhealthrecord 15 March 2015

46

Published Paper

1 Ravish Adil Kazi Prof Kalpana R Bodke PHR Based Health Care And Emergency Aid Sys-

tem Using Google Cloud Messaging International Journal of Advanced Research in Computer

ScienceMarch 2015

47

Research PaperPHR BASED HEALTH CARE AND EMERGENCY AID SYSTEM USING GOOGLE

CLOUDMESSAGING

Ravish Adil KaziBE Computer Engineering

AIKTC PanvelMumbaiIndia

ravish1kazigmailcom

Prof Kalpana BodkeAssistant Professor Computer Engineer


kalpananmehergmailcom

AbstractRecently there has been a remarkable upsurge in activity surrounding the adoption of Personal Health Records (PHRs) PHRs containglobal patient information and not certain pieces collected by individual healthcare providersThus they can be used as basic infrastructuresfor building and operating several important systems for healthcare system Emergency medical systems (EMS) are among the mostcrucial ones as they involve a variety of activities which are performed from the time of a call to an ambulance service till the time ofpatients discharge from the emergency department of a hospital and are closely interrelated so that collaboration and coordinationbecomes a vital issue for patients and for emergency healthcare service performance The integration of leading-edge technologies such ascloud-based services and mobile technology with Personal Health Records (PHRs) can prove important in emergency care delivery as itcan facilitate authorized access to comprehensive and unified health information The proposed EMS is accessible by Android-enabledmobile devices and incorporates a customized asynchronous notification feature whereby caregivers are notified on critical data updates ina way that efficient utilization of mobile device resources is achieved

Keywords Google Cloud Messaging Client Server Architecture Android Operating System Push Notification Database

I INTRODUCTION

PHR is abbreviated as Personal Health Record Forkeeping track and share past and current information aboutperson health or collect all PHR information this tool can beused[1] This concept of PHR Based Health Care Systemcan act as connecting bridge between patient and doctorwith no restriction of time and place In this System thepatient have its own PHR record and cannot update his PHRrecord and can also links hisher family doctor to PHRrecord When a Doctor updates PHR record the patient whohas linked PHR record will get automatic notification Thusdoctor get updates about recent condition of patient and canalso give suggestion to patient as required

Emergency Aid System more commonly known as EASis a system that provides emergency medical care [1] TheConcept of Emergency Aid System using PHR is thatSuppose an accident of person occurs who has a PHR recordheshe can immediately notify through hisher digital deviceabout accident to nearest registered hospital from thelocation where accident has took place The correspondinghospital will get notification about the accident whichcontains persons user id for PHR record Thus the hospitalpersonnel can get the persons health related information andlocation where accident has taken place in advance and thuscan do emergency treatment appropriately The project willbe implemented on android platform [2]

A Scope of Project

1 Provide a tool to a person to keep track collect and sharetheir present and past Health information by means of PHR(Personal Health Record) [3]

2 Minimizing the communication gap between Patient andDoctor by means of PHR regardless of their place or timeand thus contributing to overall enhancement of health careservice for patient3 Enhancing Emergency Medical service by giving person amedium to notify nearest emergency center immediately incase of an accident or emergency4 Helping Emergency team in providing emergencymedical treatment by providing them with the PHR recordof the person who has to be given emergency treatmentThus there will be an efficient communication betweenpatient and doctor by the medium of PHR and also PHR willbe used to improve emergency medical service

B Advantages over Current Health Care System

It makes dealing with your illness easier by helping youstay organized Never forget a doctor visit medication orcontact many number again Since it implements concept ofusing PHR in Emergency Aid System which can providesufficient past and present health information about theperson and also provide exact location where accident hastaken place to Emergency team Thus this model provide anefficient way for communication of health informationbetween patient and doctor Also there no online tool forbetter emergency aid service for the person This modelprovide an effective way for emergency aid system usingPHR[6]

II REVIEW OF LITERATURE

A Current Technology for PHR Based Health Care andEmergency Aid System and Their Drawback

Many tools available to maintain PHR such as Web basedservice tools like iHealthRecordorg [4] Care plan is tool forpatients with longer term illnesses like cancer heart diseasediabetes etc [4] Software based tools like Personal PortableElectronic Medical Records and ID Clade Health Trackeretc and Paper based tools such as MyPRO Medical-HealthRecords Organizer Jakoter Health Organizer etc But noneof them implements concept of using PHR as connectingbridge between patient and doctor with no restriction of timeand place That is Patient can share hisher healthinformation with his doctor due to which doctor can getregular update about patientrsquos health which can contribute tobetter Health care procedure There also many EmergencyAid System in Web based service or Software form such asAmbutrax Advance Dispatch Ambulance DispatchSoftware AmbuPad etc Since they doesnrsquot make use ofPHRT Thus Emergency team cannot use this information toprovide better emergency medical service to the person Thusthere are no online tool which can provide an efficientmedium to communicate with the doctor to provide each andevery current information about patient

B Correlation of emergency system and Android operatingsystem

Figure 1a represents increasing emergency incidents overyears It could be clearly seen that from the year 1994 there isa tremendous increase in the emergency incidents till nowand the figure 1b represents the use of android operatingsystem among users in the year 2014 The number of androidusers are more as compared to other platform users

Figure 1a - Hospital Emergency incidents[5]

Figure 1b - Android operating system preference amongUsers[6]

Thus it is clear that increasing emergency medical systemrequire a platform which should be popular among most ofthe usersSo use of android smart phones as a platform toserve for emergency medical system is quite feasible and willhelp improve emergency medical service

C User of the System

The user of this system can be broadly classified as-

1 Patient

2 Doctor

The Patient access the system to create or updatehisher PHR record and register or update hisher familydoctors name As soon As patient updates hisher PHRrecord the updated fields of PHR is notified to device ofpatients family doctor Thus PHR will become an effectivemedium for communication between patient and doctor Thepatient can also press an emergency button to sendemergency medical service team a notification regardingaccident of patient Thus a timely notification is send toemergency team and emergency team then can perform theemergency medical service efficiently

III PROPOSED SYSTEM ARCHITECTURE

As the project will be implemented on androidplatform the medium for user of system to interact with thesystem will be digital devices with android platform such assmartphones tablets etc Android is chosen as platform as itis popular and it is best suited as client device for thissystem architecture The server will be web server to whichAndroid clients connect through HTTP in order to sendrequest and receive responses along with data contents A

Figure 2System Architecturedatabase will be present behind web server which store allsystem relevant user information such as patients identityhealth details doctors identity etc Web server will providedata to clients where the data will be the data stored indatabase A client can also send data to other client in formof notification The notification will be send through webserver using Google Cloud Messaging

The explanation of the System Architecture as shown infigure 2 is as follows -

Step 1 - Patient informs to doctor his name using whichdoctor creates personal health record for patient

Step 2 - Personal health record created by doctor appears inthe list of Personal health records of patientNow Patient canattach test report as per advised by doctor in patient healthrecord

Step 3 - Doctor will be notified when patient attaches testreport to the Personal health record created by Doctorhimself

Step 4 - Doctor then can create new Personal health recordfor patient after getting test report along with Personalhealth record from patient which then again will be notifiedto patient and so on

The Doctor receives notification about the updated PHRrecord which is updated by patient through the system The

Doctor thus can get the current as well as past informationof the patient and also receive updates about any currentinformation about patients health Doctor can also send anysuggestion about any health related issue to patients towhich heshe is registered as family doctor

Ideally the PHR should include as much relevant data aspossible over the individuals lifetime from multiple sourcesincluding health care facilities as well as the individual Thespecific data source of each item should be labeled andvisible to the user The more comprehensive the datacontained in a PHR are the more useful the data will be topatients and care providers Although there are noconventions for what data should be contained in a PHRsymposium participants suggested that the items listed inTable 1 should be included in any PHR A number ofdifferent sources may furnish the data outlined in Table 1[7]

IV IMPLEMENTATION

Fig 3a shows home page of app in which user willprovided with two option either to select patient or doctor

Fig 3b shows different options provided to doctor afterlog in successfully from the home page given in Fig 3aThe options are -

1)Create PHR record of a Patient2)Update hisher personal details3)View the notification given by patient

Fig 3cshows different options provided to patient afterlog in successfully from the home page given in Fig 3aThe options are -

1)Send Emergency notification to doctor2)View hisher own PHR record3)Update personal details4)View Notification given by Doctor

Figure3aHome Page

Figure3bDoctorrsquos homePage

Figure 3c -PatientrsquosHome Page

A Working

Firstly the patient will tell his name to the Doctor then theDoctor will check his name in the Database If the name isalready present the Doctor will check the record of the patientand can update or create a new PHR of patient Else the doctorwill ask the information of the patient and generate a newPHR of the patient[8]

Now the patient will be notified by the applicationregarding the new PHR update or the suggestion made by theDoctor and will undergo the treatment as per suggested by theDoctorThe new PHR will be updated to the patient recordThe patient can be view his PHR record and can undergo thetest suggested by the Doctor After the patient has gonethrough all the test the patient will updatelinksubmit his testreport in the application software The

Doctor will get the notification of the same The Doctorthen can view all the test undergone by the patient and willgenerate the new PHR of the patient if required or will suggestthe medicines to the patientFigure 4 represents a sample PHR record generated

through the implemented android applicationThis PHR recordis in its digital form and is stored in pdf format

Figure 4 Pdf generated

V APPLICATIONS

PHRs grant patients access to a wide range of healthinformation sources best medical practices and healthknowledge All of an individualrsquos medical records are storedin one place instead of paper-based files in various doctorsrsquooffices Upon encountering a medical condition a patientrsquoshealth information is only a few clicks away [9] PHRs offerpatients the opportunity to submit their data to their cliniciansPHRs This helps clinicians make better treatment decisionsby providing more continuous data[7][10]In part PHRs represent a repository for patient data but

PHR systems can also include decision-support capabilitiesthat can assist patients in managing chronic conditions Mostconsumers and patients receive care from many health careproviders and consequently their health data are dispersedover many facilities

VI CONCLUSION

PHR provide a tool to a person to keep track collect andshare their present and past Health information It alsominimizes the communication gap between Patient andDoctor regardless of their place or time and thuscontributing to overall enhancement of health care servicefor patient

PHR also enhances Emergency Medical service by givingperson a medium to notify nearest emergency centerimmediately in case of an accident or emergency It alsohelps Emergency team in providing emergency medicaltreatment by providing them with the PHR record of theperson who has to be given emergency treatment

VII REFERENCES

[1] NHTSA EMS ldquoWhat Is EMSrdquohttpwwwemsgovwhatisemshtm March 2 2015

[2] Koufi V World Summit on the Information SocietyGeneva 2003-Tunis 2005

[3] Ahima Foundation ldquoWhat is a Personal Health Record(PHR)rdquohttpwwwmyphrcomStartaPHRwhat_is_a_phraspx 28 Feb 2015

[4] CarePlanrdquoGet Startedrdquo httpcareplancoMarch 152015

[5] rdquoNIDA FoundationrdquohttparchivesdrugabusegovNIDA_NotesNNVol16N5Conferencehtml

[6] Katherine Leonard httplonelybrandcomblogmobile-finance-users-a-demographic-breakdown-for-insurance-and-banking-services

[7] Paul C Tang(MD MS) Joan S Ash(PhD) David WBates (MD) J Marc Overhage(MD PhD) and Daniel ZSands (MD MPH) Personal Health RecordsDefinitions Benefits and Strategies for OvercomingBarriers to Adoption Journal of the American MedicalInformatics Association JAMIA

[8] California Office of Privacy Protection (COPP) PHRfact sheet ldquoIs a Personal Health Record Right for Yourdquohttpwwwprivacycagovconsumerscis13englishpdf

[9] httpenwikipediaorgwikiPersonal_health_record 15March 2015

[10] Accelerate Technologies rdquoPersonal health Recordsrdquohttpwwwserviceitcroenindustrieshealthcarepersonal-health-record-154 Sep 14

Appendix I

How to install our application in your system

To install our android application whose setup file which is also known as apk file which will

be stored in storage space in your android smart phonejust open that apk file then it shows you

a message whether to install or not if you click on install button than the application will be

installed on your device

Figure 91 Installation Of App

How to use the application

On opening the appthe first screen is home page which shows the option to user either to

select doctor or to select patient

48

Chapter 9 Conclusion and Future Scope

Figure 92 Home Page

On selecting doctor the user is forwarded to fill his or her personal details if heshe selects

doctor option then the user is forwarded to form page in which the user is given a form which

allows the user to fill hisher personal detailsotherwise if user visits more then one time than

he will be forwarded to home page for doctor Similarly for patient for first time visit user is

forwarded to personal detail form otherwise heshe will be forwarded to patient home page

On doctor home page there are three options - 1) Create Phr record 2) Update personal details

3) View Latest Notification by patient


In 1st option the doctor is given the option to create the PHR recordAfter selecting 1st

option doctor is guided to further three option - 1) View previous phr record of patient 2) View

PHR record of patient created by you 3) Create new PHR record

with 1st option doctor is forwarded to the list of previous phr record of patient shown by

49

92 Future Scope


dates with 2nd option doctor is forwarded to the list of phr record of patient created by doctor

himself shown by dates with 3rd option doctor is forwarded to a form where heshe can create

PHR record

Now by selecting above given rsquoupdate personal detailsrsquo option user can update hisher personal

details And by selecting rsquoView Latest Notification by patientrsquo option user can view latest noti-

fication given by patient

On patient home page there are four options - 1) Send Emergency Notification 2) View

PHR records 3) Update personal details 4) See notifications by doctor

In 1st option patient can send emergency notification to doctor who most recently created

hisher PHR record In 2nd option patient can view hisher PHR record In 3rd option patient

can update his her personal details In 4th option patient can view notification given by doctor

50



51

ACKNOWLEDGMENT

I would like to take the opportunity to express my sincere thanks to my guide Prof Kalpana R Bodke

Assistant Professor Department of Computer Engineering AIKTC School of Engineering Panvel for

her invaluable support and guidance throughout my project research work Without her kind guidance amp

support this was not possible

I am grateful to her for her timely feedback which helped me track and schedule the process effec-

tively Her time ideas and encouragement helped me complete my project efficiently

I would also like to thank Dr Abdul Razak Honnutagi AIKTC Panvel for his encouragement and for

providing an outstanding academic environment also for providing the adequate facilities

I am thankful to Prof Tabrez Khan HOD Department of Computer Engineering AIKTC School

of Engineering Panvel and all my BE teachers for providing advice and valuable guidance

I also extend my sincere thanks to all the faculty members and the non-teaching staff and friends for

their cooperation

Last but not the least I am thankful to all my family members whose constant support and encour-

agement in every aspect helped me to complete my project


11CO17

(Department of Computer Engineering)

University of Mumbai

52

CERTIFICATE


Anjuman-I-Islamrsquos Kalsekar Technical CampusKhanda GaonNew Panvel Navi Mumbai 410206

This is to certify that the project entitled ldquoPHR Based Health Care And Emergency AidSystem Using Google Cloud Messagingrdquo is a bonafide work of Kazi Ravish Adil Rashida(11CO17) submitted to the University of Mumbai in partial fulfillment of the requirement forthe award of the degree of ldquoBachelor of Engineeringrdquo in Department of Computer Engi-neering

Prof Kalpana Bodke Prof Tabrez Khan

SupervisorGuide Co-SupervisorGuide

Prof Tabrez Khan Dr Abdul Razak Honnutagi

Head of Department Director



Examiners

1 2

Supervisors1 2

Chairman

Declaration



Abstract







iv

Contents










v
















vi







References 46

References 47

Appendix I 48

Acknowledgment 52

vii

List of Figures





41 Home 142 Doctorrsquos Home Page 2143 Patientrsquos Home Page 2244 Patientrsquos personal Detail form 2245 Doctorrsquos personal Detail Form 2346 Pop up in doctorrsquos home page to enter patientrsquos name 2347 Optionrsquos for doctor to create or view Patientrsquos PHR record 2448 Software architecture Design 2449 sequence Diagram Scenario 1 25410 sequence Diagram Scenario 2 25411 Collaboration Diagram Scenario 1 26412 Collaboration Diagram Scenario 2 26413 Activity Diagram Scenario 1 27414 Activity Diagram Scenario 2 27415 State Diagram Scenario 1 28416 State Diagram Scenario 2 28417 ER Diagram 29418 Data Flow Diagram 1 30419 Data Flow Diagram 1 30


viii




ix

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52



Examiners

1 2

Supervisors1 2

Chairman

Declaration



Abstract







iv

Contents










v
















vi







References 46

References 47

Appendix I 48

Acknowledgment 52

vii

List of Figures







viii




ix

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Declaration



Abstract







iv

Contents










v
















vi







References 46

References 47

Appendix I 48

Acknowledgment 52

vii

List of Figures







viii



91 Installation Of App 4892 Home 993 Doctorrsquos Home Page 4994 Optionrsquos for doctor to create or view Patientrsquos PHR record 5095 Patientrsquos Home Page 51

ix

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Abstract







iv

Contents










v
















vi







References 46

References 47

Appendix I 48

Acknowledgment 52

vii

List of Figures







viii



91 Installation Of App 4892 Home Page 4993 Doctorrsquos Home Page 4994 Optionrsquos for doctor to create or view Patientrsquos PHR record 5095 Patientrsquos Home 1

ix

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Contents










v
















vi







References 46

References 47

Appendix I 48

Acknowledgment 52

vii

List of Figures







viii




ix

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52
















vi







References 46

References 47

Appendix I 48

Acknowledgment 52

vii

List of Figures







viii




ix

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52







References 46

References 47

Appendix I 48

Acknowledgment 52

vii

List of Figures







viii




ix

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

List of Figures







viii




ix

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52




ix

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

List of Tables


x












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52












xi

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Chapter 1

Project Overview

11 Introduction

111 Motivation














1





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52





























2


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


















data for itself


Doctor)

3












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52












4


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


















our project






result discussion







5

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Chapter 2




211 Description















6











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52











212 Pros


tion

213 Cons






221 Description



7




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52




















8


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


















natively by Android











data respectively

9


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


222 Pros


223 Cons







231 Description









vice




10




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52




















11























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52























applications

232 Pros


233 Cons


12







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52







241 Description









242 Pros



13


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


243 Cons






251 Description







14


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


























252 Pros


15


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


253 Cons























16




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52




17

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Chapter 3














18



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52



1) Apache server

2) Mysql database









19

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Chapter 4

Project Design

41 Design Approach














20



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52



Figure 41 Home Page


21

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

41 Design Approach



22




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52




23






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52






the Database



24







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52







25





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52





26





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52





27


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


424 State Diagram



28


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


43 Database Design

431 E-R Diagram


29

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

44 Work-flow Design

44 Work-flow Design

441 Flow Graph



30

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Chapter 5


















31













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52













requires













32



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52



required












1 Patient

2 Doctor













family doctor

33







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52







34


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


531 Usecase Report


35

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Chapter 6


61 Test Cases




















36













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52













37





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52





38

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Chapter 7

Project Time Line



39





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52





40

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Chapter 8

Task Distribution



Activity TimePeriod

Comment








41




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52




StartDate

EndDate

Comment








42


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


M1 FrontEnddesign


M1 BackEnddesign














43




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52




GUIConnec-tivity




M1 Unittesting






44

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Chapter 9


91 Conclusion






patient





92 Future Scope



added

45

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

References













Association JAMIA




46

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

Published Paper



ScienceMarch 2015

47


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


CLOUDMESSAGING



ravish1kazigmailcom






I INTRODUCTION



A Scope of Project















1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52









1 Patient

2 Doctor













IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52









IV IMPLEMENTATION






Figure3aHome Page



A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

A Working






V APPLICATIONS



VI CONCLUSION



VII REFERENCES











Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52



Appendix I










48


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52


Figure 92 Home Page













49

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

92 Future Scope




PHR record









50



51

ACKNOWLEDGMENT












their cooperation




11CO17



52



51

ACKNOWLEDGMENT












their cooperation




11CO17



52

ACKNOWLEDGMENT












their cooperation




11CO17



52

phr based health care and emergency aid system using ... · phr based health care and emergency aid...

Documents