Requirements for a Flexible and Generic API Enabling Mobile Crowdsensing mHealth Applications

Presently, mHealth becomes increasingly important in supporting patients in their everyday life. For example, diabetes patients can monitor themselves by the use of their smartphones. On the other, clinicians as well as medical researchers try to exploit the advantages of mobile technology. More specifically, mHealth applications can gather data in everyday life and are able to easily collect sensor or context data (e.g., the current temperature). Compared to clinical trials, these advantages enable mHealth applications to gather more data in a rather short time. Besides, humans often behave atypically in a clinical environment and, hence, mHealth applications collect data in a setting that reflects the daily behavior more naturally. Hitherto, many technical solutions emerged to deal with such data collection settings. Mobile crowdsensing is one prominent example in this context. We utilize the latter technology in a multitude of large-scale projects to gather data of several chronic disorders. In the TrackYourTinnitus project, for example, we pursue the goal to reveal new medical insights to the tinnitus disorder. We learned in the realized projects that a sophisticated API must be provided to cope with the requirements of researchers from the medical domain. Notably, the API must be able to flexibly deal with requirement changes. The work at hand presents the elicited requirements and illustrate the pillars on which our flexible and generic API is built on. Although we identified that the maintenance of such an API is a challenging endeavor, new data evaluation opportunities arise that are promising in the context of chronic disorder management.