Pain Diary : Pain Management Platform

University essay from Uppsala universitet/Institutionen för informationsteknologi

Author: Antonio Bustamante Mirayo; [2012]

Keywords: ;

Abstract:

In the context of current human diseases and conditions, chronic pain is among the most typical reasons for seeking medical attention and is seen in 20 to 50 percent of patients attending primary care (Bajwa Z. H., 2012). With those figures in hand, the medical specialty of pain is of increasing interest to the scientific community and other parties involved in the management of chronic diseases. In the practical sense, chronic pain patients usually have, as of now, regular check-up appointments with their pain specialist, where medication is modified or maintained depending on the frequency and intensity of the patient’s pain episodes. As a matter of fact, between appointments, patients are usually encouraged to write a comprehensive account of their pain episodes and their characteristics in the form of a pain diary. In such diary, they write the intensity of their pain in a relative scale from 1 to 10, the location of the pain in their body, and other relevant comments, namely medication side-effects or the activity they were performing when pain appeared. This set of data is then used by pain specialists to calibrate the patient’s medication and follow their treatment. Pain Diary, the project developed and described in the present document, seeks a more flexible, precise approach for patients to record their pain diaries. The project emphasizes on the interaction between the patient and an electronic pain diary, in the form of an application for the iOS platform. This document discusses the human-computer interaction analysis, usability tests, accessibility tests, and prototypes created to develop a comprehensive user-oriented  solution for patients of cancer and other chronic diseases. Finally, the paper will present a functional prototype  created for iOS, taking into account UX (user experience) design and interaction, as well as a RESTful back-end to consider in a future large scale implementation of the project.

  AT THIS PAGE YOU CAN DOWNLOAD THE WHOLE ESSAY. (follow the link to the next page)