Chapter 7 148 7.6.1 Future of the Inclusive eHealth Guide Looking to the future of the IeG, it will be important to address its long-term viability. Academic projects risk falling in disuse after their initial launch, losing relevance and interest over time. Therefore, for the future of the IeG, it will be crucial to focus on its dissemination. This dissemination could be targeted at forming strategic partnerships with organizations focused on eHealth design or low-SEP groups to utilize their networks, resources, and platforms to enhance visibility and impact. Moreover, future research should be dedicated to the IeG’s continual development, concentrating on incorporating both practical (e.g., lessons learned, examples) and theoretical (e.g., frameworks, mechanisms) insights from the field. This ensures the guide stays relevant and addresses the evolving challenges and opportunities within eHealth for people with a low SEP. Regular assessments and updates of the guide’s design and applicability will be vital to keep it user-friendly and relevant. The application cycle presented in this dissertation yields several recommendations for improving the guide’s design applicability. The first recommendation, predominantly arising from the evaluation with professionals in Chapter 4 and yet to be implemented, is establishing the IeG as a dynamic and evolving tool. Its impact can be enhanced when it is extensively circulated and actively employed. Professionals should, therefore, not only use the guide in their diverse projects but also share their experiences and context-specific challenges. To achieve this, the tool should ideally become a crowd-based platform, where users collaboratively edit and manage content. While this approach raises concerns about the information’s credibility, our findings do suggest that most of the required content is practical, such as examples, dos and don’ts, and lessons learned. This type of content may not need strict quality or credibility checks, making it better suited for such an open format. Another recommendation emerged from the application of the guide in Chapter 5. While the guide’s comprehensive nature is its strength, the many recommendations can be overwhelming. To address this, a section could be added that illustrates potential methodologies for applying the guide, such as those applied in Chapter 5. For example, it can be used to check inventory before starting a project or to review afterward what recommendations were and still need to be followed. By proposing these methodologies alongside the guide, we can provide professionals with inspiration that respects the diversity of their projects. A third improvement identified in Chapter 5 is the addition of a downloadable, coded table of recommendations to the guide, which professionals can use for planning, tracking, and retrospectively evaluating their projects. This tool could facilitate the usage of the guide in various project stages and aid communication among project members.
RkJQdWJsaXNoZXIy MTk4NDMw