Data Protection

Backend as a Service is a relatively new approach to app design. It places the emphasis on designing your API first, forcing you to consider what you really need to implement. For eHealth apps, it allows you to quickly and easily ensure compliance with GDPR and HIPAA.

The MDR will be enforced from May 2020. To help companies prepare for it, the EU has published a step-by-step implementation plan. Here we explain how the 12 step plan applies to eHealth companies.

Pseudonymization is a sensible security precaution but it will not make your application GDPR compliant by itself. In this blog we look in more detail at pseudonymization and the implications of using it.

Pseudonymization is a key data protection technique. However, it is not sufficient to make you GDPR compliant. Our infographic provides definitions and will clarify the legal and technical implications of pseudonymization.

No data security is ever foolproof. There is always a weak link in the security chain, and all too often that link is a human. In this blog, we look at some of these human factors and suggest ways you can help to reduce these risks.

The new Medical Device Regulation promotes many eHealth apps to Class II or even Class III medical devices. Use our useful infographic to find out what MDR class your app is.

The Data Protection Officer (DPO), is a corporate figure introduced by the General Data Protection Regulation GDPR, the EU's new law on Data Protection and Privacy matters.

Anonymisation and pseudonymisation are two key concepts for the General Data Protection Regulation (GDPR). The GDPR provides exceptions to many of the most burdensome provisions of the regulation when steps are taken to de-identify personal data using anoymisation or pseudonymisation.

The motivations behind MDR and its impact on the EU eHealth market We look in more detail at the background to the new MDR. Read on to find out if MDR will be an innovation killer or lifesaver!