What’s more important than health? Surprisingly, digital health has become a hot industry topic only in the last few years.
And it's developing very quickly.
Once designed for entertainment and employee benefits, these devices are now a huge part of our professional and personal lives.
Mental and physical health became the center of attention not only because of the patients’ condition. It was also due to the significant savings in the health service. In the United States alone, this annual savings potential is calculated to be as much as $7 billion.
As a result, health has become one of the most important trends in the development of new applications that are linked to external devices or stand-alone services.
TL;DR: Key takeaways from this article:
Creating a successful application is a challenge.
But creating a successful digital health application is a superb challenge.
4 areas you need to pay most attention to while developing your project:
Remember that you are working with very sensitive data concerning users’ health. Make sure that this data is safe and ends up in the right hands. If in doubt, ask your company's CTO or use an external auditor.
When you introduce products or services that deal with digital health, you are subject to the regulations that apply to your market.
For the USA it will be the U.S. Food and Drug Administration (FDA) and for the EU — the EU Regulations for medical devices (MDR).
In the case of digital health applications, test the functionality of your app on your target group. Consult with medical specialists. Think from the end-user's perspective. Remember, easy is easy, simple is not easy.
4. Testing = Quality.
We expect digital health applications to work flawlessly. Do not save on testing the performance of the application by an experienced Quality Assurance Specialist, who will detect technical errors.
What exactly is a digital health application? Why is it emerging?
The World Health Organisation defines digital health as providing health solutions through mobile devices.
Mobile Health (mHealth) is an area of electronic health (eHealth) and it is the provision of health services and information via mobile technologies such as mobile phones and Personal Digital Assistants (PDAs).
Interestingly, the health service so far has worked in if you need help, pay for it model. Thankfully, it is changing. To put it directly: bigger revenue can be made only when your patients are kept healthy. They can spend more money if any potential diseases are prevented rather than cured.
Why building a digital health app is different?
Is the development process for digital health applications different from developing other apps?
I can only answer this question from my point of view - a representative of a software company, that for the last 4 years has been working every day on digital health and FemTech products, such as Elvie Pump, Elvie Trainer, and MysteryVibe.
And let me tell you, the satisfaction from working on a project that actually helps people to live a healthier and more comfortable life... feels different.
When I talked to Bart Hugo Trzciński, Untitled Kingdom's CTO, he said that quality and security are the basis of every project. In digital health, it’s necessary to estimate the risk assessment. To make security a priority.
When developing a digital health application, we are dealing with a lot of personal data. Sensitive data requires very robust security measures, also in terms of analytics, which must be completely anonymous, without the possibility of linking the data to a specific user.
We must also pay attention to integration with other applications or products — both on the code side and on the user side, we must be 100% sure that nothing will be shared and used. In the case of IoT devices, the protection must ensure that no one else can connect without the user’s consent.
Check the security features with a CTO or your technical expert. If you have further doubts about the data protection system, consider using an external security audit, including threat modeling and risk assessment. When our CTO prepares such an audit, the questions we go through include, among 60 other things:
Are you ready to handle a cyber attack?
Do you have a cybersecurity policy in place? (Privacy, Internet Access, Communication, Remote, Encryption, etc.)
Do you use local encryption solutions for every computer/workstation used in your company?
Do you have a policy on password guidelines and security practices for your team members?
Do you use 2FA in your team at least for the most crucial services?
Is your application/service protected from DDoS attacks?
Do you follow e.g. OWASP Secure Coding Practices?
When an app enters a specific market, it must be adjusted to the regulations of the country in question. Most of the documentation or security issues are the responsibility of the producer of the device, but on the software side, it’s also a key problem. Otherwise, the product may not be authorized to enter the market.
According to device classification, we conform to the required development process documentation. Several times we’ve had to meet the expectations of the U.S. Food and Drug Administration (FDA) or the EU Regulations for medical devices (MDR). That’s where we know what they pay attention to. In fact, compared to other applications, in the case of digital health mainly the amount of documentation increases significantly.
Before releasing the product, it’s also worth asking security companies to conduct penetration testing. The regulations don’t say directly what needs to be done, but rather you need to prove that something has been done, so they can determine whether a given security measure is sufficient.
User Experience and User Interface are essential in every project but especially important in the case of creating applications for people with limitations, illnesses, or the elderly. It will be crucial to include people from the target group at the testing stage and take their feedback seriously.
In the case of creating digital health applications, it’s certainly much more worth focusing on the value of a given functionality, transparency than spectacular design. This doesn’t mean that the design should be weak. It’s simply sometimes not the key.
From our experience in the development of digital health applications, the most important thing is the ease of use, a sense of safety, or adaptation of the product to the needs of people with disabilities. We cannot use our intuition here, instead, we should try to think like our product’s user. We have to feel the problems of the person who is to use the application at the end.
We also believe that users’ satisfaction lies in their experience of the entire service. You should keep in mind both offline activities and online actions, to provide experience as a whole. As they say, easy is easy, simple is not easy.
Testing = Quality
Even if the entire application development process is very well planned, in line with the regulation data and user needs, the testing phase is very important. Especially, if the application concerns health and affects the comfort of the user, we don’t want his peace or comfort to be disturbed.
When working with digital health or FemTech applications, we conduct even more user interviews, tests, and consultations with industry specialists (e.g. neurology or gynecology) than with business products. It is extremely important that testers are from the right target group, in the case of digital health they have specific illnesses or problems.
For very accurate detection of any technical errors, we work with an experienced Quality Assurance Specialist, because as every user we expect each device to simply work well.
However, especially for delicate issues such as breastfeeding with Elvie Pump, kegel muscle training with Elvie Trainer, or enjoying MysteryVibe, the interaction between the device and the application simply has to be flawless.
Why we focus on digital health apps?
The greatest fun for us is creating world-changing products in the area of digital health or FemTech because they realistically change the comfort of life or improve the state of health. These projects are the biggest challenges for us, we learn the most with them, but also get the most satisfaction later on.
We are certainly a different team than when we started our first digital health project. We made a few mistakes, from which we learned the lesson and improved the processes so that they were adapted to the development of the product and eHealth applications.
So if your product or solution solves an important medical problem, we’re all eyes and ears to create with you another life-changing app. Just contact us.