# Roadmap

## **Roadmap & Upcoming Releases**

### **High-Level Product Roadmap**

We build our product roadmap using the "Now, Next, Future" framework to drive our product focus and vision for the future. The below provides our high level roadmap and is no inclusive of all new product enhancements, bug fixes, and feature sets that we will introduce in the next versions. For information on our full product prioritization process, see our [Prioritization Framework](#prioritization-framework) below.

{% tabs %}
{% tab title="Now" %}

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Ability to import the country geographic data</strong></td><td>Automated the previously time-consuming process of loading district, county, and sub-county details into SPICE, enabling bulk uploads of geospatial data via the admin portal.</td><td></td></tr><tr><td><p><strong>CHW Performance Monitoring</strong><br></p><p>Peer supervisors can monitor community health workers' performance by viewing daily metrics, including the number of assessments, follow-up visits, and calls completed.</p></td><td></td><td></td></tr><tr><td><strong>AI Model to predict patient retention</strong></td><td>We are building a patient retention model to identify patients that are likely to be lost to follow-up and design interventions within SPICE to engage these patients before they churn.</td><td></td></tr></tbody></table>
{% endtab %}

{% tab title="Next " %}

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>New Clinical Workflows for CHW:</strong></td><td><p>We will expand the platform to the following clinical areas:</p><ul><li>NCD</li><li>TB and HIV</li><li>Family Planning</li><li>Community-Based Surveillance</li></ul></td><td></td></tr><tr><td><strong>New Medical Review Workflows</strong></td><td><p>We will expand the platform to the following clinical areas:</p><ul><li>Immunizations</li><li>TB and HIV</li><li>NCD</li><li>Family Planning</li></ul></td><td></td></tr><tr><td><strong>Distance and Directions to Patient Location</strong></td><td>Future integration with Google Maps to display distance and directions to patients' households.</td><td></td></tr><tr><td><strong>Displaying CHW Activity through Geo-tagging</strong></td><td>Use latitude and longitude data from activities (e.g., assessments, follow-ups) to visualize movement patterns of community health workers.</td><td></td></tr><tr><td><strong>LLMs for Community Health Workers (CHWs)</strong></td><td>We are exploring the use of LLMs to aid CHWs in performing their duties; ideas range from a ChatBot with job aid information to personalized education information</td><td></td></tr></tbody></table>
{% endtab %}

{% tab title="Future" %}

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Workflow Builder - Add new workflow with Clinical decision support (CDSS)</strong></td><td>Clinical Authors and Implementor will be able to add new workflows in SPICE with country specific guidelines.</td><td></td></tr><tr><td><strong>Patient Application within SPICE</strong></td><td><ul><li>Access to the patient longitudinal journey</li><li>Upload assessments</li><li>Medication adherence nudges</li><li>Appointment reminders</li></ul></td><td></td></tr><tr><td><strong>Insights Generation</strong></td><td>Analytics module to generate user-specific insights<br></td><td></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

### **Upcoming 2.0 Release - Coming September 2024**

Our next major open source release will be SPICE 2.0. We are building SPICE 2.0 to be the next generation primary care platform; re-imagining primary care to be data-driven and outcomes focused.

The SPICE 2.0 release will support the following features:

* Algorithm-driven disease pathways for NCDs, TB, Malaria, HIV, ANC, PNC, child health, and immunization
* Closed loop, risk-based follow-up at community and facility levels
* Advanced admin portal features
* Customized dashboards for community & facility performance
* Real-time outcomes tracking by disease area
* FHIR Hybrid Architecture

<figure><img src="https://1478837505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc8r5CWDYQD5YGrlFur8R%2Fuploads%2Fgit-blob-3faa7ceb735f707e5026428d9eaa77a12a32dfc4%2F2%20(1).png?alt=media" alt=""><figcaption><p>SPICE 2.0 Features</p></figcaption></figure>

## New Feature Requests & Prioritization

### **Submitting Feature Requests**

To submit a new feature request, raise an issue in GitHub in the specific project (Android, Admin Web, Server, FHIR Adapter). To best prioritize the feature requests, we need to understand the why, what, and how of the requests coming from the end users.

**Follow the steps below to submit a new feature request:**

1. Add a descriptive Title summarizing the feature
2. Describe the feature with as much detail as possible in the Description field. Include the following details:
   1. Problem Statement
   2. Priority (Highest, High, Medium, Low)
   3. Impacted Users
   4. Impacted Workflows
3. Tag the issue as a "enhancement" using the labels
4. If possible, attach any images to further explain the feature request (screenshots are very helpful!)

### **Prioritization Process**

Medtronic LABS will review all feature requests and issues submitted through the formal channel. In order to prioritize the issues and features, we follow the below process to prioritize new feature requests, enhancements, and bug fixes/issues.

#### Prioritizing Framework: MoSCoW: Must Have, Should Have, Could Have, Won't Have

<table data-header-hidden><thead><tr><th width="212"></th><th></th></tr></thead><tbody><tr><td><strong>Must Have</strong><br>Highest Priority</td><td>We genuinely cannot launch without this due to business needs, legal reasons and safety concerns—it would be a terrible idea to launch without this!</td></tr><tr><td><strong>Should Have</strong><br>High Priority</td><td>It would be best to include these, but our product won’t be an absolute failure without them.</td></tr><tr><td><strong>Could Have</strong><br>Medium Priority</td><td>Nice-to-haves if we have the resources and time. But not necessary for success. Think of how each requirement (or lack thereof) will affect customer experience.</td></tr><tr><td><strong>Won't Have</strong><br>Low Priority</td><td>We’ve made an active decision that it’s not coming out with this launch.</td></tr></tbody></table>

#### Factors that influence the prioritization:

1. Value Proposition
2. Stakeholder Prioritizations
3. Feedback from the end users
4. Number of users Impacted
5. Product Usage and Adoption metrics
6. Patient Outcomes
7. Patient Engagement
8. Design, Development and Efforts
9. Priority of the issue/defect.

We also look at the Value/Effort scale for feature requests.

1. The objective is to identify features that will have the highest impact with the lowest effort.
2. Build these first. Next, build high impact, high effort features. This will also differ based on the request from different region.
3. Each feature is rated by a) effort to build the feature and b) potential impact on business value - Highest, High, Medium Priority items from the previous process.
4. Deprioritizing low impact, low effort features, and do NOT build low impact, high effort features!

<figure><img src="https://1478837505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc8r5CWDYQD5YGrlFur8R%2Fuploads%2Fgit-blob-2b34055bf1022376a2874f148fdc46b74b0c7a1c%2Fimage%20(4).png?alt=media" alt="" width="375"><figcaption></figcaption></figure>