🛣️Roadmap
Last updated
Last updated
@2024 Medtronic LABS
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 below.
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
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:
Add a descriptive Title summarizing the feature
Describe the feature with as much detail as possible in the Description field. Include the following details:
Problem Statement
Priority (Highest, High, Medium, Low)
Impacted Users
Impacted Workflows
Tag the issue as a "enhancement" using the labels
If possible, attach any images to further explain the feature request (screenshots are very helpful!)
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.
Value Proposition
Stakeholder Prioritizations
Feedback from the end users
Number of users Impacted
Product Usage and Adoption metrics
Patient Outcomes
Patient Engagement
Design, Development and Efforts
Priority of the issue/defect.
We also look at the Value/Effort scale for feature requests.
The objective is to identify features that will have the highest impact with the lowest effort.
Build these first. Next, build high impact, high effort features. This will also differ based on the request from different region.
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.
Deprioritizing low impact, low effort features, and do NOT build low impact, high effort features!
Ability to import the country geographic data
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.
ICCM - Integrated Community Case Management workflow
Integrated community case management workflow added to available assessments for CHW
Password change option
Expanded password changes and resets from email notifications to include mobile phone text messages.
Household Creation
Allows community health workers (CHWs) to collect household details and social determinants of health (SDOH) data from families.
RMNCH
Reproductive, maternal, neonatal, and child health workflow to be added to the workflows.
Household visit Follow-up
Generated list of patients for household visit follow-ups provided to community health workers in the Follow-up option
Referral Follow-up
Generated list of patients for facility visits, previously referred, provided to community health workers via the SPICE mobile app for direct contact in the Follow-up option
Medical Review - Follow-up
Generated list of patients needing medical review for facility appointments provided to community health workers in the Follow-up option
Above 5y (General Register), Mother & Neonate, Under 5 Age < 2M,Under 5y (2M to 5y) Registers:
Integrated facility registers for diverse disease conditions into the Medical Review workflow. Physicians can use them for specific patient conditions to enhance treatment decisions.
CHW Performance Monitoring
Peer supervisors can monitor community health workers' performance by viewing daily metrics, including the number of assessments, follow-up visits, and calls completed.
AI Model to predict patient retention
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.
New Clinical Workflows for CHW:
We will expand the platform to the following clinical areas:
NCD
TB and HIV
Family Planning
Community-Based Surveillance
New Medical Review Workflows
We will expand the platform to the following clinical areas:
Immunizations
TB and HIV
NCD
Family Planning
Distance and Directions to Patient Location
Future integration with Google Maps to display distance and directions to patients' households.
Displaying CHW Activity through Geo-tagging
Use latitude and longitude data from activities (e.g., assessments, follow-ups) to visualize movement patterns of community health workers.
LLMs for Community Health Workers (CHWs)
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
Workflow Builder - Add new workflow with Clinical decision support (CDSS)
Clinical Authors and Implementor will be able to add new workflows in SPICE with country specific guidelines.
Patient Application within SPICE
Access to the patient longitudinal journey
Upload assessments
Medication adherence nudges
Appointment reminders
Insights Generation
Analytics module to generate user-specific insights
Must Have Highest Priority
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!
Should Have High Priority
It would be best to include these, but our product won’t be an absolute failure without them.
Could Have Medium Priority
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.
Won't Have Low Priority
We’ve made an active decision that it’s not coming out with this launch.
