1. Project-1 CSE 2102 Individual Project Background  What is 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

2. Project-2 CSE 2102 Four Code Repositories  Android PHA-Patient  iOS PHA-Patient  iOS PHA-Provider using Titanium/Javascript  Security Backend for PHA

3. Project-3 CSE 2102 PHA Android Verison

4. Project-4 CSE 2102 PHA Android Version

5. Project-5 CSE 2102 PHA Android Version

6. Project-6 CSE 2102 PHA Android Version

7. Project-7 CSE 2102 PHA Android Version

8. Project-8 CSE 2102 PHA Android Version

9. Project-9 CSE 2102 PHA Android Overview Screen

10. Project-10 CSE 2102 Introduced Categories of Meds OpenEMR MSHV

11. Project-11 CSE 2102 PHA iOS Version

12. Project-12 CSE 2102 PHA iOS Version

13. Project-13 CSE 2102 PHA iOS Version

14. Project-14 CSE 2102 PHA iOS Version

15. Project-15 CSE 2102 PHA iOS Version

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

17. Project-17 CSE 2102 Misc Class Declarations

18. Project-18 CSE 2102 Misc Class Declarations

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

20. Project-20 CSE 2102 TrackedItem Class Declarations

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

22. Project-22 CSE 2102 TrackPatientData Class Declarations

23. Project-23 CSE 2102 Condition Class Declarations

24. Project-24 CSE 2102 ODLs and Medications Declarations

25. Project-25 CSE 2102 Person and Patient Declarations

26. Project-26 CSE 2102 Exercise Declarations

27. Project-27 CSE 2102 Instantiating the Classes

28. Project-28 CSE 2102 The Big Picture

29. Project-29 CSE 2102 Other Capabilities   Two Types of ODLs  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

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

31. Project-31 CSE 2102 PHA in Eclipse

32. Project-32 CSE 2102 Additional Functionality   Two Broad Focuses for  Update Prescription Screen with OpenEMR Integration and FDA Daily Meds Access  New Medication Reconciliation and Interaction Checking Screen and Algorithms

33. Project-33 CSE 2102 Revised Architecture

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

35. Project-35 CSE 2102 Use of 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

36. Project-36 CSE 2102 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  Java Test/API Program for Interaction Checking  Mods to Current Med Screen  New Checking Interaction Screen

37. Project-37 CSE 2102 Final Capabilities   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

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

39. Project-39 CSE 2102 Architecture Diagram

40. Project-40 CSE 2102 Diabetes Management

41. Project-41 CSE 2102 Overall Architecture

42. Project-42 CSE 2102 Current Architecture

43. Project-43 CSE 2102 Current Architecture

44. Project-44 CSE 2102 HealthVault RESTful Exchange Service

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