1 / 22

Smart Mobile Health Monitoring System

ENGR 4901U – Software Engineering Systems II. Smart Mobile Health Monitoring System. Final Presentation. Prepared By: Travis Brown Andrew Nauth Jonathan Shida Prepared For: Dr. Kamran Sartipi. Date: 04/7/2012. vNurse. Team vNurse consists of Project Leader Travis Brown

kyoko
Download Presentation

Smart Mobile Health Monitoring System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ENGR 4901U – Software Engineering Systems II Smart Mobile Health Monitoring System Final Presentation Prepared By: Travis Brown Andrew Nauth Jonathan Shida Prepared For: Dr. Kamran Sartipi Date: 04/7/2012

  2. vNurse • Team vNurse consists of • Project Leader Travis Brown • Andrew Nauth • Jonathan Shida • Supervisor Dr. Kamran Sartipi • Instructor Dr. Vijay Sood

  3. Current Approach - Problems • Limited info • Redundant • Only added when visiting health care providers • Not widely accessible • Lack of patient-physician relationship

  4. New Approach: Personal Health Record (PHR) • Power in hands of patient • Personalized records • Extremely modifiable • Widely accessible • The future of health care

  5. vNurse – Project Overview

  6. Software Development Lifecycle Iterative Waterfall Model

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

  8. Design - Components 1) 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

  9. Component Diagram

  10. Activity Diagram

  11. Use Case Diagram

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

  13. Prototype Version 2 • UI translated to code • Scalability problems • Login system implemented • Back-end development initiated • Integration planning began

  14. Lessons Learned • Pursuit of new knowledge • PHP, Objective-C, JSON, Client-Server, SQL • Continuous design updating • Refining requirements • Design must be perfected

  15. Prototype Version 3 • Complete integration of components • Administrator role • Unique user IDs created • Task Manager Revamped

  16. 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

  17. Testing • UIAutomation in Code • Unit, integration, system • Issues: Cross-platform • Results

  18. Scenario • Dr. Chris Kyle

  19. 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)

  20. 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

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

More Related