Case study
Outcomes4me.
An AI medical platform dedicated to helping cancer patients navigate all aspects of their treatment by providing them with personalized tools and resources.
Get a quote
Key results.
10K+
Patients
1K+
Doctors
100K+
Successful Diagnostics
+1
Happy Client
Description
Outcomes4me is an AI based medical mobile app and platform built to help cancer patients navigate their treatment and care.
The app helps patients achieve better outcomes by analyzing their health information and providing them with personalized options for approved treatments and clinical trials. Moreover, users are provided with tools to track their treatments, symptoms and outcomes.
MCRO has developed this application in partnership with MVP Factory; our main focus was the react-native mobile app and automated builds configuration.
The app helps patients achieve better outcomes by analyzing their health information and providing them with personalized options for approved treatments and clinical trials. Moreover, users are provided with tools to track their treatments, symptoms and outcomes.
MCRO has developed this application in partnership with MVP Factory; our main focus was the react-native mobile app and automated builds configuration.
Challenge
Users have to go through a medical questionnaire to complete the registration, but also a second time during the onboarding process, after they sign in for the first time.
Our biggest challenge was to develop a dynamic questionnaire where question_2 is dependent on question_1’s answer.
The problem with this was that every time an user updated an answer, we had to reset the questionnaire (and make the request for the list of results) from that point on; if the user decided to go back, we had to reset the questionnaire back with the previous answers (and again, making the request for the list of results).
Our biggest challenge was to develop a dynamic questionnaire where question_2 is dependent on question_1’s answer.
The problem with this was that every time an user updated an answer, we had to reset the questionnaire (and make the request for the list of results) from that point on; if the user decided to go back, we had to reset the questionnaire back with the previous answers (and again, making the request for the list of results).
Solution
The solution was to create the correct redux structure so that the saved answers were kept separately, the latest answers were used for the API requests and all the properties were set properly depending on the user's action: submit, cancel or go back to previous question.
As in all of our projects, we worked in an agile and flexible way. The daily standups, weekly status reports and demo meetings helped our team stay in sync and up-to-date in all areas of the project.
The continuous collaboration we maintained with various stakeholders from our client’s part helped us ensure that all parties were on the same page and working towards the same common goal.
As in all of our projects, we worked in an agile and flexible way. The daily standups, weekly status reports and demo meetings helped our team stay in sync and up-to-date in all areas of the project.
The continuous collaboration we maintained with various stakeholders from our client’s part helped us ensure that all parties were on the same page and working towards the same common goal.
Services provided
Mobile Development
QA & Automation
Technology stack
React Native
ES@Next (6+)
Redux
React Navigation
Canvas
SVG
iOS
Android
Cross Platform
Expo.IO
NodeJS
GraphQL
Socket.IO
