1 / 45

Individual Project Background

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

august-lester
Download Presentation

Individual Project Background

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. 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 • OpenEMRStandalone version for Providers • Seek to Integrate into PHA • Support Medication Reconciliation

  2. Four Code Repositories • Android PHA-Patient • iOS PHA-Patient • iOS PHA-Provider using Titanium/Javascript • Security Backend for PHA

  3. PHA Android Verison

  4. PHA Android Version

  5. PHA Android Version

  6. PHA Android Version

  7. PHA Android Version

  8. PHA Android Version

  9. PHA Android Overview Screen

  10. Introduced Categories of Meds OpenEMR MSHV

  11. PHA iOS Version

  12. PHA iOS Version

  13. PHA iOS Version

  14. PHA iOS Version

  15. PHA iOS Version

  16. Miscellaneous Declarations • Classes used by Other classes (inclusion) • Enumeration Types

  17. Misc Class Declarations

  18. Misc Class Declarations

  19. TrackedItem Declarations • Tracks the Different • Conditions, ODLs, Meds that have or are being Tracked

  20. TrackedItem Class Declarations

  21. TrackPatientData Hierarchy • Bring Together all of the Concepts

  22. TrackPatientData Class Declarations

  23. Condition Class Declarations

  24. ODLs and Medications Declarations

  25. Person and Patient Declarations

  26. Exercise Declarations

  27. Instantiating the Classes

  28. The Big Picture

  29. 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. Conditions/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. PHA in Eclipse

  32. 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. Revised Architecture

  34. Design new Interactions Screen Use Current Web Version as Example

  35. Use of REST APIs • RxNormnames for clinical drugs linked to drug vocabularies used in pharmacies • RxTermsinterface 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/RxTermsAPIs.html# • http://rxnav.nlm.nih.gov/NdfrtAPIs.html# • FDA Daily Meds • http://dailymed.nlm.nih.gov/dailymed/help.cfm#webservices

  36. 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. 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/MSHVandOpenEMRAccess.pdf

  38. 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. Architecture Diagram

  40. Diabetes Management

  41. Overall Architecture

  42. Current Architecture

  43. Current Architecture

  44. HealthVault RESTful Exchange Service

  45. HealthVault Class – JSON Mapping.

More Related