Data Protection

Introduction

Processing Personal Data presents inherent risks to the rights of research participants under the General Data Protection Regulation (GDPR) a Data Protection Impact Assessment (DPIA) must be conducted before carrying out any processing that is likely to result in a high risk to individual’s rights and freedom (whether it is physical, material, or non-material). The ULHG and CHO3 dataprotection function is provided by Allone Corporate Solutions Ltd and our dataprotection consultant is Annette Ridley.

Annette Ridley

HSE-DPIA Screening Tool

Instructions on using the HSE-DPIA Screening Tool

1. Complete the Tool not later than at the start of your Project (at the very latest) and before you prepare your Ethics Application

2. Complete the Project General Information Green Section first (Project title & contact, & 10 close-ended questions) 

3. Complete the Project Technical Information Part Blue Section of the Tool  (10 close-ended questions)

4. The result of your scoring will automatically appear    

5. Ensure you safely keep a copy of findings to fulfil your obligations under the GDPR. 

6. The recorded findings can additionally be used for submission to HSE Reference RECs and/or other RECs when required

There is useful guidance and information relating to Data Protection in Health and Social Care Research available at, https://hseresearch.ie/data-protection-and-research/.

As well as the ‘Risk Scoring Tool to Determine if a DPIA is Required or Not’ there have been two recent developments in the Data Protection sphere:

·         Health Research Data Protection Impact Assessment Form

·         Companion Guidance to the HSE and S38, 39s, Universities and Pharmaceutical Organisations Data Protection Impact Assessment Form

This new Health Research-specific DPIA should now be used by all researchers rather than the generic HSE template.

Anonymisation and pseudonymisation

‘Pseudonymisation’ of data (defined in Article 4(5) GDPR) means replacing any information which could be used to identify an individual with a pseudonym, or, in other words, a value which does not allow the individual to be directly identified.

Example of Pseudonymisation of Data:

 Student NameStudent NumberCourse of Study
Original DataJoe Smith12345678History
Pseudonymised DataCandidate 1XXXXXXXXHistory

Fully ‘anonymised’ data does not meet the criteria necessary to qualify as personal data and is therefore not subject to the same restrictions placed on the processing of personal data under the General Data Protection Regulation (GDPR).Data can be considered ‘anonymised’ when individuals are no longer identifiable. It is important to note that a person does not have to be named in order to be identifiable. If there is other information enabling an individual to be connected to data about them, which could not be about someone else in the group, they may still ‘be identified’. In this context, it is important to consider what ‘identifiers’ (pieces of information which are closely connected with a particular individual, which could be used to single them out) are contained in the information held.

Where data has been anonymised, the original information should be securely deleted to prevent any reversing of the ‘anonymisation’ process. In most cases, if this deletion does not take place then the data is classified as ‘pseudonymised’ rather than ‘anonymised’, and is still considered personal data.

Data protection law does not prescribe any particular technique for ‘anonymisation’, so it is up to individual data controllers to ensure that whatever ‘anonymisation’ process they choose is sufficiently robust.

Please see our guidance note on ‘anonymisation’ and ‘pseudonymisation’ for further information including identification risks and examples of anonymisation techniques.

USEFUL LINK:

Dataprotection comissioner