1. Project Navel Applications Group 6 -Brian Baker -Conor Brady -Kevin Cawlfield -Brad Duncan

2. Background  Many medical appliances on the market today.  Most focus on just one area.  Very few provide good service for those in remote areas.  There is a need for a high quality all-in- one medical appliance that works well in the bush.

3. Project Navel Goals  Provide communication with doctors.  Allow for monitoring of patient data.  Allow patient to check diagnoses of various medical conditions.  Allow patient to check for reactions to poisons, drugs, etc.  Provide a “daily living database” that gives advice for a healthy lifestyle.

4. Application #1 – Communication  Communicate with doctor in an on- demand situation.  During diagnosis, if condition is critical, immediately contact a doctor.  Contact doctor in triage situation.

5. Application #2 – Data Monitoring  Monitor a patient in an on-demand situation and simultaneously check condition database.  Accumulate statistics for daily living database.  Monitor automatically during an emergency.

6. Application #3 – Diagnosis  Diagnosis starts upon command from user in either an on-demand or triage situation.  Instruments are monitored and readings are compared to diagnosis database in order of severity.  Serious Condition  Intermediate Condition  Mild Condition  Reaction  Doctor is contacted if necessary.

7. Diagnosis Database Contents  Vital Signs  Non-quantitative symptoms  Predicted Disease  Reactions  Action to be taken

8. Application #4 - Reactions  This feature is activated by the user in an on-demand situation.  Monitor instruments if necessary.  Depending on the severity and type of the reaction, inform a doctor.  Instructions on what to do if symptoms worsen.

9. Reaction Database Contents  Predicted disease  Severity  Necessity of calling a doctor  Suggested reaction

10. Application #5 – Daily Living  This serves the need of the user who goes for long periods of time in a remote area like a submarine.  Will contain non-emergency topics only, but if a serious condition is encountered, the diagnosis application will take over.  Focus on maintaining health and hygiene.

11. Daily Living Database Contents  Hygiene  Food/liquid intake  Sleep  Exercise  Cautionary procedures  Preventive measures

12. Basic Program Flow  At any time, the user may check the daily living database for advice on maintaining good health  When the user wants to check his/her health the progression is as follows:  Monitor Data  Check databases in following order:  Serious condition database  Intermediate condition database  Mild condition database  Reaction database  If necessary, contact a doctor

13. Application Architecture

14. User Data Gathering Serious Condition Database Intermediat e Condition Database Mild Condition Database Reaction Database Daily Living Database Call Doctor

15. Thank You Q&A