Case Study: EPIONE

April 14, 2020

By Emilie Hankar, Harold Van Den Bosch, Christophe Raes & François Piquard

What is EPIONE?

EPIONE is a digital health assistant for patients diagnosed with epilepsy and their specialized doctor. Its main goal is to track, understand and manage the disease by bringing more autonomy and a better quality of life to the patient. It also helps neurologists or epileptologists to better understand epilepsy on a case-by-case basis.

In order to help solving the problems inherent to the condition and support epilepsy care, EPIONE developed an interactive digital platform for both patients and the medical staff.

The EPIONE system contains and provides continuous, evidenced-based information thanks to patient seizure-recording with sensors. Because of the sensitive nature of patients’ confidential data, the company is actively trying to pass ISO 13485 and OWASP level 2 certifications.

Historical context

This Belgian-based startup was created in 2017. The project has been developed in close collaboration with neurologists/epileptologists and epileptic patients. In 2018, it began to raise interest and several actors, including the BlueHealth Innovation Fund, joined the team leading to the preparation of a 500.000EUR capitalization phase.

The startup now intends to continue to grow and aims at internationalisation, targeting countries such as France, the Netherlands or the UK. Being able to reach its global customers is of utmost importance for the team behind this project.  

Link with Technologies?

The EPIONE application’s goal is to improve the quality of life of patients, smoothen the care pathways and reduce its financial burden. The EPIONE platform, a class I medical software comprising an Application and a Dashboard, was designed for patients and doctors to monitor patients’ chronic neurological disorders.

The EPIONE Application and the Dashboard are JavaScript applications specifically designed for patients and physicians to monitor patients’ epilepsy. One of the client’s need was to leverage AWS in order to reduce the number of operations and free up more time for R&D.

Why Amazon Web Services?

EPIONE was already client of AWS and was more than satisfied with the platform. A fleet of EC2s were powering their NodeJS back-ends. The choice to stay with AWS was obvious but they wanted to make greater use of the platform’s functionalities.

The idea was to see beyond the IaaS offering and benefit from fully managed solutions such as AWS Fargate to lower their SysOps. In order to best leverage one of AWS latest and most innovative services in an efficient and safe manner, the existing infrastructure had to be consolidated.

One of ADNEOM’s Tech Lead carried out the first phase by analysing the client’s AWS environment and looked up for the most common misconfigurations (e.g. misconfigured IAM, reduced traceability with no S3 logging, etc.). The goal was to guarantee the construction of a solid architecture by securing and fixing the existing one.

In the next phase, we designed a more appropriate architecture that would better fit the client’s needs and reduce his TCO, SysOps and DevOps costs.  

Here are some AWS services we implemented and their uses:

AWS Fargate (Orchestration) is a serverless compute engine for containers that works conjointly with Amazon Elastic Container Service (ECS). This managed solution reduced the client’s SysOps needs and improved security through application isolation by design (e.g. no SSH access). For both data and applicative layers, AWS Fargate runs each task in its own kernel providing them an isolated compute environment.

We used CloudFront and its integration to securely deliver EPIONE’s data with low latency and high transfer speeds. In addition, it protected the architecture against most DDoS attacks thanks to integrated services such as AWS Shield. Further services where leveraged and the resulting architecture offers more flexibility and responsiveness. ADNEOM’s efforts prepared EPIONE for better growth, scalability and innovation.

Emilie Hankar, Harold Van Den Bosch, Christophe Raes & François Piquard

Categorised in:

This post was written by mcochet