Project Name: OMRA (Online Medical Record Application) Group Name: The Innovators

1. Project Name: OMRA (Online Medical Record Application) Group Name: The Innovators Members: Purdey Law, AnalisaCorbo, Nicholas Lobo, Kevin Carey, Daniel Nguyen, & John Carlo Sampang Class: CCT380 - Human Computer Interaction Date: Friday November 25, 2011

2. Introduction • Our application allows patients and doctors to access online digital medical records • This system is designed to benefit health care specialists and administration by allowing them to organize and manage their files more efficiently.

3. Methodology • Brainstorm/Conceptualization • Information Management System / Data Input System • Hardware Specifications • Tablet, Mobile, Terminals • Prototyping • Functionalities

4. Design: Functional Requirements • Hardware requirements • enterprise-scale data such as electronic medical information • system infrastructure must be highly scalable • lightweight footprint • extensibility. • Software Requirements: • Touch-based interface, • ease of use, • lightweight and portable, • rapid search and rapid sort. • Data and Information Requirements: • Digitization of physical documents, • Conversion from a scan/image to a manipulable text format, • Decomposition of document into fields, • Standardized schema for compatibility of databases • Internal and External Interface requirements • VPN protocol-enabled Local Area Network (LAN) • Secure HTTP (HTTPS)

5. Design: Non-Functional Requirements • System capacity and response • Highly Scalable • On demand virtual resource allocation to accommodate peak • Security • Fault-tolerance • Database technologies and sources • Current database implementation: Oracle • Future database support: IBM DB2 • Zero-downtime data center

6. Design Prototyping: Patient Prototyping: • Sign In (Swipe) • Sign In (Manual) • Input Condition (Text or Touch) • Appointment Options (Non-ER) • Calendar Selection (Non-ER) • Create Appointment (Non-ER) Doctor Prototyping: • Display Patient Information • Display Medical History • Display Medical Encounters • Display Orders & Prescriptions • Display Progress Notes • Display Patient Test Results • Display Other Information

7. Design: Usability testing • Jakob Nielsen’s 10 Usability Heuristics • Visibility of system status • Match between system and the real world • User control and freedom • Consistency and standards • Error prevention • Recognition rather than recall • Flexibility and efficiency of use • Aesthetic and minimalist design • Help users recognize, diagnose, and recover from errors • Help and documentation

8. Limitations Existing EMR Problems: • Digitization of existing medical records • No universal EMR system implemented • Security and Privacy concerns (Hackers gaining confidential information) Combining Scenarios/Storyboards: • ER (Non-Fatal) • Non-ER (Appointment Options) • Doctor's View

9. Conclusion • The general idea is to create a device that can make the ER service more convenient and processed at a much faster pace. • The prototype meets these requirements successfully as it digitally stores patient’s records and allows for easy access for the users. • The prototype is designed to have functions where doctors and patients can access it for their own individual uses. • e-Health care system is made to improve to process much quicker and more efficiently.

10. Future work

11. Future work (cont’d) • Sub-phase 1 "Selling the Concept“ • Sub-phase 2 "Minimum Viable Product“ • Sub-phase 3 "Medical Prescription” • Sub-phase 4 "Illness Information Engine” • Sub-phase 5 "Illness Analysis and Suggestion Engine” • Requirements for future work: • Patient medical must be digitized • Stored in relational databases • Agreements must be made by hospital institutions • Hardware must be provided • Features in consideration: • Analysis of photo of injury instead of requiring user input in the ER.