To allow medical facilities to use either online or hosted solution, in case a hospital faces challenges with the Internet or power supply.

Both online and hosted solutions have their pros and cons. With an online solution, the hospital has access to the newest code and full support. With the on-premise solution, a hospital can be independent from the Internet. Our first step was to use Docker to handle app image, so it can be easily installed on an independent server. Then, we had to create a custom architecture and an admin panel, where on-premise instances could be monitored, configured and updated.

Ensure the highest possible uptime of the application with constant access to the patient's data 24/7, 365 days.

A hospital cannot afford downtimes. Lack of access to patients’ data results in longer patient queues, and could badly affect doctor’s decisions and even cause death. To make sure that the application is available for up to 100% of the time, we used Kubernetes. To make sure that the platform is capable of providing patients data even if something goes wrong, we are working at multiple levels of redundancy. For example hosting a second, parallel instance of our app that is hosted on independent servers. And this is all to make us prepared for a situation like a datacenter downtime.

An intuitive user interface, to minimize the organizational overhead usually imposed by onsite staff trainings.

The user interface is continuously improved as we are constantly learning how doctors and hospital staff is using the product. Even though the main design of mHealth app was done well, we iterate on it and provide quarterly design improvements, to keep the product more intuitive with each iteration.