1. MOUNTAIN MEDIC Team Out Cold Final Presentation 2013

2. The Problem, in a Nutshell: People play sports People fall down People have problems getting back up People need to be evaluated to obtain medical attention Evaluation takes time and effort, and is inefficient to document Less time documenting injuries means more time caring for patients

3. (Re)Introducing Mountain Medic Improve patient processing process at Hunt Hollow Provide a highly usable way to record incidents Access data to prevent incidents from occurring Lessen exposure to red tape Guide patient interview process for injuries

4. DEMO

5. Solution Set Tablet app prompts users to ask the right questions Analytics allow patrollers to find unsafe locations or activities Forms are auto- generated to save time Body exam makes it easy to record wounds

6. Form Printouts Auto-generate forms using MS Access Sponsors can add, edit forms later without heavy technical knowledge

7. Body Exam Before Mountain Medic: Injuries were described textually Potential mix-ups based on details in description (where is ‘upper arm’? etc.) Now: Draw injuries on a body Replace text with images Speak scenarios instead of typing Caretaker is reminded to ask questions based on injuries indicated

8. Measurements Tablet makes it easy to record patient data Records vitals, demographic information, etc. Percent indicators remind patrollers to ask all questions

9. Excel Analytics Performing analysis and creating charts is super easy Numbers are also freely available for further analysis

10. Backups Previously: forms are kept but physical backups are difficult New system can export in several different ways Forms can now be kept or they can be electronically backed up

11. Execution

12. Why? Android has a low cost of entry and is easy to deploy Java/Android matched member skillsets Utilizing Office saved weeks of development time MySQL was a mature option that members had used before

13. The System

14. What Went Well? Lots of process and progress in the winter Android tablets were cheap and allowed everyone to develop Process methodology was great for the project High levels of sponsor support Team gelled well

15. What Didn’t Go Well? Some loss of focus in the spring Poor estimates on feature work meant some delays occurred Testing Not enough time for stylistic improvements Mixed stack caused compatibility/configuration issues

16. Current Status Tablet app is feature-complete Excel and Access display data well Server in progress – suffered due to poor estimates

17. Next Steps Pass off to Hunt Hollow Potential maintenance by local team member Future Senior Project?

18. QUESTIONS?