GDPR has focussed everyone’s attention on data protection. But often, people get confused between data security and data protection. Read on to learn the difference.

The eHealth market is one of the fastest growing in the world. Users want to access the benefits of personalised healthcare, but in doing so, they are entrusting you with their most valuable and personal data. Mess up and you risk losing that trust and killing your market.

Here at Chino.io, we attend the most exciting eHealth conferences around the world. Medica, Pioneers, DMEA to name just a few. One such is HIMSS, which starts on 11 June this year.

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.

May 25, 2018 revolutionised data protection. That was the day the GDPR came into effect. One year on, what have we learned about GDPR, and what do you still need to focus on?

Chino.io participated in the 17th Bionnale, one of the biggest Life Sciences events in the Berlin area. The event focuses on biotechnology, pharmaceuticals and medical technology, attracting 900+ attendees from over 20 countries.

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.