1 / 9

Healthcare Toolkit Architecture and User Interface

IE 546 – Project Progress Report 1. Healthcare Toolkit Architecture and User Interface. Objectives. Design the architecture for an integrator app: Accessing EMR Displaying EMR Sharing EMR with other applications. Research Literature. Works Cited.

gzifa
Download Presentation

Healthcare Toolkit Architecture and User Interface

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. IE 546 – Project Progress Report 1 Healthcare Toolkit Architecture and User Interface

  2. Objectives • Design the architecture for an integrator app: • Accessing EMR • Displaying EMR • Sharing EMR with other applications

  3. Research Literature

  4. Works Cited Boulos, M. N. K., Wheeler, S., Tavares, C., & Jones, R. (2011). How smartphones are changing the face of mobile and participatory healthcare: an overview, with example from eCAALYX. Biomedical Engineering OnLine. Retrieved from www.osulibrary.oregonstate.edu/ Doukas, C., Pliakas, T., & Maglogiannis, I. (2010). Mobile Healthcare Information Management utilizing Cloud Computing and Android OS. 32nd Annual International Conference of the IEEE EMBS. Retrieved from www.osulibrary.oregonstate.edu/ Hall, E. S., Vawdrey, D. K., Knutson, C. D., & Archibald, J. K. (2003). Enabling Remote Access to Personal Electronic Medical Records. IEEE Engineering in Medicine and Biology Magazine. Retrieved from www.osulibrary.oregonstate.edu/ Liu, C., Zhu, Q., Holroyd, J. A., & Seng, E. K. (2011). Status and trends of mobile-health applications. The Journal of Systems and Software 84. Retrieved from www.osulibrary.oregonstate.edu/ Nkosi, M. T., & Mekuria, S. M. (2010). Cloud Computing For Enhanced Mobile Health Applications. 2nd IEEE International Conference on Cloud Computing Technology and Science. Retrieved from www.osulibrary.oregonstate.edu/ Vieira-Marques, P. M., Cruz-Correia, R. J., Robles, S., Cucurull, J., Navarro, G., & Martí, R. (2006). Secure Integration of Distributed Medical Data Using Mobile Agents. IEEE Agents in Healthcare. Retrieved from www.osulibrary.oregonstate.edu/

  5. OCS – Appearance & Interface • Appearance: • Handheld Tablet Device w/multi-touch functionality (iPad, iPod, iPhone) • Interface: • Color scheme consistent with existing prototypes • Intuitive • Buttons, menu bars, clear labeling

  6. OCS – Use/Misuse • Use • Retrieve, navigate, share, enter data with minimal or no use of external apparatus. • Misuse • Privacy • Security

  7. OCS – Hardware/Software • Hardware • Mobile device: iPhone, iPad, android phones, or any other portable tablet • Software • Development of application: App Cooker, Vizi Apps, and html language • Protocols to link apps

  8. OCS - Users • Physicians and nurses • Skills: • Medical knowledge, basic understanding of mobile devices • Training: • How to interact, retrieve, add, and edit patient’s information via HT. • Confidentiality, privacy and security settings and guidelines

  9. OCS - Others • Time to retrieve information • Kind of sharing software to use • Use of tablet with medical supplies

More Related