Designing eHealth that Matters via a Multidisciplinary Requirements Development Approach

Abstract

BackgroundRequirements development is a crucial part of eHealth design. It entails all the activities devoted to requirements identification, the communication of requirements to other developers, and their evaluation. Currently, a requirements development approach geared towards the specifics of the eHealth domain is lacking. This is likely to result in a mismatch between the developed technology and end user characteristics, physical surroundings, and the organizational context of use. It also makes it hard to judge the quality of eHealth design, since it makes it difficult to gear evaluations of eHealth to the main goals it is supposed to serve.ObjectiveIn order to facilitate the creation of eHealth that matters, we present a practical, multidisciplinary requirements development approach which is embedded in a holistic design approach for eHealth (the Center for eHealth Research roadmap) that incorporates both human-centered design and business modeling.MethodsOur requirements development approach consists of five phases. In the first, preparatory, phase the project team is composed and the overall goal(s) of the eHealth intervention are decided upon. Second, primary end users and other stakeholders are identified by means of audience segmentation techniques and our stakeholder identification method. Third, the designated context of use is mapped and end users are profiled by means of requirements elicitation methods (eg, interviews, focus groups, or observations). Fourth, stakeholder values and eHealth intervention requirements are distilled from data transcripts, which leads to phase five, in which requirements are communicated to other developers using a requirements notation template we developed specifically for the context of eHealth technologies.ResultsThe end result of our requirements development approach for eHealth interventions is a design document which includes functional and non-functional requirements, a list of stakeholder values, and end user profiles in the form of personas (fictitious end users, representative of a primary end user group).ConclusionsThe requirements development approach presented in this article enables eHealth developers to apply a systematic and multi-disciplinary approach towards the creation of requirements. The cooperation between health, engineering, and social sciences creates a situation in which a mismatch between design, end users, and the organizational context can be avoided. Furthermore, we suggest to evaluate eHealth on a feature-specific level in order to learn exactly why such a technology does or does not live up to its expectations.

Value-based design for the elderly: An application in the field of mobility aids

“…Where human-centered design is mainly "artefact-centered" and focused on identifying product features that are desired by (potential) end-users, value-based design aims to create useworthy design that caters for a person's values in life (Cockton, 2005). Values have been defined as "ideals or interests a (future) end user aspires to or has" (Van Velsen, Wentzel, & Van Gemert-Pijnen, 2013). For example, a value for parents can be that their children can grow up safely, and their actions in life will be motivated by this value.…”

Implementing antibiotic stewardship using eHealth and business modeling

“…Focus groups offer an opportunity to obtain insights regarding the experiences, observations, and opinions of group members [40]. As Prahalad and Ramaswamy [39] point out, to understand the individual experiences for cocreation, the problem analysis, inspired by action research, sense making [41], and previous research [42], should encompass a general discussion of the entire process, including individual tasks, information, and communication needs, as well as the problems experienced and bottlenecks.…”

“…Cross-border healthcare faces differences in healthcare systems and policies, subsequently differentiating the quality of care. A comparison between the Netherlands versus Nord-Rhein Westfalen showed that in 2010 the German region had 32-fold higher incidence of MRSA than the Netherlands [41]. This big difference was attributable to the Dutch Search-and-Destroy policy for MRSA whereas Germany did not have such a preventive screening policy [42].…”

“…It is possible to inspire business models from other industries for eHealth, for example, in 2000. Parente described four e-commerceinspired eHealth business models that were emerging at that time along with the growth of e-commerce generally [41]. E-commerce activities are probably easier to mimic from other industries than business models for health services and their complex value co-creation activities.…”

Smart tailoring of real-time physical activity coaching systems

“…This chapter will focus on office workers and their wish to combat a sedentary lifestyle. In accordance with the user-centered design philosophy (Van Velsen et al 2013) we will clarify the context of the work in the form of the following scenario.…”