| Literature DB >> 35526274 |
Rebecca Baines1, Hannah Bradwell1, Katie Edwards1, Sebastian Stevens1, Samantha Prime1, John Tredinnick-Rowe1, Miles Sibley2, Arunangsu Chatterjee1.
Abstract
INTRODUCTION: The importance of meaningfully involving patients and the public in digital health innovation is widely acknowledged, but often poorly understood. This review, therefore, sought to explore how patients and the public are involved in digital health innovation and to identify factors that support and inhibit meaningful patient and public involvement (PPI) in digital health innovation, implementation and evaluation.Entities:
Keywords: codesign; digital health; digital innovation; ehealth; patient and public involvement; systematic review
Mesh:
Year: 2022 PMID: 35526274 PMCID: PMC9327849 DOI: 10.1111/hex.13506
Source DB: PubMed Journal: Health Expect ISSN: 1369-6513 Impact factor: 3.318
Search terms
| S | ehealth or ‘e health’ or e‐health OR ‘digital health*’ OR mHealth OR m‐health OR Telemedicine OR Telehealth OR telecare OR ‘mobile app*’ OR ‘web‐based intervention*’ ‘web based intervention*’ OR ‘internet‐based intervention*’ OR ‘internet based intervention*’ OR ‘wearable*’ OR ‘social robotic*’ OR ‘smart speakers’ OR ‘virtual reality’ OR ‘VR” or ‘augmented reality’ OR ‘AR’ AND design OR evaluation OR implementation OR innovation |
| P | consumer* OR patient* OR client* OR citizen* OR carer* OR user* OR ‘end user’ OR stakeholder* OR public* OR communit* OR service‐user* OR ‘service user*’ |
| I | involve* OR ‘co‐produc*’ OR coproduc* OR ‘co‐design*’ OR codesign* OR participat* OR engage* OR collaborat* OR ‘experience based design’ OR ‘experience based co‐design’ OR ‘experience based codesign’ OR ‘user‐led’ OR co‐creat* OR cocreat* OR ‘user centered’ OR ‘user centred’ |
| C | N/A |
| E | N/A |
Figure 1Preferred Reporting Items for Systematic Reviews and Meta‐Analysis diagram
Identified barriers and their implications for meaningful PPI in digital health innovation, implementation and evaluation
| Barrier | Implication |
|---|---|
| Time and resource intensive | Influencing how, when, with who and how often PPI in digital innovation occurs |
| Not always a priority | Meaning limited time, resources and recognition are directed towards meaningful involvement |
| Not involved early on | Meaning important design and evaluation decisions including evaluation assessments/criteria are made without patient involvement, jeopardizing product relevance and acceptability |
| Competing/unaligned timelines | Meaning time for meaningful involvement is not always possible, or as frequent as developers and communities would like |
| Prolonged design process | Meaning possible delays to market launch, but possible prevention of resource expenditure further down the line |
| Limited direct contact between developers and patients | Leading to a possible disconnect, meaning decisions made do not always reflect patient requirements, undermining product success and sustainability |
| Lack of flexibility and open‐mindedness | Limiting the involvement and incorporation of patient insights |
| Balancing competing demands and priorities | Leading to potential delays or disengagement if patients do not feel listened to and heard |
| Use of ineffective methods | Meaning methods used to support innovation design and/or evaluation are ineffective or inappropriate for meaningful PPI, with some suggestions that existing methods are often ‘developer‐focused’ as opposed to ‘patient‐centred’ |
| Extensive exclusion criteria | Often means that design decisions and evaluations are based on an intentionally, often healthy, selected proportion of the total target population. People affected by mental health, individuals with limited literacy levels, low levels of education or smartphone ownership appear to be disproportionately affected |
| Limited interoperability or IT governance systems | This can prevent involvement opportunities and lead to a potential biasing of innovation and evaluation responses/decisions |
| Recruiting a ‘sizable’ and representative sample | This can be hard, particularly when working with individuals from ‘seldom‐heard’ communities, but is often considered essential in ensuring product relevance, cultural sensitivity and acceptance. Patient confidentiality can also make it difficult for developers to recruit from active patient lists |
| Maintaining interest and preventing dropout rates | This can be challenging, particularly when working with ‘oversaturated’ or fatigued communities, or people likely to experience deteriorating health such as when working with people with dementia. However, maintaining levels of interest is considered essential for maintaining continuity and reducing possible bias |
| Discussing sensitive/personal topics in group settings and unequal opportunities to take part in group sessions | This can prevent equitable and authentic involvement, with some patients withholding information that may be integral to innovation design, implementation and/or evaluation. The presence of carers and/or parents was also felt to prevent some people from being honest in their responses |
| Data privacy, security and trust | Failure to establish trust and provided assurances of data privacy and security can affect people's willingness to be involved and inhibit product acceptance |
| Bias | A number of biases can be introduced into PPI initiatives including the setting in which PPI activities are undertaken, recruitment methods, for example, primarily all online, preventing involvement from those considered to be digitally excluded, volunteer bias (people who opt in or take part in research/innovation may have greater interests/motivations and may therefore present the perspective of early adopters only), sharing existing digital innovations/ideas before data collection inducing possible response bias, previous involvement in digital innovation creation when evaluating the product leading to possible social desirability bias, exclusion from data analysis and shortened evaluation times that may present an overinflated experience |
| Practical difficulties including reimbursement, identifying times when everyone is free, not recording involvement sessions, not articulating why it may be beneficial to get involved, not considering the cost of downloading required content, for example, data charges, and sharing incorrect contact information | This can significantly hinder PPI activities and experience and collection of meaningful insights |
Abbreviation: PPI, patient and public involvement.
Suggested enablers to support meaningful PPI in digital health innovation, implementation and evaluation
| Suggested enablers | Supporting quotes |
|---|---|
| Commit to sharing power, working in equal partnerships that treat insights equally, irrespective of their source | Specifically ‘better balancing the power relations that exist’ |
| Involve patients early on | ‘Findings from this study confirm the importance of including PPI at the early design stage of medical devices’. |
| Work in an interactive, open‐minded and adaptive manner | ‘The whole process required flexibility, an open mind, and a willingness to revise material iteratively’. |
| Work to establish trust | ‘It was critical to ensure timely and consistent follow‐up in response to any technical or personal issues that are reported by the participants. This is an important part of building participants' trust in the intervention and the staff. Trust of the programme and trust of outreach workers was a priority issue, which needed to be addressed during all aspects of the programme roll‐out. It was helpful to brand the Mobile Link programme and have Cambodian government buy‐in so that women know that the programme they are signing up for is medically accurate and trustworthy’. |
| Be sensitive to people's spiritual, religious and cultural beliefs/values | Considering peoples ‘spiritual, religious and families values when designing digital health innovations’ |
| Create engaging activities | ‘It is important to ensure that the methods and user activities fully engage the participants’ |
| Communicate clearly, regularly and inclusively in an age‐appropriate and developmentally appropriate way, including the perceived benefits of taking part | ‘A developmental or age‐appropriate approach is needed regarding the content and design of a programme, and accounting for the range of interests and tastes’. |
| Offer people involved a choice of communication methods | For example, ‘WhatsApp was a significant production asset, useful in soliciting feedback from community members who did not regularly use email and did not feel comfortable editing scripts using Google Drive’. |
| Clarify people's roles, decision‐making processes and manage expectations | Creating a ‘memorandum of understanding’ |
| Provide clear instructions, tech support and relevant device access | ‘The elderly can be insecure because they are afraid of doing something wrong, so giving clear directions and affirmation is important. They also often need repeated explanations and daily training or courses in learning how to use a tablet for instance’. |
| ‘Members of the research team set up patients' phones and supported them throughout the study. Phones with the app pre‐loaded were available on loan for people without an Android phone’ (84). | |
| ‘Provide a hotline in case of technical difficulties’ (85). | |
| Allow time for people to become familiar with the tech | ‘Given access for a minimum of 2 months to allow sufficient time to work through the programme’. |
| Work with local organizations to facilitate recruitment | ‘One of the core principles of patient participation relates to ensuring that engagement is made as easy, feasible and as flexible as possible… With these goals in mind, it was deemed that participant recruitment through a familiar agency… would be optimal’. |
| Acknowledge people's time | Articles described a range of ways to acknowledge peoples time including prize draws, certificates of attendance/achievement, education credit, gift cards (ranging from $5–$100 depending on time spent and level of activity), shopping vouchers and grocery cards. |
| Encourage developers and patients to work together in the same room | ‘We also recommend organizing meetings between developers and users, like test sessions during which the developers would be present to see for themselves the ways in which end‐users actually use the technology. Another option would be to use video in order to show developers the reactions of the end‐users when interacting with the devices and application’. |
| Create a safe space for people to share their thoughts and ideas | ‘We put the primary focus on ensuring all stakeholders felt a part of the process and opened up about their experiences without feeling judged. During all phases, we highlighted the importance of anonymity for this purpose and thus did not collect the demographic information of the participants’ (87); ‘Each session took place at a convenient venue (e.g., community clinic) on weeknights, ranged from 90 to 120 min, and was audio recorded. Before each session, participants shared a meal and informally discussed community health and events. All meetings began with an opening prayer by church leadership to set an atmosphere of creativeness, inspiration, and togetherness among the attendees’ (88). |
| Hold activities in suitable locations | ‘Interviews were held either at Cardiff University or a location convenient for the participant (e.g., home and school). During the interviews, young people stated they were able to discuss the programme openly and appreciated that they could choose the location, and whether they were seen with their parents or carers’. |
| Provide people with a choice of how and who they would like to be involved | ‘Young people were asked whether they would like to be interviewed alone or with a parent or carer. The parent or carer was also asked whether they would like to be interviewed separately’. |