Table of Contents
Overview of Guideline and Personalization Deliverables
The above diagram depicts how findings from co-design become different articulations or renditions in different contexts. While the diagram may imply a linear progression from go design to guidelines or platform architecture, in reality all these parts are interconnected and inform each other.
The diagram does not portray other investigation and research activities in this project such as literature research, and conversations with subject matter experts.
Guideline model for inclusion in virtual healthcare
| Task | Schedule # | People | Status | Notes |
|---|---|---|---|---|
| Review of Canadian Virtual Healthcare guidelines | 2.1 | DONE | Review documentation: Review of Existing Relevant Virtual Health Guidelines and Practices | |
| Review of recommended practices | 2.2 | DONE | Analysis of the recommended practices can be read in Review of Existing Relevant Virtual Health Guidelines and Practices. | |
| Review of indirectly related guidance | 2.3 | DONE | Review of indirectly relevant guidelines can be found in Review of Existing Relevant Virtual Health Guidelines and Practices. | |
| Ongoing guideline model updates | 2.4 | ONGOING | Model for Inclusive Guidelines in Virtual Healthcare Revision of this model will be ongoing and refined as a result of co-design contributions. | |
| Ongoing guideline literature review | 2.4 | IN PROGRESS |
Report on the affected contexts and stakeholders in virtual healthcare gaps
Note: The original task was to establish a list of "vulnerable groups". Instead, the work will explore the contexts and functions where gaps exist and barriers arise that prevent people from engaging in their healthcare virtually.
| Task | Schedule # | People | Status | Notes |
|---|---|---|---|---|
| Draft lifecycle of virtual care deployment and stakeholders | 3.1 | Jon | ON HOLD | Through our meetings we have begun to identify actors and flows within virtual care deployment. A system diagram has not yet been developed. Virtual Care Systems Diagram Planning (3.1) To be completed once co-design is completed. |
Identify functions and contexts that create barriers and gaps | 3.2, 3.4 | Jon | ONGOING | See: |
| Consult with advocacy groups | 3.3 | Lisa, Caren | IN PROGRESS | To be incorporated into co-design process. |
| Draft report of barriers, gaps, and functions that exclude people from engaging in virtual healthcare | 3.5 | Jon | ONGOING | |
Ongoing updates to draft report | 3.6 | ONGOING | See: Functional Barriers to Access for Virtual Care |
Co-design virtual healthcare guidelines
| Task | Schedule # | People | Status | Notes |
|---|---|---|---|---|
| Recruit co-designers for guideline criteria | 4.1 | Lisa, Caren | IN PROGRESS | |
| Iteratively co-design guideline criteria | 4.2 | Lisa, Caren | IN PROGRESS | |
| Recruit co-designers not represented | 4.3 | Lisa, Caren, Jon | IN PROGRESS |
Co-design presentations of inclusive virtual healthcare guidelines
Co-design presentations of guidelines with guideline implementers (includes procurement language, evaluation tools, and contextualized criteria for vendors)
- Guidelines are only useful if they can be operationalized by the various stakeholders in the implementation. These stakeholders have diverse backgrounds and objectives. The guidelines will be presented from the viewpoint of the diverse stakeholders, including technical development, legal, policy, and assessment.
| Task | Schedule # | People | Status | Notes |
|---|---|---|---|---|
| Create draft guideline for vendor and procurement contexts | Jon, Justin, Vera | Aspects to cover:
Some of this can be started before co-designed criteria. For example there is already existing understanding of accessibility, procurement policies, standards, and regulations. | ||
| Recruit co-designers for evaluation of guideline presentations | 5.1 | Jon | ||
| Iteratively co-design evaluation of guideline presentations | 5.2 | Jon | ||
| Recruit co-designers not represented for guideline criteria evaluation | 5.3 | Jon |
Report on guidelines and guideline development process
| Task | Schedule # | People | Status | Notes |
|---|---|---|---|---|
| Engage with stakeholders review guidelines and presentations | 6.1 | Jon | ||
Refine guidelines and presentations based on reviews | 6.2 | Jon | ||
| Draft report on guidelines and process of development | 6.3 | Jon |
Use Cases for personalization in virtual healthcare
| Task | Schedule # | People | Status | Notes |
|---|---|---|---|---|
| Using list of barriers, gaps, and contexts, articulate personalization gaps and needed features for virtual healthcare | 7.1 | Jon, Justin | IN PROGRESS | See: Personalization in virtual healthcare tools |
| Draft personalization use cases | 7.2 | Jon, Justin | IN PROGRESS | See: Software Approaches for Expressing Personal Preferences for Healthcare and Personal Preferences Platform Architecture Overview |
Co-designed personalization artifacts and synthesis
| Task | Schedule # | People | Status | Notes |
|---|---|---|---|---|
| Recruit co-designers to explore personalization | 8.1 | Caren, Jon, Lisa | IN PROGRESS | |
| Conduct co-design on healthcare personalization | 8.2 | Caren, Jon, Lisa | IN PROGRESS | |
| Recruit co-designers not represented | 8.3 |
Personalization software integration and report
| Task | Schedule # | People | Start | End | Status | Notes |
|---|---|---|---|---|---|---|
| Integrate UIO into NRC bConnected web and mobile app | 9.1 | Justin | Feb 1 | Feb 28 |
| |
| Save preferences to centralized / accessible location for bConnected web app | 9.1 | Feb 22 | Mar 5 | probably in JSON | ||
| Create basic designs for UI Options personalization in bConnected web app | 9.1 | Jon | Mar 1 | Mar 26 | ||
Retrieve UIO preferences in bConnected mobile app | 9.1 | Mar 1 | Mar 12 | |||
Implement basic designs for responding to UI Options preferences in bConnected web and mobile apps | 9.1 | Justin | Mar 15 | Apr 30 | IN PROGRESS | Explore UIO in React. |
| Implementation of basic designs resulting from co-design | 9.1 | TBD | TBD | Additional preferences may be informed from co-design Round 2. | ||
| Document integration and extensibility process | 9.2 | |||||
Analyse and synthesize outcomes from co-design | 9.2 | Jon | Feb 15 | May 31 | ||
Create basic designs resulting from co-design that could be implemented within scope of project time and resources | 9.2 | Mar 15 | Apr 16 | Consider support for different medical health record formats and remote patient monitoring interoperability. | ||
Create an evolving resource that compiles the ideas, artifacts, and designs for personalization in virtual healthcare software. | 9.2 | Jon | Feb 15 | May 31 | Includes: Diagrams Scenarios of different implementations and their pros/cons Enough resources and guidance to help implementation later. | |
| Complete report on framework development and results | 9.3 |
Reporting
| Task | Schedule # | People | Start | End | Status | Notes |
|---|---|---|---|---|---|---|
Report on inclusive design approaches
| ||||||