Smart Mobile Health Monitoring System

Prepared By: Travis Brown

Andrew NauthJonathan Shida

Prepared For: Dr. Kamran Sartipi

Date: 04/7/2012

ENGR 4901U – Software Engineering Systems II

Final Presentation

vNurse

• Team vNurse consists of– Project Leader Travis Brown – Andrew Nauth– Jonathan Shida

• Supervisor Dr. Kamran Sartipi• Instructor Dr. Vijay Sood

Current Approach - Problems

• Limited info

• Redundant

• Only added when visiting health care

providers

• Not widely accessible

• Lack of patient-physician relationship

New Approach: Personal Health Record (PHR)

• Power in hands of patient

• Personalized records

• Extremely modifiable

• Widely accessible

• The future of health care

vNurse – Project Overview

Software Development Lifecycle

Iterative Waterfall Model

Languages/Tools Used

• Objective-C (programming language)• PHP (scripting language)• MySQL (database language)• JSON (parsing language)• UML (modeling language)• LaTeX (markup language)• Paradigm UML • Client-Server Architecture• Xcode IDE• Adobe Photoshop

Design - Components1) vNurse Application

– Patient View• Create account, edit profile, view tasks, view/delete messages and input health data

– Physician View• Create account, edit profile, edit patient list, send message, generate report

create/remove, schedule/unschedule, and edit, tasks

– Administrator View• Set physician policies for schedulable tasks

2) Web Server– Responsible for processing and forwarding tasks to patient– Responsible for retrieving and updating data from the PHR database

3) PHR Database– Responsible for storing personal health records of all patients as well as additional

information such as user ID, full name, DOB and physician-patient relationships

Component Diagram

Activity Diagram

Use Case Diagram

Prototype Version 1

• Vertical Prototype• Initial UI designed in Photoshop• Focus on overall feel and navigation• Basis for version 2

Prototype Version 2

• UI translated to code• Scalability problems• Login system implemented• Back-end development initiated• Integration planning began

Lessons Learned

• Pursuit of new knowledge– PHP, Objective-C, JSON, Client-Server, SQL

• Continuous design updating• Refining requirements• Design must be perfected

Prototype Version 3

• Complete integration of components

• Administrator role

• Unique user IDs created

• Task Manager Revamped

Admin Role

• Set policies to control what tasks physicians can schedule

• Manager of access control settings• Used to reflect the wide range of roles

physicians can fulfill

Testing

• UIAutomation in Code

• Unit, integration, system

• Issues: Cross-platform

• Results

Scenario

• Dr. Chris Kyle

Future Plans• Task Manager

– Types of tasks, specialized wizards

• Service Agent• Database

– Extended health data (fitness, diet, allergies, family history)

• Server– Remote Server (worldwide access)

• Security– Encryption, sensitive data, proxy server

• Additional Roles– Pharmacists

• GPS Integration• Revise Admin View

– Additional access control features (manage admins)

Service Agent Component

• Problems– Liability, autonomous, lack of expert knowledge

• Components– Task Layer• Task Schedule, Task Model, Task Knowledge, Task Data

– Service Agent• Inputs, Outputs, Task Queue, Knowledge, Business Rule

Engine, Task Manager

Conclusion

• Career Related Experience• Team Work• Importance of Documentation• Exposure to new concepts and health industry• Feeling of accomplishment