Share on LinkedInShare on LinkedIn

ARTICLE · 04 SEPTEMBER 2017

Privacy In mHealth Apps (Part II)

Mason Hayes & Curran LLP
Mason Hayes & Curran LLP
Contributor
Mason Hayes & Curran LLP

Mason Hayes & Curran LLP

Managing Partner: Will Carmody Chair: Philip Nolan Number of partners: 124 Languages: French,...

View firm profile
Explore more from Mason Hayes & Curran LLP

In our recent article, Privacy in Mobile mHealth Apps (Part I), we discussed the core aim of the ‘Code of Conduct on privacy for mHealth apps' (Code): to regulate and secure the personal data...

European UnionPrivacy

In our recent article, Privacy in Mobile mHealth Apps (Part I), we discussed the core aim of the 'Code of Conduct on privacy for mHealth apps' (Code): to regulate and secure the personal data gathered by mHealth apps. However, compliance with the Code doesn't necessarily equate to compliance with data protection law. Any code for mHealth will need to be consistent with the meaning and spirit of the GDPR, which comes into effect in 2018. Now, we assess the interplay between the proposed Code and the GDPR.

The Code and GDPR

The Article 29 Working Party (WP29) – the collective group of EU data protection authorities – provided recommendations to amend the text of the Code in April 2017. In a letter issued to the project editor of the draft Code, WP29 underlined that the Code should not only be compliant with current law, the Data Protection Directive (Directive), but also with GDPR. WP29 also highlighted that consent to personal data processing for

We operate a free-to-view policy, asking only that you register in order to read all of our content. Please login or register to view the rest of this article.

See more popular content from