{"id":31,"date":"2026-02-19T14:56:32","date_gmt":"2026-02-19T14:56:32","guid":{"rendered":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/?p=31"},"modified":"2026-09-14T12:50:23","modified_gmt":"2026-09-14T11:50:23","slug":"what-is-a-dpia","status":"publish","type":"post","link":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/what-is-a-dpia\/","title":{"rendered":"What is a DPIA?"},"content":{"rendered":"<p style=\"font-weight: 400\">Data&#8230;Person&#8230;I&#8230;am?<\/p>\n<p style=\"font-weight: 400\">Data&#8230;People&#8230;in&#8230;Academia?<\/p>\n<p style=\"font-weight: 400\">Data\u2026Processing\u2026is\u2026Awesome?<\/p>\n<p style=\"font-weight: 400\">Of course, a DPIA is none of the above. It is \u2013 in fact \u2013 a catchy acronym for what\u2019s known as a <strong><em>Data Protection Impact Assessment<\/em><\/strong><em>.<\/em> And just what does <em>that <\/em>mean, exactly?<\/p>\n<p style=\"font-weight: 400\">Well, in essence, exactly what it sounds like; a process by which you, yes YOU: the researcher, calculates and analyses the level of risk attached to (or the <strong><em>impact<\/em> <\/strong>of) the protection of the data you plan to use in your research, through which you can determine how to best minimise said risk appropriately.<\/p>\n<h2 style=\"font-weight: 400\"><strong>A useful way to consider this might be to ask yourself the following:<\/strong><\/h2>\n<div><i>If I didn\u2019t take measures to protect this data, would it be considered high-risk already?\u201d<\/i><\/div>\n<div><\/div>\n<div>Conducting a DPIA is sure-fire way to ensure you\u2019ve considered these risks and have taken the necessary measures to meet your legal obligations as to the protection of the data. Doing so will help you ultimately decide if the level of risk is commensurate with the expected benefit(s) of your research.<\/div>\n<h2 style=\"font-weight: 400\"><strong>On that note\u2026<\/strong><\/h2>\n<p style=\"font-weight: 400\">If you work with healthcare data, it\u2019s extremely likely that you will almost <em>always<\/em> be using \u2018high-risk\u2019 data in your research. Most medical data, for example genetic data, or biometric data, particularly when used for identification purposes, are classified as \u2018special category\u2019 data under<a href=\"https:\/\/gdpr-info.eu\/art-9-gdpr\/\">Article 9 of UK GDPR<\/a><sup>1<\/sup> (as part of the Data Protection Act of 2018). Special category essentially equates to sensitive, personal data for which the additional legal basis for their collection, processing, and retention is required.<\/p>\n<p style=\"font-weight: 400\"><strong>TL;DR<\/strong> \u2013 rule of thumb: the more protection attached to the data, the higher the risk.<\/p>\n<p style=\"font-weight: 400\">Whilst there is no set template for conducting a DPIA, <a href=\"https:\/\/ico.org.uk\/media2\/migrated\/2553993\/dpia-template.docx\">options are available<\/a><sup>2<\/sup>, but the particular needs will vary from one research project to the next. This may seem quite laissez-faire but make no mistake \u2013 a DPIA is a legal obligation for the processing of data. Failure to do so can land you with a whopping fine (up to \u00a38.7m!). So, this is serious business for serious people!<\/p>\n<p style=\"font-weight: 400\">I\u2019ll assume most of us made our way into the world of healthcare research along a spectrum of commonality as to the importance of people and their wellbeing. Whether working in a clinical capacity, or in data, or in academia, or in an administrative capacity, name a role \u2013 it should be obvious by now, but the rights and freedoms of the individuals whom we work with and for as health care professionals are paramount.<\/p>\n<h2 style=\"font-weight: 400\"><strong>We\u2019ve talked a lot about risk, but what exactly do we mean?<\/strong><\/h2>\n<p style=\"font-weight: 400\">Yes, rights and freedoms, within which we can include protection against discrimination of any kind, financial and identity fraud, loss of the right to privacy, professional\/reputational damage, and social or economic disadvantage, but there are less-concrete risks to consider, too; such as loss of public trust within society writ large (not just at the individual level) of the institution in which you conduct your research should something go wrong, e.g., an academic institution, or an NHS health board, etc. The domino-effect can ultimately lead to a lack of public trust in these institutions and make similar research more difficult to conduct for others \u2013 which we can all agree, is bad news all around for everyone from the researchers to the public themselves. *<\/p>\n<p style=\"font-weight: 400\"><a href=\"https:\/\/gdpr-info.eu\/recitals\/no-75\/\">Recital 75<\/a><sup>3<\/sup> is your friend, here.<\/p>\n<p style=\"font-weight: 400\"><em>* A slightly morose, but nonetheless important note is that when we are talking about rights and freedoms, we are referring to those of \u2018natural persons\u2019 \u2013 that is to say, <strong>people who are currently living.<\/strong> The same rights and freedoms <u>do not apply<\/u> to the deceased. <\/em><\/p>\n<h3 style=\"font-weight: 400\"><strong>Evidence<\/strong><\/h3>\n<p style=\"font-weight: 400\"><strong><em>\u00a0<\/em><\/strong><\/p>\n<p style=\"font-weight: 400\">Consider a DPIA an <strong>evidencing of this understanding<\/strong>; that all associated data of said persons be seen as an extension <em>of<\/em> the said persons, and the <strong>impact<\/strong> any misuse (however unintentional) of their data might have. You know, <em>primum non nocere, <\/em>or \u201cFirst, do no harm\u201d \u2013 or perhaps more realistically, weigh up the calculated risk (cost of potential harm) against potential patient benefit \u2013 and <u>show your workings<\/u>. *<\/p>\n<p style=\"font-weight: 400\">*Trivia! \u2013 did you know, although <em>primum non nocere<\/em> is attributed to Hippocrates, it comes from the treatise \u2018Of the Epidemics\u2019 (Book I), not the Hippocratic Oath, itself. Honest, Google it!<\/p>\n<h3 style=\"font-weight: 400\"><strong>Accountability<\/strong><\/h3>\n<p style=\"font-weight: 400\">Completing a DPIA allows you to \u2018forecast\u2019 any potential difficulties with the processing of the data you need for your research <strong>ahead of time. <\/strong>It shows that you are serious about protecting the rights of your research participants, it shows your funders that you are legitimate and accountable, and helps others \u2013 whether your research participants, or the public, or potential collaborators, understand why \u2013 <em>and importantly how<\/em> \u2013 you intend to use this information.<\/p>\n<ul>\n<li>It\u2019s good for your reputation.<\/li>\n<li>It\u2019s good for building and maintaining rapport and trust with your research participants.<\/li>\n<li>It\u2019s good for your continued professional development and understanding of patient needs and concerns.<\/li>\n<li>Heck, it\u2019s good for your moral compass and a strong reminder that we can never separate the numbers from the people they represent.<\/li>\n<\/ul>\n<p style=\"font-weight: 400\">Moreover, the forward thinking a DPIA encourages means you could negate any potential upset during your research before it arises, perhaps even reduce the costs of your research, ensuring you collect and process only the data absolutely necessary, saving you both time and money in the long run.<\/p>\n<h3 style=\"font-weight: 400\"><strong>Evaluate, then re-evaluate!<\/strong><\/h3>\n<p style=\"font-weight: 400\">DPIAs need not be static and rather viewed as frameworks that can be referred to at any point and amended where necessary to ensure you remain accountable to the interests of your participants throughout. Don\u2019t be afraid to revisit your DPIA if for some reason the research necessitates a different path; this is an opportunity to reevaluate the risks of the data required \u2013 seek engagement from your participants and collaborators. Have those crucial discussions and stay transparent.<\/p>\n<p style=\"font-weight: 400\">You may find that a new software is introduced which might speed up your processing requirements; great! But what are the risks of using this software; are you required to share the data for off-site processing (e.g., involving a third party) \u2013 do you need another data processing agreement? Is this a well-established software developer with a robust professional reputation? What security measures do they have in place for the protection of the data they process on your behalf? You get the idea\u2026<\/p>\n<p style=\"font-weight: 400\"><strong><em>References<\/em><\/strong><\/p>\n<ol>\n<li><a href=\"https:\/\/gdpr-info.eu\/art-9-gdpr\/\"> 9 GDPR \u2013 Processing of special categories of personal data &#8211; General Data Protection Regulation (GDPR)<\/a><\/li>\n<li><a href=\"https:\/\/ico.org.uk\/media2\/migrated\/2553993\/dpia-template.docx\">ICO DPIA Template<\/a><\/li>\n<li><a href=\"https:\/\/gdpr-info.eu\/recitals\/no-75\/\">Recital 75 &#8211; Risks to the Rights and Freedoms of Natural Persons &#8211; General Data Protection Regulation (GDPR)<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"Data...Person...I...am? Data...People...in...Academia? Data\u2026Processing\u2026is\u2026Awesome? Of course, a DPIA is none of the above. It is \u2013 in fact \u2013 a catchy [&hellip;]","protected":false},"author":7176,"featured_media":32,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-31","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-data-governance"],"meta_box":[],"_links":{"self":[{"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/posts\/31","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/users\/7176"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/comments?post=31"}],"version-history":[{"count":4,"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/posts\/31\/revisions"}],"predecessor-version":[{"id":36,"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/posts\/31\/revisions\/36"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/media\/32"}],"wp:attachment":[{"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/media?parent=31"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/categories?post=31"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.cardiff.ac.uk\/bioresource-data-accelerator\/wp-json\/wp\/v2\/tags?post=31"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}