1. Project-1 CSE 2102 Project 4   Organize Class in Teams of 3 with one Team of 2   Mutli-Pronged Approach  Modifications of Existing Screens  Addition of New Functionalities   Two Broad Focuses for Project 4  Update Prescription Screen with OpenEMR Integration and FDA Daily Meds Access  New Medication Reconciliation and Interaction Checking Screen and Algorithms

2. Project-2 CSE 2102 Introduce Categories of Meds OpenEMR MSHV

3. Project-3 CSE 2102 Revised Architecture

4. Project-4 CSE 2102 Design new Interactions Screen Use Current Web Version as Example

5. Project-5 CSE 2102 Learn and Use REST APIs   RxNorm names for clinical drugs linked to drug vocabularies used in pharmacies   RxTerms interface terminology derived from RxNorm for medication history recording   NDF-RT is a concept-oriented terminology  http://rxnav.nlm.nih.gov/RxNormAPIs.html# http://rxnav.nlm.nih.gov/RxNormAPIs.html#  http://rxnav.nlm.nih.gov/RxTermsAPIs.html# http://rxnav.nlm.nih.gov/RxTermsAPIs.html#  http://rxnav.nlm.nih.gov/NdfrtAPIs.html# http://rxnav.nlm.nih.gov/NdfrtAPIs.html#  FDA Daily Meds  http://dailymed.nlm.nih.gov/dailymed/help.cfm#w ebservices http://dailymed.nlm.nih.gov/dailymed/help.cfm#w ebservices

6. Project-6 CSE 2102 Proposed Component Organization   Develop Test Java Program with Client Classes that Gets you Familiar with Retrieving from all Four APIs  RxNorm, RxTerms, NDF-RT, FDA Daily Meds  Consider Following Decomposition of Project  One Teammate– Java Test/API Program  One Teammate- Mods to Current Med Screen  One Teammate- New Checking Interaction Screen  Teams of 3 (17) and one team of 2  Email Teams and NetIDs  Usage of Github  http://about.github.uconn.edu/ http://about.github.uconn.edu/  Need to Log on to have NetID Initialized  Add NetIDs for Solomon and sad02010

7. Project-7 CSE 2102 Project 4   Team Formation:  Email members Names, Emails, NetIDs   Revisions to Medication Screen:  Organize Drugs by MSHV and OpenEMR  OpenEMR are read-only - cannot be changed   Link from Med to FDA Daily Meds   New Medication Checking Screen: This can be  Combined list of meds (MSHV & OpenEMR)  Returns a list of meds and their interactions   Usage of External Web Services:  FDA Daily Meds, RxNorm, RxTerms, NDF-RT  Updated Doc: http://www.engr.uconn.edu/~steve/Cse2102/MSHVan dOpenEMRAccess.pdf http://www.engr.uconn.edu/~steve/Cse2102/MSHVan dOpenEMRAccess.pdf http://www.engr.uconn.edu/~steve/Cse2102/MSHVan dOpenEMRAccess.pdf

8. Project-8 CSE 2102 Semester Project  Personal Health Assistant (PHA)  Patient Version for Medication and Chronic Disease Management and Authorizing Providers  Identify Overmedication, adverse interactions, and adverse reactions  Provider Version for Viewing Patient Data that has been Authorized  Personal Health Record Microsoft HealthVault  A Person Can Track Medical Information  Used as Backend Repository to PHA  OpenEMR Standalone version for Providers  Seek to Integrate into PHA  Support Medication Reconciliation

9. Project-9 CSE 2102 Project 1  Install, Deploy, and Test all Involved SW Packages  Download/Install Eclipse 4.3/UML Designer  Download/Install Android SDK  Load/Build/Exevute PHA into Android SDK  Source Code on Uconn Filelocker  Resetting Android Version to 2.2.3 (Version 10)  Hello World Application – Familiarize w/Android  Microsoft Health Vault – create an Account  Download/Install OpenEMR  Be Patient – long install  Create yourself as Patient  Document via word file all of your progress  Email to Dr. Berhe by 12 midnight on September 4

10. Project-10 CSE 2102 Project 2 Initial Design  Design a Class Library using UML Designer/Eclipse  Classes for Chronic Diseases  Classes for Patient  Classes for Medications  Classes for Observations of Daily Living  Classes for Exercise, Diet and Nutrition  Use of Enumeration type  NO CODE – Just a UML Design  Prepare MS Word Design Document that contains:  Multiple UML Class Diagrams each Labeled as a Figure (Figure 1. caption., etc.)  Write a paragraph explaining each Diagram  Email to Dr. Berhe by 12 midnight on September 18

11. Project-11 CSE 2102 Project 2 Initial Design  Each UML Diagram should contain a set of Classes where each Class has:  Set of Protected Data (Attributes)  Set of Public Methods  Include Signature on Each Method (parameters and return type)  Why Protected?  Analyze the Requirements in order to Identify:  Commonalities to be Captured in Parent Class  Differences that are Pushed down to Child Class  Enumerations to Distinguish Between Data States  Email to Dr. Berhe by 12 midnight on September 18

12. Project-12 CSE 2102 Project 2 Final Program  Start from Design Solution for Project 2 Initial Design  Set of Classes  Attributes and Methods Define  No Code  Three Main Tasks: 1. Implementing class library solution 2. Developing screens and Navigating Among them 3. Staging data from screens to class library and back  Upload to HuskyCT by 12 midnight on October 9 th – to be Decided

13. Project-13 CSE 2102 Miscellaneous Declarations  Classes used by Other classes (inclusion)  Enumeration Types

14. Project-14 CSE 2102 Misc Class Declarations

15. Project-15 CSE 2102 Misc Class Declarations

16. Project-16 CSE 2102 TrackedItem Declarations  Tracks the Different  Conditions, ODLs, Meds that have or are being Tracked

17. Project-17 CSE 2102 TrackedItem Class Declarations

18. Project-18 CSE 2102 TrackPatientData Hierarchy  Bring Together all of the Concepts

19. Project-19 CSE 2102 TrackPatientData Class Declarations

20. Project-20 CSE 2102 Condition Class Declarations

21. Project-21 CSE 2102 ODLs and Medications Declarations

22. Project-22 CSE 2102 Person and Patient Declarations

23. Project-23 CSE 2102 Exercise Declarations

24. Project-24 CSE 2102 Instantiating the Classes

25. Project-25 CSE 2102 The Big Picture

26. Project-26 CSE 2102 Overview Screen

27. Project-27 CSE 2102 Emphasis for Project 2 Final Program   Designing and implementing new screens for Conditions and Exercise – Two Types  Create a new Condition/Exercise/ODL  Collect Patient Entered data on Condition/Exercise/ODL   Modifying, if necessary, the ODL and Medication screens that already exist   Hooking the current ODL and Medication screens so that information is stored in the new classes   Lots of Sample Screens for Conditions Given in the Rest of this Presentation

28. Project-28 CSE 2102Conditions/ODLs/Exercise  Create a new Condition/Exercise/ODL  Each New Condition/Exercise/ODL needs TrackedItems Entry  This is Part of Patient Class  Placed in TrackedItemsListMSHV  For Condition/Exercise/ODL  Collect Entered data on Condition/Exercise/ODL  Actual Data for a Condition/Exercise/ODL  E.g., Diabetes would have  Glucose Level  Carbs Eaten  Type of Fasting  Insulin Taken

29. Project-29 CSE 2102 PHA in Eclipse

30. Project-30 CSE 2102 History of Mobile Computing 2009

31. Project-31 CSE 2102 History of Mobile Computing – Aug 2013

32. Project-32 CSE 2102 History of Mobile Computing - Tablets

33. Project-33 CSE 2102 Observations of Daily Living  Observations of Daily Living and PHRs  Passive – Once Initiated, Collects Data  Accelerometer  Pedometer  Pill Bottle that Sends a Time Stamp Message (over Bluetooth?) to SmartPhone  Active – Patient Initiated  Providing Information via Smartphone on: –Diabetes (Glucose, Weight, Insulin) –Asthma (Peak Flow, use of Inhaler) –Heart Disease (Pulse, BP, Diet) –Pain, Functional status, Fatigue, etc.

34. Project-34 CSE 2102 Architecture Diagram

35. Project-35 CSE 2102 Diabetes Management

36. Project-36 CSE 2102 Overall Architecture

37. Project-37 CSE 2102 Current Architecture

38. Project-38 CSE 2102 Current Architecture

39. Project-39 CSE 2102 iOS PHA – Patient Version

40. Project-40 CSE 2102 iOS PHA – Patient Version

41. Project-41 CSE 2102 iOS PHA – Patient Version

42. Project-42 CSE 2102 iOS PHA – Provider Version

43. Project-43 CSE 2102 Android PHA Screenshots

44. Project-44 CSE 2102 Android PHA Screenshots

45. Project-45 CSE 2102 Android PHA Screenshots

46. Project-46 CSE 2102 HealthVault RESTful Exchange Service

47. Project-47 CSE 2102 HealthVault Class – JSON Mapping.

48. Project-48 CSE 2102 Prior Work - Blackberry Team  Ability to Track Information on ODLs and Prescriptions  Login Screen  Connection to Google Health  Health Screen to Track ODLs  Charting of ODLs over Time  Loading Scripts from Google Health  Prescription Alarms  Adam Siena, Kristopher Collins, William Fidrych

49. Project-49 CSE 2102 Screen Shots

50. Project-50 CSE 2102 Screen Shots

51. Project-51 CSE 2102 Screen Shots

52. Project-52 CSE 2102 Screen Shots

53. Project-53 CSE 2102 Screen Shots

54. Project-54 CSE 2102 Android Team  Similar Capabilities to Blackberry Project  Wellness Diary and Medication Alarm  Integration with Google Health  Much Improved ODL Screens  Male and Female Faces  Change “Face” Based on Value  Tracking Prescriptions and Alarms  Reports via. Google Charts  Ishmael Smyrnow, Kevin Morillo, James Redway

55. Project-55 CSE 2102 Screen Shots

56. Project-56 CSE 2102 Screen Shots

57. Project-57 CSE 2102 Screen Shots

58. Project-58 CSE 2102 Screen Shots

59. Project-59 CSE 2102 iPhone Team  Similar Capabilities to Blackberry Project  Tracking of Conditions, Medications, and Allergies  ODLs for:  Blood-Glucose, Peak-Flow, and Hypertension  Generation of Reports  Synchronization with Google Health  Brendan Heckman, Ryan McGivern, Matthew Fusaro

60. Project-60 CSE 2102 Screen Shots

61. Project-61 CSE 2102 Screen Shots

62. Project-62 CSE 2102 Screen Shots

63. Project-63 CSE 2102 Screen Shots